Configuration Guide: Harris Canada, Inc. Controls Division Distributed Automation Products

Harris Canada, Inc.
Controls Division
Distributed Automation Products
8979 DPA
CONFIGURATION GUIDE
Document Number: A002-0CG.WES
Version : 6.02
Date : 96.06.13
Submitted By: Authorized By:

Signature:
Name:
Date:
Classification: Restricted
Release: Full
NOTICE OF COPYRIGHT & PROPRIETARY RIGHTS
©1996, Harris Canada, Inc. All rights reserved.

The contents of this manual are the property of Harris Canada, Inc. No part of this work
may be reproduced or transmitted in any form or by any means, except as permitted by
written license agreement with Harris Canada, Inc.
Harris Canada, Inc. has made every reasonable attempt to ensure the completeness and
accuracy of this document, however, the information contained in this manual is subject
to change without notice, and does not represent a commitment on the part of Harris
Canada, Inc.
Any attached hardware schematics and technical descriptions, or software listings that
disclose source code, are for information purposes only. Reproduction in whole or in
part to create working hardware or software for other than Harris Canada, Inc.
products is strictly prohibited, except as permitted by written license agreement with
Harris Canada, Inc.
TRADEMARK NOTICES
WESDAC is a registered trademark of Harris Canada, Inc. All other brand and product
names mentioned in this document are trademarks or registered trademarks of their
respective companies.
8979 DPA Configuration Guide

A002-0CG.WES, Version 6.02 i
Harris Controls - Distributed Automation Products
ii A002-0CG.WES, Version 6.02
MODIFICATION RECORD
VERSION DATE INITIALS COMMENT
90.05.30 AS Created for version 3.00 of the 8979 protocol.
91.01.31 CD The display of ADC values on the custom

WESMAINT and return of analog references
Append A through fc 05.c.
91.02.04 LB Re-named document from D20DA021 (DW4format)

to A002-1CG.d20 (WP format). Moved directory
from O:\DOCUMENT\D20DOCS\D20DA to
M:\APPL\A002.1\DOC. Changed footers, fonts, all
D20DA references, deleted headers.
1.00 91.11.20 NM Removed references to Lousiana Power and Light

(LP&L) and Landis & Gyr (L&G).
1.01 92.05.06 TN WIN version.
1.02 92.05.20 LA Cleaned up the format.
1.03 92.08.05 LA Editorial revisions as per C. Huene.
1.04 93.07.21 AV Formatted to Harris standards and revisions as per

Tim Ngo.
3.00 93.08.25 AV Changed footers for new version numbers.
4.00 94.11.21 AV Versioned up the document to 4.00 to match

software version 4.00.
5.00 95.06.20 DC Major revisions based on A002-1CG.WES Ver.2.00.

Updated config parameters and error messages.
Changed file extension to .wes.
6.00 95.10.02 DY Added com_fail timeout and com_fail control output

parameters in A002_COM. Added local/remote
status point, local mode state, time_sync config
parameters in A002_LRU.
6.01 96.01.09 RS Added note about First SBO Output in A002_LRU
6.02 96.06.13 SK Removed “Local Mode” information message.

A002-0CG.WES, Version 6.02 iii
iv A002-0CG.WES, Version 6.02
TABLE OF CONTENTS
ABOUT THIS GUIDE

PURPOSE OF THIS GUIDE xiii
WHO SHOULD USE THIS GUIDE xiii
ADDITIONAL DOCUMENTATION xiv
HOW THIS GUIDE IS ORGANIZED xiv
CONVENTIONS USED IN THIS GUIDE xvi
OVERVIEW xvii
Chapter 1: CONFIGURATION TABLES

1.1 CONFIGURATION SEQUENCE 1-3
Chapter 2: CONFIGURING THE A002_COM TABLE

2.1 GENERAL INFORMATION 2-1
2.2 DESCRIPTION OF FIELDS 2-1
2.2.1 Port Name 2-2
2.2.2 Baud Rate 2-2
2.2.3 Transmit Timeout 2-3
2.2.4 Com_Fail Timeout 2-3
2.2.5 Com_Fail Control Output 2-3
2.2.6 Receive Squelch 2-3
2.2.7 RTS On Delay 2-3
2.2.8 RTS Off Delay 2-4
2.2.9 Character Timeout 2-4
2.2.10 Number of LRUs 2-4
2.2.11 First LRU 2-4

A002-0CG.WES, Version 6.02 v
Chapter 3: CONFIGURING THE A002_LXR TABLE
3.2.1 LRU Address 3-2
3.2.2 LRU Number 3-2
Chapter 4: CONFIGURING THE A002_LRU TABLE

4.2.1 Number of Indication Points 4-3
4.2.2 First Indication Point 4-3
4.2.3 Number of SOE Points 4-4
4.2.4 First SOE Point 4-4
4.2.5 SOE Buffer Size 4-4
4.2.6 Number of Accumulator Inputs 4-4
4.2.7 First Accumulator Input 4-4
4.2.8 Number of Analog Inputs 4-4
4.2.9 First Analog Input 4-5
4.2.10 Analog Integration Frequency 4-5
4.2.11 Number of ADC References 4-5
4.2.12 First ADC Reference 4-5
4.2.13 Number of SBO Outputs 4-5
4.2.14 First SBO Output 4-6
4.2.15 SBO Timer Increment 4-6
4.2.16 SBO Timeout 4-6
4.2.17 SBO Queue Inhibit 4-6
4.2.18 Pulse Output Pairs 4-7
4.2.19 First Pulse Output Pair 4-7
4.2.20 Analog Outputs 4-7
4.2.21 First Analog Output 4-7
4.2.22 Digital Input Words 4-7
4.2.23 First Digital Input Word 4-7
4.2.24 Digital Output Words 4-8
4.2.25 First Digital Output Word 4-8
4.2.26 Local/Remote Status Point 4-8
4.2.27 Local Mode State 4-8
4.2.28 Support Warm Restart 4-8
4.2.29 Time Synchronization 4-9

vi A002-0CG.WES, Version 6.02
Chapter 5: CONFIGURING THE A002MT00 TABLE
5.2.1 Indication Point Number 5-2
5.2.2 Indication Type 5-2
Chapter 6: CONFIGURING THE A002MSOE TABLE

6.2.1 SOE Point Number 6-2
6.2.2 SOE Type 6-2

7.2.1 Accumulator Point Number 7-2
7.2.2 Accumulator Type 7-2
7.2.3 Freeze Ownership 7-2
7.2.4 Accumulator Source 7-3

8.2.1 Analog Input Point Number 8-2
8.2.2 Range 8-2
8.2.3 Divider 8-2
8.2.4 Offset 8-3
8.2.5 Analog Input Type 8-3

9.2.1 Zero Reference Point Number 9-3
9.2.2 Zero Range 9-3
9.2.3 Zero Divider 9-3
9.2.4 Zero Offset 9-3
9.2.5 Zero Reference Type 9-4
9.2.6 Negative Reference Point Number 9-4
9.2.7 Negative Range 9-4
9.2.8 Negative Divider 9-4
9.2.9 Negative Offset 9-4
9.2.10 Negative Reference Type 9-5
9.2.11 Positive Reference Point Number 9-5

A002-0CG.WES, Version 6.02 vii
9.2.12 Positive Range 9-5
9.2.13 Positive Divider 9-5
9.2.14 Positive Offset 9-5
9.2.15 Positive Reference Type 9-6

10.2.1 SBO Output Point Number 10-2
10.2.2 Control Type 10-2
Chapter 11: CONFIGURING THE A002MTRL TABLE

11.2.1 Raise Point Number 11-2
11.2.2 Lower Point Number 11-2

12.2.1 Analog Output Point Number 12-2
12.2.2 Range 12-2
12.2.3 Divider 12-3
12.2.4 Offset 12-3
12.2.5 Analog Output Type 12-3
Chapter 13: CONFIGURING THE A002MTDI TABLE

13.2.1 Digital Input Point Numbers 13-2
13.2.2 Input Types 13-2
Chapter 14: CONFIGURING THE A002MTSP TABLE

14.2.1 Digital Output Point Numbers 14-2
Chapter 15: CONFIGURING THE A002CHAS TABLE

15.2.1 Config Data 15-2

viii A002-0CG.WES, Version 6.02
Appendix A: WESDAC CONFIGURATION SYSTEM CONTEXT
CONFIGURATION FILE STRUCTURE A-1
Naming Conventions A-1
Definition Section A-2
Data Section A-2
DATA CONVENTIONS A-3
WIN CONFIGURATION A-4
COMPILE TIME CHECKING A-4
SAMPLE CONFIGURATION A-5
Appendix B: MESSAGES LOGGED BY THE 8979 DPA

FATAL ERROR MESSAGES B-2
NON-FATAL ERROR MESSAGES B-27
WARNING MESSAGES B-31
Memory Allocation Warnings B-31
WIN Interface Warnings B-31
Message Exchange Warnings B-32
INFORMATION MESSAGES B-32
GLOSSARY OF TERMS G-1
LIST OF ACRONYMS AND ABBREVIATIONS L-1

A002-0CG.WES, Version 6.02 ix
x A002-0CG.WES, Version 6.02
LIST OF FIGURES AND TABLES
Figure 1 System Overview xviii
Table 1-1 8979 DPA Configuration Tables 1-2

Table 2-1 8979 A002_COM Configuration Table 2-2
Table 3-1 8979 A002_LXR Configuration Table 3-2
Table 4-1 8979 A002_LRU Configuration Table 4-2
Table 5-1 8979 A002MT00 Configuration Table 5-2
Table 6-1 8979 A002MSOE Configuration Table 6-2
Table 11-1 8979 A002MTRL Configuration Table 11-2
Table 13-1 8979 A002MTDI Configuration Table 13-2
Table 14-1 8979 A002MTSP Configuration Table 14-2
Table 15-1 8979 A002CHAS Configuration Table 15-2

A002-0CG.WES, Version 6.02 xi
xii A002-0CG.WES, Version 6.02
ABOUT THIS GUIDE
PURPOSE OF THIS GUIDE
This guide describes, in detail, how to configure the 8979 Data Processing Application
(DPA) for WESDAC products. The configuration information customizes the behavior of
the 8979 DPA for emulation of the 8979 protocol in communications with master
stations.
Each configurable parameter for the 8979 DPA is described along with the range of valid
entries and a typical entry where applicable. The grouping of related parameters is also
described.
WHO SHOULD USE THIS GUIDE
This document is intended for use by individuals responsible for the configuration of the
8979 DPA in Harris RTUs. These people should be familiar with the operation and
maintenance of RTUs in general, but may not be familiar with the Harris WESDAC
family of products.
Before reading this document, you should have a basic understanding of the WESDAC
hardware environment, the configuration system, and the 8979 DPA.

A002-0CG.WES, Version 6.02 xiii
ADDITIONAL DOCUMENTATION
If you require more detail than this document provides, several supporting texts are
available. These include:
8979 DPA Functional Specification (A002-0FS.WES) Version 5.00
WIN User's Configuration Guide for the WESDAC D20 (B008-0CG.D20)
Config Pro Configuration System User's Guide (P012-0UG)
WESDAC Configuration System User's Guide (P005-0UG)
WESMAINT II Maintenance Facility Configuration Guide (B014-0CG)
HOW THIS GUIDE IS ORGANIZED
This guide is organized into the following sections:

OVERVIEW: discusses the general operation of the 8979 DPA and describes the
conventions used in its configuration.
Chapter 1: CONFIGURATION TABLES provides general information on the
configuration tables required by the 8979 DPA.
Chapter 2: CONFIGURING THE A002_COM TABLE provides detailed
information on configuring the communication parameters table required
by the 8979 DPA.
Chapter 3: CONFIGURING THE A002_LXR TABLE provides detailed
information on configuring the LRU cross reference table required by the
8979 DPA.
Chapter 4: CONFIGURING THE A002_LRU TABLE provides detailed
information on configuring the LRU table required by the 8979 DPA.
Chapter 5: CONFIGURING THE A002MT00 TABLE provides detailed
information on configuring the indication map table required by the 8979
DPA.

xiv A002-0CG.WES, Version 6.02
Chapter 6: CONFIGURING THE A002MSOE TABLE provides detailed
information on configuring the SOE map table required by the 8979
DPA.
information on configuring the accumulator map table required by the
8979 DPA.
information on configuring the analog input map table required by the
8979 DPA.
information on configuring the analog reference point map table required
by the 8979 DPA.
information on configuring the select-before-operate digital output map
table required by the 8979 DPA.
Chapter 11: CONFIGURING THE A002MTRL TABLE provides detailed
information on configuring the pulse output (raise/lower) table required
by the 8979 DPA.
information on configuring the analog output map table required by the
8979 DPA.
Chapter 13: CONFIGURING THE A002MTDI TABLE provides detailed
information on configuring the digital input word map table required by
the 8979 DPA.
Chapter 14: CONFIGURING THE A002MTSP TABLE provides detailed
information on configuring the digital output word map table required by
the 8979 DPA.
Chapter 15: CONFIGURING THE A002CHAS TABLE provides detailed
information on configuring the RTU chassis information table required
by the 8979 DPA.
Appendix A: WESDAC CONFIGURATION SYSTEM CONTEXT describes the
8979 DPA configuration within the context of the WESDAC
Configuration System.
Appendix B: MESSAGES LOGGED BY THE 8979 DPA provides information on
the error processing performed by the 8979 DPA.

A002-0CG.WES, Version 6.02 xv
CONVENTIONS USED IN THIS GUIDE
There are a few formatting conventions used in this guide to make it easier to read and
understand. They are listed below.
• New or special terms are highlighted in bold text.
• Chapter references are highlighted in bold text, with the chapter title in CAPITAL
LETTERS (for example, Chapter 2: SPECIAL REQUIREMENTS). Table
names are also bold (e.g. AXXX_CFG)
• References to main section titles are highlighted using italics, as are book and
document titles, and words used with special emphasis.
• Lists of procedural instructions are numbered in the order they should be performed.
Other lists of information are bulleted, like this list is.
• Specific keyboard keys are indicated in BOLD CAPITAL LETTERS like this:
<ENTER>, <ALT>, <BACK SPACE>.
• Words or instructions to be typed into your computer are indicated exactly as they
should be typed, in bold italics. (For example, type in the command diskcopy a: b:
and then press the <ENTER> key.)
• Specific function and field names are in CAPITAL LETTERS, but not bold.
(e.g. TRIP function, GROUP ADDRESS field).

xvi A002-0CG.WES, Version 6.02
OVERVIEW
The 8979 data-processing application (DPA) is a software application which will

communicate with one or more hosts using the 8979 protocol, defined in the 8979 DPA
Functional Specification. It will have the ability to emulate several distinct 8979 remote
terminal units (RTUs). Each such emulation is called a logical remote unit (LRU), and
appears as a single physical 8979 RTU to any host communicating with it.
The core communication system is based on a master/slave communications model,
where the 8979 DPA acts as the slave device.
The 8979 DPA is intended to be installed in a RTU to communicate with a host for the
purpose of transmitting information and executing commands. It is intended to be
integrated in a modular software environment with one or more data collection
applications to provide basic SCADA functionality.
A general system overview is illustrated in Figure 1: System Overview.

A002-0CG.WES, Version 6.02 xvii
HOST
Command WIN Response WIN Response Operator
Wesmaint
8979 DPA 8979 Request
WIN Event WIN Event Wesmaint Display
Host Response DPA Display
(VT100)
Data
WIN
WIN WESDAC Command
8979 DPA Data WESDAC Command Interface Data Update WESDAC
Tables Tables
DCA Node DCA
Command (WIN) Command
Local I/O
DCA Data
DCA Data
Data DCA Event DCA Event Data

Data
Local Request Local I/O Collection Request Remote
Hardware Requested DCA DCA DCA Application Requested Hardware
(DCA)
Data Response Response Data
Figure 1 System Overview

xviii A002-0CG.WES, Version 6.02
Chapter 1:
CONFIGURATION TABLES
Configuration tables are data structures created and compiled using a Harris configuration
system, then downloaded into the NVRAM of an RTU for use by its applications.
For the 8979 DPA, there are two main types of tables:
• remote configuration tables
• data map / characteristic tables
Remote configuration tables are used to define:
• communications port characteristics
• each unique logical remote unit (LRU) along with its data I/O parameters and
emulation specific variables
• correspondence between communications port(s) and logical remote unit process(es).
• chassis configuration
Data map tables are used to relate the system points to the 8979 points and to define
point-specific parameters for each LRU process.
The table names used in configuration files must not contain more than eight characters.
Each table is named according to a standard convention used for all tables found in
WESDAC RTU applications. The standard Harris naming convention dictates that the
prefix, or first four characters, of the table name consist of an application descriptor. This
is an identification code chosen by Harris to indicate the application with which the table
is associated. For example, the application descriptor for the 8979 DPA is A002.

A002-0CG.WES, Version 6.02 1-1
Each table name contains the application identification prefix and is followed by up to
four characters which describe the function of the table. For example, the 8979 table titled
A002_COM holds communication port parameters.
Table 1-1 provides the name and description of each table used in the 8979 DPA
configuration.
TABLE NAME DESCRIPTION
A002_COM This table contains communication port related parameters. One record is
entered for each port the application will use.
A002_LXR This table contains the cross references between A002_COM records and
A002_LRU records. One record is entered for each cross reference
required.
A002_LRU This table contains LRU related parameters. One record is

entered for each LRU in the system.
A002MT00 This table contains indication data point mappings and attributes.
One record is entered for each indication data point.
A002MSOE This table contains sequence of events data point mappings and
attributes. One record is entered for each SOE data point.
A002MT03 This table contains accumulator point mappings and attributes.

One record is entered for each accumulator point.
A002MT04 This table contains analog input point mappings and attributes.
One record is entered for each analog input point.
A002MT11 This table contains analog reference point mappings and

attributes. One record is entered for each group of three ADC
points.
A002MT02 This table contains select before operate output point mappings
and attributes. One record is entered for each SBO point.
A002MTRL This table contains pulse output (raise / lower) point mappings
and attributes. One record is entered for each raise / lower pair.
A002MT05 This table contains analog output point mappings and attributes.
One record is entered for each analog output point.
A002MTDI This table contains digital input word point mappings and
attributes. One record is entered for each digital input word (16
digital input points).
A002MTSP This table contains digital output word point mappings and
attributes. One record is entered for each digital output word (24
digital output points).
A002CHAS This table contains RTU chassis information.
Table 1-1 8979 DPA Configuration Tables

1-2 A002-0CG.WES, Version 6.02
1.1 CONFIGURATION SEQUENCE
The following is a list of the steps required to configure the 8979 DPA:
1. Edit the configuration tables for all other applications that will run on the
WESDAC product. Prepare them according to their own configuration guides.
2. Edit the 8979 DPA configuration tables. Prepare them according the guidelines in
this document and the specific use for which the 8979 DPA is required.
3. Compile the configuration and download it to the WESDAC product using the
WESDAC Configuration System. The list of applications to be compiled must
include the 8979 DPA.
4. Power up the WESDAC product. The 8979 DPA will check the validity of its
configuration parameters and begin its initialization. If it determines that a
configuration parameter is incorrect or encounters an error during its initialization, it
will log a message to the WESMAINT Error Log and then, depending on the severity
of the error, terminate or continue with its run-time function. Self-termination of the
8979 DPA prevents it from running using invalid data.
5. Check for error messages. Log into the WESMAINT maintenance interface, select
the SYSTEM FUNCTIONS item from the Main Menu, and then select the ERROR
LOG item from the System Functions Menu. If any error messages are displayed,
correct the problem as described in Appendix B: MESSAGES LOGGED BY THE
8979 DPA, and repeat steps 3 through 5.
When the 8979 DPA has successfully validated all the configuration parameters,
configuration is complete.

Chapter 2:
CONFIGURING THE A002_COM
TABLE
This chapter describes the configurable parameters in the Communication Port

(A002_COM) table.
2.1 GENERAL INFORMATION
The A002_COM table provides information for each communication port which is to be
used by the 8979 DPA. The table contains one record for each communication port
required and allows the user to customize the communications related settings. An
example of this table may be found in Appendix A: WESDAC CONFIGURATION
SYSTEM CONTEXT. Each field contained in the table is described in the next section
of this chapter.
2.2 DESCRIPTION OF FIELDS
Where applicable, Table 2-1 describes the data type, high and low entry limit, special case
entry, and typical entry for each field of the A002_COM table. Following the table is a
textual description of each field's meaning.

Field Low Limit High Limit Special Typical
Port Name N/A N/A N/A “COM1"
Baud Rate 0 65535 N/A 1200
Transmit 01 4294967295 N/A 2250

Timeout (at 1200 baud)
Com_Fail 1 65535 N/A 60

Timeout
Com_Fail 0 Specified with the range of control -1 N/A

Control Output point defined in the system (disable)
Receive Squelch 1 65535 0 5

(Disabled)
RTS On Time 1 65535 N/A 25
RTS Off Time 01 65535 N/A 25
Character 01 65535 N/A 60

Timeout
Number of 1 255 N/A N/A

LRUs (Indexes A002_LXR)
First LRU 0 255 N/A N/A

(Indexes A002_LXR)
Table 2-1 8979 A002_COM Configuration Table
2.2.1 Port Name

A four character (null terminated) ASCII name which identifies the physical
communications port in the RTU. A valid port (dependent on the Harris hardware
platform) name must be entered. Note that "COM0" is usually reserved for the
WESMAINT port.
2.2.2 Baud Rate

The receive and transmit baud rates for the communication port. The available baud rates
are: 110, 300, 600, 1200, 2400, 4800, 9600.
1
A minimum value will be enforced by the DPA

2.2.3 Transmit Timeout
The maximum number of milliseconds allowed for the RTU to complete a transmission.
This value should include any RTS on and off times configured for this port and should
be configured to accommodate the maximum length message.
Transmit Timeout > RTS On Delay

RTS Off Delay
(Max. Messages Length 10000)
Baud Rate
The transmit timeout is forced, in software, to be at least equal to the configured RTS on
delay, plus 134 character times, plus the RTS off delay.
2.2.4 Com_Fail Timeout

The maximum number of seconds allowed to wait for receiving a host request on the
channel. When the time expires, an assigned digital output could be operated.
2.2.5 Com_Fail Control Output

The system point number of the digital output to be operated for the Com_Fail Timeout.
A negative one (-1) indicates the control is not implemented. If the control is
implemented then the control point number must be less than the total number of controls
defined in the system.
2.2.6 Receive Squelch

The number of milliseconds to delay between detection of data carrier (DCD) and
enabling the receiver. This allows the RTU to account for poor line conditions or slow
settling times. A value of zero disables this functionality, meaning the receiver will
immediately be enabled upon detection of DCD. This parameter is dependent on the type
of communication equipment being used.
2.2.7 RTS On Delay

The number of milliseconds that RTS is to be asserted prior to transmission of a protocol
message. This parameter cannot be configured as zero, and is dependent on the speed and
type of communication equipment being used.

2.2.8 RTS Off Delay
The number of milliseconds that RTS is to be maintained after the final character in a
protocol message is loaded for transmission. This value is in addition to any modem
delays. This value is forced, in software, to be at least equal to a single-character time.
This ensures that RTS is not cancelled prior to transmission of the last character. This
parameter is dependent on the speed and type of communication equipment being used.
2.2.9 Character Timeout

The maximum number of milliseconds to wait for each character to be received by the
RTU. This value is forced, in software, to be at least a single-character time. This ensures
that enough time is allowed for receipt of a character. This parameter is dependent on the
speed and type of communication equipment being used.
2.2.10 Number of LRUs

The number of LRUs that may be addressed on this communications channel. This value
when added to the First LRU must fall within the range of entries in the logical remote
unit cross-reference table (A002_LXR).
2.2.11 First LRU

The offset to the first entry in the logical remote unit cross-reference table (A002_LXR)
for this channel. The sum of this value and the Number of LRUs, must fall within the
range of entries in the logical remote unit cross-reference table and is checked in software
on power-up.
• WARNING: Although many of the timing parameters are checked and forced to
minimum values at power-up, these minimum values are absolute
minimums and may not be sufficient for reliable communications.
Minimum values may cause a good communications circuit to
intermittently or persistently time-out.

Chapter 3:
CONFIGURING THE A002_LXR
TABLE
This chapter describes the configurable parameters in the LRU Cross-Reference

(A002_LXR) table.
The A002_LXR table provides cross-references between entries in the Communication

Port table (A002_COM) and the LRU table (A002_LRU). The table contains one record
for each cross-reference required. An example of this table may be found in Appendix A:
WESDAC CONFIGURATION SYSTEM CONTEXT. Each field contained in the
table is described in the next section of this chapter.
entry, and typical entry for each field of the A002_LXR table. Following the table is a

LRU Address 1 255 N/A N/A
LRU Number 0 255 (Indexes A002_LRU) N/A N/A
Table 3-1 8979 A002_LXR Configuration Table
3.2.1 LRU Address

A 8979 protocol address to which a LRU will respond. The address 0 is reserved to
represent an all station, or global, address.
3.2.2 LRU Number

The offset to the required entry in the LRU Table (A002_LRU). This value must be
specify an existing record in the A002_LRU table.

Chapter 4:
CONFIGURING THE A002_LRU
TABLE
This chapter describes configurable parameters in the LRU (A002_LRU) table.
The A002_LRU table provides information for all LRUs which are to be used within the
8979 DPA. The table contains one record for each LRU required. An example of this
table may be found in Appendix A: WESDAC CONFIGURATION SYSTEM
CONTEXT. Each field contained in the table is described in the next section of this
chapter.
entry, and typical entry for each field of the A002_LRU table. Following the table is a

Table 4-1 8979 A002_LRU Configuration Table
Field Low High Limit Special Typical

Limit

Indication Points (Indexes A002MT00)
First Indication 0 65535 N/A N/A

Point (Indexes A002MT00)
Number of SOE 0 4096 N/A N/A

Points (Indexes A002MSOE)
First SOE Point 0 65535 N/A N/A

(Indexes A002MSOE)
SOE Buffer Size 0 65535 N/A 40

Accumulator (Indexes A002MT03)
Inputs
First Accumulator 0 65535 N/A N/A

Input (Indexes A002MT03)
Number of Analog 0 4096 N/A N/A

Inputs (Indexes A002MT04)
First Analog Input 0 65535 N/A N/A

(Indexes A002MT04)
Analog Integration 1 2147483647 N/A 2500

Frequency
Number of ADC 0 4096 N/A N/A

References (Indexes A002MT11)
First ADC 0 65535 N/A N/A

Reference (Indexes A002MT11)
Number of SBO 0 256 N/A N/A

Outputs (Indexes A002MT02)
First SBO Output 0 65535 N/A N/A

(Indexes A002MT02)
SBO Timer 1 65535 N/A N/A

Increment
SBO Timeout 1 2147483647 N/A 5000
SBO Queue Inhibit NO YES N/A N/A

(0) (1)
Number of Pulse 0 256 N/A N/A

Output Pairs (Indexes A002MTRL)
First Pulse Output 0 65535 N/A N/A

Pair (Indexes A002MTRL)

Field Low High Limit Special Typical
Limit
Number of Analog 0 256 N/A N/A

Outputs (Indexes A002MT05)
First Analog 0 65535 N/A N/A

Output (Indexes A002MT05)
Number of Digital 0 256 N/A N/A

Input Words (Indexes A002MTDI)
First Digital Input 0 65535 N/A N/A

Word (Indexes A002MTDI)
Number of Digital 0 256 N/A N/A

Output Words (Indexes A002MTSP)
First Digital 0 65535 N/A N/A

Output Word (Indexes A002MTSP)
Local/Remote 0 Specified with the range of digital -1 N/A

Status Point input defined in the system (disable)
Local Mode State OFF ON N/A N/A

(0) (1)
Support Warm NO YES N/A N/A

Restart (0) (non-zero)
Time Sync DISABLE ENABLE N/A ENABLE

(0) (non-zero) (non-zero)
4.2.1 Number of Indication Points

The number of indication points within this logical RTU. This value can not exceed 4096
and, when added to the First Indication Point, must fall within the range of entries in the
Indication Point Map Table (A002MT00). If the number of points defined is not an even
multiple of eight, the remainder of the last returned byte in a force report will be padded
with zeros.
4.2.2 First Indication Point

The offset to the first entry in the Indication Point Map Table (A002MT00) for this LRU.
This value, when added to the Indication Points, must fall with in the range of entries in
the Indication Point Map Table. The integrity of the selected point range is confirmed on
power-up.

4.2.3 Number of SOE Points
The number of SOE points within this logical RTU. This value can not exceed 4096 and,
when added to the First SOE Point, must fall within the range of entries in the SOE Map
Table (A002MSOE). If the number of points defined is not an even multiple of eight, the
remainder of the last returned byte in a force report will be padded with zeros.
4.2.4 First SOE Point

The offset to the first entry in the SOE Map Table (A002MSOE) for this LRU. This
value, when added to the SOE Points, must fall within the range of entries in the SOE
Map Table. The integrity of the selected point range is confirmed on power-up.
4.2.5 SOE Buffer Size

The maximum number of events that the SOE log buffer can hold before it overwrites the
oldest event. The upper limit of this parameter may be constrained by the availability of
on-board NVRAM.
4.2.6 Number of Accumulator Inputs

The number of accumulator input points within this logical RTU. This value can not
exceed 256 and, when added to the First Accumulator Input, must fall within the range
of entries in the Accumulator Input Map Table (A002MT03).
4.2.7 First Accumulator Input

The offset to the first entry in the Accumulator Input Map Table (A002MT03) for this
LRU. This value, when added to the Accumulator Inputs, must fall within the range of
entries in the Accumulator Input Map Table. The integrity of the selected point range is
confirmed on power-up.
4.2.8 Number of Analog Inputs

The number of analog input points within this logical RTU. This value can not exceed
4096 and, when added to the First Analog Input, must fall within the range of entries in
the Analog Input Map Table (A002MT04).

4.2.9 First Analog Input
The offset to the first entry in the Analog Input Map Table (A002MT04) for this LRU.
This value, when added to the Analog Inputs, must fall within the range of entries in the
Analog Input Map Table. The integrity of the selected point range is confirmed on
power-up.
4.2.10 Analog Integration Frequency

This parameter defines a period for analog integrations in milliseconds. At the end of
each period, the difference between current analog values and the corresponding last
reported values is calculated and added to a running integrated delta value on a per point
basis. The upper limit for this parameter is approximately equal to 24 days.
• NOTE: The number of analog input points configured and the frequency of the
analog integration can affect system performance. A value no less than
100ms is recommended.
4.2.11 Number of ADC References

The number of ADC reference point groups within this logical RTU. Each group is
comprised of three reference points. This value can not exceed 4096 and, when added to
the First ADC Reference, can not exceed the number of entries in the ADC Reference
Map Table (A002MT11).
4.2.12 First ADC Reference

The offset to the first entry in the ADC Reference Map Table (A002MT11) for this LRU.
This value, when added to the ADC References, can not exceed the number of entries in
the ADC Reference Map Table. The integrity of the selected point group range is
4.2.13 Number of SBO Outputs

The number of SBO control output points within this logical RTU. This value can not
exceed 256 and, when added to the First SBO Output, must fall within the range of
entries in the SBO Output Map Table (A002MT02).

4.2.14 First SBO Output
The offset to the first entry in the SBO Output Map Table (A002MT02) for this LRU.
This value, when added to the SBO Outputs, must fall within the range of entries in the
SBO Output Map Table. The integrity of the selected point range is confirmed on
power-up.
• NOTE: This point will be operable for SBO select and SBO operate requests
even if the LRU is in local mode.
4.2.15 SBO Timer Increment

SBO output requests from the host include a requested contact duration (in counts). The
8979 DPA multiplies the requested duration by the SBO Timer Increment to arrive at an
actual contact duration.
4.2.16 SBO Timeout

This parameter specifies the maximum allowed duration (in milliseconds) between select
and operate requests from the host for this LRU. That is, once the LRU has received an
SBO select request, the corresponding SBO operate request must be received within the
specified time. An SBO operate request received after the specified time results in an
SBO mismatch exception.
4.2.17 SBO Queue Inhibit

When SBO queuing is enabled, SBO output requests are queued up by the system until all
previously requested outputs have been operated. Setting the SBO Queue Inhibit flag
causes an SBO request to cancel all current requests by the LRU in order to operate the
new request immediately. The following values are valid:
No (0): SBO queuing enabled
Yes (1): SBO queuing disabled
• NOTE: The SBO Queue Inhibit functions on a per LRU basis, meaning the
operation of an SBO by one LRU will not cancel the current operation
requested by another LRU. The SBO Queue Inhibit is also not
applicable to SBO controls configured for latching outputs. Latching
output controls will never cancel a currently active control, not with
they be cancelled on a new SBO request.
4.2.18 Pulse Output Pairs

The number of pulse output point (raise / lower) pairs within this logical RTU. This value
can not exceed 256 and, when added to the First Pulse Output Pair, must fall within the
range of entries in the Pulse Output Map Table (A002MTRL).
4.2.19 First Pulse Output Pair

The offset to the first entry in the Pulse Output Map Table (A002MTRL) for this LRU.
This value, when added to the Pulse Output Pairs, must fall within the range of entries
in the Pulse Output Map Table. The integrity of the selected point range is confirmed on
power-up.
4.2.20 Analog Outputs

The number of analog output points within this logical RTU. This value can not exceed
256 and, when added to the First Analog Output, must fall within the range of entries in
the Analog Output Map Table (A002MT05).
4.2.21 First Analog Output

The offset to the first entry in the Analog Output Map Table (A002MT05) for this LRU.
This value, when added to the Analog Outputs, must fall within the range of entries in
the Analog Output Map Table. The integrity of the selected point range is confirmed on
power-up.
4.2.22 Digital Input Words

The number of digital input words within this logical RTU. This value can not exceed
256 and, when added to the First Digital Input Word, must fall within the range of
entries in the Digital Input Word Map Table (A002MTDI).
4.2.23 First Digital Input Word

The offset to the first entry in the Digital Input Word Map Table (A002MTDI) for this
LRU. This value, when added to the Digital Input Words, must fall within the range of
entries in the Digital Input Word Map Table. The integrity of the selected point range is

4.2.24 Digital Output Words
The number of digital output words within this logical RTU. This value can not exceed
256 and, when added to the First Digital Output Word, must fall within the range of
entries in the Digital Output Word Map Table (A002MTSP).
4.2.25 First Digital Output Word

The offset to the first entry in the Digital Output Word Map Table (A002MTSP) for this
LRU. This value, when added to the Digital Output Words, must fall within the range of
entries in the Digital Output Word Map Table. The integrity of the selected point range is
4.2.26 Local/Remote Status Point

The system point number of the digital input which corresponds to the Local/Remote
Input. A negative one (-1) indicates the point is not implemented. If the point is
implemented, the status point number must be less than the total number of binary input
records in the system table.
4.2.27 Local Mode State

The state of Local/Remote Status Point which represents the local mode. Allowable
states are either ON (1) or OFF (0).
If the point is not implemented, this value is ignored and the system will always be in the
remote mode.
4.2.28 Support Warm Restart

When the RTU power is cycled, each LRU will report either a Cold or Warm Restart
exception code, appended to the first response requested by the host.
Cold Restart occurs:
- for every LRU on the first power-up after a configuration download.
- for an LRU that was requested to restart using the Restart RTU function code.
Warm Restart occurs:
- for every LRU on any power-up, excluding the first power-up after a configuration
download, where no LRU was requested to restart.
- for all remaining LRUs configured if an LRU was requested to restart.

Setting this parameter will cause the LRU to return the Warm Restart exception code in
the above cases; otherwise the LRU will always return the Cold Restart exception code.
The following values are valid:
No (0): Warm Restart disabled
Yes (non-zero): Warm Restart enabled
4.2.29 Time Synchronization

This parameter is a flag which is used to enable or disable use of the 8979 DPA time
synchronization functionality. The following values are valid:
Disable (0): Time Synchronization disabled
Enable (non-zero): Time Synchronization enabled

Chapter 5:
CONFIGURING THE A002MT00
TABLE
This chapter describes the configurable parameters in the Indication Mapping

(A002MT00) table.
The A002MT00 table provides information on each indication data point used by the
8979 DPA. The table must contain one record for each point required. An example of this
chapter.
entry, and typical entry for each field of the A002MT00 table. Following the table is a

Indication 0 32767 Spare (-1) N/A

Point Number (Indexes Digital Input table)
Indication Normal (0) Inverted (1) N/A Normal (0)

Type
Table 5-1 8979 A002MT00 Configuration Table
5.2.1 Indication Point Number

The system status input point number used as the source for the LRU point. The upper
entry is limited by the number of status input points in the system database. A test is
performed on power-up to confirm whether the point number is valid. Each system point
can only be mapped once per LRU. A spare point (-1) indicates that the point is unused
(not mapped to a real system point). Zero is returned for spare points.
5.2.2 Indication Type

This parameter is a flag used to assign attributes to the point. The following values are
valid:
Normal (0): Normal point values are returned
Inverted (1): Inverted point values are returned
This parameter has no effect on spare points.
• NOTE: When using status inputs from Harris peripheral modules, ensure that
the SOE attribute in the Hardware Configuration is always enabled.
The 8979 DPA uses SOE events for generation of all data associated
with status inputs.

Chapter 6:
CONFIGURING THE A002MSOE
TABLE
This chapter describes the configurable parameters in the SOE Mapping (A002MSOE)
table.
The A002MSOE table provides information on each SOE data point used by the 8979
DPA. The table must contain one record for each point required. An example of this table
may be found in Appendix A: WESDAC CONFIGURATION SYSTEM CONTEXT.
Each field contained in the table is described in the next section of this chapter.
entry, and typical entry for each field of the A002MSOE table. Following the table is a

SOE Point 0 32767 Spare (-1) N/A

Number Indexes Digital Input table)
SOE Type Normal (0) Inverted (1) N/A Normal (0)
Table 6-1 8979 A002MSOE Configuration Table
6.2.1 SOE Point Number

The system status input point number used as the source for the LRU point. The upper
entry is limited by the number of status input points in the system database. A test is
performed on power-up to confirm whether the point number is valid. Each system point
can only be mapped once per LRU. A spare point indicates that the point is unused (not
mapped to a real system point). Zero is returned for spare points.
6.2.2 SOE Type

valid:
with status inputs.

Chapter 7:
TABLE
This chapter describes the configurable parameters in the Accumulator Mapping

(A002MT03) table.
The A002MT03 table provides information on each accumulator input point used by the
chapter.

Accumulator 0 32767 (Indexes Spare (-1) N/A

Point Number Accumulator table)
Accumulator Transition Counter (0) Pulse Counter (1) N/A Transition Counter (0)
Type
Freeze No Ownership (0) Freeze Ownership (1) N/A Freeze Ownership (1)
Ownership
Accumulator Frozen Buffer (0) Running Buffer (1) N/A Frozen Buffer (0)
Source
7.2.1 Accumulator Point Number

The system accumulator input point number used as the source for the LRU point. The
upper entry is limited by the number of accumulator input points in the system database.
A test is performed on power-up to confirm whether the point number is valid. A spare
point (-1) indicates that the point is unused (not mapped to a real system point). Zero is
returned for spare points.
7.2.2 Accumulator Type

valid:
Transition Counter (0): Counts transitions
Pulse Counter (1): Counts pulses
7.2.3 Freeze Ownership

valid:
No Ownership (0): Point can not be frozen
Freeze Ownership (1): Point can be frozen

7.2.4 Accumulator Source
This parameter is used to decide whether to send the frozen or running accumulator value
to the master after an accumulator request. Valid values are:
Frozen Buffer (0): Returns the frozen buffer
Running Buffer (1): Returns the running buffer

Chapter 8:
TABLE
This chapter describes the configurable parameters in the Analog Input (A002MT04)
table.
The A002MT04 table provides information on each analog input point used by the 8979

Analog Input 0 32767 Spare (-1) N/A

Point Number (Indexes Analog Input table)
Range -32767 32767 N/A 2047
Divider -32767 32767 N/A 32767
Offset -32767 32767 N/A 0
Analog Input Type Bipolar (0) Unipolar (1) N/A Bipolar (0)

Some of the table parameters should be considered in concert as they can be used to scale
the 16 bit system database analog values into 12 bit 8979 protocol values. Parameters
used to scale analog values include the range, divider, and offset.
Y = Ax + B
where:
Y = Desired scaled value (12 bit 8979 value)
x = Raw value (16 bit database value)
A = Range / Divider
B = Offset
8.2.1 Analog Input Point Number

The analog input point number used as the source for the LRU point. The upper entry is
limited by the number of analog input points in the system database. A test is performed
on power-up to confirm whether the point number is valid. A spare point (-1) indicates
that the point is unused (not mapped to a real system point). Zero is returned for spare
points.
8.2.2 Range
This is typically intended to represent the maximum value to be returned through the host
protocol. This parameter has no effect on spare points.
8.2.3 Divider
This is typically intended to represent the maximum value of an analog point in the
system database. This parameter has no effect on spare points.

8.2.4 Offset
A value to be added as an offset for specific analog scaling. This parameter has no effect
on spare points.
8.2.5 Analog Input Type

valid:
Bipolar (0): Analog value is bipolar
Unipolar (1): Analog value is unipolar
In the 8979 protocol, unipolar analog points can assume values from 0 through 4095,
inclusive. Bipolar analog points can assume values from -2048 through 2047, inclusive.

Chapter 9:
TABLE
This chapter describes the configurable parameters in the ADC Reference (A002MT11)
table.
The A002MT11 table provides information on each ADC reference point group used by
the 8979 DPA. Each ADC reference group is comprised of three reference points. The
table must contain one record for each point group required. An example of this table

Zero Reference 0 32767 Spare N/A

Point Number (Indexes Analog Input (-1)
table)
Zero Range -32768 32767 N/A 2047
Zero Divider -32768 32767 N/A 32767
Zero Offset -32768 32767 N/A 0
Zero Reference Bipolar Unipolar N/A Bipolar

Type (0) (1) (0)
Negative 0 32767 Spare N/A

Reference (Indexes Analog Input (-1)
Point Number table)
Negative -32768 32767 N/A 2047

Range
Negative -32768 32767 N/A 32767

Divider
Negative Offset -32768 32767 N/A 0
Negative Bipolar Unipolar N/A Bipolar

Reference Type (0) (1) (0)
Positive 0 32767 Spare N/A

Reference (Indexes Analog Input (-1)
Point Number table)
Positive Range -32768 32767 N/A 2047
Positive -32768 32767 N/A 32767

Divider
Positive Offset -32768 32767 N/A 0
Positive Bipolar Unipolar N/A Bipolar

Reference Type (0) (1) (0)

the 16 bit system database analog reference values into 12 bit 8979 protocol values. For
each of the three reference points, parameters used to scale analog reference values
include the range, divider, and offset.

Y = Ax + B
where:
Y = Desired scaled value (12 bit 8979 value)
x = Raw value (16 bit database value)
A = Range / Divider
B = Offset
9.2.1 Zero Reference Point Number

points.
9.2.2 Zero Range

This parameter applies to the zero reference point and is typically intended to represent
the maximum value to be returned through the host protocol. This parameter has no effect
on spare points.
9.2.3 Zero Divider

This parameter applies to the zero reference point and is typically intended to represent
the maximum value of an analog point in the system database. This parameter has no
effect on spare points.
9.2.4 Zero Offset

This parameter applies to the zero reference point and is a value to be added as an offset
for specific analog scaling. This parameter has no effect on spare points.

9.2.5 Zero Reference Type
This parameter is a flag used to assign attributes to the zero reference point. The
following values are valid:
Bipolar (0): Analog reference value is bipolar
Unipolar (1): Analog reference value is unipolar
9.2.6 Negative Reference Point Number

points.
9.2.7 Negative Range

This parameter applies to the negative reference point and is typically intended to
represent the maximum value to be returned through the host protocol. This parameter
has no effect on spare points.
9.2.8 Negative Divider

This parameter applies to the negative reference point and is typically intended to
represent the maximum value of an analog point in the system database. This parameter
9.2.9 Negative Offset

This parameter applies to the negative reference point and is a value to be added as an
offset for specific analog scaling. This parameter has no effect on spare points.

9.2.10 Negative Reference Type
This parameter is a flag used to assign attributes to the negative reference point. The
9.2.11 Positive Reference Point Number

points.
9.2.12 Positive Range

This parameter applies to the positive reference point and is typically intended to
represent the maximum value to be returned through the host protocol. This parameter
9.2.13 Positive Divider

This parameter applies to the positive reference point and is typically intended to
represent the maximum value of an analog point in the system database. This parameter
9.2.14 Positive Offset

This parameter applies to the positive reference point and is a value to be added as an
offset for specific analog scaling. This parameter has no effect on spare points.

9.2.15 Positive Reference Type
This parameter is a flag used to assign attributes to the positive reference point. The

Chapter 10:
TABLE
This chapter describes the configurable parameters in the SBO Mapping (A002MT02)
table.
The A002MT02 table provides information on each SBO control output point used by the
chapter.
Where applicable, Table 10-1 describes the data type, high and low entry limit, special
case entry, and typical entry for each field of the A002MT02 table. Following the table is
a textual description of each field's meaning.

SBO Output 0 32767 Spare (-1) N/A

Point Number (Indexes Digital Output table)
Control Type Trip/Close Latch ON/OFF Control N/A Trip/Close

Control (0) (2) Control (0)
10.2.1 SBO Output Point Number

The digital output point number used as the source for the LRU point. The upper entry is
limited by the number of digital output points in the system database. A test is performed
that the point is unused (not mapped to a real system point). Spare points can not be
operated.
10.2.2 Control Type

valid:
Trip/Close Control (0)
Pulse ON Control (1)
Latch ON/OFF Control (2)

Chapter 11:
CONFIGURING THE A002MTRL
TABLE
This chapter describes the configurable parameters in the Pulse Output (A002MTRL)
table.
The A002MTRL table provides information on each pulse control output (raise / lower)
point pair used by the 8979 DPA. The table must contain one record for each point pair
required. An example of this table may be found in Appendix A: WESDAC
CONFIGURATION SYSTEM CONTEXT. Each field contained in the table is
described in the next section of this chapter.
case entry, and typical entry for each field of the A002MTRL table. Following the table
is a textual description of each field's meaning.

Raise Point 0 32767 Spare (-1) N/A

Number (Indexes Digital Output table)
Lower Point 0 32767 Spare (-1) N/A

Number (Indexes Digital Output table)
Table 11-1 8979 A002MTRL Configuration Table
11.2.1 Raise Point Number

The digital output point number used as the source for the LRU point when raise
commands are issued by the host. The upper entry is limited by the number of digital
output points in the system database. A test is performed on power-up to confirm whether
the point number is valid. A spare point (-1) indicates that the point is unused (not
mapped to a real system point). Spare points can not be operated.
11.2.2 Lower Point Number

The digital output point number used as the source for the LRU point when lower
commands are issued by the host. The upper entry is limited by the number of digital
output points in the system database. A test is performed on power-up to confirm whether
the point number is valid. A spare point (-1) indicates that the point is unused (not
mapped to a real system point). Spare points can not be operated.

Chapter 12:
TABLE
This chapter describes the configurable parameters in the Analog Output (A002MT05)
table.
The A002MT05 table provides information on each analog output point used by the 8979
case entry, and typical entry for each field of the A002MT05 table. Following the table is

Analog Output 0 32767 Spare (-1) N/A

Point Number (Indexes Analog Output table)
Range -32768 32767 N/A 32767
Divider -32768 32767 N/A 2047
Offset -32768 32767 N/A 0
Analog Output Bipolar (0) Unipolar (1) N/A Bipolar (0)

Type

the 12 bit 8979 protocol values into 16 bit system database analog values. Parameters
used to scale analog values include the range, divider, and offset.
Y = Ax + B
where:
Y = Desired scaled value (16 bit database value)
x = Raw value (12 bit 8979 value)
A = Range / Divider
B = Offset
12.2.1 Analog Output Point Number

The analog output point number used as the source for the LRU point. The upper entry is
limited by the number of analog output points in the system database. A test is performed
that the point is unused (not mapped to a real system point). Spare points can not be
modified.
12.2.2 Range
This is typically intended to represent the maximum value of an analog point in the
system database. This parameter has no effect on spare points.

12.2.3 Divider
This is typically intended to represent the maximum value as received through the host
protocol. This parameter has no effect on spare points.
12.2.4 Offset
A value to be added as an offset for specific analog scaling. This parameter has no effect
on spare points.
12.2.5 Analog Output Type

valid:
Bipolar (0): Analog value is bipolar
Unipolar (1): Analog value is unipolar

Chapter 13:
CONFIGURING THE A002MTDI
TABLE
This chapter describes the configurable parameters in the Digital Input Word Mapping
(A002MTDI) table.
The A002MTDI table provides information on each digital input word used by the 8979
DPA. Each digital input word references 16 system status input points. The table must
contain one record for each word required. An example of this table may be found in
Appendix A: WESDAC CONFIGURATION SYSTEM CONTEXT. Each field
contained in the table is described in the next section of this chapter.
case entry, and typical entry for each field of the A002MTDI table. Following the table is

Digital Input 0 32767 Spare N/A

Point Number 1 (Indexes Digital Output (-1)
table)
Input 1 Type Normal Inverted N/A Normal

(0) (1) (0)

table)

(0) (1) (0)
... ... ... ... ...

table)

(0) (1) (0)
Table 13-1 8979 A002MTDI Configuration Table
13.2.1 Digital Input Point Numbers

Each of the 16 system status input point numbers used as the source for the LRU points.
The upper entry is limited by the number of status input points in the system database. A
test is performed on power-up to confirm whether each point number is valid. Each
system point can only be mapped once per LRU. A spare point (-1) indicates that the
point is unused (not mapped to a real system point). Zero is returned for spare points.
13.2.2 Input Types

This parameter is a flag used to assign attributes to one of the 16 points. The following
values are valid:

with status inputs.

Chapter 14:
CONFIGURING THE A002MTSP
TABLE
This chapter describes the configurable parameters in the Digital Output Word Mapping
(A002MTSP) table.
The A002MTSP table provides information on each digital output word used by the 8979
DPA. Each digital output word references 24 system digital output points. The table must
contain one record for each word required. An example of this table may be found in
Appendix A: WESDAC CONFIGURATION SYSTEM CONTEXT. Each field
contained in the table is described in the next section of this chapter.
case entry, and typical entry for each field of the A002MTSP table. Following the table is

Digital Output 0 32767 Spare (-1) N/A

Point Number 1 (Indexes Digital Output table)

... ... ... ... ...

Table 14-1 8979 A002MTSP Configuration Table
14.2.1 Digital Output Point Numbers

Each of the 24 system digital output point numbers used as the source for the LRU points.
The upper entry is limited by the number of digital output points in the system database.
A test is performed on power-up to confirm whether each point number is valid. A spare
point (-1) indicates that the point unused (not mapped to a real system point). Spare
points can not be controlled.

Chapter 15:
CONFIGURING THE A002CHAS
TABLE
This chapter describes the configurable parameters in the Chassis Configuration

(A002CHAS) table.
The A002CHAS table provides information on the equivalent chassis configuration used
by the 8979 DPA. This table is necessary as its contents are used to advise the host:
• what types of points are configured
• how many points are configured
The table data is not referenced or interpreted by the 8979 DPA so the table structure is
undefined; data is entered in an unstructured fashion. An example of this table may be
found in Appendix A: WESDAC CONFIGURATION SYSTEM CONTEXT. Each
field contained in the table is described in the next section of this chapter.

case entry, and typical entry for each field of the A002CHAS table. Following the table is
Field Type Low Limit High Limit Special Typical
Config Data Unsigned Byte 0 255 N/A N/A
Table 15-1 8979 A002CHAS Configuration Table
15.2.1 Config Data

The contents of this table are transmitted to the host in response to a configuration
request. Please refer to 8979 protocol documentation as supplied by the host vendor for
format details.
For reference purposes, each LRU must have its own unique configuration entered into
this table. The end of each process' configuration is then marked with a terminating FF
hexadecimal.
• NOTE: This termination character is not required for the last configuration
entry in this table.

Appendix A:
WESDAC CONFIGURATION SYSTEM
CONTEXT
This appendix describes the content of the previous chapters within the context of the
WESDAC Configuration System, and provides a sample configuration. No attempt is
made to explain the operation of the configuration system or the internal configuration
operation. See Additional Documentation in the document preface for reference material.
CONFIGURATION FILE STRUCTURE
WESDAC configuration files are ASCII text files which may be modified with any text
editor which stores files as unformatted ASCII text. Configuration files contain user
entered parameters which allow a user to customize the operation of an application.
Related parameters are grouped together in tables.
Naming Conventions
Configuration files and tables are named according to a standard convention that is used
for all WESDAC applications. The prefix or first four characters of the file name and
each table name it contains denote an application descriptor.
This descriptor is a unique identification code chosen to indicate the application with
which the table is associated. The application descriptor for the 8979 DPA is A002.

A002-0CG.WES, Version 6.02 A-1
The 8979 configuration file is named A002_CFG.TXT. This name comes from the
application identification, followed by an abbreviation to indicate this is a configuration
file, and lastly, the extension '.txt' to indicate this is an ASCII text file.
Definition Section
The definition section for each table may be identified by the keyword DEFINE_TABLE.
Each definition contains:
• table name
• table structure
• access and control word
• number of records to allocate for the table (MAXRECS)
Only the number of records may be changed by the user (i.e. the MAXRECS = "N"
entry). MAXRECS must be set to reflect the actual number of records defined in the data
section.
Data Section
The data section for each table may be identified by the keyword DATA_TABLE. The
data section consists of entries that must be entirely configured by the user. Each table
contains its own unique set of data. However, certain general rules apply to all tables:
• Data must comply with the format specified in the definition section.
• All entries must be separated by commas and are interpreted using the rules given in
the WESDAC Configuration System User's Guide (P005-0UG).
The number of records for each table in the DATA_TABLE section must match the
MAXRECS value for that same table defined in the DEFINE_TABLE section.

A-2 A002-0CG.WES, Version 6.02
DATA CONVENTIONS
The 8979 DPA uses the following conventions for its configuration parameters:
• All parameters are expressed as numeric constants. The valid ranges for each
parameter depend on its data type:
- alpha-numeric characters (s*5): A to Z, 0 to 9
- signed bytes (i*1): -128 to +127
- signed integers (i*2): -32768 to +32767
- long signed integers (li*4): -2,147,483,648 to
+2,147,483,647
- unsigned bytes (u*1): 0 to 255
- unsigned integers (u*2): 0 to 65535
- long unsigned integers (lu*4): 0 to 4,294,967,295
• These ranges may be further limited for each field depending on what the valid values
for that field are. Valid values are detailed in the chapters for each configuration table.
• All configurable table offsets are zero based, I.E. the first record is record 0, the
second record is record 1, etc. Note that this is different from Config Pro which uses a
one based system.
• Any parameter for which a value of zero is required must be entered as 00. Leading
zeros should NOT be used elsewhere as these numbers will be interpreted as octal by
the configuration compiler.
• WARNING: It is extremely important to be accurate when modifying any of the

configuration tables. Very little checking is done by the WESDAC
Configuration System to ensure that the tables contain correct or
valid data. An error in configuration can cause problems at
run-time that are very difficult to diagnose.

WIN CONFIGURATION
The num_dpa entry in the CFG_WIN table of the WIN configuration file
(B008_CFG.TXT) must be modified to accommodate the 8979 DPA. The num_dpa field
is used by the RTU base software to ensure that DCAs and DTAs do not report events
until DPAs and DTAs are ready to receive them. As a minimum, the entry for num_dpa
must be the total of all LRUs defined for the 8979 DPA. The entry may be larger if other
DPAs and DTAs in the system also require start-up coordination.
COMPILE TIME CHECKING
During table compilation, the WESDAC Configuration System, checks that the
defined data is valid, given the element definitions. It also verifies that the
number of records defined does not exceed the MAXRECS definition. For further
information about the Configuration System, refer to the WESDAC Configuration
System User's Guide (P005-0UG).

SAMPLE CONFIGURATION
/*
* File: a002_cfg.txt VERSION 3.02
*
* Author: T. Ngo
* Date: 14 Aug 91
*
* ((C)) Copyright Harris Corp ., 1991. All rights reserved.
* Licensed Material - Property of Harris Corp.
*
* Description:
* This file defines the configuration for the 8979 Protocol as * implemented
on the WESDAC D20 M.
*
* Revision History:
* Num Modified By Date Reason
* --- ------------ --------- ------------------------------
* 0.0 T. Ngo 12 Sept 91 WIN version
* 3.0 T. Ngo 1 July 93 Scaling for A/D references.
* 302 F.SETO 18 OCT 94 Added SBO LOCK OUT parameter.
* 500 sk 95/04/24 Changed 'num_lxr', 'lxr_off', 'address',
* 'lru_off', and most mapping table
* parameters to match the expected type.
* Renamed 'sbo timer base' to 'sbo timer
* increment'.
* Added spare point functionality to
* mapping tables.
* Added configuration parameter to A002_LRU
* to support configurable COLD/WARM restart.
* Changed port name to a 6 byte array.
* Change baud rate to UINT. User now
* configures the actual baud rate (e.g. 9600)
* which will apply to Tx and Rx.
* Added latching ON/OFF output support to
* SBO controls.
* 600 D.Yu 95/09/26 Added com_fail timeout and com_fail
* control output parameters in A002_COM.
* Added local/remote status point, local
* mode state, and time_sync parameters in
* A002_LRU.
*/
/*
* 8979 Communications Port Configuration Record Definition
*/
DEFINE_TABLE = 1
NAME = A002_COM
MAXRECS = 2 /* Two unique communications ports */
CONTROL_WORD = 0x92
DEFINE_RECORD:
SIZE = * {11}
DEFINE_DATA:
s*6, /* communications port description */
u*2, /* baud rate */
lu*4, /* transmit timeout (ms) */

u*2, /* com_fail timeout (s) */
i*2, /* com_fail control output point number */
/* (-1 if not used) */
u*2, /* receive squelch (ms) */

u*2, /* RTS on time delay (ms) */
u*2, /* RTS off time delay (ms) */
u*2, /* character to character timeout (ms) */

u*1, /* number of RTU addresses on this port */
u*1 /* offset into LRU cross reference table */
/*
* 8979 Logical Remote Unit cross reference table
*/
DEFINE_TABLE = 2
NAME = A002_LXR
MAXRECS = 2 /* 2 responding addresses - all ports */
CONTROL_WORD = 0x92
DEFINE_RECORD:
SIZE = * {2}
DEFINE_DATA:
u*1, /* RTU address */
u*1 /* Process number and offset into cfg */
/*
* 8979 process configuration table
*/
DEFINE_TABLE = 3
NAME = A002_LRU
MAXRECS = 2 /* 2 unique protocol processes */
CONTROL_WORD = 0x92
DEFINE_RECORD:
SIZE = * {29}
DEFINE_DATA:
u*2, /* number of indication points */
u*2, /* offset into indication map table */
u*2, /* number of SOE points */

u*2, /* offset into SOE map table */
u*2, /* SOE Log buffer size (events) */
u*2, /* number of accumulators */

u*2, /* offset into accumulator map table */
u*2, /* number of analog points */

u*2, /* offset into analog map table */
lu*4, /* analog integration process freq (ms) */
u*2, /* number of ADCs to be reported */

u*2, /* offset into ADC map table */
u*2, /* number of SBO points */

u*2, /* offset into SBO map table */
u*2, /* SBO timer increment (ms) */
lu*4, /* SBO timeout value (ms) */
u*2, /* inhibit SBO queuing? 1=yes, 0=no */

u*2, /* number of pulse output pairs */
u*2, /* offset into pulse output map table */
u*2, /* number of analog outputs */

u*2, /* offset into analog output map table */
u*2, /* number of digital input points */

u*2, /* offset into digital input map table */
u*2, /* number of digital output blocks */

u*2, /* offset into digital output map table */
i*2, /* local/remote status point number */

u*2, /* local mode state */
u*2, /* Support WARM_RESTART (NO=0, YES=nonzero) */
u*2 /* enable or disable time synchronization */

/* (DISABLE=0, ENABLE=nonzero) */
/*
* 8979 Change of State/Indication Map Table Definition
*/
DEFINE_TABLE = 4
NAME = A002MT00
MAXRECS = 72
CONTROL_WORD = 0x90
DEFINE_RECORD:
SIZE = * {2}
DEFINE_DATA:
i*2, /* D20 system point number (-1 for spare) */
i*2 /* D20 system point option */
/* Normal = 0; inverted = 1 */
/*
* 8979 Sequence of Events Map Table Definition
*/
DEFINE_TABLE = 5
NAME = A002MSOE
MAXRECS = 64
CONTROL_WORD = 0x90
DEFINE_RECORD:
SIZE = * {2}
DEFINE_DATA:
i*2 /* D20 system point option */
/* Normal = 0; inverted = 1 */
/*
* 8979 Accumulator Map/Type Table Definition
*/
DEFINE_TABLE = 6
NAME = A002MT03
MAXRECS = 8
CONTROL_WORD = 0x92
DEFINE_RECORD:
SIZE = * {4}

DEFINE_DATA:
i*2, /* D20 input accumulator point (-1 for spare) */
i*1, /* Accumulator type: */
/* transition counting = 0, pulse counting = 1 */
i*1 /* freeze ownership ( 0 = NOT OWNED ) */
i*2 /* Source to read from: */
/* Frozen buffer = 0, running buffer = 1 */
/*
* 8979 Analog Input Map Table Definition
*/
DEFINE_TABLE = 7
NAME = A002MT04
MAXRECS = 40
CONTROL_WORD = 0x92
DEFINE_RECORD:
SIZE = * {5}
DEFINE_DATA:
i*2, /* D20 system input point (-1 for spare) */
i*2, /* analog input scale range */
i*2, /* analog input scale divider */
i*2, /* analog input scale offset */
i*2 /* analog input type (unipolar = 1) */
/*
* 8979 ADC Map Table Definition
*/
DEFINE_TABLE = 8
NAME = A002MT11
MAXRECS = 2
CONTROL_WORD = 0x92
DEFINE_RECORD:
SIZE = * {15}
DEFINE_DATA:
i*2, i*2, i*2, i*2, i*2, /* point,range,divider,offset,type */
i*2, i*2, i*2, i*2, i*2, /* repeat for zero, negative and positive */
i*2, i*2, i*2, i*2, i*2, /* references (-1 for spare points) */
/*
* 8979 Select-Before-Operate Map Table Definition
*/
DEFINE_TABLE = 9
NAME = A002MT02
MAXRECS = 24
CONTROL_WORD = 0x90
DEFINE_RECORD:
SIZE = * {2}
DEFINE_DATA:
i*2 /* type: 0 = T/C; 1 = PULSE; 2 = ON/OFF */
/*
* 8979 Pulse Output Map Table Definition
*/

DEFINE_TABLE = 10
NAME = A002MTRL
MAXRECS = 8
CONTROL_WORD = 0x92
DEFINE_RECORD:
SIZE = * {2}
DEFINE_DATA:
i*2, /* D20 system raise point (-1 for spare) */
i*2 /* D20 system lower point (-1 for spare) */
/*
* 8979 Analog Output Map Table Definition
*/
DEFINE_TABLE = 11
NAME = A002MT05
MAXRECS = 8
CONTROL_WORD = 0x92
DEFINE_RECORD:
SIZE = * {5}
DEFINE_DATA:
i*2, /* analog output scale range */
i*2, /* analog output scale divider */
i*2, /* analog output scale offset */
i*2 /* analog output type (unipolar = 1) */
/*
* 8979 Digital input Word Map Table Definition
*/
DEFINE_TABLE = 12
NAME = A002MTDI
MAXRECS = 4
CONTROL_WORD = 0x90
DEFINE_RECORD:
SIZE = 4 {16}
DEFINE_DATA:
i*2 i*2 {16} /* 16 points and options for every */
/* block least significant point first. */
/* (-1 for spare points) */
/*
* 8979 Digital output Word Map Table Definition
*/
DEFINE_TABLE = 13
NAME = A002MTSP
MAXRECS = 2
CONTROL_WORD = 0x92
DEFINE_RECORD:
SIZE = * {24}
DEFINE_DATA:
i[24]*2 /* D20 system point number */
/* 24 points for every block. */
/* least significant point first */
/* (-1 for spare) */

/*
* 8979 Chassis/RTU Descriptor Table Definition
*/
DEFINE_TABLE = 14
NAME = A002CHAS
MAXRECS = 34
CONTROL_WORD = 0x90
DEFINE_RECORD:
SIZE = *
DEFINE_DATA:
i*1 /* for each byte to return */
/*************************************************************************
* *
* A002_CFG.TXT - PART 2 *
* *
* In this section of the file, the configurer defines the data to be *
* loaded into each table. Be sure to match the DATA_TABLE numbers to the*
* correct DEFINE_TABLE numbers. *
* *
**************************************************************************/
/*
* 8979 Communications Port Configuration Table Data
*/
DATA_TABLE = 1 /* COMMUNICATIONS PORT #1 */

"COM1", /* communications port description */
9600, /* BAUD Rate */
5000, /* 5.000 second transmit timeout */
60, /* 60 second com_fail timeout */

-1, /* com_fail control output point number. */
00, /* No receive squelch */

15, /* RTS on time delay ( ms ) */
15, /* RTS off time delay ( ms ) */
15, /* character to character timeout ( ms ) */

2, /* two logical RTUs on this channel */
00, /* first and second in cross reference table */
/* COMMUNICATIONS PORT #2 */
"COM2", /* communications port description */
1200, /* BAUD Rate */
5000, /* 5.000 second transmit timeout */
60, /* 60 second com_fail timeout */

1, /* com_fail control output point number. */
00, /* No receive squelch */

15, /* RTS on time delay ( ms ) */
15, /* RTS off time delay ( ms ) */
15, /* character to character timeout ( ms ) */

1, /* one LRU on this channel */
1 /* third in LRU cross reference table */

/*
* 8979 Logical Remote Unit cross reference table
*/
DATA_TABLE = 2
1,00, /* address 1, process 0, COM1 (unique) */

2, 1 /* address 2, process 1, COM1 (redundant) */
/*
* 8979 LRU Configuration table
*/
DATA_TABLE = 3 /* First 8979 protocol process (process 0) */
31, /* number of indication points */
00, /* offset into indication map table */
32, /* number of SOE points */

00, /* offset into SOE map table */
40, /* SOE Log buffer size ( events ) */
4, /* number of pulse accumulators */

00, /* offset into acc. map table */
16, /* number of analog points */

00, /* offset into analog map table */
2500, /* analog integration process run freq (ms) */
1, /* number of ADC groups */

00, /* offset into ADC map table */
24, /* number of SBO points */

00, /* offset into SBO map table */
100, /* SBO timer increment ( ms ) */
10000, /* SBO timeout value ( ms ) */
00, /* inhibit SBO queuing? 1=yes, 0=no */
6, /* number of pulse output pairs */

00, /* offset into pulse output map table */
8, /* number of analog outputs */
00, /* offset into analog output map table */
2, /* number of digital input blocks */

00, /* offset into digital input map table */
2, /* number of digital output blocks */
00, /* offset into digital output map table */
-1, /* local/remote status point number */

1, /* local mode state (0=OFF, 1=ON) */
00, /* Support WARM_RESTART (NO=0, YES=nonzero) */
00 /* enable or disable time synchronization */

/*
* 8979 Configuration Table Data - invocation 2
*/
/* Second 8979 protocol process (process 1) */
32, /* number of indication points */
32, /* offset into indication map table */

32, /* number of SOE points */
32, /* offset into SOE map table */
40, /* SOE Log buffer size ( events ) */
4, /* number of pulse accumulators */
4, /* offset into acc. map table */
24, /* number of analog points */

16, /* offset into analog map table */
500, /* analog integration process run freq (ms) */
1, /* number of ADC groups */

1, /* offset into ADC map table */
16, /* number of SBO points */

8, /* offset into SBO map table */
100, /* SBO timer increment ( ms ) */
10000, /* SBO timeout value ( ms ) */
1, /* inhibit SBO queuing? 1=yes, 0=no */
4, /* number of pulse output pairs */
4, /* offset into pulse output map table */
4, /* number of analog outputs */

4, /* offset into analog output map table */
3, /* number of digital input points */

1, /* offset into digital input map table */
1, /* number of digital output blocks */

1, /* offset into digital output map table */
1, /* local/remote status point number */

1, /* local mode state (0=OFF, 1=ON) */
1, /* Support WARM_RESTART (NO=0, YES=nonzero) */

1 /* enable or disable time synchronization */
/*
* 8979 Change of State/Indication Map Table Data
*/
DATA_TABLE = 4
00,0x01, 1,0x01, 2,0x01, 3,0x01, 4,0x01, 5,0x01, 6,0x01, 7,0x01,
8,0x01, 9,0x01, 10,0x01, 11,0x01, 12,0x01, 13,0x01, 14,0x01, 15,0x01,
16,0x00, 17,0x00, 18,0x00, 19,0x00, 20,0x00, 21,0x00, 22,0x00, 23,0x00,
24,0x00, 25,0x00, 26,0x00, 27,0x00, 28,0x00, 29,0x00, 30,0x00, 31,0x00,
32,0x00, 33,0x00, 34,0x00, 35,0x00, 36,0x00, 37,0x00, 38,0x00, 39,0x00,
40,0x00, 41,0x00, 42,0x00, 43,0x00, 44,0x00, 45,0x00, 46,0x00, 47,0x00,
48,0x00, 49,0x00, 50,0x00, 51,0x00, 52,0x00, 53,0x00, 54,0x00, 55,0x00,
64,0x00, 65,0x00, 66,0x00, 67,0x00, 68,0x00, 68,0x00, 70,0x00, 71,0x00,
72,0x00, 73,0x00, 74,0x00, 75,0x00, 76,0x00, 77,0x00, 78,0x00, 79,0x00,
/*
* 8979 Sequence of Events Map Table Data
*/
DATA_TABLE = 5
8,0x00, 9,0x00, 10,0x00, 11,0x00, 12,0x00, 13,0x00, 14,0x00, 15,0x00,
16,0x00, 17,0x00, 18,0x00, 19,0x00, 20,0x00, 21,0x00, 22,0x00, 23,0x00,
24,0x00, 25,0x00, 26,0x00, 27,0x00, 28,0x00, 29,0x00, 30,0x00, 31,0x00,
32,0x01, 33,0x01, 34,0x01, 35,0x01, 36,0x01, 37,0x01, 38,0x01, 39,0x01,
40,0x01, 41,0x01, 42,0x01, 43,0x01, 44,0x01, 45,0x01, 46,0x01, 47,0x01,
48,0x01, 49,0x01, 50,0x01, 51,0x01, 52,0x01, 53,0x01, 54,0x01, 55,0x01,
64,0x01, 65,0x01, 66,0x01, 67,0x01, 68,0x01, 69,0x01, 70,0x01, 71,0x01,
72,0x01, 73,0x01, 74,0x01, 75,0x01, 76,0x01, 77,0x01, 78,0x01, 79,0x01,

/*
* 8979 Pulse Accumulator Map Table
*/
DATA_TABLE = 6
0, 1, 1, 1,
1, 1, 1, 1, /* reports all 8 accumulators */
2, 1, 1, 1, /* has freeze ownership of all 8 */
3, 1, 1, 1,
4, 0, 1, 0,
5, 0, 1, 0,
6, 0, 1, 0,
7, 0, 1, 0
/*
* 8979 Analog Map Table Data
*/
DATA_TABLE = 7
0, 2047, 32767, 0, 1, /* unipolar inputs - first 16 */
1, 2047, 32767, 0, 1,
2, 2047, 32767, 0, 1,
3, 2047, 32767, 0, 1,
4, 2047, 32767, 0, 1,
5, 2047, 32767, 0, 1,
6, 2047, 32767, 0, 1,
7, 2047, 32767, 0, 1,
8, 2047, 32767, 0, 1,
9, 2047, 32767, 0, 1,
10, 2047, 32767, 0, 1,
11, 2047, 32767, 0, 1,
12, 2047, 32767, 0, 1,
13, 2047, 32767, 0, 1,
14, 2047, 32767, 0, 1,
15, 2047, 32767, 0, 1,
16, 2047, 32767, 0, 0, /* bipolar inputs - next 16 */
17, 2047, 32767, 0, 0,
18, 2047, 32767, 0, 0,
19, 2047, 32767, 0, 0,
20, 2047, 32767, 0, 0,
21, 2047, 32767, 0, 0,
22, 2047, 32767, 0, 0,
23, 2047, 32767, 0, 0,
24, 2047, 32767, 0, 0,
25, 2047, 32767, 0, 0,
26, 2047, 32767, 0, 0,
27, 2047, 32767, 0, 0,
28, 2047, 32767, 0, 0,
29, 2047, 32767, 0, 0,
30, 2047, 32767, 0, 0,
31, 2047, 32767, 0, 0,
32, 2047, 32767, 0, 0,
33, 2047, 32767, 0, 0,
34, 2047, 32767, 0, 0,
35, 2047, 32767, 0, 0,
36, 2047, 32767, 0, 0,
37, 2047, 32767, 0, 0,
38, 2047, 32767, 0, 0,
39, 2047, 32767, 0, 0,

/*
* 8979 ADC Map Table Data
*/
DATA_TABLE = 8
40, 2047, 2047, 00, 00,
41, 2047, 2047, 00, 00,
42, 2047, 2047, 00, 00,
00, 2047, 32767, 00, 00,
1, 2047, 32767, 00, 00,
2, 2047, 32767, 00, 00,
/*
* 8979 Select-Before-Operate Map Table Data
*/
DATA_TABLE = 9
00, 0, /* normal TRIP/CLOSE */
1, 0,
2, 0,
3, 0,
4, 0,
5, 0,
6, 0,
7, 0,
8, 1,
9, 1,
10, 1,
11, 1,
12, 1,
13, 1,
14, 1,
15, 1,
32, 2,
33, 2,
34, 2,
35, 2,
36, 2,
37, 2,
38, 2,
39, 2
/*
* 8979 Pulse Output Map Table Data
* RAISE - LOWER
*/
DATA_TABLE = 10
16, 17,
18, 19,
20, 21,
22, 23,
24, 25,
26, 27,
28, 29,
30, 31

/*
* 8979 Analog Output Map Table Data
*/
DATA_TABLE = 11
0, 32767, 2048, 0, 0,
1, 32767, 2048, 0, 0,
2, 32767, 2048, 0, 0,
3, 32767, 2048, 0, 0,
4, 32767, 4095, 0, 1,
5, 32767, 4095, 0, 1,
6, 32767, 4095, 0, 1,
7, 32767, 4095, 0, 1
/*
* 8979 digital input word map table
*/
DATA_TABLE = 12
0,0x01, 3,0x01, 1,0x01, 6,0x01, 4,0x01, 5,0x01, 2,0x01, 7,0x01,
8,0x01, 9,0x01, 11,0x01, 14,0x01, 12,0x01, 13,0x01, 10,0x01, 15,0x01,
16,0x01, 17,0x01, 18,0x01, 19,0x01, 20,0x01, 21,0x01, 29,0x01, 23,0x01,
24,0x01, 26,0x01, 25,0x01, 27,0x01, 28,0x01, 22,0x01, 30,0x01, 31,0x01,
32,0x00, 33,0x00, 34,0x00, 37,0x00, 35,0x00, 36,0x00, 38,0x00, 39,0x00,
40,0x00, 41,0x00, 42,0x00, 43,0x00, 44,0x00, 47,0x00, 46,0x00, 45,0x00,
48,0x00, 49,0x00, 50,0x00, 51,0x00, 52,0x00, 53,0x00, 54,0x00, 55,0x00,
56,0x00, 57,0x00, 58,0x00, 59,0x00, 60,0x00, 61,0x00, 62,0x00, 63,0x00,
/*
* 8979 digital output word map table
*/
DATA_TABLE = 13
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23,
16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37,
38, 39
/*
* 8979 Chassis/RTU Table Data
*/
DATA_TABLE = 14
28,28,31,31,31,31,31,31,31,31,31,31,31,31,31,31,
0xFF, /* terminator */
28,28,31,31,31,31,31,31,31,31,31,31,31,31,31,31,
0xFF, /* terminator */

Appendix B:
MESSAGES LOGGED BY THE 8979
DPA
This appendix describes all fatal error, non-fatal, warning, and information messages
logged by the 8979 DPA to the Wesmaint Error Log.
Messages logged on the WESMAINT Error Log are prepended by the ID of the issuing
application process (PID). The PID will either be:
A002:
or
A002-<x>-<yy>:
where:
<x> is either A, C, L, M, P, or W
<y> is the process invocation number

A002-0CG.WES, Version 6.02 B-1
FATAL ERROR MESSAGES
During startup, the 8979 DPA checks its configuration and begins its initialization. If the
8979 DPA encounters errors in the configuration or the initialization that will impede the
overall functionality of the DPA, it will log a error message to the WESMAINT Error
Log and the suspend.
This section contains a description of all these fatal errors. Expressions in angular
brackets like "<x>", are filled with the appropriate values by the 8979 DPA. Each fatal
error message contains a unique identification number, within the range of 0 through 299.
100: cannot find A002_LXR config table

Cause:
• The 8979 DPA was unable to locate the A002_LXR configuration table in NVRAM.
Remedy:
• Ensure that table A002_LXR exists in the configuration, and is comprised of at least
one record.
101: cannot find A002_LRU config table

Cause:
• The 8979 DPA was unable to locate the A002_LRU configuration table in NVRAM.
Remedy:
• Ensure that table A002_LRU exists in the configuration, and is comprised of at least
one record.

B-2 A002-0CG.WES, Version 6.02
102: cannot find A002MT00 config table
Cause:
• Indication points were configured for at least one LRU in the A002_LRU table, but
the 8979 DPA was unable to locate the A002MT00 configuration table in NVRAM.
Remedy:
• Ensure indications are required by at least one LRU, and ensure the table exists in the
configuration with enough records to cover the needs of the LRU(s).
103: cannot find A002MSOE config table

Cause:
• SOE points were configured for at least one LRU in the A002_LRU table, but the
8979 DPA was unable to locate the A002MSOE configuration table in NVRAM.
Remedy:
• Ensure SOEs are required by at least one LRU, and ensure the table exists in the

Cause:
• Accumulator points were configured for at least one LRU in the A002_LRU table,
but the 8979 DPA was unable to locate the A002MT03 configuration table in
NVRAM.
Remedy:
• Ensure accumulators are required by at least one LRU, and ensure the table exists in
the configuration with enough records to cover the needs of the LRU(s).

Cause:
• Analog inputs were configured for at least one LRU in the A002_LRU table, but the
8979 DPA was unable to locate the A002MT04 configuration table in NVRAM.
Remedy:
• Ensure analog inputs are required by at least one LRU, and ensure the table exists in
the configuration with enough records to cover the needs of the LRU(s).

Cause:
• ADC reference points were configured for at least one LRU in the A002_LRU table,
NVRAM.
Remedy:
• Ensure ADC reference points are required by at least one LRU, and ensure the table
exists in the configuration with enough records to cover the needs of the LRU(s).

Cause:
• SBO points were configured for at least one LRU in the A002_LRU table, but the
8979 DPA was unable to locate the A002MT02 configuration table in NVRAM.
Remedy:
• Ensure SBO points are required by at least one LRU, and ensure the table exists in the

108: cannot find A002MTRL config table
Cause:
• Pulse output points were configured for at least one LRU in the A002_LRU table, but
the 8979 DPA was unable to locate the A002MTRL configuration table in NVRAM.
Remedy:
• Ensure pulse output points are required by at least one LRU, and ensure the table

Cause:
• Analog output points were configured for at least one LRU in the A002_LRU table,
NVRAM.
Remedy:
• Ensure analog output points are required by at least one LRU, and ensure the table
110: cannot find A002MTDI config table

Cause:
• Digital input words were configured for at least one LRU in the A002_LRU table, but
the 8979 DPA was unable to locate the A002MTDI configuration table in NVRAM.
Remedy:
• Ensure digital input words are required by at least one LRU, and ensure the table

111: cannot find A002MTSP config table
Cause:
• Digital output words were configured for at least one LRU in the A002_LRU table,
but the 8979 DPA was unable to locate the A002MTSP configuration table in
NVRAM.
Remedy:
• Ensure digital output words are required by at least one LRU, and ensure the table
112: cannot find A002CHAS config table

Cause:
• The 8979 DPA was unable to locate the A002CHAS configuration table in NVRAM.
Remedy:
• Ensure that table A002CHAS exists in the configuration, and contains a valid
configuration, as described in CHAPTER 15.
113: cannot find WESDAC_1 table

Cause:
• At least one non-spare binary input point was configured in either the A002MT00,
A002MSOE or A002MTDI table, but the DPA was unable to locate the binary input
database table.
Remedy:
• Ensure at least one record within the WIN CFG_DCA table contains binary inputs.

Cause:
• At least one non-spare binary output point was configured in either the A002MT02,
A002MSRL or A002MTSP table, but the DPA was unable to locate the binary
output database table.
Remedy:
• Ensure at least one record within the WIN CFG_DCA table contains binary outputs.

Cause:
• At least one non-spare accumulator point was configured in the A002MT03 table, but
the DPA was unable to locate the counter input database table.
Remedy:
• Ensure at least one record within the WIN CFG_DCA table contains counter inputs.

Cause:
• At least one non-spare analog input point was configured in the A002MT04 table, but
the DPA was unable to locate the analog input database table.
Remedy:
• Ensure at least one record within the WIN CFG_DCA table contains analog inputs.

Cause:
• At least one non-spare analog output point was configured in the A002MT05 table,
but the DPA was unable to locate the analog output database table.
Remedy:
• Ensure at least one record within the WIN CFG_DCA table contains analog outputs.
118: COM rec <x>, invalid RTS on time

Cause:
• The RTS on time configured in record <x> of the communication table is invalid.
Remedy:
• Ensure the RTS on time configured in record <x> of the A002_COM table contains a
valid value. Valid values are in the range 1 - 65535.
119: COM rec <x>, invalid com_fail timeout

Cause:
• The Com_Fail Timeout configured in record <x> of the communication table is
invalid.
Remedy:
• Ensure the Com_Fail Timeout configured in record <x> of the A002_COM table
contains a valid value. Valid values are in the range 1 - 65535.

120: COM rec <x>, invalid point number of com_fail control output
Cause:
• The number of Com_Fail Control Output configured in record <x> of the
communication table is invalid.
Remedy:
• Ensure the Com_Fail Control Output in record <x> of the A002_COM table contains
a valid value. A negative one (-1) indicates the control is not implemented. If the
control is implemented, the control output point number must be less than the total
number of controls defined in the system (WESDAC_2 table).
121: COM rec <x>, invalid number of LXR records

Cause:
• The number of LRUs specified in the communication table is zero.
Remedy:
• Ensure the Number of LRUs plus the First LRU specified in record <x> of the
A002_COM table is neither zero, nor greater than the number of records in
A002_LXR table.
122: COM rec <x>, invalid offset into LXR table

Cause:
• The LRU offset specified in the communication table is too large, or when combined
with the Number of LRUs, defines a range of A002_LXR records that exceeds the
size of the table.
Remedy:
• Ensure the Number of LRUs plus the First LRU specified in record <x> of the
A002_COM table is not greater than the number of records in A002_LXR.

123: LXR rec <x>, invalid LRU address
Cause:
• An invalid LRU address has been specified in the LRU cross reference table.
Remedy:
• Ensure that the LRU address configured in record <x> of the A002_LXR table is in
the range 1 - 255.
124: LXR rec <x>, invalid offset into LRU table

Cause:
• An invalid LRU offset has been specified in the LRU cross reference table.
Remedy:
• Ensure the LRU Offset configured in record <x> of the A002_LXR table is less than
the number of records in A002_LRU.
125:LRU rec <x>, invalid range of MT00 records
Cause:
• The range of indication points specified for LRU <x> exceeds the number of
configured indication points.
Remedy:
• Ensure the First Indication Point plus the Number of Indication Points configured
in record <x> of the A002_LRU table is not greater than the number of records in the
A002MT00 table.
126:RU rec <x>, invalid range of MSOE records

Cause:
• The range of SOE points specified for LRU <x> exceeds the number of configured
SOE points.
Remedy:
• Ensure the First SOE Point plus the Number of SOE Points configured in record
<x> of the A002_LRU table is not greater than the number of records in the
A002MSOE table.

127:LRU rec <x>, invalid range of MT03 records
Cause:
• The range of accumulator points specified for LRU <x> exceeds the number of
configured accumulator points.
Remedy:
• Ensure the First Accumulator Point plus the Number of Accumulator Points
configured in record <x> of the A002_LRU table is not greater than the number of
records in the A002MT03 table.
128: LRU rec <x>, invalid range of MT04 records

Cause:
• The range of analog input points specified for LRU <x> exceeds the number of
configured analog input points.
Remedy:
• Ensure the First Analog Input plus the Number of Analog Inputs configured in
record <x> of the A002_LRU table is not greater than the number of records in the
A002MT04 table.
129: LRU rec <x>, invalid analog int. frequency

Cause:
• LRU <x> is configured with an invalid analog integration frequency.
Remedy:
• Ensure the Analog Input Frequency configured in record <x> of the A002_LRU
table is in the range 1 - 2147483647.

Cause:
• The range of ADC points specified for LRU <x> exceeds the number of configured
ADC points.
Remedy:
• Ensure the First ADC Point plus the Number of ADC Points configured in record
A002MT11 table.

Cause:
• The range of SBO points specified for LRU <x> exceeds the number of configured
SBO points.
Remedy:
• Ensure the First SBO Point plus the Number of SBO Points configured in record
A002MT02 table.
132: LRU rec <x>, invalid SBO timer increment

Cause:
• LRU <x> is configured with an invalid SBO timer increment.
Remedy:
• Ensure the SBO Timer Increment configured in record <x> of the A002_LRU
table is in the range 1 - 65535.
133: LRU rec <x>, invalid SBO timeout

Cause:
• LRU <x> is configured with an invalid SBO timeout value.
Remedy:
• Ensure the SBO Timeout configured in record <x> if the A002_LRU table is in the
range 1 - 2147483647.

134: LRU rec <x>, invalid SBO queue inhibit
Cause:
• LRU <x> is configured with an invalid SBO lockout.
Remedy:
• Ensure the SBO Queue Inhibit field configured in record <x> of the A002_LRU
table is either 00 (no) or 1 (yes).
135: LRU rec <x>, invalid range of MTRL records

Cause:
• The range of pulse output (raise/lower) points specified for LRU <x> exceeds the
number of configured pulse output points.
Remedy:
• Ensure the First Pulse Output Pair plus the Number of Pulse Output Pairs
records in the A002MTRL table.

Cause:
• The range of analog outputs specified for LRU <x> exceeds the number of configured
analog outputs.
Remedy:
• Ensure the First Analog Output plus the Number of Analog Outputs configured
in record <x> of the A002_LRU table is not greater than the number of records in the
A002MT05 table.

137: LRU rec <x>, invalid range of MTDI records
Cause:
• The range of digital input words specified for LRU <x> exceeds the number of
configured digital input words.
Remedy:
• Ensure the First Digital Input Word plus the Number of Digital Input Words
records in the A002MTDI table.
138: LRU rec <x>, invalid range of MTSP records

Cause:
• The range of digital output words specified for LRU <x> exceeds the number of
configured digital output words.
Remedy:
• Ensure the First Digital Output Word plus the Number of Digital Output Words
records in the A002MTSP table.
139: LRU rec <x>, invalid local/remote status point number

Cause:
• The Local/Remote status point specified for LRU <x> is invalid.
Remedy:
• Ensure the Local/Remote Status Point configured in record <x> of the A002_LRU
table contains a valid value. A negative one (-1) indicates the point is not
implemented. If the point is implemented, the point number must be less than the total
number of binary input in the system table (WESDAC_1 table).

140: LRU rec <x>, invalid local state
Cause:
• The Local state specified for LRU <x> is invalid.
Remedy:
• Ensure the Local State configured in record <x> of the A002_LRU table contains a
valid value. Allowable states are either On (0) or Off (1).
141: MT00 rec <x>, invalid WESDAC_1 point

Cause:
• An invalid digital input point is being selected as an indication point.
Remedy:
• Ensure the Indication Point Number selected in record <x> of the A002MT00 table
refers to an existing digital input point.
142: MT00 rec <x>, invalid option selected

Cause:
• An invalid option setting is configured for an indication point.
Remedy:
• Ensure the Indication Type configured in record <x> of the A002MT00 table is
either 00 (normal) or 1 (inverted).
143: MSOE rec <x>, invalid WESDAC_1 point

Cause:
• An invalid digital input point is being selected as an SOE point.
Remedy:
• Ensure the SOE Point Number selected in record <x> of the A002MSOE table
refers to an existing digital input point.

144: MSOE rec <x>, invalid option selected
Cause:
• An invalid option setting is configured for a SOE point.
Remedy:
• Ensure the SOE Type configured in record <x> of the A002MSOE table is either 00
(normal) or 1 (inverted).

Cause:
• An invalid point is being selected as an accumulator point.
Remedy:
• Ensure the Accumulator Point Number selected in record <x> of the A002MT03
table refers to an existing accumulator point.

Cause:
• An invalid accumulator type is configured for an accumulator point.
Remedy:
• Ensure the Accumulator Type configured in record <x> of the A002MT03 table is
either 00 (transition) or 1 (pulse).
147: MT03 rec <x>, invalid freeze option

Cause:
• An invalid freeze ownership value is configured for an accumulator point.
Remedy:
• Ensure the Freeze Ownership flag in record <x> of the A002MT03 table is either 00
(no freeze ownership) or 1 (freeze ownership).

148: MT03 rec <x>, invalid read option
Cause:
• An invalid accumulator source is configured for an accumulator point.
Remedy:
• Ensure the Accumulator Source in record <x> of the A002MT03 table is either 00
(frozen buffer) or 1 (running buffer).

Cause:
• An invalid input point is being selected as an analog input point.
Remedy:
• Ensure the Analog Input Point Number selected in record <x> of the A002MT04
table refers to an existing analog input point.
150: MT04 rec <x>, divider cannot equal 0

Cause:
• A zero divider has been configured in the analog input map table.
Remedy:
• Ensure the Divider configured in record <x> of A002MT04 is non-zero.
151: MT04 rec <x>, invalid input type

Cause:
• An invalid input type is configured for an analog input point.
Remedy:
• Ensure the Analog Input Type configured in record <x> of the A002MT04 table is
either 00 (bipolar) or 1 (unipolar).

Cause:
• An invalid input point is being selected as an ADC reference point.
Remedy:
• Ensure all three Reference Point Numbers selected in record <x> of the A002MT11
table refers to existing analog input points.

Cause:
• A zero divider has been configured in the ADC reference map table.
Remedy:
• Ensure all three Dividers configured in record <x> of A002MT11 are non-zero.
154: MT11 rec <x>, invalid input type

Cause:
• An invalid input type is configured for an ADC reference point.
Remedy:
• Ensure all three Reference Types configured in record <x> of the A002MT11 table
are either 00 (bipolar) or 1 (unipolar).

Cause:
• An invalid digital output point is being selected as a SBO output point.
Remedy:
• Ensure the SBO Output Point Number selected in record <x> of the A002MT02
table refers to an existing digital output point.

Cause:
• An invalid input type is configured for an analog input point.
Remedy:
• Ensure the Analog Input Type configured in record <x> of the A002MT04 table is
157: MTRL rec <x>, invalid WESDAC_2 raise

Cause:
• An invalid digital output point is being selected as a raise point.
Remedy:
• Ensure the Raise Point Number selected in record <x> of the A002MTRL table
refers to an existing digital output point.
158: MTRL rec <x>, invalid WESDAC_2 lower

Cause:
• An invalid digital output point is being selected as an point.
Remedy:
• Ensure the Lower Point Number selected in record <x> of the A002MTRL table
refers to an existing digital output point.

Cause:
• An invalid point is being selected as an analog output point.
Remedy:
• Ensure the Analog Output Point Number selected in record <x> of the A002MT05
table refers to an existing analog output point.

Cause:
• A zero divider has been configured in the analog output map table.
Remedy:
• Ensure the Divider configured in record <x> of A002MT05 is non-zero.
161: MT05 rec <x>, invalid output type

Cause:
• An invalid output type is configured for an analog output point.
Remedy:
• Ensure the Analog Output Type configured in record <x> of the A002MT05 table is
162: MTDI rec <x> pt <y>, invalid WESDAC_1 point

Cause:
• An invalid digital input point range is being selected as a digital input word bit.
Remedy:
• Ensure the Digital Input Point Number for digital input <y> in record <x>of the
A002MTDI table refers to an existing digital input point.
163: MTDI rec <x> pt <y>, invalid option

Cause:
• An invalid input type is configured for one of the bits in a digital input word.
Remedy:
• Ensure the Input Type for digital input <y> in record <x> of the A002MTDI table
is either 00 (normal) or 1 (inverted).

164: MTSP rec <x> pt <y>, invalid WESDAC_2 point
Cause:
• An invalid digital output point is being selected as a digital output word bit.
Remedy:
• Ensure the Digital Output Point Number for digital output <y> in record<x> of the
A002MTSP table refers to an existing digital output point.
165: Not enough chassis configs defined

Cause:
• The chassis configuration table uses a free format where each processes configuration
ends with a termination byte (0xFF), excluding the last configuration, where the
termination byte is optional. There were not enough of these termination bytes found
in the chassis table.
Remedy:
• Ensure that each chassis configured in A002CHAS ends with 0xFF (the last chassis
configuration is optional). Refer to the chapter on configuring the chassis table
(chapter 15) for more detail.
166: LXR rec <x> and rec <y> same addr on <port>
Cause:
• Two LRUs are assigned the same address on the same communication port, in the
A002_LXR.
Remedy:
• Ensure that, for each communication port, all LRUs are assigned unique LRU
Addresses in the A002_LXR table.

200: Initial DPA Channel Failed
Cause:
• The DPA was unable to open an initial channel to WIN.
Remedy:
• Contact the Customer Service Department and report this error.
201: COMM_002 table creation error

Cause:
• The DPA was unable to create one of its internal data tables in NVRAM.
Remedy:
• Decrease the amount of NVRAM used by this and other applications if possible.
• Upgrade to a larger memory model.
202: get_pointer error on COMM_002

Cause:
• The DPA was unable to get a pointer to one of its internal data tables.
Remedy:
203: Error allocating A002-P-00 database

Cause:
• The DPA was unable to allocate enough memory for the Pulse Output process internal
database.
Remedy:
• Decrease the amount of RAM used by this and other applications if possible.

204: Error <x>, creating A002-P-00 exchange
Cause:
• The DPA was unable to create a message exchange for the Pulse Output Process.
Remedy:
205: Error <x> spawning A002-P-00

Cause:
• The DPA was unable to spawn the Pulse Output process.
Remedy:
206: Error <x> activating A002-P-00

Cause:
• The DPA was unable to activate the Pulse Output process.
Remedy:
207: Error allocating A002-L-<xx> database

Cause:
• The DPA was unable to allocate enough memory for the LRU's internal database.
Remedy:

208: Error <x> creating A002SL<yy> table
Cause:
• The DPA was unable to create an internal SOE log table for the LRU.
Remedy:
• Decrease the amount of NVRAM used by this and other applications if possible.
209: Error <x> setting rec #s in A002SL<yy> tbl

Cause:
• The DPA encountered an error while trying to set the number of records for the SOE
log.
Remedy:
210: Error <x> assigning A002SL<yy> table

Cause:
• The DPA encountered an error while trying to get ownership of an SOE log table.
Remedy:
211: Error <x> get_pointer on A002SL<yy>

Cause:
• The DPA was unable to get a pointer to one of its internal SOE log data tables.
Remedy:

212: Error <x>, creating A002-L-<yy> exchange
Cause:
• The DPA was unable to create a message exchange for one of the LRU processes.
Remedy:
213: Error <x> spawning A002-L-<yy>

Cause:
The DPA was unable to spawn one of the LRU processes.
Remedy:
Contact the Customer Service Department and report this error.
214: Error <x> activating A002-L-<yy>

Cause:
• The DPA was unable to activate one of the LRU processes.
Remedy:
215: Error <x> spawning A002-A-<yy>

Cause:
• The DPA was unable to spawn one of the analog integration processes.
Remedy:

216: Error <x> activating A002-A-<yy>
Cause:
• The DPA was unable to activate one of the analog integration processes.
Remedy:
217: Error allocating all COM process databases

Cause:
• The DPA was unable to allocate enough memory for all of the communication
processes' internal databases.
Remedy:
218: Error <x> spawning A002-C-<yy>

Cause:
• The DPA was unable to spawn one of the communication processes.
Remedy:
219: Error <x> activating A002-C-<yy>

Cause:
• The DPA was unable to activate one of the communication processes.
Remedy:

220: Error child process died!
Cause:
• One of the DPA's processes was deleted.
Remedy:
NON-FATAL ERROR MESSAGES
Non-fatal errors cause the offending process to log a message to the WESMAINT Error
Log and suspend without affecting the rest of the DPA. For example, if a single LRU
encounters a non-fatal error, that LRU will suspend processing, but all other LRUs will
continue to run normally.
This section contains a description of all these non-fatal errors. Expressions in angular
brackets like "<x>", are filled with the appropriate values by the 8979 DPA. Each
non-fatal error message contains a unique identification number, within the range of 300
through 599.
300: Error <x> on WIN open

Cause:
• The pulse output processes was unable to attach to WIN.
Result:
• Pulse outputs will not be available to any LRU configured.
Remedy:

400: Error <x> on WIN open
Cause:
• One of the LRU processes was unable to attach to WIN.
Result:
• This LRU will be unavailable to the host.
Remedy:
401: Error <x> on binary input REPORT_ENABLE

Cause:
• One of the LRU processes was unable attach a binary input event handler to WIN.
This handler is needed to maintain a local copy of the digital inputs.
Result:
Remedy:
402: Error <x> on DPA READY command

Cause:
• One of the DPAs was unable to issue a DPA READY command to WIN. This
command is used to signal the system that the LRU is ready to begin processing
messages.
Result:
Remedy:

500: Error <x> opening port <port>
Cause:
• One of the communication processes was unable to open the required communication
port.
Result:
• Communication through this port will be unavailable to the host. All LRUs
configured to communicate through this communication port will also be unavailable,
unless they are redundantly ported through another valid port.
Remedy:
• Ensure the port is not already being used by another communication process or by
another application.
501: Port <port>, invalid baud rate <x>

Cause:
• One of the communication processes has been configured to use an invalid baud rate.
Result:
Remedy:
• Ensure the baud rate set in A002_COM for the communication port, <port>, is set to
a valid rate.

502: Port <port>, error <x> setting char structure
Cause:
• One of the communication processes was unable to correctly set the operational
parameters for <port>.
Result:
Remedy:
503: Port <port>, error <x> setting port timers

Cause:
• One of the communication processes was unable to correctly set the port timers
needed for communications for <port>.
Result:
Remedy:

WARNING MESSAGES
This section describes the warning messages the 8979 DPA may log to the WESMAINT
Error Log. The warnings can be divided into three groups: memory allocation warnings,
WIN interface warnings, and message exchange warnings. If you find any of these
messages in the Error log, contact the Customer Service Department and report the
message.
Expressions in angular brackets like "<x>", are filled with the appropriate values by the
8979 DPA. Each warning message is given a unique identification number, within the
range of 600 through 899.
Memory Allocation Warnings

Whenever the 8979 DPA executes a command, a block of RAM is allocated by the 8979
DPA and passed to the appropriate DCA or DTA. Once the command has been executed,
the block of RAM is passed back to the 8979 DPA and made available again (free'd) to
all other applications in the system. If this memory cannot be allocated, the requested
command cannot be executed. If the memory cannot be free'd, system resources will be
reduced and will eventually cause the system to halt. Memory allocation warnings are
numbered 600 through 699.
600: Warning <x> on grab_seg call
601: Warning <x> on alloc_seg call
602: Warning <x> on free_seg call
603: Warning on malloc call
604: Warning <x> on free call
WIN Interface Warnings

During run-time, the 8979 DPA interfaces to the WESDAC Interface Node by writing
various commands. If any of these writes fail, the command can not be passed to other
applications in the system. WIN interface warnings are numbered 700 through 799.
700: Warning <x> on win_write call

Message Exchange Warnings
The 8979 DPA uses a number of message exchanges for inter-process communications. If
a process is unable to send a message to another process, or read from a message
exchange, the functionality of the 8979 DPA may be compromised. Message exchange
warnings are numbered 800 through 899.
800: Warning <x> sending msg to A002-L-<yy>

801: Warning <x> jamming A002-L-<yy> exchange
802: Warning <x> sending msg to A002-P-00
INFORMATION MESSAGES
Information messages are posted when the DPA encounters an situation were it must
perform some action as a result. Expressions in angular brackets like "<x>", are filled
with the appropriate values by the 8979 DPA. Each information message is given a
unique identification number, within the range of 900 through 999.
900: cannot find A002_COM config table

Cause:
• The DPA was unable to locate the main configuration table. When this table is
missing the DPA assumes that it is not required and deletes itself.
901: Tx Timeout set to default <x> ms
Cause:
• An invalid Transmit Timeout was configured for one of the communication ports in
A002_COM. The DPA is using a default value of <x> milliseconds instead.

902: RTS Off Time set to default <x> ms
Cause:
• An invalid RTS Off Delay was configured for one of the communication ports in
903: Inter-char Time set to default <x> ms

Cause:
• An invalid Character Timeout was configured for one of the communication ports in

GLOSSARY OF TERMS
application A piece of software (a program) consisting of one or

more processes and supporting functions.
ASCII American Standard Code for Information

Interchange. A seven-bit code that standardizes a set
of characters representing letters and numbers for
international use.
Baud rate A measurement of the speed of a communications

line; the number of times a line can change state in
one second; the rate at which a signal is modulated.
Binary A number system having only two symbols (1 and

0), and where values are expressed in the base two
number system.
Bit Abbreviation of binary digit. The smallest unit of

information in a binary system. Has a value of either
one (1) or zero (0).
Byte A group of eight adjacent bits that function as a

single unit. Defined as an octet by the International
Electrotechnical Commission (IEC).

A002-0CG.WES, Version 6.02 G-1
Change of state A significant change (as defined by a particular
system) in the condition of a point being monitored,
for example, a change in flow rate, temperature,
voltage, etc. Usually associated with dual-state
status (that is, alarm/normal conditions).
Abbreviated as COS.
Char The name of a data-type in the C programming

language. Stands for character, or a group of eight
bits that function as a single unit.
Configuration information The data or information that defines the operational

limits and characteristics of a particular device.
Depending on the device, this information is either
manually downloaded into NVRAM or EEPROM,
or is pre-programmed into EPROM.
Configuration system See WESDAC Configuration System.
Data-collection application A software application that acquires data from and

sends data to various intelligent electronic devices.
Abbreviated as DCA.
Data-processing application A software application that requests and processes

data as it is required by (usually) a master station.
Abbreviated as DPA.
Data-translation application A software application that translates data from one

form to another (for example digital input to analog
input). A data-translation application usually has no
direct interface to external devices. Abbreviated as
DTA.
Decimal A number system having ten symbols, and where

values are expressed in the base ten number system.
Erasable programmable A type of data storage (memory

read-only memory chip) designed to be programmed more than once.
Can be read but not altered by the system, because it
is a type of permanent memory. Abbreviated as
EPROM.

G-2 A002-0CG.WES, Version 6.02
Hexadecimal A number system having 16 symbols, and where
values are expressed in the base 16 number system.
Commonly used to abbreviate binary data.
Sometimes referred to as hex. Hexadecimal
numbers are often preceded by the prefix 0x.
Host The client or host station/computer, with which the

RTU equipment communicates. Also called a
master or master station.
Input/output A type or types of hardware device(s) used to

achieve human-to-machine or machine-to-machine
communication. Abbreviated as I/O.
Logical remote unit An RTU existing in software, but not physically.

LRUs are created by software partitioning of a
single physical RTU so that it appears to the master
station as two or more RTUs. This technique is
usually employed as a means by which to overcome
the point-addressing limitations of a particular
protocol, or to form a logical grouping of data.
Abbreviated as LRU.
Master The client or host station or computer, with which

the RTU equipment communicates. Also referred to
as a host or host computer.
Non-volatile random-access A semi-permanent type of data

memory storage (memory) that is backed up by batteries to
maintain stored data even if system power is lost.
Can be both read and changed by the system.
Abbreviated as NVRAM.
Port An interface point connecting a communications

channel and a device.
Random-access memory A type of temporary data storage (memory) that can

be read and changed while the computer is in use.
Data stored in random-access memory is lost if the
system loses power. Abbreviated as RAM.

Read-only memory A type of permanent data storage (memory) that can
be read but not altered by the system. Data stored in
read-only memory is not affected by power loss to
the system. Abbreviated as ROM.
Remote terminal unit A piece of equipment located at a distance from a

master stat ion to monitor and control the status of
outlying equipment, and to communicate the
information back to the master station or host.
Abbreviated as RTU.
Sequence of events A time-tagged change of state, logged as part of a

chronological record of significant changes in the
condition of a particular point or points being
monitored. Abbreviated as SOE.
Slave See sub-remote unit.
Source code A piece of code that has not yet been compiled or
assembled (that is, it is still in the language it was
programmed in) and so cannot yet run on a
machine.
Sub-remote unit A physical device (e.g., peripheral boards, D20

RTUs, non-D20 RTUs, meters, or other intelligent
electronic device) that collects data, processes it in
some way, and communicates it to a master remote
unit (MRU). SRUs (also called slave units) are able
to respond to commands from MRUs.
System points A list of points owned by a data-collection

application or a data-translation application.
System points may include hardware points, and
pseudo-points.
Trip/close A type of digital output that stops or starts an action.

Trip/close outputs utilize two relays: a master relay
and a select relay. Abbreviated as T/C.

WESDAC Interface Node A module of software that manages the transfer,
storage, and manipulation of data between data-
collection applications (DCA), data-processing
applications (DPA) and data-translation applications
(DTA). Abbreviated as WIN.
WESDAC Configuration System A menu-oriented software program that operates on

a personal computer and allows you to download
configuration information to D20 RTUs or CPM
RTUs.

LIST OF ACRONYMS
AND ABBREVIATIONS
ADC analog-to-digital converter

ASCII American Standard Code for Information
Interchange
COM communication
DCA data-collection application

DCD data-carrier detect
DPA data-processing application
I/O input/output
LRU logical remote unit
MAXRECS maximum number of records

ms milliseconds
NVRAM non-volatile random-access memory
RAM random-access memory

RTS request to send
RTU remote terminal unit
SBO switch-before-operate
SCADA supervisory control and data acquisition
SOE sequence of events

A002-0CG.WES, Version 6.02 L-1
WESDAC WESDAC Data Acquisition and Control
WESMAINT WESDAC Maintenance Facility
WIN WESDAC Interface Node

L-2 A002-0CG.WES, Version 6.02

Configuration Guide: Harris Canada, Inc. Controls Division Distributed Automation Products

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

Configuration Guide: Harris Canada, Inc. Controls Division Distributed Automation Products

Uploaded by

Copyright:

Available Formats

Harris Canada, Inc.

Submitted By: Authorized By:

©1996, Harris Canada, Inc. All rights reserved.

8979 DPA Configuration Guide

VERSION DATE INITIALS COMMENT

90.05.30 AS Created for version 3.00 of the 8979 protocol.

91.01.31 CD The display of ADC values on the custom

91.02.04 LB Re-named document from D20DA021 (DW4format)

1.00 91.11.20 NM Removed references to Lousiana Power and Light

1.01 92.05.06 TN WIN version.

1.02 92.05.20 LA Cleaned up the format.

1.03 92.08.05 LA Editorial revisions as per C. Huene.

1.04 93.07.21 AV Formatted to Harris standards and revisions as per

3.00 93.08.25 AV Changed footers for new version numbers.

4.00 94.11.21 AV Versioned up the document to 4.00 to match

5.00 95.06.20 DC Major revisions based on A002-1CG.WES Ver.2.00.

6.00 95.10.02 DY Added com_fail timeout and com_fail control output

6.01 96.01.09 RS Added note about First SBO Output in A002_LRU

6.02 96.06.13 SK Removed “Local Mode” information message.

8979 DPA Configuration Guide

ABOUT THIS GUIDE

Chapter 1: CONFIGURATION TABLES

Chapter 2: CONFIGURING THE A002_COM TABLE

8979 DPA Configuration Guide

Chapter 4: CONFIGURING THE A002_LRU TABLE

Harris Controls - Distributed Automation Products

Chapter 6: CONFIGURING THE A002MSOE TABLE

Chapter 7: CONFIGURING THE A002MT03 TABLE

Chapter 8: CONFIGURING THE A002MT04 TABLE

Chapter 9: CONFIGURING THE A002MT11 TABLE

8979 DPA Configuration Guide

Chapter 10: CONFIGURING THE A002MT02 TABLE

Chapter 11: CONFIGURING THE A002MTRL TABLE

Chapter 12: CONFIGURING THE A002MT05 TABLE

Chapter 13: CONFIGURING THE A002MTDI TABLE

Chapter 14: CONFIGURING THE A002MTSP TABLE

Chapter 15: CONFIGURING THE A002CHAS TABLE

Harris Controls - Distributed Automation Products

Appendix B: MESSAGES LOGGED BY THE 8979 DPA

GLOSSARY OF TERMS G-1

LIST OF ACRONYMS AND ABBREVIATIONS L-1

8979 DPA Configuration Guide

Figure 1 System Overview xviii

Table 1-1 8979 DPA Configuration Tables 1-2

8979 DPA Configuration Guide

PURPOSE OF THIS GUIDE

WHO SHOULD USE THIS GUIDE

8979 DPA Configuration Guide

HOW THIS GUIDE IS ORGANIZED

This guide is organized into the following sections:

Harris Controls - Distributed Automation Products

8979 DPA Configuration Guide

Harris Controls - Distributed Automation Products

The 8979 data-processing application (DPA) is a software application which will

8979 DPA Configuration Guide

Data DCA Event DCA Event Data

Figure 1 System Overview

Harris Controls - Distributed Automation Products

8979 DPA Configuration Guide

TABLE NAME DESCRIPTION

A002_LRU This table contains LRU related parameters. One record is

A002MT03 This table contains accumulator point mappings and attributes.

A002MT11 This table contains analog reference point mappings and