Configuration Technical Reference Manual

SCADAPack E Configuration
Technical Reference
2 SCADAPack E Configuration Technical Reference
Table of Contents
Part I Configuration Technical 5

1 Technical
...................................................................................................................................
Support 5
2 Safety ...................................................................................................................................
Information 6
3 Introduction
................................................................................................................................... 8
4 RTU Configuration
................................................................................................................................... 10
4.1 Concepts .......................................................................................................................................................... 11
4.2 I/O Num bering.......................................................................................................................................................... 12
4.2.1 Methodology .........................................................................................................................................................
& System Points 13
4.2.2 Physical I/O......................................................................................................................................................... 14
4.2.2.1 SCADAPack E Physical .........................................................................................................................................
I/O Numbering 15
4.2.2.2 SCADAPack ES Physical .........................................................................................................................................
I/O Numbering 16
4.2.2.3 SCADAPack ES Remote .........................................................................................................................................
I/O Units 18
4.2.3 User Points......................................................................................................................................................... 21
4.3 RTU Start-Up &..........................................................................................................................................................
Configuration Revisions 22
4.4 Configurations ..........................................................................................................................................................
Becom ing Active 24
4.4.1 Point Attributes and Properties Becoming Active & Configurations and
ISaGRAF ......................................................................................................................................................... 25
4.5 SCADAPack E..........................................................................................................................................................
I/O Configurations 26
4.6 SCADAPack ER ..........................................................................................................................................................
I/O Configurations 26
4.6.1 I/O Card Configuration
.........................................................................................................................................................
& Applying I/O Configurations 28
4.6.2 Assignment.........................................................................................................................................................
of DNP Points to Physical Channels 28
5 Point ...................................................................................................................................
Attributes 30
5.1 Com m on Point ..........................................................................................................................................................
Attribute Configurations 31
5.1.1 DNP Point Number,
.........................................................................................................................................................
Point Type & Data Class 33
5.1.2 Slot Channel......................................................................................................................................................... 35
5.1.3 Control Interlocks
......................................................................................................................................................... 35
5.1.4 Interlock Alarm
.........................................................................................................................................................
Timeout & Point is Bad 37
5.1.5 Alarm & Trend
.........................................................................................................................................................
Inhibit & Profile ID 38
5.1.6 IEC 60870 -.........................................................................................................................................................
IOA & ASDU Type 39
5.1.7 Conitel Slave
.........................................................................................................................................................
Type 40
5.2 Binary Point Attributes
.......................................................................................................................................................... 41
5.2.1 DNP Object.........................................................................................................................................................
Type 45
5.2.2 Alarm Active.........................................................................................................................................................
& Invert Point State & Unsolicited 46
5.2.3 Time Deadband
.........................................................................................................................................................
Into & Out of Alarm 47
5.2.4 De-bounce.........................................................................................................................................................
Time & Drop Output on Interlock Active 48
5.2.5 Output Pulse.........................................................................................................................................................
Time 49
5.2.6 Trip Close Partner
.........................................................................................................................................................
Point 50
5.3 Analog Point Attributes
.......................................................................................................................................................... 51
5.3.1 DNP3 Static.........................................................................................................................................................
Object Type 62
5.3.2 Point Properties
.........................................................................................................................................................
DNP Binary Points 63
5.3.3 Engineering.........................................................................................................................................................
Limits & Unsolicited Alarm Limit Events 64
5.3.4 Integer to Engineering
.........................................................................................................................................................
Conversion & Rate of Rise and Fall 65
5.3.5 Over-range.........................................................................................................................................................
and Under-range Limits & IEC 870 - Cyclic Scan 66
5.3.6 No Change.........................................................................................................................................................
& Value Deadband Out of Alarm 67
5.3.7 Time Deadband
.........................................................................................................................................................
Into & Out of Alarm 68
5.3.8 Zero Threshold
.........................................................................................................................................................
Limit 69
Contents 3
5.3.9 Limit Transgression

.........................................................................................................................................................
- DNP Event Enable 70
5.3.10 Event Deviation
.........................................................................................................................................................
& Event Deviation Type 71
5.4 Counter Point..........................................................................................................................................................
Attributes 72
5.4.1 DNP Object .........................................................................................................................................................
Type & Unsolicited 74
5.4.2 Counter Reset,.........................................................................................................................................................
High Counter Limit & Counter Limit Exceeded 75
5.4.3 Counter High
.........................................................................................................................................................
Limit Exceeded & Significant Change Deviation 76
5.5 Trend Record..........................................................................................................................................................
Configuration 77
6 Point ...................................................................................................................................
Properties 78
6.1 Com m on Point ..........................................................................................................................................................
Properties 79
6.1.1 Point Quality .........................................................................................................................................................
Reason 80
6.1.2 I/O Not Responding
.........................................................................................................................................................
& Remote Control Interlock 81
6.1.3 Under ISaGRAF .........................................................................................................................................................
Control & Point is Failed 82
6.2 Digital Point Properties
.......................................................................................................................................................... 83
6.3 Analog Point Properties
.......................................................................................................................................................... 85
6.3.1 Current Value .........................................................................................................................................................
Integer & Engineering 86
6.3.2 Over-Range .........................................................................................................................................................
& Under-Range 87
6.3.3 A/D Reference .........................................................................................................................................................
Error & No Change State 88
6.3.4 Rate of Change.........................................................................................................................................................
Rise & Fall States 89
6.3.5 Analog Limits .........................................................................................................................................................
Transgressed 90
6.3.6 Time Dead-band.........................................................................................................................................................
Active 91
6.4 Counter Point..........................................................................................................................................................
Properties 91
7 Point ...................................................................................................................................
Database Access 93
7.1 Database Record ..........................................................................................................................................................
Exchange Area 95
7.2 Record Exchange ..........................................................................................................................................................
Area System Points 96
7.3 Reading Database
..........................................................................................................................................................
Point Records 100
7.3.1 Reading Digital
.........................................................................................................................................................
Point Records 102
7.3.2 Reading Analog
.........................................................................................................................................................
Point Records 103
7.3.3 Reading Counter
.........................................................................................................................................................
Point Records 105
7.3.4 Reading Database
.........................................................................................................................................................
Trend Records 106
7.4 Writing Database
..........................................................................................................................................................
Point Records 108
7.4.1 Required .........................................................................................................................................................
Point Type Enumeration for Write Record Exchange 109
7.4.2 Writing to.........................................................................................................................................................
a Digital Point Record 110
7.4.3 Writing to.........................................................................................................................................................
an Analog Point Record 112
7.4.4 Writing to.........................................................................................................................................................
a Counter Point Record 114
7.4.5 Writing to.........................................................................................................................................................
a Trend Point Record 116
7.4.6 Notes and.........................................................................................................................................................
Limitations of Writing Database Records 117
7.4.6.1 Record Exchange .........................................................................................................................................
Failures 118
7.4.6.2 RTU Configuration .........................................................................................................................................
Revision Numbers 119
7.4.6.3 Trend Deletion Results .........................................................................................................................................
in No Trends Being Deleted 120
7.4.6.4 Restarting the Profiler,.........................................................................................................................................
Sampler and IEC 60870-5 tasks 121
7.5 Using Record..........................................................................................................................................................
Exchange to m odify configuration in the RTU 122
7.5.1 Adding & .........................................................................................................................................................
Disabling Points 123
7.5.2 Using Record Exchange w ith ISaGRAF, Profiler, Sampler & IEC 60870-5
tasks ......................................................................................................................................................... 124
7.6 Double Status ..........................................................................................................................................................
Points 125
8 RTU ...................................................................................................................................
System Points 126
8.1 Binary System
..........................................................................................................................................................
Point Map 127
8.2 Analog System
..........................................................................................................................................................
Point Map 132
8.3 String System
..........................................................................................................................................................
Point Map 153
8.4 BOOTP Configuration
..........................................................................................................................................................
Records 155
3
Configuration Technical 5
I Configuration Technical
©2013 Control Microsystems Inc.

All rights reserved.
Printed in Canada.
Version: 8.05.7
The information provided in this documentation contains general descriptions and/or technical
characteristics of the performance of the products contained herein. This documentation is
not intended as a substitute for and is not to be used for determining suitability or reliability of
these products for specific user applications. It is the duty of any such user or integrator to
perform the appropriate and complete risk analysis, evaluation and testing of the products
with respect to the relevant specific application or use thereof. Neither Schneider Electric nor
any of its affiliates or subsidiaries shall be responsible or liable for misuse of the information
contained herein. If you have any suggestions for improvements or amendments or have
found errors in this publication, please notify us.
No part of this document may be reproduced in any form or by any means, electronic or
mechanical, including photocopying, without express written permission of Schneider
Electric.
All pertinent state, regional, and local safety regulations must be observed when installing and
using this product. For reasons of safety and to help ensure compliance with documented
system data, only the manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant
instructions must be followed. Failure to use Schneider Electric software or approved
software with our hardware products may result in injury, harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
1 Technical Support
Support related to any part of this documentation can be directed to one of the following
support centers.
Technical Support: The Americas

Available Monday to Friday 8:00am – 6:30pm Eastern Time
Toll free within North America 1-888-226-6876
Direct Worldwide +1-613-591-1943
Email [email protected]
Technical Support: Europe

Available Monday to Friday 8:30am – 5:30pm Central European Time
Direct Worldwide +31 (71) 597-1655
Technical Support: Asia

Available Monday to Friday 8:00am – 6:30pm Eastern Time (North America)
Direct Worldwide +1-613-591-1943
Technical Support: Australia

Inside Australia 1300 369 233
2 Safety Information
Read these instructions carefully, and look at the equipment to become familiar with the
device before trying to install, operate, or maintain it. The following special messages may
appear throughout this documentation or on the equipment to warn of potential hazards or to
call attention to information that clarifies or simplifies a procedure.
The addition of this symbol to a Danger or Warning safety label

indicates that an electrical hazard exists, which will result in personal
injury if the instructions are not followed.
This is the safety alert symbol. It is used to alert you to potential

personal injury hazards. Obey all safety messages that follow this
symbol to avoid possible injury or death.
DANGER
DANGER indicates an imminently hazardous situation which, if not avoided, will
result in death or serious injury.
WARNING
WARNING indicates a potentially hazardous situation which, if not avoided, can
result in death or serious injury.
CAUTION
CAUTION indicates a potentially hazardous situation which, if not avoided, can
result in minor or moderate.
CAUTION
CAUTION used without the safety alert symbol, indicates a potentially hazardous
situation which, if not avoided, can result in equipment damage..
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by qualified
personnel. No responsibility is assumed by Schneider Electric for any consequences arising
out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction and
operation of electrical equipment and the installation, and has received safety training to
recognize and avoid the hazards involved.
BEFORE YOU BEGIN

Do not use this product on machinery lacking effective point-of-operation guarding. Lack of
effective point-of-operation guarding on a machine can result in serious injury to the operator
of that machine.
CAUTION
EQUIPMENT OPERATION HAZARD
Verify that all installation and set up procedures have been completed.
Before operational tests are performed, remove all blocks or other temporary
holding means used for shipment from all component devices.
Remove tools, meters, and debris from equipment.
Failure to follow these instructions can result in injury or equipment

damage.
Follow all start-up tests recommended in the equipment documentation. Store all equipment
documentation for future references.
Software testing must be done in both simulated and real environments.
Verify that the completed system is free from all short circuits and grounds, except those
grounds installed according to local regulations (according to the National Electrical Code in
the U.S.A, for instance). If high-potential voltage testing is necessary, follow
recommendations in equipment documentation to prevent accidental equipment damage.
Before energizing equipment:
Remove tools, meters, and debris from equipment.
Close the equipment enclosure door.
Remove ground from incoming power lines.
Perform all start-up tests recommended by the manufacturer.
OPERATION AND ADJUSTMENTS

The following precautions are from the NEMA Standards Publication ICS 7.1-1995 (English
version prevails):
Regardless of the care exercised in the design and manufacture of equipment or in the
selection and ratings of components, there are hazards that can be encountered if such
equipment is improperly operated.
It is sometimes possible to misadjust the equipment and thus produce unsatisfactory or
unsafe operation. Always use the manufacturer’s instructions as a guide for functional
adjustments. Personnel who have access to these adjustments should be familiar with the
equipment manufacturer’s instructions and the machinery used with the electrical
equipment.
Only those operational adjustments actually required by the operator should be accessible
to the operator. Access to other controls should be restricted to prevent unauthorized
changes in operating characteristics.
3 Introduction
This manual describes the technical aspects of the SCADAPack E RTU Configurations. Technical
information provided for RTU configurations include:
Physical Points
User Points
System Points
Point Attributes
Point Properties
Trend Records
Record Exchange
4 RTU Configuration
Concepts 11
I/O Numbering 12
RTU Start-Up & Configuration Revisions 22

Configurations Becoming Active 24
SCADAPack ER I/O Configurations 26

4.1 Concepts
Points are used in the SCADAPack E RTU to access data and RTU system configurations. Each RTU
point is accessible through DNP3 protocol. Points fall into one of two categories:
Physical RTU internal representation of electrical terminations on a Main RTU or Remote I/O
Points: Unit. These may be either Input Points or Output Points.
Derived RTU internal data. These may be either User Points (created by a user defined
Points: configuration) or System Points (managed by the SCADAPack E RTU operating
system)
The SCADAPack E RTU supports various point types.

Point Type and Point Number uniquely identify each point in the SCADAPack E RTU.
See Section I/O Numbering / Methodology 13 for information on Point Numbering methodologies.
Point Type may be one of the following:

Digital Point These may be Input, Output, User or System points.
(also referred to as “Binary Point” throughout the DNP3 protocol documentation and the SCADAPack
E RTU documentation)
Analog Point These may be Input, Output, User or System points.
Counter Point These are Input points on an SCADAPack E RTU.
String Point These are System points on an SCADAPack E RTU.
The shaded intersections in the following diagram indicate the valid Point Types for the SCADAPack E
RTU.
The RTU Point Types refer to points in the SCADAPack E RTU point database, and are not necessarily
the same as the point objects used by communication protocols when representing point data.
4.2 I/O Numbering

The information in this section describes the I/O Point Numbering Methodology used for SCADAPack E
RTUs, for Inputs, Outputs, User Points and System Points.
Methodology & System Points 13
Physical I/O 14
User Points 21
4.2.1 Methodology & System Points
Methodology
The general methodology rules are:
Point numbers are not necessarily unique across point types.
Physical I/O points may have the same point index across Digital Input, Digital Output, Analog Input,
Analog Output and Counter Input types, but they refer to different physical points. e.g. Physical Digital
Input 7 is different from Physical Digital Output 7, Analog Input 7, etc.
Derived points are both input and output points simultaneously, with a common point index between
like input and output types. E.g. Derived Analog Input 57 and Derived Analog Output 57 refer to the
same RTU database point.
DNP3 16-bit point index numbering is used throughout the SCADAPack E RTU (valid point index
numbers are 0-65535 for each point type).
For more information see the SCADAPack E Data Processing Technical Reference.
SCADAPack E physical I/O numbers may be assigned as required (except for the SCADAPack ES).
The valid range for a SCADAPack E physical I/O point number is 0 to 49999.
The SCADAPack ES RTU has fixed Physical I/O numbering starting at point index "1" for each point
type. It has limited support for point number 0. See SCADAPack ES Physical I/O Numbering 16 .
RTU I/O provided by SCADAPack ES Remote I/O Units transparently forms additional I/O for Main RTU
Unit (SCADAPack ES and SCADAPack ER only).
System Points
SCADAPack E System Point numbers start at DNP3 point index 50000
System Points exist in the RTU and are of fixed point number and data type according to the function
of the system point
Some System Points may be configured with complete RTU database functionality e.g. report events
in class polls, etc. These are known as Configurable System Points.
System Points can be accessed through DNP3 Level 3 point read requests
4.2.2 Physical I/O
Physical I/O numbering is subject to the following rules:

DNP3 Binary Input, Binary Output, Analog Input, Analog Output and Counter objects accessing
physical RTU points may share the same DNP3 point numbers.
Different DNP3 objects refer to different physical device connections, subject to the rules of the
DNP3 User Group’s Data Object Library document,
See Binary Point Attributes 41 .
Physical I/O is accessed according to DNP3 Object Groups as follows:
o Object Groups 1,2 (binary input objects) access Physical Digital Inputs
o Object Groups 10,12 (binary output objects) access Physical Digital Outputs
o Object Groups 20-23 (counter objects) access counters associated with
o RTU Physical Digital Inputs
o Object Groups 30-33 (analog input objects) access Physical Analog Inputs
o Object Groups 40,41 (analog output objects) access Physical Analog Outputs
Local physical point numbers for SCADAPack ES start at DNP point 1, whereas local physical point
numbers for other SCADAPack E RTUs may be assigned as required (valid range 0 – 49999).
SCADAPack ES Remote I/O point numbering can be automatically assigned or specifically defined.
Remote physical points can be interleaved with User points. Refer to the SCADAPack ES Remote I/
O Technical Reference for more information.
On power-up or RTU restart, Physical output points are cleared by default.
4.2.2.1 SCADAPack E Physical I/O Numbering
SCADAPack E Physical I/O Numbering

The numbering of physical I/O points in SCADAPack E RTUs utilises DNP3 point indexes.
SCADAPack 300E RTUs and SCADAPack ER RTUs allow the user to assign DNP3 point indexes to
physical I/O points.
SCADAPack ES RTUs have fixed DNP3 point indexes for physical I/O points on a Main RTU. See
SCADAPack ES Physical I/O Numbering 16 .
SCADAPack ES Remote I/O numbering can be assigned automatically (by default) or can be user
assigned. See SCADAPack ES Remote I/O Units 18 .
SCADAPack 300E Physical I/O Numbering

The assignment of DNP point numbers on SCADAPack 300E RTUs is user configurable.
The following information summaries the physical module address and channel numbering
methodology for SCADAPack 300E physical points,
I/O module addresses are enumerated from 0 to 15. Modules off different I/O types can have the same
module address, however modules of similar I/O types (including mixed modules) must have unique
addresses within those module types. For more information see the relevant I/O Module Hardware
manuals.
The channel numbers indicated for a given module are 0-based, e.g. for a 5506 AI module at module
address 0. The available channels are identified as follows:
Module 0: AI channel 0 to 7
The assignment of DNP point numbers to these physical channels is a user configuration issue. The
following rules must apply to allocation of DNP points to physical I/O channels:
valid DNP point numbers allowed are 0 – 49999
for a given point type (i.e. DI / DO / AI / AO / CTR), there is a strict 1-1 mapping of point number to
channel.
Therefore any valid point number (0-49999) can be assigned to any physical channel.
HINT. It is preferable to use contiguous point numbers on a given module. This can reduce the DNP3
response size for points that are to be returned in DNP integrity polls.
The mapping of RTU configuration points to physical channels is discussed in Section Assignment of
DNP Points to Physical Channels 28 .
SCADAPack ER Physical I/O Numbering

The assignment of DNP point numbers on SCADAPack ER RTUs is user configurable.
The following information summaries the physical slot and channel numbering methodology for
SCADAPack ER physical points,
The rack's slots are enumerated from 1 (next to processor card) to 13 (recommended power supply
location).
The channel numbers on a given slot are 1-based, e.g. for a 16 RO card (card type 0x21) on local slot 2.
The available channels are identified as follows:
Slot 2: DO channel 1 to 16
The assignment of DNP point numbers to these physical channels is up to the user configuration. The
following rules apply to allocation of DNP points to physical I/O channels:
valid DNP point numbers allowed are 0 – 49999
for a given point type (i.e. DI / DO / AI / AO / CTR), there is a strict 1-1 mapping of point number to
channel.
Therefore any valid point number (0-49999) can be assigned to any physical channel.
HINT. It is preferable to use contiguous point numbers on a given slot. This can reduce the DNP
response size for points that are to be returned in DNP class 0 polls.
The mapping of RTU configuration points to physical channels is discussed in Section Assignment of
DNP Points to Physical Channels 28 .
There are SCADAPack E Configurator facilities on the which assists in the creation of initial
configurations according to detected I/O cards. These are on the SCADAPack E Configurator I/O /
SCADAPack ER I/O page and presented as Get IO (No Num.) and Get IO (Auto Num.) buttons. These
retrieve the I/O configurations from the RTU and build configuration based on the detected I/O cards.
Get IO (No Num.) retrieves configurations for the installed I/O cards without applying any I/O
configuration numbering.
Get IO (Auto Num.) retrieves configurations for the installed I/O cards and applies automatic I/O point
numbering, starting at DNP Point index 0 for the first card of each type detected, then applies sequential
numbering for further I/O cards and channels.
The same functionality is available through the command line function “GETmagcfg”, Refer to the
SCADAPack E RTU Operational Reference manual for more information.
4.2.2.2 SCADAPack ES Physical I/O Numbering
Main RTU Unit

A standard RTU configuration may have consist of a Main RTU only. SCADAPack ES Main RTU I/O
DNP3 point numbering is fixed and cannot be changed. See table below.
In a SCADAPack ES, Binary Input Point 0, Binary Output Point 0, Analog Input Point 0, Analog Output
Point 0 and Counter Point 0 are NOT Physical I/O points. These points do exist by default as derived
points in the SCADAPack ES RTU point database. As such, reads and controls to the relevant point 0
objects are successful.
A Main RTU may be expanded by addition of SCADAPack ES Remote I/O Unit(s) (see Section
SCADAPack ES Remote I/O Units 18 for details)
SCADAPack ES DNP3 I/O Numbering

SCADAPack
ES DIGITAL IN DIGITAL OUT ANALOG IN ANALOG OUT COUNTER
RTU Model
Model A 1..32 1..16 1..12 1..4 1..32
Model B N/A N/A N/A N/A N/A
Model E 1..16 1..8 1..6 1..2 1..16
Also see SCADAPack E RTU Hardware Manual.

4.2.2.3 SCADAPack ES Remote I/O Units
SCADAPack ES Remote I/O Units
SCADAPack ES RTUs can currently be used as Remote I/O RTUs. SCADAPack ES and SCADAPack
ER RTUs can be Main RTUs and extend their I/O with SCADAPack ES Remote I/O units.
If SCADAPack ES Remote I/O is used, it is strongly recommended that the specific point number
assignment method is used to map the physical points on the main RTU to avoid overlapping of remote
and local physical points. Refer to the SCADAPack E Remote I/O Technical Reference for more
information
Remote I/O Units provide an increase in the I/O capacity of an RTU Main Unit.
Remote I/O units have DNP3 I/O point numbering as described in the following examples.
The numbering for Remote units can be assigned in one of two ways, i.e. automatic point number
assignment or specific point number assignment.
The following examples illustrates the Remote I/O point numbering when the point numbers are
automatically assigned, however the point mapping can be specifically defined by using the Data
Concentrator configuration interface.
Refer to the SCADAPack ES Remote I/O Technical Reference and the SCADAPack E Data
Concentrator Technical Reference for more information.
SCADAPack ES Automatic Point Number Assignment

The automatic numbering for the first SCADAPack ES Remote I/O Unit starts at 101, with each
additional unit numbering beginning on a consecutive multiple of 100.
For a FIRST SCADAPack ES Remote I/O Unit with the following I/O capacity (assuming it is a
SCADAPack ES model A):
32 Digital Inputs
16 Digital (Relay) Outputs
12 Analog Inputs
4 Analog Outputs
The I/O numbering is as follows (where SCADAPack ES RTUs other than Model A units are used, the
upper I/O numbering will be lower):
DIGITAL IN DIGITAL OUT ANALOG IN ANALOG OUT COUNTER
101..132 101..116 101..112 101..104 101..132
For a SECOND SCADAPack ES Remote I/O Unit with the same I/O capacity, the I/O numbering is as
follows:
DIGITAL IN DIGITAL OUT ANALOG IN ANALOG OUT COUNTER
201..232 201..216 201..212 201..204 201..232

4.2.3 User Points
User Point numbering is subject to the following rules:

DNP3 Binary Input and Binary Output objects access the same User RTU points, with common
DNP3 point numbers.
DNP3 Analog Input, Analog Output and Counter objects access the same User RTU analog points,
with common DNP3 point numbers.
Grouping of DNP3 objects for User points is subject to the rules of the DNP3 User Group’s Data
Object Library document, Section Binary Point Attributes 41 .
User Points are accessed according to DNP3 Object Groups as follows:
Object Groups 1,2, 10, 12 (binary input & output objects) access User Digital Points
Object Groups 20-23 (counter objects) and Groups 30-33 (analog input objects) and Groups 40,41
(analog output objects) access RTU User Analog Points
For SCADAPack ES RTUs, user point numbers start above the maximum local physical I/O point
number of the same primary point type, i.e. binary or analog, and need to be less than RTU System
Point numbers.
User points can be interleaved with remote physical points. On SCADAPack E RTUs other than
SCADAPack ES, User points may be also be interleaved with local Physical points.
User points exist only in the Main RTU of a Remote I/O system.
RTU User points need to be created in the RTU before they can be used. (i.e. by ISaGRAF applications,
peer communication, etc.). They can be initialized from an RTU configuration file or dynamically created
using Record Exchange (see Section Using Record Exchange to Add or Disable Points in the RTU
122 ).
User point configurations specify the type of User Point created. For example 16-bit integer, 32-bit
integer, or 32-bit floating point.
The size of a User Analog Point does not affect sequential DNP addresses of the same type. For
example, Analog point 10,000 could be configured as a 16-bit integer and Analog point 10,001 could be
configured as a 32-bit integer.
User numbering should be allocated to account for possible expansion of RTU I/O (e.g. 5000 Series I/O,
SCADAPack ES Remote I/O). For example, starting user points at 300 would allow for automatic
numbering of a Remote I/O system with a Main RTU + up to 2 additional Remote I/O units.
On power-up or RTU restart, User points retain their previous value.
4.3 RTU Start-Up & Configuration Revisions

RTU Start-Up
User points are created when an RTU Configuration is loaded to the RTU.
Current values for User and System points are stored in non-volatile memory in the RTU, and are
retained following RTU Restart, Power-up of the RTU, etc.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Evaluate the operational state of the equipment monitored and controlled by the
SCADAPack E RTU prior to initializing the SCADAPack E RTU.
Failure to follow these instructions can result in death, serious

injury or equipment damage.
The RTU will set Physical Analog Outputs (AO) to zero and de-energies Physical Digital Outputs (DO)
on power-up, RTU Restart on SCADAPack E Configurator Initialize Controller.
When an ISaGRAF User Application is started or restarted, the application can elect to have output
points on I/O boards hold on stop (stay in their current state).
Where hold on stop is not selected on an ISaGRAF output board, the ISaGRAF target kernel(s)
executing on the RTU sets user application output board points to the zero state before the first user
application cycle is executed. RTU physical output points ARE affected during this start-up process if
hold on stop is selected on an output board.
RTU Configuration Revisions

The SCADAPack E RTU provides a revision number tracking facility for RTU configurations.
The following rules are applied when configurations are changed. The RTU maintains the configuration
revision numbers is non-volatile RTU memory.
CONFIGURATION MAJOR REVISION NO.: System Analog Point 50050

CONFIGURATION MINOR REVISION NO.: System Analog Point 50051
The CONFIGURATION MAJOR REVISION NUMBER is updated under the following conditions:
When the RTU configuration is built, or re-built with a full configuration (.RTU file), the Major Revision
Number is incremented by 1
If the Major Revision Number is written via System Analog Point 50050.
The CONFIGURATION MINOR REVISION NUMBER is updated under the following conditions:
When the RTU configuration is built, or re-built with a full configuration (.RTU file), the Minor Revision
Number is reset to 0.
When the RTU configuration is updated with an incremental configuration (.INC file), the Minor
Revision Number is incremented by 1.
When a Record Exchange modification is made by a Master Station or SCADAPack E Configurator

to the RTU for Point record attributes or Trend records.
If the Minor Revision Number is written via System Analog Point 50051.
The Minor Revision Number is not incremented when the Master Station record exchange configurations
are individually made to the following point attribute fields.
Point Alarm Inhibit attribute
Point Trend Inhibit attribute
Point is Bad attribute
(SCADAPack E Configurator does not individually change attributes using Record Exchange (rather it
submits all attributes), so the Minor Revision Number is updated, regardless of which attributes are
modified.
For more information on Record Exchange see Section Point Database Access 93 .
4.4 Configurations Becoming Active

RTU hardware interface configuration changes take effect only after an RTU Restart has been performed.
This is a protection feature of the RTU to stop inadvertent reconfiguration of parameters (e.g.
communication baud rates) that would result in the RTU going off-line immediately, and being remotely
unrecoverable.
Physical RTU output states are not affected by the RTU performing the following operations:
Profiler Restart
Trend Sampler Restart
DNP driver Restart (DNP3 Warm Restart)
Configuration Restart
ISaGRAF application restart when hold on stop output board parameter is on.
Parameters affecting the RTU’s DNP3 protocol behavior take effect only after a DNP3 Warm Restart or
RTU Restart has been performed on the RTU, e.g. DNP link confirm modes, timeouts & retries,
application timeouts, etc. Typically SCADAPack E Configurator sends this when required, although
performing SCADAPack E configuration externally needs to take this into account.
RTU route table configuration may be changed dynamically, and changes take effect immediately.
Parameters affecting the RTU's IEC 60870-5 slave protocol behaviour (i.e. -101 and -104 protocols), take
effect only after an IEC 60870-5-101/104 Restart or RTU Restart has been performed.
SCADAPack E Configurator automatically restarts DNP3 and IEC 60870-5 drivers when required to
activate configurations.
4.4.1 Point Attributes and Properties Becoming Active & Configurations and ISaGRAF
Point Attributes and Properties Becoming Active

RTU points that have a configuration definition have Point Attributes and Point Properties. Attributes and
Properties are available to ISaGRAF user applications through ‘C’ Function Blocks.
Point attributes can be set through the following methods:
RTU Configuration File
point write Record Exchange (REX) system points
through ISaGRAF function blocks.
Point properties are read-only and presented through the following methods:
DNP status flags
point read Record Exchange (REX) system points
through ISaGRAF function blocks or I/O boards.
Configuration changes to Point Attributes through the point write record exchange are dynamic and take
effect immediately.
Configuration changes through RTU Configuration Files require a “CONFIG RESTART” to take effect.
SCADAPack E Configurator automatically applies configuration after downloading a new configuration.
Configurations and ISaGRAF

An SCADAPack E RTU may be reconfigured on-line while an ISaGRAF application is executing. The
following should be considered when the RTU undergoes a configuration restart.
For control integrity, execution of the ISaGRAF application may be delayed during the on-line RTU
re-configuration process.
An ISaGRAF application using point database read access function blocks: the function blocks may
return unsuccessful status codes during the on-line RTU re-configuration process. Function blocks
reading point database fields may not update their output variables. The user application should
handle function block status codes that indicate unsuccessful point database field access.
An ISaGRAF application using point database write access function blocks: the function blocks may
return unsuccessful status codes during the on-line RTU re-configuration process. Function blocks
writing data to point database fields may not update the requested fields. The user application
should handle function block status codes that indicate unsuccessful point database field access.
Function block status codes are further described in SCADAPack E ISaGRAF Technical Reference
manual.
4.5 SCADAPack E I/O Configurations

This section details the configuration for RTU I/O and 5000 Series I/O on the SCADAPack E RTUs (other
than for the SCADAPack ER).
There are 2 steps in configuring the SCADAPack E configurations, i.e.

Specifying Card Types for specific modules.
Mapping RTU configuration points to specific channels (in configured slots).
Details on these steps are defined in the SCADAPack E 5000 Series I/O Expansion Reference manual
and SCADAPack E Configurator User Manual
4.6 SCADAPack ER I/O Configurations

This section details the configuration that is specific to the SCADAPack ER RTU. The I/O Cards
supported by this RTU are listed in Table 4.1 26 .
Table 4.1: Supported SCADAPack ER I/O Cards
Hot Swap
Card Description Part Number Card Type
supported
32 Digital Inputs ER-32DI-A 32 (0x20) Yes
16 Relay Output ER-16DO-A 33 (0x21) Yes
16 Analog Inputs ER-16AI-A 34 (0x22) Yes
4 Analog Outputs ER-4AO-A 36 (0x24) Yes
There are 2 major stages in developing the SCADAPack ER configurations, i.e.

Specifying Card Types for specific slots.
Mapping RTU configuration points to specific channels (in configured slots).
The configuration file mnemonics for these SCADAPack ER I/O configurations are detailed in the
SCADAPack E Configuration File Format manual.
The SCADAPack ER I/O Card Configuration interface in SCADAPack E Configurator is shown in Figure
4.1 27 .
Figure 4.1: SCADAPack E Configurator - SCADAPack ER I/O Card Configuration
This interface allows the user to configure a specific card type in a given slot. The left hand grid
corresponds to the available slots. Clicking on a row that corresponds to a given slot will display a
column of entries on the right hand side. These entries correspond to the available channels on the
selected slot, whose quantity and types are dependant on the card type selected. The channel entry (on
the right hand side) allows a single RTU configuration point to be mapped to the specified channel (on
the selected slot), i.e. maps a single point (using DNP point number) to a single channel (1-1 mapping).
4.6.1 I/O Card Configuration & Applying I/O Configurations
I/O Card Configuration

A successful configuration requires that the necessary card types are configured in the appropriate
slots. The available cards are listed in a “drop-down” combo box in the left hand grid.
In order to configure a specific slot, click on the row (in the left hand grid) that corresponds to the
required slot. Then select the required card type from the list displayed in the drop-down box (e.g. ER-
16DO-A Relay Output). Observe that the right hand grid is now displayed with the quantity of channels
as implied by the card type (e.g. 16 digital output channels).
For example, the I/O card configurations displayed in the previous figure 27 can be summarized as
follows :
32 DI card (Card Type = 0x20) in Slot 1
16 RO card (Card Type = 0x21) in Slot 2
16 AI card (Card Type = 0x1E) in Slot 3
Applying SCADAPack ER I/O Configurations

The SCADAPack ER I/O configurations are specified in either a full (*.RTU) or incremental (*.INC) file.
These configurations may be applied in the RTU using SCADAPack E Configurator (Write RTU
Configuration command), or by executing the “restart config filename” at the RTU command line.
SCADAPack ER I/O Card Configurations (both I/O Cards and assigned point numbers) require a
COLD RESET of the SCADAPack ER for these configurations to take effect. The preferred
method of Cold Reset of the RTU is via a DNP3 Cold Reset command from SCADAPack E
Configurator or from a Master Station.
4.6.2 Assignment of DNP Points to Physical Channels
This section details how DNP point numbers may be assigned to physical channels. These points need
NOT to exist in the configuration database when assigning point numbers to physical channels on the
SCADAPack ER I/O page. They will be created as required as the configuration is constructed.
If points that are assigned already exist, the configuration point will not be modified, whereas newly
created configuration points will be created with default values.
Manual DNP Point Number Assignment

The previous section described the configuration of the slots with respect to card types. In the process of
doing this, the “User Interface” reflected this configuration by displaying the appropriate channels (in the
right hand column) for the configured slot. The DNP address of the mapped configuration point may be
entered in the right hand side (corresponding to a given channel). The physical channels may be
manually assigned DNP point numbers in this way. It is not necessary for each channel to be assigned
DNP configuration points if these channels are not to be used.
HINT! This is a fairly laborious approach to assigning point numbers to channel. The process can be
accelerated by using the ‘F9’ function key if the point numbers are to be contiguous for a given slot, i.e.
enter the DNP point number for the first channel, and the repeatedly press the ‘F9’ key to fill in the
subsequent channels with advancing point numbers.
Automatic DNP Point Number Assignment

In preference to manually assigning point numbers to channels, there is a also command line facility to
assist in developing initial SCADAPack ER I/O configurations. Two methods are provided for this:
Use SCADAPack E Configurator Get IO (No Num.) or Get IO (Auto Num.) buttons. For more
information see SCADAPack ER Physical I/O Numbering 15 .
Use the command line GETmagcfg command. This will generate an RTU configuration file according
to the detected I/O cards. Various point numbering schemes are available. Refer to the SCADAPack
E Operational Reference manual for more information regarding this command. The generated RTU
configuration file may then be loaded into SCADAPack E Configurator for further modifications.
5 Point Attributes
Point Attributes are read/write fields of point configurations describing (to the RTU) and potentially
controlling a characteristic of a point.
Configurable points in the RTU share a common set of point attributes. Individual point types have
unique point attributes in addition to the common point attributes.
Common Point Attribute Configurations 31
Binary Point Attributes 41
Analog Point Attributes 51

Counter Point Attributes 72
Trend Record Configuration & Profile Configuration 77
5.1 Common Point Attribute Configurations

These attributes describe common characteristics of each configured point in the RTU:
Attribute Description Attribute Value Comment
DNP point number 16-bit 0-65535
Point type Physical Input Point

Physical Output Point
User Point
System Point
Point data class Class 0 static Assigns DNP3 static

Class 1 Class 0 / Class 1 (e.g.
Class 2 alarm) / Class 2 (e.g
event) to SCADA master,
Class 3
Class 3 or Local non
Local SCADA master point
eg. Peer only point
Slot Channel Indicates physical channel Set by SCADAPack ER

on a given slot for I/O configuration. Only
SCADAPack ER only applicable to physical
point types on the
SCADAPack ER
hardware
Remote control enabled interlock DNP binary control point # Applicable to physical
for interlock point is an output and RTU user
attribute of control point. point configurations only.
(The interlock point needs
to be an input type, i.e. a
user binary point or a
physical input)
Interlock alarm timeout (secs) Remote control interlock RTU will generate an
point checked by the Data alarm on Interlock point
Processor (for Binary & (if appropriately
Analog controls). Setting configured) after this
the interlock point restarts period and every 10
the timer. minutes thereafter while
the Interlock point is set.
Point is Bad (Normal) – User attribute Settable attribute from Affects point “Point is
ISaGRAF User Failed” property, “Point
Application. Indicated via Quality” property & DNP3
DNP3 point status point status.
“Online” flag
Alarm Inhibit (Alarm Enable) Stops DNP driver from May be Alarm Inhibited /
generating events on the Enabled by ISaGRAF
point, and stops point’s application, SCADAPack
“Point is in Alarm” E Configurator or SCADA
property from being master

activated.
Trend Inhibit (Trend Enable) If this attribute is TRUE or May be Trend Inhibited /
the Trend Trigger point is Enabled by ISaGRAF
OFF, trend samples will application, The
not be collected for this SCADAPack E
point Configurator or SCADA
master
Profile ID ID of profile to perform Can set current value of

active control of this point Digital points, current
integer value of analog
points, current
engineering value of
analog points, 4L..4H
alarm & control limits for
analog points
IEC 870 – Information Object Address 16-bit 0-65535 Used only for IEC 60870-
(IOA) 5-101 & -104 Slave
configurations as a
unique identifier.
IEC 870 – ASDU Type 8-bit 0-255 Used only for IEC 60870-
5-101 -104 Slave
configurations to identify
how the point is to be
reference in IEC
communications.
Conitel Slave Type Various Conitel attributes Used only for Conitel
(SCADAPack ER - P620 only) (e.g. Conitel function, bit Slave configurations to
and frame position, etc) identify how the point is
to be reference in Conitel
communications.
5.1.1 DNP Point Number, Point Type & Data Class
DNP Point Number

The “DNP point number” attribute specifies the identifier for a point type, as described in Section
Methodology 13 . This attribute cannot be changed after creation. It is mandatory that this attribute be
defined for each point.
Point Type
This is an integer value, one of System, Physical Input, Physical Output or User type. User needs to
specify the type in the configuration file. Point type is readable by an ISaGRAF user application or the
SCADAPack E Configurator. The attribute cannot be changed after creation and it is mandatory that this
attribute is defined for each point.
Point Data Class

The “Point data class” attribute affects the way the data is reported externally from the RTU. If a point
configuration has a Point data class other than “Local”, changes will be reported to the SCADA Master
in the indicated DNP3 data class. As per DNP3 standard requirements, any data configured for Class
1,2,3 is also returned in response to a Class 0 poll request.
If a point configuration has a Point data class of “Local” it is not available to the SCADA Master through
the Class 0,1,2,3 mechanisms. Points so configured would be accessible to a peer DNP3 node, an
ISaGRAF user application and the SCADAPack E Configurator application.
RTU System Points are only reported to the SCADA Master through Class 0,1,2,3 mechanisms if the
user configures appropriate attributes for the system point in a configuration record. Only selected
groups of RTU system points may be assigned a configuration record by the user. System point current
values (for any system point), may be accessed by an ISaGRAF user application, the SCADAPack E
Configurator and Peer RTUs without point database configuration entries.
The SCADAPack E RTUs support DNP Multi-Master operation. The “Point Data Class” common point
attribute has been extended to make it configurable on a per-Master basis. This allows the RTU to
present a different “view” of its non-local points to different DNP Masters. This feature has applications in
local HMI situations or for RTUs being used for custody transfer. The SCADAPack E RTU allow for three
DNP Masters.
User points and remote I/O unit physical points are not accessible without point database configuration
entries.
Valid DNP3 Point data class values are:
Local
Class 0 (Static)
Class 1
Class 2
Class 3
This attribute may be changed after point creation, and events reported via DNP3 will use the modified
point attribute.
The default value for this attribute is “Local”.
“Local” data class points are not returned in response to a DNP3 Class 0 poll request, and DNP events
are not generated. They may be read by a Master using specific DNP3 point index reads, are available
to peer nodes via DNP3 requests for specific point index data, or the local ISaGRAF user application.
A point configuration set as Class 1,2 or 3 Events also returns a static data object in response to a
DNP3 Class 0 poll request, and allows the point to generate events in the selected event class.
Static data object formats are determined by the point’s “DNP Object Type” attribute. Event data object
format is determined by the global DNP3 Event Configuration. See SCADAPack E DNP3 Technical
Reference.
RTU point values are available for Peer RTU access. This includes physical and system points as well
as configured user points.
5.1.2 Slot Channel
Slot Channel
This attribute is only applicable to SCADAPack ER physical points.
It is required to associate the given configuration point (and therefore its DNP point number) with a
physical I/O channel on a SCADAPack ER I/O card.
Remote physical points (i.e. physical point types mapped to remote I/O RTUs) do not have the Slot
Channel attribute.
5.1.3 Control Interlocks
The purpose of control interlocks is to arbitrate control of physical output points and user RTU points
(digital and analog) between an ISaGRAF user application, and remote DNP3 control requests.
The “Remote control interlock” attribute of a point associates a separate RTU binary point with a point to
be controlled. Remote Control Interlock points can be associated with Physical Digital Output points,
Physical Analog Output points, user Digital points and user Analog points. The remote control interlock
point itself may be a Physical Digital Input point or a user Digital point.
If the Remote Control Interlock point value is zero, then there will be no interlock on the controlled point.
Where a DNP3 control request is received for a point without a defined control interlock point, and the
point is not on an ISaGRAF output board, the point will be controlled successfully. Where a DNP3
control request is received for a point without a control interlock point, and the controlled point is on an
ISaGRAF output board, the DNP3 control will be rejected, as detailed above.
Where an interlock point is specified, the “Remote Interlock Point” can be controlled externally via
DNP3.
When the interlock point is inactive (OFF) and the controlled point is on an ISaGRAF Output Board,
external DNP3 control requests for the physical output point will be rejected. Controls asserted through
an ISaGRAF application Output Board control the physical output point. When the interlock point is
active (ON), external DNP3 control of the physical output point is allowed, and controls through an
ISaGRAF Output board will be ignored.
As the Interlock Point is writeable, either external DNP3 requests or an ISaGRAF application may
control its state. ISaGRAF control of the interlock point requires a specific function block call e.g.
WR1BIN to Local_Data. If potentially controlled from an ISaGRAF application and DNP3, the interlock
point should not be on an ISaGRAF output board, otherwise it will itself require an interlock point to
arbitrate access.
For example, user defined analog point 1000 is controlled via a user application variable attached to an
ISaGRAF Analog Output Board. Analog point 1000 has an associated Remote Control Interlock user
digital point 1107. If digital point 1107 is activated, changes to the ISaGRAF variable will no longer
control analog point 1000. Instead, DNP3 controls may be sent to analog point 1000 to change its
value.
As the Interlock Point is writeable, either external DNP3 requests or an ISaGRAF application may
control its state. ISaGRAF control of the interlock point requires a specific function block call e.g.
WR1BIN to Local_Data. If potentially controlled from an ISaGRAF application and DNP3, the interlock
point should not be on an ISaGRAF output board, otherwise it will itself require an interlock point to
arbitrate access.
When the interlock point is deactivated (OFF) via a DNP3 control, the Data Processor updates the state
of the interlock in the point database, and clears the “Output point remote control interlock active”
property. Internally, however, the interlock release is delayed by 2 seconds. This is to allow running
ISaGRAF user applications to see the change in the interlock point state (or interlock property) and
adjust the output board variable, if necessary, prior to the Data Processor reverting point control back to
the ISaGRAF output board.
The acceptable range of this attribute is a value in the range 1-49999, and needs to be a configured RTU
binary point. The default attribute value is zero (no interlock point).
5.1.4 Interlock Alarm Timeout & Point is Bad
Interlock Alarm Timeout

The RTU’s Data Processor tracks the period of time that the Interlock binary point is in an Active (ON)
state.
Each time the Interlock point is set ON, the timer is restarted. If the timer period exceeds the value of
the “Interlock alarm timeout (secs)” attribute, the Data Processor generates a DNP event on the Interlock
user binary point if the Interlock point has an event class configuration.
The DNP binary change event generated will contain the current state of the Interlock point (ON). The
DNP event will be regenerated every 10 mins whilst the Interlock point is still active (ON).
When the Interlock point is deactivated (OFF), the 10 min and “Interlock alarm timeout” timers are
cleared and a change event will be generated for the Interlock point (with point state OFF).
Valid attribute values are in the range 0-32767 secs. Default is zero (no interlock alarm timeout).
Point is Bad
The “Point is bad” attribute is controlled by an ISaGRAF user application.
This attribute has one of two values: TRUE or FALSE. Its purpose is to enable an application to signal
that a point is not behaving correctly.
If an application sets this point to TRUE, the Data Processor will set the “Point is failed “ property to
TRUE and the “Point Quality reason” property to “Point is Bad”.
Also see Section Point is Failed 82 . If the “Point is Failed “ property is active, DNP will clear the “On-
line” status flag for the DNP point to indicate “Off-line”.
5.1.5 Alarm & Trend Inhibit & Profile ID
Alarm Inhibit
This attribute is to allow an ISaGRAF user application or SCADAPack E Configurator to inhibit the RTU
collecting and reporting DNP events on a point-by-point basis.
This attribute has one of two values: TRUE or FALSE. If the point attribute is TRUE, events are inhibited
and the “Point is in Alarm” property is not activated. ISaGRAF reads of the “Point is in Alarm” property
will indicate FALSE. The default attribute value is FALSE.
The SCADA Master can reconfigure this attribute by transferring a new full or incremental RTU
configuration file, or by using the RTU attribute modification facility.
* If the DNP3 event has been forced using the GEN_EVT or GENMSEVT ISaGRAF function blocks, the
state of the Alarm Inhibit attribute is not tested, i.e. the DNP3 event is generated irrespective of the state
of the Alarm Inhibit attribute.
The Alarm Inhibit attribute is not used for physical output points.
Trend Inhibit
This attribute is to allow an ISaGRAF user application or SCADAPack E Configurator to inhibit the RTU
collecting trends on a point-by-point basis.
This attribute has one of two values: TRUE or FALSE. If the point attribute is TRUE, trending is
inhibited. The default attribute value is FALSE.
The SCADA Master can reconfigure this attribute by transferring a new RTU configuration file, or by
using the RTU attribute modification facility.
Profile ID
This attribute is specified in the configuration file. This attribute has valid values 1 to 999. Default value
is zero (indicates no profile is active for the point).
This attribute associates the point with a control profile. The association is by way of the Profile file’s
name, which contains the profile ID.
The Profile file contains information required to control the point. i.e. timing, attributes of point to control,
values of attributes, etc.
This attribute may be modified by ISaGRAF to allow user application changes to profile operation.
Requires RTUPARAM function block call to restart Profiler task. This attribute may be modified by the
SCADAPack E Configurator.
Following a profile parameter change, the user can issue a SCADAPack E Configurator “Restart Profiler”
command. See SCADAPack E Configurator Commands / Restart Services / Restart Profiler
For more information see the SCADAPack E Profiler Technical Reference manual.
5.1.6 IEC 60870 - IOA & ASDU Type
IEC 60870 - IOA (Information Object Address)

This attribute is applicable for RTUs using IEC 60870-5-101 Slave or IEC 60870-5-104 Slave
communications.
The IOA attribute defines a 16-bit field that has valid values in the range of 0 to 65535.
The IOA attribute allows a given configuration point to be uniquely identified in IEC 60870-5-101 and IEC
60870-5-104 slave protocol communications.
For more information (including default values) see the SCADAPack E IEC 60870-5-101 Slave Technical
Reference manual.
IEC 60870 - ASDU (Application Service Data Unit) Type

communications.
The ASDU Type attribute defines an 8-bit field that has valid values in the range of 0 to 255.
The ASDU Type attribute allows a given configuration point to be assigned a IEC 60870-5 point type in
IEC 60870-5-101 or IEC 60870-5-104 slave protocol communications.
For more information (including default values) see the SCADAPack E IEC 60870-5-101 / 104 Slave
Technical Reference manual.
5.1.7 Conitel Slave Type
Conitel Slave Type

This attribute is only relevant for the SCADAPack ER - P620 RTUs licensed for Conitel Slave
communication.
The Conitel Slave Type defines 7 fields that describe various Conitel mapping attributes for the point.
For more information (including default values) see the SCADAPack ER Conitel Slave Reference
manual.
5.2 Binary Point Attributes

The following diagrams indicate active attributes for Physical Input Binary Points, Physical Output Binary
Points and User (derived) Binary Points.
Figure 5.1: Physical Binary Input Point Attributes

Figure 5.2: Physical Binary Output Point Attributes

Figure 5.3: User (Derived) Binary Point Attributes
Except where noted, the following attributes apply to physical binary input points, physical binary output
points, user binary points and configurable system binary points.
See common attributes above.
DNP object type DNP3 binary static objects
Unsolicited Trigger attribute Allows events on this point to

trigger a DNP3 unsolicited
transmission
Alarm Active State Indicates which current Alarm active state refers to
value state is the alarm post inverted current state
state
Time dead band before alarm or event is Data Processor function

generated (secs)
Time dead band before alarm is returned Data Processor function

to normal (secs)
Output pulse time (ms) Pre-configured pulse time

for ISaGRAF “RTUPULSE”
function
Invert point state I/O sub-system function Valid for Physical Digital Input
points only. Only available
where provided by hardware.
Not supported for
SCADAPack 300E RTUs or
5000 Series I/O
Debounce time (ms) I/O sub-system function. Valid for Physical Digital Input
Period of time a raw digital points only. Only available
input needs to remain in a where provided by hardware.
new state before being Not supported for
reported as a state SCADAPack 300E RTUs or
change 5000 Series I/O
Output pulse time (ms) Pre-configured pulse time Not Valid for Physical Digital
for ISaGRAF “RTUPULSE” Input points.
function. Also used if zero
pulse time specified in
DNP3 CROB.
Trip Close Partner Point Allows for complementary Not Valid for Physical Digital
control functions on a Input points.
single DNP index.
Drop Output on Interlock Active Optionally drops a Digital Not Valid for Physical Digital
Output point when its Input points..
Interlock becomes active.
5.2.1 DNP Object Type
DNP Object Type

This attribute is set in the configuration file and describes the data object returned in response to a
DNP3 static data poll request (i.e. Class 0 request). It is mandatory that this attribute is defined for
each digital point. One of the following types is valid:
Group Var Description

1 1 Binary Input
1 2 Binary Input Status
10 2 Binary Output Status
5.2.2 Alarm Active & Invert Point State & Unsolicited
Alarm Active State

The “Alarm Active State” indicates which value of “Current Point State” is considered to be an alarm
condition. If “Alarm Active State” is TRUE, the “Current Point State” TRUE is the alarm state. If “Alarm
Active State” is FALSE, the “Current Point State” FALSE is the alarm state.
Invert Point State

“Invert Point State” attribute is set in the configuration file and is valid for Physical Input Points only. It
has two states, TRUE and FALSE, and is used by the I/O sub-system. If the attribute is FALSE, the
“Current Point State” property is the same as the “Raw Input State” as long as the Raw Input State
remains the same for the debounce time. If “Invert Point State” attribute is TRUE, the “Current Point
State” property is the inverse of the “Raw Input State”. Default value is FALSE (no inversion).
Only available where provided by hardware.
Not supported for SCADAPack 300E RTUs or 5000 Series I/O.
Unsolicited
The "Unsolicited" attribute determines the behavior of events generated from an individual binary point.
A DNP3 unsolicited transmission will occur upon a change in a point state when the following conditions
are met:
Unsolicited attribute is enabled
Point's Data Class is selected for Class 1, Class 2 or Class 3
The selected DNP3 Class has been enabled for Unsolicited transmission. This is typically set by a
Master Station during DNP3 communications startup with the RTU.
The internal attribute naming (e.g. for attribute interfaces through ISaGRAF function blocks, Record
Exchange, etc) refers to "TRIGGERED", while the attribute naming provided to the user through
SCADAPack E Configurator is "UNSOLICITED".
5.2.3 Time Deadband Into & Out of Alarm
Time Deadband Into Alarm

“Time Deadband Into Alarm” attribute is set in the configuration file and sets a delay before the “Point is
in Alarm” property becomes TRUE after the alarm is determined to be active (i.e. Delays the transition
from point Normal to Alarm state). The range of values for this attribute is 0-32767 secs. A value of zero
disables the time deadband in to alarm. Default value is zero.
Time Deadband Out of Alarm

“Time Deadband Out of Alarm” attribute is set in the configuration file and sets a delay before the “Point
is in Alarm” property becomes FALSE after the alarm is determined to be inactive (i.e. Delays the
transition from point Alarm to Normal state). The range of values for this attribute is 0-32767 secs. A
value of zero disables the time deadband out of alarm. Default value is zero.
5.2.4 De-bounce Time & Drop Output on Interlock Active
De-bounce Time
“De-bounce Time” attribute is set in the configuration file and is valid for Physical Input Points only. It has
valid values 0-2500 ms, and is used by the I/O sub-system to de-bounce changes in physical digital
input points. If the state of the physical input changes, it needs to remain in the new state for the “De-
bounce Time” before it is reported as having changed. The change in the point will be ignored if a
transition back to the original state occurs during the de-bounce time. Default value is zero (no de-
bounce). The “De-bounce Time” is also applied to counters on the digital input point. For more
information see Section Counter Point Properties 91 (Counter Current Value) 91 . The Timestamp
applied to the changing digital input is the time when the point initially changes value, as illustrated in
Figure 3.2.4.
Figure 5.4: Debounce Timestamping
Only available where provided by hardware.

Not supported for SCADAPack 300E RTUs or 5000 Series I/O.
Drop Output on Interlock Active

The “Drop Output on Interlock Active” attribute is only valid for Digital Output point types.
In previous firmware versions, when an Output point had its interlock enabled, the RTU would hold
whatever value the output point had immediately prior to the interlock being enabled. In certain
situations, this can be risky as the point was under ISaGRAF control prior to the interlock being
activated. Therefore the RTU firmware has the ability to conditionally set a digital output’s Current State
to “OFF” when it’s interlock transitions to the “ON” state. The Digital Output point needs to be under
“ISaGRAF Control”, otherwise the interlock point and this attribute will have no effect.
The default state of this attribute is “OFF”, i.e. the same as the previous RTU behavior.
5.2.5 Output Pulse Time
The “Output Pulse Time” attribute can be used by ISaGRAF for control of pulsed physical output points.
A new ISaGRAF function block “RTUPULSE” takes a pulse time input that may use this attribute. If a
zero pulse time is specified as the pulse time input to the function block, this attribute will be used as
the pulse time. The ISaGRAF function will return an error if the pulse request cannot be executed, or if
the digital output point has a remote interlock set. To latch a point from an ISaGRAF application, use a
Boolean output board.
The ISaGRAF “RTUPULSE” function block causes the RTU to control digital outputs in a similar fashion
to the DNP3 CROB object. The main differences are:
The pulse duration time is specified by the ISaGRAF application, or is preset by this point attribute if
ISaGRAF specifies a time of zero. If both the ISaGRAF specified time and the “output pulse time”
point attribute are zero, a minimum value of 10ms is used.
Only a single pulse is generated.
Default value of this attribute is zero (no ISaGRAF output pulse).
When a DNP3 CROB pulse request is received by the RTU, the pulse details contained in the CROB are
used to control the digital output. I.e. The pulse on time, pulse off time and count supplied with the
CROB request are used to control the digital output. If CROB parameters are zero, the following defaults
are applied:
CROB Parameter Occurring when … Result
On-time >= 10ms On-time = CROB On-time
On-time = 0 Output Pulse Time attribute >= 10ms On-time = Output Pulse Time
On-time = 0 Output Pulse Time attribute < 10ms On-time = 10ms
On-time < 10ms On-time = 10ms
Off-time >= 10ms Count > 1 Off-time = CROB Off-time
Off-time < 10ms Count > 1 Off-time = 10ms
Count = 0 No pulse action carried out.

Response to CROB request
indicates success.
5.2.6 Trip Close Partner Point
The “Trip Close Partner Point” attribute may be used to support complementary control functions for
Control Relay Output Block controls (CROB) on a single DNP3 index. It is valid for binary point types
except Physical Digital Inputs, and is only supported in firmware versions 7.4-2 and later.
This attribute effectively connects 2 binary output points as TRIP CLOSE partner points, where the lower
point number is identified as the TRIP point, and the higher point number is identified as the CLOSE
point. Consider the following example for a SCADAPack ER RTU.
Physical Binary Output 101 maps to Slot 1 Channel 1 on the SCADAPack ER rack.
Physical Binary Output 102 maps to Slot 1 Channel 2 on the SCADAPack ER rack.
Physical Binary Output 101 has a TRIP CLOSE partner point attribute value of 102
Physical Binary Output 102 has a TRIP CLOSE partner point attribute value of 101
A TRIP/PULSE ON request for DNP3 index 101 maps to Physical DO 101 (Slot Channel 1). A CLOSE/
PULSE ON request for DNP3 index 101 maps to Physical DO 102 (Slot Channel 2).
The TRIP/PULSE ON requests for DNP3 index 102 map to Physical DO 101 (Slot Channel 1), and
CLOSE/PULSE ON requests for DNP3 index 102 map to Physical DO 102 (Slot Channel 2).
It only necessary to define a 1-way mapping when creating these configurations as the SCADAPack E
firmware will automatically update the reverse mapping when the configuration is processed in the RTU
(immediately for Record Exchange), e.g. using the example above, it is only necessary to set the “Trip
Close Partner Point” for Physical Binary Output 101 to be 102. The “Trip Close Partner Point” attribute
for Physical Binary Output 102 will be updated to 101 when the configuration is processed by the RTU.
The Trip Close Partner Point needs to exist in the point database for a valid configuration, i.e. the partner
point is NOT automatically created by the RTU. If a configuration error is detected regarding Trip Close
Partner Points, the system error code is updated with the value 3001
(CONFIG_TRIP_CLOSE_ERROR).
Refer to the SCADAPack E Operational Reference manual for more information regarding system error
codes.
This attribute is valid for binary point types except physical digital inputs, and the default value for this
attribute is 65535, which represents an invalid Trip Close partner point.
5.3 Analog Point Attributes

The following diagrams indicate active attributes for Physical Input Analog Points, Physical Output
Analog Points and User (derived) Analog Points.
Figure 5.5: Physical Analog Input Point Attributes

Figure 5.6: Physical Analog Output Point Attributes

Figure 5.7: User (Derived) Analog Point Attributes

Except where noted, the following attributes apply to physical analog input points, physical analog
output points, user analog points and configurable system analog points.
See Common Point Attribute

Configurations 31 above
DNP object type DNP3 static analog objects
4 High Engineering Limits * Data Processor function [floats]

(1H, 2H, 3H, 4H) Profiler / ISaGRAF may set
attributes
4 Low Engineering Limits * Data Processor function [floats]

(1L, 2L, 3L, 4L) Profiler / ISaGRAF may set
attributes
Unsolicited Alarm Limit Events Unsol. Trigger enable allows selection of individual
alarm limit events to trigger a
DNP3 unsolicited transmission
Integer to Engineering Value Data Processor function MIN_RAW [integer]

conversion MAX_RAW [integer]
MIN_ENG [float]
MAX_ENG [float]
Over-range limit * Data Processor function to [float]

derive over-range status
Under-range limit * Data Processor function to [float]

derive under-range status
Rate of Rise value (%) * Data Processor function to % of MAX-MIN range [float]
derive “Exceeded Rate of
Rise” status
Rate of Fall value (%) * Data Processor function to % of MAX-MIN range [float]
derive “Exceeded Rate of
Fall” status
Rate of Change Period (secs) * [integer]
No Change value (%) * Data Processor function to % of MAX-MIN range [float]

derive “No Change” status
No Change Time (secs) * [integer]
Rate of Rise Exceeded property DNP3 0 = no-point Point number

binary point number * Valid User Point Number = If non-zero it needs to be unique
pointer to associated & not used for any other
binary point for Rate of purpose
Rise Exceeded property [integer]
Rate of Fall Exceeded property DNP3 0 = no-point Point number

binary point number * Valid User Point Number = If non-zero it needs to be unique
pointer to associated & not used for any other
binary point for Rate of Fall purpose
Exceeded property [integer]
No Change property DNP3 binary point 0 = no-point Point number

number * Valid User Point Number = If non-zero must be unique &
pointer to associated not used for any other purpose
binary point for No Change [integer]
property
Time dead band before event or alarm is Data Processor function [integer]
generated (secs) * (affects Hi/Lo flags)
Time dead band before alarm is cleared Data Processor function [integer]
(secs) * (affects Hi/Lo, OR/UR
flags)
Value dead band before event or alarm Data Processor function Engineering units [float]
is cleared * (affects Hi/Lo flags) Value above 1L-4L to clear &
below 1H-4H to clear
Zero Threshold Limit * Data Processor function [float]

Clamps values below zero
threshold limit to 0.0
Limit Transgression – DNP Event 8 Binary Attributes for 4L- Selects which alarm limits
enabled * 4H limits generate a DNP event when
transgressed
Change deviation for Event (%) * Significant analog change [float]

for DNP event generation
IEC 60870 Enable Cyclic Scan Used to indicate that the Used only for IEC 60870-5-101
analog point is to be Slave configurations
included in IEC 60870-5-
101 cyclic responses
Event Deviation Type Selects the value deviation Enumerated Type

deadband algorithm for the
point.
* Not applicable to physical analog outputs.

5.3.1 DNP3 Static Object Type
DNP3 Object Type

DNP3 static data poll request (i.e. Class 0 data). It is mandatory that this attribute is defined for each
analog point. One of the following types is valid:

30 1 32-bit Analog Input
30 2 16-bit Analog Input
30 3 32-bit Analog Input No Flag
30 4 16-bit Analog Input No Flag
30 5 Short Floating Point Analog Input -
Engineering Value
20 1 32-bit Counter Input
20 5 32-bit Counter Input No Flag
40 1 32-bit Analog Output Status
40 2 16-bit Analog Output Status
40 3 Short Floating Point Analog Output Status -
Engineering Value
5.3.2 Point Properties DNP Binary Points
Point Properties DNP Binary Points

Point properties that cannot be returned via standard DNP3 object status flags are mapped into the
RTU’s DNP3 User Binary points address space. The following analog point properties may be optionally
associated with DNP3 binary points:
Rate of RISE Exceeded
Rate of FALL Exceeded
No Change
A separate point attribute for each of these properties configures the associated binary point for the
property. Binary points may be individually configured for none, all, or any combination of the properties.
Binary points for two or more of these properties need not necessarily be contiguous. If the binary point
specified for a property is a user point, a separate point configuration should exist in the configuration file
for that binary point.
Further details including descriptions of system points that configure the operation of the SCADAPack E
RTU’s Rate of Rise, Fall and No Change are provided in the SCADAPack E Data Processing Technical
Reference manual.
5.3.3 Engineering Limits & Unsolicited Alarm Limit Events
Engineering Limits
There are a total of 8 engineering limit attributes for each analog point. Configuration of these alarm
limits in the analog point configuration is optional. Engineering limit attributes are floating point values,
and are compared with the Analog point’s Current Engineering Value property.
These attributes may be specified in the point configuration file, or may be changed at run-time from the
Profiler, ISaGRAF user application, or SCADAPack E Configurator.
These attributes are used to determine the state of the 8 limit transgressed properties of the analog
point. The criteria for operation of the engineering limits, takes account of value and time dead-banding
for each limit. The fundamental processing of the engineering limits, i.e. what determines an alarm
condition is detailed in the SCADAPack E Data Processing Technical Reference manual.
The 8 alarm limits are divided into two sets of 4 (i.e. 4 low alarm limits and 4 high alarm limits). They are
named 4L, 3L, 2L, 1L, 1H, 2H, 3H, 4H. There is no restriction on which alarm limits can be used,
however they must be configured such that the values of the limits are as follows: 4L <= 3L <= 2L <= 1L
<= 1H <= 2H <= 3H <= 4H
For more information with respect to the impact of deadbands on these engineering limits, refer to the
Time & Value deadband attributes.
Unsolicited Alarm Limit Events

Each of the eight Analog point alarm limits has an associated "Unsol." unsolicited attribute. In addition
to each of the eight analog point Alarm Limits, Point Quality change events and Current Value deviation
events can be individually assigned to generate either “Buffered” DNP event types or "Triggered"
Unsolicited events (providing the event class for the point has unsolicited reporting enabled by the
Master Station).
This feature has advantages for RTU’s using dial-up or on “pay-per-byte” links where the user wants to
minimize unsolicited reporting and hence communications costs. For example, an RTU may be
configured to Buffer Current Value events, but to send Unsolicited events if an Analog alarm limit is
transgressed.
RTU data points configured as events have one of two event attributes:
The occurrence of an event with a BUFFERED attribute is added to the internal event list. No direct
action is taken by the RTU after the event is added to the list unless the new event causes an event
list size to exceed the transmission limit for an unsolicited event class.
The occurrence of an event with an UNSOLICITED attribute is also added to the internal event list,
but causes the RTU to generate an unsolicited transmission containing the events currently on the
event list, provided that the event class in enabled for Unsolicited transmission. (This is typically set
by Master Station as part of the DNP3 startup communications with the RTU). The unsolicited
message is generated after the configurable Event Notification Delay.
SCADAPack E Configurator is "UNSOL." or "UNSOLICITED".
5.3.4 Integer to Engineering Conversion & Rate of Rise and Fall
Integer to Engineering Conversion

Four attributes of an analog point define the conversion between Integer and Engineering (floating point)
value point properties. The same attributes are also used to convert from Engineering to Integer value
point properties. It is mandatory for these parameters to be specified in the point configuration.
Modification of these attributes takes effect upon the next database write to either the Current Integer
value or Current Engineering value . The following range checking is performed on these attributes:
RAW_MAX > RAW_MIN, ENG_MAX > ENG_MIN. Invalid parameters will result in the analog point not
being configured.
Integer to Engineering value conversions and Engineering to Integer value conversions are performed by
the RTU, and further described in the SCADAPack E Data Processing Technical Reference manual.
Rate of Rise and Fall

The Data Processor determines if an analog point value is rising or falling too rapidly.
Three attributes are used to determine if a rate of rise or fall has been exceeded for an analog point:
Rate-of-Rise-%
Rate-of-Fall-%
Rate-of-Change Period (secs)
The Data Processor compares the value of the analog’s Current Value now, with its value at the specified
time period, previously, and calculates the rate of change accordingly. The rate of rise and rate of fall
calculation is evaluated every time that the current value of the analog point changes.
The % specified in the attributes is a % of the analog point’s full scale range defined between Eng-Min
and Eng-Max limits.
If the rate of rise is exceeded, the analog point’s Rate-Of-Rise Exceeded property is set TRUE. The
property is set FALSE when the analog point changes resulting in a rate of rise not exceeding the limit.
It is also cleared if the Rate-Of-Fall property is set.
If the rate of fall is exceeded, the analog point’s Rate-Of-Fall Exceeded property is set TRUE. The
property is set FALSE when the analog point changes resulting in a rate of fall not exceeding the limit.
It is also cleared if the Rate-Of-Rise property is set.
When the rate of rise or fall is exceeded, the start time for the period is reset so that rapid changes in
point value within the time period are detected, and that rapid transitions from rate of rise exceed to rate
of fall exceeded are detected.
Default attribute values are Rate-of-Rise 100%, Rate-of-Fall 100%, Rate-of-Change Period 0 (indicating
disabled Rate of Rise/Fall checking).
5.3.5 Over-range and Under-range Limits & IEC 870 - Cyclic Scan
Over-range and Under-range Limits

These two floating point attributes are compared against the point’s Current Engineering Value property
to determine the state of the over range and under range properties respectively. Refer to the
SCADAPack E Data Processing Technical Reference manual for detailed information on the criteria for
determination of over range and under range conditions
Default value of Over-range attribute is +3.40282e+038 (FLOAT_MAX).
Default value of Under-range attribute is -3.40282e+038 (-FLOAT_MAX).
IEC 870 - Cyclic Scan

communications.
The Cyclic Scan attribute identifies the analog point to be included in IEC 60870-5 Cyclic responses.
Default value of this attribute is OFF.
For more information see the SCADAPack E IEC 60870-5-101 / 104 Slave Technical Reference manual.
5.3.6 No Change & Value Deadband Out of Alarm
No Change
The Data Processor determines if an analog point value is not changing fast enough.
Two attributes are used to determine if the rate of change is too small (i.e. No significant change) for an
analog point:
No-Change-Value-%
No-Change-Period
The Data Processor compares the value of the analog’s engineering value now, with its value at the
specified time period, previously, and calculates the rate of change accordingly. The rate of change
calculation is evaluated every time that the current value of the analog point changes.
The % specified in the attribute is a % of the analog point’s full scale range defined between Eng-Min
and Eng-Max limits.
If the analog is not significantly changing, the analog point’s No-Change property is set TRUE. The
property is set FALSE when the analog point changes resulting in a rate of change exceeding the No-
Change-Value % attribute.
Default attribute values are No-Change-Value 0%, No-Change Period 0 (indicating disabled No-change
detection)
Value Deadband Out of Alarm

When an alarm limit has been transgressed, a point’s value needs to return to within the limit and the
deadband before it is cleared, thus avoiding the generation of excessive alarms when a value is
fluctuating around an alarm limit. A single value deadband may be specified as a floating-point number
that operates on all eight of the point’s limits. It is subtracted from the High limits and added to the Low
limits. For example, if a point’s value exceeds the 1H limit, the point’s 1H Analog limit transgressed
property would be set TRUE. The state of this property would only return to FALSE if the point’s value
returns to below the 1H limit minus the value deadband. Default value is 0.0 (no value deadband).
Maximum value is ENG-MAX, minimum value is ENG-MIN. The value deadband does not apply to the
over range and under range limits.
5.3.7 Time Deadband Into & Out of Alarm
Time Deadband Into Alarm

This attribute represents the time in seconds that the value of a point needs to be in an alarm condition
(for one of the eight point limits) before the appropriate Analog limit transgressed property would be set
TRUE. The default value is zero (no time dead-band). Maximum value is 32767 seconds and the
minimum value is zero seconds. The “time deadband into alarm” does not apply to the over range and
under range limits.
Time Deadband Out of Alarm

After the Analog limit transgressed, over range or under range property is set TRUE, the value of an
analog point must be in a non-alarm range for the time of the dead-band out-of-alarm period, before the
appropriate Analog property is returned to the FALSE state. (i.e. The analog must return back below a
high limit minus out-of-alarm value dead-band*, or back above the low limit plus out-of alarm value dead-
band*). This time dead-band applies to the eight engineering, over range and under range limits, though
when applied to the over range and under range limits, the actual time deadband value applied is 1/10th
of the analog point’s configuration value. This attribute is measured in seconds. Default value is zero
(no time dead-band). Maximum value is 32767 seconds and the minimum value is zero seconds.
*The value deadband does not apply to the over range and under range limits.
5.3.8 Zero Threshold Limit
Zero Threshold Limit

This attribute is used to clamp analog engineering values below this limit to 0.0. This attribute is
applicable to analog point types except Physical Analog Output points. The default of this attribute is -
3.40282e+038 (no zero threshold).
Significant Change Deviation

The purpose of this attribute is to detect changes in an analog point’s current value. A significant
change exceed the deviation % specified in this attribute causes a DNP event to be generated, subject
to the alarm inhibit attribute being FALSE, and the point being configured in a DNP event class.
The % specified in this attribute is a % of the analog point’s full scale range defined between Eng-Min
and Eng-Max limits.
Default value of this attribute is 100% (resulting in no significant change deviation events).
5.3.9 Limit Transgression - DNP Event Enable
This attribute indicates which combination of the 8 alarm limits will be used to generate a DNP event.
Individual Limit Transgression enables are represented as bits within this integer attribute. I.e. This
attribute is a bit-mask, where a bit ON indicates the limit transgression DNP event is enabled.
Alarm Limit Attribute value (hex)
4L 0x1
3L 0x2
2L 0x4
1L 0x8
1H 0x10
2H 0x20
3H 0x40
4H 0x80
5.3.10 Event Deviation & Event Deviation Type
Event Deviation value

The purpose of this attribute is to detect changes in an analog point’s current value. A significant
change exceed the deviation value (floating point) specified in this attribute causes a DNP3 event to be
generated, subject to the alarm inhibit attribute being FALSE, and the point being configured in a DNP3
event class.
The interpretation of the value in this field depends upon the selection of the Event Deviation Type 71
field.
Default value of this attribute is 100% (resulting in no significant change deviation events) assuming the
Event Deviation Type 71 field is set to the default Percentage of Span setting.
Event Deviation Type

This attribute allows the value dead-band algorithm to be configured on a per-point basis. It was
introduced with firmware versions 7.76 and later. This attribute is applicable to analog point types except
Analog Output points.
The Event Deviation Type attribute is an enumerated value with the following values:
Percentage of = 0 (This is the default method)

Span
Absolute = 1
Integration = 2
None = 3
For more information on Event Deviation Type, see the SCADAPack E Data Processing Technical
Reference.
Method: Percentage of Span
This dead-band method allows for the deviation to be specified as a percentage of the point range. The
configuration of the Event Deviation Type defaults to this setting. An Event Deviation Value 71 set at
100% in an RTU configuration will be equivalent to setting the Event Deviation Type to None.
If the DNP3 Static Object Type 62 of the point is set to a floating point (AI group 30 variation 5 or AO
group 40 variation 3) then the Event Deviation Value 71 will be interpreted as a % of the analog point’s
full scale range defined between Eng-Min and Eng-Max limits. Otherwise, the percentage span deviation
will apply to the Integer range of the point, defined between Raw-Min and Raw-Max limits.
Method: Absolute
This method allows for a fixed value deviation. If the DNP3 Static Object Type 62 of the point is set to a
floating point (AI group 30 variation 5 or AO group 40 variation 3) then the absolute value deviation will
apply to the Engineering value of the point. Otherwise, the absolute value deviation will apply to the Raw
value of the point.
Method: Integration
The analog point deviation is calculated as a sum of “value change and time products” since the last
protocol reported value. A small point change over a long time period can contribute to the deviation as
well as a large point change over a short time period.
The Event Deviation value has units of "Unit-Seconds". If the DNP3 Static Object Type 62 of the point is
set to a floating point (AI group 30 variation 5 or AO group 40 variation 3) then the integration deviation
units will apply to the Engineering value of the point. Otherwise, the integration deviation units will apply
to the Raw (integer) value of the point. The time component of the integration Event Deviation is
Seconds.
For more information on Event Deviation Type, see the SCADAPack E Data Processing Technical
Reference.
Method: None
When this method is selected, the point is prevented from generating events as a result of a value
change. This method is also inferred by setting the Percentage of Span to be 100.
5.4 Counter Point Attributes

The following diagrams indicate active attributes for RTU Physical Input Counter Points.
Figure 5.8: Physical Counter Input Point Attributes

The following attributes apply to RTU physical counter input points:
See common attributes above
DNP object type DNP3 static counter objects
Unsolicited Triggered attribute Allows events on this point to

trigger a DNP3 unsolicited
transmission
High Counter Limit Derives counter limit [32-bit integer] Available to

exceeded property ISaGRAF User applications.
Counter Reset Counter resets to zero [binary]

upon start-up 0 = Retain Previous Value
1 = Reset to zero
Counter Limit Exceeded property DNP3 0 = no-point Point number

binary point number 1-49999 = pointer to If non-zero it needs to be
associated binary point unique & not used for any
for Counter Limit other purpose
Exceeded property [integer]
Counter significant change deviation Generates DNP event [32-bit integer]

5.4.1 DNP Object Type & Unsolicited
DNP Object Type

DNP3 static data poll request (i.e. Class 0 request). It is mandatory that this attribute be defined for
each physical counter point. One of the following types is valid:

Unsolicited
The "Unsolicited" attribute determines the behavior of events generated from an individual counter point.
A DNP3 unsolicited transmission will occur upon a Counter point event* when the following conditions
are met:
Unsolicited attribute is enabled
Point's Data Class is selected for Class 1, Class 2 or Class 3
The selected DNP3 Class has been enabled for Unsolicited transmission. This is typically set by a
Master Station during DNP3 communications startup with the RTU.
*Counter events are generated when a high limit is exceeded, or when a significant change deviation
occurs. See Counter High Limit Exceeded & Significant Change Deviation 76 .
SCADAPack E Configurator is "UNSOLICITED".
5.4.2 Counter Reset, High Counter Limit & Counter Limit Exceeded
Counter Reset
This property enables the counter to default, on power-up or Cold Reset of the Main RTU unit, either to
the value reached before power-down, or to zero.
High Counter Limit

This attribute sets the high limit for the counter value, above which the “Counter Limit Exceeded”
property is set. Default value is 0 (indicating no high counter limit). For more information see Section
Counter Reset 91 .
Counter Limit Exceeded Property DNP Binary Point

Point properties that cannot be returned via standard DNP3 object status flags are mapped into the
RTU’s DNP3 User Binary points address space. The following counter point properties may be optionally
associated with DNP3 binary points:
5.4.3 Counter High Limit Exceeded & Significant Change Deviation
Counter High Limit Exceeded

A point attribute corresponding to this property configures the associated binary point for the property. A
binary point may optionally be configured for this property. If the binary point specified for this property
is a user point, a separate point configuration should exist in the configuration file for that binary point.
The current value of a binary point set as the “Counter High Limit Exceeded Property Binary Point”
follows the state of the “Counter Limit Exceeded” property on a counter point. I.e. when the “Counter
Limit Exceeded” property is TRUE, the binary point current value is set to “1”. When the “Counter Limit
Exceeded” property is FALSE, the binary point current value is set to “0”.
Counter Significant Change Deviation

The purpose of this attribute is to detect changes in a counter value. A counter value change exceeding
the deviation specified in this attribute causes a DNP event to be generated, subject to the alarm inhibit
attribute being FALSE, and the point being configured in a DNP event class.
Default value of this attribute is 0 (resulting in no counter change events).
5.5 Trend Record Configuration

Trend Record Configuration
The RTU database supports Trend Record configuration via point fields in the RTU Configuration File, or
through record exchange.
The Add Trend Record dialog is shown below. For information on the attributes shown, and operation of
the Trend Sampler, see the SCADAPack E Trend Sampler Technical Reference.
For information on Trend Configuration via Record Exchange, see Section Reading Database Trend
Records 106 and Writing to a Trend Point Record 116 .
Figure 5.9: Add Trend Record

6 Point Properties
Point Properties are generally read only point database fields describing (to the SCADA Master, The
SCADAPack E Configurator and ISaGRAF application) a status or characteristic of a point.
Common Point Properties 79
Digital Point Properties 83
Analog Point Properties 85
Counter Point Properties 91

6.1 Common Point Properties
Property Description Property Value Comment
Point Quality reason Accessible by ISaGRAF [16-bit integer]

user application e.g.
Comms Lost
Point is Bad
A/D Reference Check
Under-range
Over-range
Exceeded Rate of Rise
Exceeded Rate of Fall
No Change
Point Is Failed Property available to Set by “Point is

ISaGRAF application, and Bad” (User) attribute.
DNP point status [bit]
I/O not responding Property available to [bit]

ISaGRAF application and
DNP point status
Output point under ISaGRAF User Property available to Only valid for output
application control ISaGRAF application and points
DNP output point status [bit]
Output point remote control Property available to Only valid for output
interlock active ISaGRAF application and points
DNP output point status [bit]
6.1.1 Point Quality Reason
A bit mask of point quality reasons is provided as a property for point objects in the RTU database.
A bit ON in the mask indicates the appropriate quality reason is active.
Multiple quality bits may be set in the Point Quality Reason property, with the value presented being the
sum of the quality bits that are active.
A value of zero in this property indicates GOOD quality (no quality reason bits set).
Quality reason Attribute value (hex)
Good 0x0
Comms Lost 0x1
Point is bad 0x2
A/D Ref Check 0x4
Under-Range 0x8
Over-Range 0x10
Exceeded RoR 0x20
Exceeded RoF 0x40
No Change 0x80
6.1.2 I/O Not Responding & Remote Control Interlock
I/O Not Responding

This property is set TRUE if the point’s state cannot be updated due to Lost Communications (eg. with I/
O card or Remote I/O unit). It may also be set for derived points if that point is mapped to a peer device.
Output Point Remote Control Interlock Active

Is set TRUE for output points that have a remote control interlock configured and activated. If this
property is active, the Output point under ISaGRAF User application control property will be set FALSE.
An ISaGRAF user application cannot control the point in these circumstances.
The ISaGRAF user application can control the remote control interlock point itself. For example the
ISaGRAF user application may reset an active interlock under special circumstances such as no
communications with the Master Station.
6.1.3 Under ISaGRAF Control & Point is Failed
Output Point Under ISaGRAF User Application Control

Is set TRUE for output points on ISaGRAF Output Boards unless a Remote Control Interlock is
configured and the Remote Control Interlock point is set TRUE. The output point is under the control of
the ISaGRAF User Application when this property is TRUE. An ISaGRAF User Application cannot
control the output point when this property is FALSE.
Point is Failed
“Point Is Failed” property (also DNP point OFF-LINE status) is indicated when any of the following
conditions exist:
Communication Lost to device handling this I/O point (also indicated in point status flag as
Comms Lost)
RTU hardware (e.g. I/O module failure, relay output failure)
“Point is Bad” attribute set by user application
6.2 Digital Point Properties
Current Point State Derived by Data Processor Post-inverted raw state of physical
digital input
Or state of physical digital output
or user digital point
Point is in Alarm Derived by Data Processor from This property is filtered by Time
current point state and Alarm Deadband in/out of alarm. A DNP
Active State attribute. This input or output event may be
property may read by ISaGRAF. generated at the same time that
this property is set.
Time Dead-band Active Derived by Data Processor from Indicates if an Alarm Time set or
current point state. This clear dead-band timer is active on
property may read by ISaGRAF. the point.
Current Point State

The value of this property is the value reported by ISaGRAF Input Boards connected to digital points,
reported through the slave communication protocols (DNP3, IEC 60870-5, Modbus) as the current value
of digital points. This property value is either TRUE or FALSE.
Point is In Alarm
The value of this property is available to the user ISaGRAF application by using the point field function
block (RDFLD_I). This property value is either TRUE or FALSE. The setting of this property may
coincide with the generation of a DNP input or output event if the point is configured to generate a DNP
event, and the point’s “Alarm Inhibit” attribute is inactive.
Time Dead-band Active

block (RDFLD_I). This property value is either TRUE or FALSE. This property is TRUE if either an
"Alarm Time Dead-band" or an "Alarm Clear Time Dead-band" timer is currently active on the point.
Supported for Digital Input or Digital User points.
Alarm Timestamps
The “Current Point State” property is presented to DNP as the real time value of the digital point. The
timestamp applied to a change in the digital point depends upon the configuration of the point attributes.
If the point does not have alarm time dead-bands configured, a change in the “Point is in Alarm” property
occurs at the same time as a change in the “Current Point State”. In this case the timestamp
associated with a current state change will be recorded as the DNP timestamp for an event from the
point. For physical digital input points with no alarm time dead-bands, the timestamp is derived from the
physical input change time recorded by the I/O sub-system.
If a point has alarm time dead-bands, the timestamp of the corresponding DNP event is the time of the
post dead-band change in the “Point is in Alarm” property. It is not possible to timestamp the event
change at its original time of occurrence as a current value cannot be sent in response to a DNP Master
request, and later sent as a DNP change event with an earlier time.
6.3 Analog Point Properties
Analog current value Integer Selected by ISaGRAF [integer]

integer variable on analog
input board
Analog current value Engineering Selected by ISaGRAF Scaled by Min/Max-Raw/

Units “real” (float) variable on Eng
analog input board [float]
Over-range Property available to Set if Engineering value

ISaGRAF application & greater than Over Range
DNP analog input point Limit
status [bit]
Under-range Property available to Set if Engineering value

ISaGRAF application & less than Under Range
DNP analog input point Limit
status [bit]
A/D Reference Error Property available to [bit]

ISaGRAF application &
DNP analog input point
status (Reference Check)
Rate of Change RISE state Property available to [bit]

as DNP Binary Point
Rate of Change FALL state Property available to [bit]

as DNP Binary Point
No Change state Property available to [bit]

as DNP Binary Point
Analog limits transgressed (4L..4H) 8 properties available to [8 bits]

ISaGRAF application
Time Dead-band Active Property available to [bit]

ISaGRAF application
6.3.1 Current Value Integer & Engineering
Current Value Integer

RTU data current values are available for Peer RTU access. This includes physical and system points
as well as configured user points.
An RTU System point is only reported to the SCADA Master through Class 0,1,2,3 mechanisms if the
user configures appropriate attributes for the point in a configuration record.
The current value Integer property is exposed to ... DNP3 integer, IEC60870-5 integer, Modbus "IEC
UINT", Modbus "IEC INT"
System points may be accessed by a user application or the SCADAPack E Configurator without a
configuration file.
Current Value Engineering

RTU data current values are available for Peer RTU access. This includes physical and system points
as well as configured user points.
An RTU System point is only reported to the SCADA Master through Class 0,1,2,3 mechanisms if the
user configures appropriate attributes for the point in a configuration record.
The current value Engineering property is used in external data in the following communication protocol
data types:
DNP3 short floating point objects (where point is configured with a DNP3 short float data type)
IEC60870-5 measured value, short float objects (where point is configured with an IEC60870-5 short
float ASDU)
Modbus Slave and Modbus/TCP Server register read responses (where point is configured with a
DNP3 short float data type)
System point values may be accessed by a user application or by the SCADAPack E Configurator
without a configuration file.
6.3.2 Over-Range & Under-Range
Over-Range
Property state set to TRUE if the point is deemed to be in an over range condition (dependant on the
point’s Current Engineering Value and the over range limit). Refer to the SCADAPack E Data
Processing Technical Reference manual for detailed information on the criteria for determination of an
over range condition. When this property is set TRUE, the Under-range, A/D Reference Error, Rate of
Rise & Rate of Fall properties are set FALSE.
Under-Range
Property state set to TRUE if the point is deemed to be in an under range condition (dependant on the
point’s Current Engineering Value and the under range limit). Refer to the SCADAPack E Data
Processing Technical Reference manual for detailed information on the criteria for determination of an
under range condition. When this property is set TRUE, the Over-range, A/D Reference Error, Rate of
Rise & Rate of Fall properties are set FALSE.
6.3.3 A/D Reference Error & No Change State
A/D Reference Error

Property state set to TRUE if the RTU’s I/O sub-system indicates an A/D conversion error. This is
detected by a reference voltage on one of the multiplexed AI channels converting to an incorrect value.
Over-range, Under-range, A/D Reference Error, Rate of Rise & Rate of Fall properties are mutually
exclusive. When this property is set TRUE, the other listed properties are set FALSE.
No Change State
The Data Processor will set this property to TRUE if the analog’s value does not change by more than
the No Change Value % attribute in the No Change period. Over-range, Under-range, A/D Reference
Error, Rate of Rise & Rate of Fall properties are mutually exclusive. When this property is set TRUE, the
other listed properties are set FALSE
6.3.4 Rate of Change Rise & Fall States
Rate of Change Rise State

The Data Processor will set this property to TRUE if the analog’s value rises faster than the Rate of Rise
% attribute in the Rate of Change period. See also Rate Of Rise And Fall 65 . Over-range, Under-range,
A/D Reference Error, Rate of Rise & Rate of Fall properties are mutually exclusive. When this property is
set TRUE, the other listed properties are set FALSE.
Rate of Change Fall State

The Data Processor will set this property to TRUE if the analog’s value falls faster than the Rate of Fall
% attribute in the Rate of Change period. See also Rate Of Rise And Fall 65 . Over-range, Under-range,
A/D Reference Error, Rate-of-Rise & Rate-of-Fall properties are mutually exclusive. When this property is
set TRUE, the other listed properties are set FALSE.
6.3.5 Analog Limits Transgressed
Analog Limits Transgressed

The Data Processor controls the state of eight properties 4L through 4H. The state of these properties
will be set TRUE if the point is deemed to be in an alarm condition (dependant on the point’s Current
Engineering Value and the relevant engineering limit). Refer to the SCADAPack E Data Processing
Technical Reference manual for detailed information on the criteria for determination of an alarm
condition. The assignment of these properties is also subject to time & value dead-band configurations.
Also see Sections Time Deadband Into & Out of Alarm 47 & Profile ID & IEC870 – Information
Object Address (IOA) [IEC870 – Information Object Address (IOA)] 39 .
Analog Time-Stamps
The “Analog Current Value” properties are presented to DNP as the real time value of the analog point.
The timestamp applied to a change in the analog point depends upon the configuration of the point
attributes. If the point does not have alarm time dead-bands configured, a DNP event may be generated
at the same time that the analog value changes. In this case the timestamp associated with a current
value change will be recorded as the DNP timestamp for an event from the point.
If a point has alarm time dead-bands, the DNP event is generated with the post dead-band time and
value. It is not possible to timestamp the event change at its original time of occurrence as a current
value cannot be sent in response to a DNP Master request, and later sent as a DNP change event with
an earlier time.
6.3.6 Time Dead-band Active
Time Dead-band Active

block (RDFLD_I). This property value is either TRUE or FALSE. This property is TRUE if either an
"Alarm Time Dead-band" or an "Alarm Clear Time Dead-band" timer is currently active on the point.
Once set, the property will only become FALSE if there are no longer any dead-band timers running on
the point.
6.4 Counter Point Properties
Description Access Comment
Counter current value Point database ISaGRAF [32-bit integer]

interfaces, DNP3 object, ISaGRAF
I/O board
Counter limit exceeded Property available to ISaGRAF [bit]

application, and DNP binary point
Counter Current Value

The counter value is a 32-bit unsigned integer value representing the number of physical transitions of
the physical digital input point. Where a hardware counter is used for high-speed digital input counting,
physical digital input transitions from 0 to 1 state are counted. I.e. high-speed hardware digital counters
can’t count inverted transitions. Where digital input counting is handled in software, 0 to 1 state
transitions are counted when the “Invert Point State” point attribute on the digital input is set FALSE.
Where digital input counting is handled in software, 1 to 0 state transitions of the digital input are
counted when the “Invert Point State” point attribute on the digital input is set TRUE.
High-speed hardware counters are supported by SCADAPack E RTU systems. These counters have a
maximum count capacity of 1KHz. See the relevant SCADAPack E RTU Hardware Manual for details.
The counting on these digital input channels is not software de-bounced, although the digital input state
change is software de-bounced according to the “De-bounce Time” attribute on the digital input point.
For more information see section De-bounce Time 48 .
The other digital input channels support software counting. The maximum count rate capacity is
dependent on the SCADAPack E RTU hardware (e.g. 50Hz). Software de-bouncing is applied to both
counting and digital input state change on these channels, set by the “De-bounce Time” attribute on the
digital input. For more information see section De-bounce Time 48 .
Counter Limit Exceeded

Set to TRUE if the Counter’s Current Value exceeds the High Counter Limit attribute. If the High Counter
Limit attribute is 0, the Counter Limit Exceeded property is not set TRUE. If the counter value is preset
by an ISaGRAF user application, or initialized using DNP3 “Initialize Data” function code, and the
counter value falls below the high limit, then the “Counter Limit Exceeded” property is set FALSE.
Counter Reset
Counter current value can be preset and cleared by an ISaGRAF user application using the ISaGRAF
“OPERATE” function. For more information see SCADAPack E ISaGRAF Technical Reference manual.
DNP3 Application Layer Function Code 15 (Init Data to Default) and Function Code 2 (Write) can also
be used to reset RTU counters (FC 2 can also preset counters). This also applies to Analog points
configured as DNP3 Counter Object Types. For more information see SCADAPack E Telemetry DNP3
Technical Reference manual.
7 Point Database Access

The RTU’s point database is contained in non-volatile (NV) memory. The NV database is used by the
RTU unless it is corrupt or empty.
On-line changes made with SCADAPack E Configurator or the SCADA Master are stored in the NV
Point Database. If required, the RTU database configuration can be written back to a Configuration file
using the RTU’s GETCONFIG command.
Upon receiving a File Exec “Restart Config” the RTU rebuilds the Point Database in NV memory by
opening the configuration file from its file system and interpreting the contents. Point current values are
not affected unless specifically set in the RTU configuration file. (e.g. Port Settings, Route Table, etc).
Three types of external operations on the point database are possible:
Add point: Points can be added to the database through a Configuration file change specifying a new
point, and take effect on a DNP File Exec “Restart Config” command. Points can also be added to the
database using the Write Record Exchange (REX) process (see Section Adding Points 123 ).
Disable/Delete Point: Points can be disabled from the database through a Configuration file change
and will take effect on a DNP File Exec “Restart Config”. Points can also be disabled in the database
using the Write Record Exchange process (see Section Disabling Points 123 ). Disabled user and
system points will be deleted from the RTU on an RTU restart (also see SCADAPack E RTU
Operational Reference manual). Disabled physical points will have their RTU point database attributes
set to defaults on an RTU Restart.
Change Attribute: Point attribute changes can be made to the database through a Configuration file
change, ISaGRAF user application, or DNP via the RTU’s Record Exchange point database interface.
Not every point attribute may be changed via Record Exchange or ISaGRAF at run-time. Changes made
with a new Configuration file will only take effect on a DNP File Exec “Restart Config” command.
These operations are summarized in Table 7.1 93 .
Table 7.1: Point Database External Operations
Situation Possible Operation Effect

DNP File Exec “Restart Add record The RTU will open the given
Config filename” command Configuration file and compare its
Change Attribute
contents with the NV database.
Disable record Points may be added. If the
filename has a “.RTU” extension
(full configuration file) database
points not in the configuration file
will be marked as “Disabled”.
Point attributes can be changed
here. If the filename has a “.INC”
extension (incremental
configuration file) database points
not in the configuration file are not
changed.
RTU Running Add record DNP or ISaGRAF application may

change many point attributes in
Change Attribute
Situation Possible Operation Effect

Disable record this situation. Points can be
added or disabled using the Write
Record Exchange Process (see
Section Using Record Exchange
to Add or Disable Points in the
RTU 122 )
RTU Cold Start with valid Delete record The RTU will delete user or system
NV database records previously marked as
“Disabled”, and set attributes on
“Disabled” physical points to
defaults.
RTU Cold Start with invalid Delete All NV point database records are
or corrupt NV database deleted. Physical point records
are added with default attributes
7.1 Database Record Exchange Area

The RTU contains a set of system points dedicated to transferring point record fields (including point
attributes and properties) between the RTU and SCADAPack E Configurator or a SCADA Master.
Separate system points are used for reading and writing to allow simultaneous reading and writing of
database records by different devices (eg. SCADA Master and SCADAPack E Configurator).
See Record Exchange Area System Points 96 .
7.2 Record Exchange Area System Points

The system point areas for the RTU database record exchanges are detailed in the following table. The
format of the record exchange areas is defined above, for each read/write exchange for the various RTU
database point types.
System Points Exchange Area Comments
61000 61049 Digital point number and type record table Written by SCADAPack
E Configurator to define
the points for which the
Digital read Exchange
Records apply
Digital read exchange record 1

61050 61066 Analog points (16-bit)
61050 61065 Binary points
…. ….
60250 60254 REX II Digital read exchange record 1

Binary points
Binary points
….
Binary points
61500 61549 Counter point number and type record table Written by the
SCADAPack E
Configurator to define the
points for which the
Counter read Exchange
Records apply
Counter read exchange record 1

Counter read exchange record 2
… …
61886 61899 Counter read exchange record 25

Binary points
60575 60584 REX II Counter read exchange record 1

Analog points (16-bit)

…
62100 62119 Analog point number record table Written by The

SCADAPack E
points for which the
Analog read Exchange
Records apply
Analog read exchange record 1

62380 62386 Analog points (32 – bit)
62450 62473 Analog float points

… … …
REX II Analog read exchange record 1

60475 60479 Analog points (32–bit)
…
62750 62752 Trend read point number table Written by The

SCADAPack E
point & record number for
which the Trend read
record exchange table
applies
Trend read record exchange table

Digital write record exchange table

REX II Digital write record points

Counter write record exchange table

REX II Counter write record exchange

62930 62939 points
Analog write record exchange table

62873 62877 Analog points (32 - bit)
REX II Analog write record exchange points

62950 62954 Analog points (32 - bit)
Trend write record exchange table

7.3 Reading Database Point Records

Four different read exchange areas are mapped into RTU system points, one for each RTU data type:
Digital, Analog and Counter, and one for Trend records. Each read exchange area has an associated
point number table that allows multiple records to be read simultaneously within one DNP3 fragment.
The read request for Read Record Exchange (REX) Table system points should contain the data types
and points in a single DNP3 fragment.
There are four Point Number Record Tables and four Read Record Exchange Tables. For Digital,
Analog, and Counter Point Records, each element in the Point Number Record Tables consists of two
DNP system points. These points define the point number and point type required to uniquely identify a
point record in the Read Record Exchange Table. For Trends, each element in the Trend Record Table
consists of three DNP system points. These points define the point number, point type, and trend
record number required to uniquely identify a trend record in the Trend Read Record Exchange Table.
One row in a Read Record Exchange Table represents the record fields for a single point or trend.
The point type enumeration required for a successful read record exchange is shown in Table 7.2 100 .
Table 7.2: Read Record Exchange Point Type Enumeration
Enumeration Point Type
1 PHYSICAL_DIGITAL_IN
2 PHYSICAL_DIGITAL_OUT
3 PHYSICAL_ANALOG_IN
4 PHYSICAL_ANALOG_OUT
5 PHYSICAL_COUNTER_IN
6 USER_DIGITAL
7 USER_ANALOG
8 SYSTEM_DIGITAL
9 SYSTEM_ANALOG
* The trend record number field is only applicable for Trend Record exchanges
Typically, transactions to each different record exchange table will occur independently. I.e. Separate
REX requests will be used to obtain data for digital, analog, counter, and trend records.
In order to read a point or trend record, the requesting DNP device (e.g. RTU Config) writes one or more
Point Number/Point Type entries to the RTU’s Point Number Record Table. For trends, the DNP device
needs to also write to the Trend Record Number entry. Point Number and Point Type entries may be
arbitrarily set for any element, and need not be consecutive. The requesting DNP device may then read
the requested records from the “Read Record Exchange Table”. Typically, transactions to each different
record exchange table will occur independently. I.e. Separate REX requests will be used to obtain data
for digital, analog, counter, and trend records.
When the read response is received, the requesting DNP device needs to check the Point Number/Point
Type (and Trend Record Number) fields for each record to confirm that the Read Record Exchange Table
data is for the requested points. If any records read from the exchange area have no matching Point
Number/Point Type (and Trend Record Number) as those requested, another external device may be
using the record exchange area. In this case, the write / read sequence needs to be repeated by the
requesting device.. SCADAPack E Configurator will handle this functionality internally and will not
require user intervention.
For Analog, Digital and Counter point records, the RTU returns a “Point Data Class” value of minus one (-
1) in the Read Record Exchange Table for any point that does not exist in the RTU’s Point Database.
The inquiry retry mechanism should not be retried in this case. SCADAPack E Configurator will indicate
to the user that an invalid point has been requested.
For Trend Records, the RTU returns a “Trend Stream Type” value of minus one (-1) in the Read Record
Exchange Table for any point that does not exist in the RTU’s Point Database. The RTU returns a
“Trend Stream Type” value of minus two (-2) in the Read Record Exchange Table for any request to a
point that does exist in the Point Database of the RTU, but for which the requested Trend Record
Number does not exist. The inquiry retry mechanism should not be retried in either case. SCADAPack
E Configurator will indicate to the user that an invalid point has been requested.
7.3.1 Reading Digital Point Records
When reading digital point records through the digital read record exchange table, a maximum of 25
point enquiries will be permitted in the digital record window. The format of a single record table
exchange row is as follows. These represent point offsets from the start of the system point area as
described in Record Exchange Area System Points 96 . DNP3 multiple point reads are used, as
described in Reading Database Point Records 100 .
16-bit Point Point Point Data DNP Static Remote Interlock unused Profile ID
Signed Number Type Class Object Control Alarm
Integer Type Interlock Timeout
Fields Point
+1 +2 +3 +4 +5 +6 +7
Point Point Limit Alarm Alarm Clear Output Debounce Double Status Point
Quality Data Generation Time Time Pulse Time
Class Triggered Deadband Deadband Time
(All
Masters
)
+8 +9 +10 +11 +12 +13 +14 +15
Slot
Channel
+16
Remote ISaGRAF Reserved

Point Is Alarm Trend Point I/O Not Control Controlled
Bad Inhibit Inhibit Failed Responding Interlock
Active
+1 +2 +3 +4 +5 +6 +7
1-bit
Fields Drop
Invert Alarm Output
Reserve Point Is In Current
Point Active on
d Alarm Point State
State State Interlock
Active
+8 +9 +10 +11 +12 +13
The “REX II” extensions used by SCADAPack E Configurator and the RTU firmware for reading the
following additional Digital Point record fields:
32-bit RESERVED RESERVED RESERVED RESERVED RESERVED

Signed
Integer
+1 +2 +3 +4
Fields
IEC870
Information IEC870 ASDU RESE
RESERVED RESERVED RESERVED RESERVED RESERVED
Object Type RVED
16-bit Address
Signed
Integer +1 +2 +3 +4 +5 +6 +7
Fields
RESERVED RESERVED
+8 +9
RESE
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
RVED
1-bit +1 +2 +3 +4 +5 +6 +7
Fields
RESERVED RESERVED
+8 +9
7.3.2 Reading Analog Point Records
When reading analog point records through the analog read record exchange table, a maximum of 10
point enquiry responses are permitted in a single DNP fragment, and the analog record window will be
restricted to enquiring 10 analog point records, simultaneously. The format of a single record table
exchange row is as follows. These represent point offsets from the start of the system point area as
described in Record Exchange Area System Points 96 . DNP3 multiple point reads are used, as
described in Reading Database Point Records 100 .
Remote Interlock
Point Point Data DNP Static
Point Type Control Alarm unused Profile ID
Number Class Object Type
Interlock Point Timeout
+1 +2 +3 +4 +5 +6 +7
Point Data Limit Alarm Clear No Rate of Rise Rate of Fall

16-bit Point Alarm Time
Class (All Generation Time Change Exceeded Exceeded
Signed Quality Deadband
Masters) Triggered Deadband Time Point Point
Integer
Fields +8 +9 +10 +11 +12 +13 +14 +15
No
Rate of
Change
Change Slot Channel Reserved Reserved Reserved
Detected
Period
Point
+16 +17 +18 +19 +20 +21
32-bit Current
Raw Min. Raw Max. Reserved Reserved Reserved Reserved
Signed Integer Value
Integer
Fields +1 +2 +3 +4 +5 +6
Engineering Engineering Engineering Engineering Engineering Engineering Engineering Engineering

Limit 4H Limit 3H Limit 2H Limit 1H Limit 1L Limit 2L Limit 3L Limit 4L
+1 +2 +3 +4 +5 +6 +7
Alarm Clear
32-bit Over Range Under Rate of
Eng. Min Eng. Max Rate of Fall No Change Value
Floating Limit Range Limit Rise
Deadband
Point
Fields +8 +9 +10 +11 +12 +13 +14 +15
Current
Event
Zero Limit Engineering Reserved Reserved Reserved Reserved Reserved
Deviation
Value
+16 +17 +18 +19 +20 +21 +22 +23
Remote
I/O Not Control ISaGRAF
Point Is Bad Alarm Inhibit Trend Inhibit Point Failed Reserved
Responding Interlock Controlled
Active
+1 +2 +3 +4 +5 +6 +7
Rate of A/D IEC870

Rate of Fall No Change Under
Reserved Rise Over Range Reference Cyclic Scan
Exceeded Detected Range
Exceeded Error Enabled
+8 +9 +10 +11 +12 +13 +14 +15

1-bit
Fields Limit Event Limit Event Limit Event Limit Event Limit Event Limit Event Limit Event Limit Event
Enable 4H Enable 3H Enable 2H Enable 1H Enable 1L Enable 2L Enable 3L Enable 4L
+16 +17 +18 +19 +20 +21 +22 +23
Limit Limit Limit Limit Limit Limit Limit

Limit
Transgress Transgress Transgress Transgress Transgress Transgress Transgress
Transgress 4L
4H 3H 2H 1H 1L 2L 3L
+24 +25 +26 +27 +28 +29 +30 +31
Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved
+32 +33 +34 +35 +36 +37 +38 +39
The “REX II” extensions used by SCADAPack E Configurator and the RTU firmware for reading additional
Analog Point record fields:
IEC870
Event
Information IEC870
Deviation RESERVED RESERVED RESERVED RESERVED RESERVED
Object ASDU Type
16-bit Type
Address
Signed
Integer +1 +2 +3 +4 +5 +6 +7
Fields
RESERVED RESERVED
+8 +9

Signed
Integer +1 +2 +3 +4
Fields

Floating
Point +1 +2 +3 +4
Fields
7.3.3 Reading Counter Point Records
When reading counter point records through the counter read record exchange table, a maximum of 25
counter point records will be permitted in the counter record window. The format of a record table
exchange row (for a single point record) is as follows. These represent point offsets from the start of the
system point area as described in Record Exchange Area System Points 96 . DNP3 multiple point
reads are used, as described in Reading Database Point Records 100 .
Remote
Interlock
Point Point Point Data DNP Static Control
Alarm unused Profile ID
Number Type Class Object Type Interlock
Timeout
Point
16-bit
Signed +1 +2 +3 +4 +5 +6 +7
Integer Point Limit
Fields Count Value
Point Data Generatio Slot Reserve
Exceeded
Quality Class (All n Channel d
Point
Masters) Triggered
+8 +9 +10 +11 +12 +13
32-bit Counter Current Change Reserve

Reserved Reserved
Unsigne High Limit Integer Deviation d
d Integer Value
Field +1 +2 +3 +4 +5
I/O Not
Alarm Trend Reserve Reserve Reserve
Point Is Bad RESERVED Respondin
Inhibit Inhibit d d d
g
+1 +2 +3 +4 +5 +6 +7
1-bit
Fields Counter
Reset To
High Reserve Reserve Reserve
RESERVED Zero On Reserved Reserved
Limit d d d
Statup
Exceeded
+8 +9 +10 +11 +12 +13 +14 +15
The “REX II” extensions used by SCADAPack E Configurator and the RTU firmware for reading additional
Counter Point record fields:
IEC870
Information IEC870
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
Object ASDU Type
16-bit Address
Signed
Integer +1 +2 +3 +4 +5 +6 +7
Fields
RESERVED RESERVED
+8 +9
7.3.4 Reading Database Trend Records
When reading trend records through the counter read record exchange table, only one trend record will
be permitted in the trend record window.
The sequence to read trend records for a single point is as follows:
1. The requesting DNP device writes Point Number, Point Type and Trend Record No. = 1 (in that
order) to the RTU’s Trend Point Number Record Table.
2. Trend record details are read from the Trend Read Exchange Table system points. When the read
response is received, the requesting device needs to check the Point Number, Point Type and Trend
Record Number fields of the received record to confirm that the data read matches what was
requested.
3. The DNP device then attempts to read the next trend record for the point by incrementing the Trend
Record No. and repeating steps 1 & 2 above. This sequence may continue until the Trend Record
No. has reached the maximum number of trends for a point (currently 99) or the point has no more
streams configured, in which case the RTU will return a Trend Stream Type of -2
The format of a the trend record table exchange row is as follows:
Trend
16-bit Point Point Stream Enable Sample Rate
Record Deviation
Integer Number Type Type Point (s)
Number
Fields
+1 +2
The format of the Trend Read Exchange Table is as follows:
Trend Trend Trigger

Point Point
Record Stream Point RESERVED RESERVED RESERVED
Number Type
Number Type Number
16-bit
Integer +1 +2 +3 +4 +5 +6 +7
Fields
Reserved Reserved
+8 +9
32-bit Sample
Deviation Reserved Reserved Reserved
Unsigned Period
Integer
Fields +1 +2 +3 +4
7.4 Writing Database Point Records

Four different write exchange areas are mapped into RTU system points to enable RTU point database
record fields to be written. One exchange area is presented for each data type: Digital, Analog and
Counter, and one exchange area is presented for Trend Records. Each write exchange area allows a
single database record to be written. However, multiple writes may be presented to the RTU in the same
DNP fragment.
The DNP device notifies the RTU to write to particular point record fields by sending controls to the
relevant system points in the “Record Exchange Table”. The DNP device needs to write a binary 1 to the
“Commence Write Record Field” and finally to both the “Point Number” field and “Point Type” field in the
Record Exchange Table regardless of what fields are modified (Trend Record Exchanges needs also
write to the “Trend Record Number” field. Writes to these fields does not modify attributes, rather they
are used to select the correct point in the RTU database. Multiple attributes may be modified for the
same point record within a single DNP fragment. The “Commence Write Record Field” Binary system
point needs to be the first object and the “Point Number” field system point needs to be the LAST object
in the DNP fragment, following the relevant system point objects representing the fields it wished to
modify in the Record Exchange Table.
WRITE RECORD EXCHANGE TABLE
Record
Commence Modify Modify
Number Point
Write Record this this …. Point Number
(Trends Type
Field Attribute Attribute
Only)
7.4.1 Required Point Type Enumeration for Write Record Exchange
The write record exchange process supports the editing and disabling of existing points and the addition
of new points. The point type enumeration required for a successful write record exchange is shown in
Table 7.3 109 .
Table 7.3: Write Record Exchange Point Type Enumeration
Enumeration Point Type
1 PHYSICAL_DIGITAL_IN
2 PHYSICAL_DIGITAL_OUT
3 PHYSICAL_ANALOG_IN
4 PHYSICAL_ANALOG_OUT
5 PHYSICAL_COUNTER_IN
6 USER_DIGITAL
7 USER_ANALOG
8 SYSTEM_DIGITAL
9 SYSTEM_ANALOG
7.4.2 Writing to a Digital Point Record
The format of the Digital write record exchange tables are as follows. These represent point offsets from
the start of the system point area as described in Record Exchange Area System Points 96 . DNP3
multiple point controls are used, as described in Writing Database Point Records 108 .
Drop
Commence
Output on RESERVED – Alarm
Write Point Is Alarm Trend
1-bit Interlock DO NOT Active Invert Point State
Record Bad Inhibit Inhibit
Fields Active WRITE State
Field
(Future)
+1 +2 +3 +4 +5 +6 +7
Remote
DNP Static Interlock Double
Point Data Control Point Data Class (All
Object Alarm unused Profile ID Status
Class Interlock Masters)
Type Timeout Point
Point
16-bit
Signed +1 +2 +3 +4 +5 +6 +7
Integer
Fields Alarm Alarm Limit RESERVED –
Output Debounce Point
Time Clear Time Generation DO NOT Point Number
Pulse Time Time Type
Deadband Deadband Triggered WRITE
+8 +9 +10 +11 +12 +13 +14 +15
The “REX II” extensions used by SCADAPack E Configurator and the RTU firmware have the following
format for writing additional Digital Point record fields:
IEC870
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
Information IEC870
– DO NOT – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT
Object ASDU Type
WRITE WRITE WRITE WRITE WRITE WRITE
Address
16-bit
Signed +1 +2 +3 +4 +5 +6 +7
Integer
Fields RESERVED RESERVED
– DO NOT – DO NOT
WRITE WRITE
+8 +9
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED

– DO NOT – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT
WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE
1-bit +1 +2 +3 +4 +5 +6 +7
WRITE WRITE
+8 +9

Signed – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT
Integer WRITE WRITE WRITE WRITE WRITE
Fields +1 +2 +3 +4
7.4.3 Writing to an Analog Point Record
The format of the Analog write record exchange tables are as follows. These represent point offsets from
Commence RESERVED RESERVED RESERVED RESERVED

Write Point Is Bad Alarm Inhibit Trend Inhibit – DO NOT – DO NOT – DO NOT – DO NOT
Record Field WRITE WRITE WRITE WRITE
1-bit
+1 +2 +3 +4 +5 +6 +7
Fields
Limit Event Limit Event Limit Event Limit Event Limit Event Limit Event Limit Event Limit Event
Enable 4H Enable 3H Enable 2H Enable 1H Enable 1L Enable 2L Enable 3L Enable 4L
+8 +9 +10 +11 +12 +13 +14 +15
Engineering Engineering Engineering Engineering Engineering Engineering Engineering Engineering

Limit 4H Limit 3H Limit 2H Limit 1H Limit 1L Limit 2L Limit 3L Limit 4L
+1 +2 +3 +4 +5 +6 +7
Alarm Clear
32-bit Over Range Under
Eng. Min. Eng. Max Rate Of Rise Rate Of Fall No Change Value
Floating Limit Range Limit
Deadband
Point
Fields +8 +9 +10 +11 +12 +13 +14 +15
RESERVED RESERVED RESERVED RESERVED
Event
Zero Limit – DO NOT – DO NOT – DO NOT – DO NOT
Deviation
WRITE WRITE WRITE WRITE
+16 +17 +18 +19 +20 +21
32-bit RESERVED RESERVED RESERVED

Signed Raw Min. Raw Max. – DO NOT – DO NOT – DO NOT
Integer WRITE WRITE WRITE
Fields +1 +2 +3 +4
Remote
Interlock RESERVED Point Data
Point Data DNP Static Control
Alarm unused Profile ID – DO NOT Class (All
Class Object Type Interlock
Timeout WRITE Masters)
16- Point
Signed +1 +2 +3 +4 +5 +6 +7
Integer
Rate Of
Rate Of Fall No Change
Fields Alarm Clear Rate of Raise Limit
Alarm Time No Change Exceeded Detected
Time Change Exceeded Generation
Deadband Time Point Point
Deadband Time Point Triggered
Number Number
Number
+8 +9 +10 +11 +12 +13 +14 +15

RESERVED
Point
– DO NOT Point Type
Number
WRITE
+16 +17 +18
The attributes Raw Min, Raw Max. and Eng. Min, Eng. Max. need to be written as pairs in a single
record exchange transaction. If only Raw Min. or Eng. Min. are written, then Raw Max. and Eng. Max.
will be set to +2^31-1 and FLT_MAX respectively. If only Raw Max. or Eng. Max. are written, then Raw
Min. and Eng. Min. will be set to -2^31 and –FLT_MAX respectively.
format for writing additional Analog Point record fields:
IEC870 RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED

Cyclic Scan – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT
Enabled WRITE WRITE WRITE WRITE WRITE WRITE WRITE
1-bit +1 +2 +3 +4 +5 +6 +7
WRITE WRITE
+8 +9
IEC870
Event RESERVED RESERVED RESERVED RESERVED RESERVED
Information IEC870
Deviation – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT
Object ASDU Type
Type WRITE WRITE WRITE WRITE WRITE
Address
16-bit
Signed +1 +2 +3 +4 +5 +6 +7
Integer
WRITE WRITE
+8 +9

Signed – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT
Integer WRITE WRITE WRITE WRITE WRITE
Fields +1 +2 +3 +4

Floating – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT
Point WRITE WRITE WRITE WRITE WRITE
Fields +1 +2 +3 +4
7.4.4 Writing to a Counter Point Record
The format of the Counter write record exchange table are as follows. These represent point offsets from
Commence
RESERVED RESERVED Reset To RESERVED
Write Point Is
1-bit Alarm Inhibit Trend Inhibit – DO NOT – DO NOT Zero On – DO NOT
Record Bad
Felds WRITE WRITE Statup WRITE
Field
+1 +2 +3 +4 +5 +6 +7
32-bit RESERVED RESERVED RESERVED

Counter Change
Unsigned High Limit – DO NOT – DO NOT – DO NOT
Deviation
Integer WRITE WRITE WRITE
Fields +1 +2 +3 +4
DNP Static RESERVED RESERVED RESERVED Point Data

Point Data
Object – DO NOT – DO NOT unused Profile ID – DO NOT Class (All
Class
Type WRITE WRITE WRITE Masters)
16-bit
Signed +1 +2 +3 +4 +5 +6 +7
Integer Property Limit RESERVED
Fields Point
Point Count Generation – DO NOT Point Type
Number
Exceeded Triggered WRITE
+8 +9 +10 +11 +12
format for writing additional Counter Point record fields:
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED –

– DO NOT – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT DO NOT
WRITE WRITE WRITE WRITE WRITE WRITE WRITE WRITE
1-bit +1 +2 +3 +4 +5 +6 +7
WRITE WRITE
+8 +9
16-bit IEC870 RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED –

IEC870
Signed Information – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT DO NOT
ASDU Type
Integer Object WRITE WRITE WRITE WRITE WRITE WRITE
Address
+1 +2 +3 +4 +5 +6 +7

WRITE WRITE
+8 +9
7.4.5 Writing to a Trend Point Record
The format of the Trend write record exchange table are as follows:
Commence
RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED
Write
1-bit – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT – DO NOT
Record
WRITE WRITE WRITE WRITE WRITE WRITE WRITE
fields Field
+1 +2 +3 +4 +5 +6 +7
32-bit Sample RESERVED RESERVED RESERVED

unsigned Rate Deviation – DO NOT – DO NOT – DO NOT
integer WRITE WRITE WRITE
Fields +1 +2 +3 +4
Trend RESERVED RESERVED RESERVED RESERVED RESERVED Trend

Trigger Point – DO NOT
Stream – DO NOT – DO NOT – DO NOT – DO NOT Record
Number WRITE
16-bit Type WRITE WRITE WRITE WRITE Number
signed
Integer +1 +2 +3 +4 +5 +6 +7
fields
Point
Point Type
Number
+8 +9
A valid write to the Trend Write Exchange Table with the “Sample Rate” field set to zero will cause that
trend record and subsequent records (with a higher record no.) for that point to be deleted.
Unlike standard points, new trend records may be created by writing a trend record using a valid (1-99)
and unused trend record number. The Trend Record Number must be the first unused Trend Record for
the given Point Number and Point Type. If an unused Trend Record is located between existing Trend
Records, and the Trend Record being created, Trend Record creation will not occur.
Trend Record Exchange writes will invoke a restart of the Sampler. See Restarting the Sampler task
121 and Using Record Exchange with Sampler 124 on how the Sampler and Profiler restart timers are
handled for subsequent Record Exchange Writes.
7.4.6 Notes and Limitations of Writing Database Records
Record exchange write transactions for a single point or trend need to be contained within a single DNP
fragment for synchronous writing to the database within the RTU’s DNP3 driver. This stops transactions
from multiple DNP devices from competing. Multiple record exchange writes can be contained in a
single fragment.
The Write Record Exchange Table system points may be read without error, but does not return useful
values.
Record Exchange Failures 118

RTU Configuration Revision Numbers 119
Trend Deletion Results in No Trends Being Deleted 120
Restarting the Profiler, Sampler and 60870-5-101 Tasks 121
7.4.6.1 Record Exchange Failures
When a Write Record Exchange transaction does not work it is indicated by a Control Status of ‘4’ –
“Control operation not supported for this point” returned by DNP in the status flag of the ‘Point Number’
control. This status indicates that at least one attribute modification did not work. There is no
mechanism to determine which control caused this without performing a record exchange on the point
and comparing the actual values to the expected values.
The RTU will return a status for the following reasons:
Attempting to modify an invalid attribute for the given point type – e.g. setting ‘Debounce Time’
for a Physical Digital Output.
Setting an attribute to an illegal value.
Setting an attribute value that is rejected by the Data Processor – for example, setting the Rate
of Rise/Fall point numbers to non-existent points, or are already assigned to other point
properties.
7.4.6.2 RTU Configuration Revision Numbers
A write exchange causes the RTU to increment the “RTU Configuration Minor Revision” system point if at
least one attribute was successfully written. When deleting trends, the minor revision number is
incremented for each trend record successfully deleted. This indicates that the RTU’s version of the
point configuration database has changed. This is true for any attribute changes, including trends,
except for the following:
Alarm Inhibit
Trend Inhibit
Point is Bad
7.4.6.3 Trend Deletion Results in No Trends Being Deleted
Setting of an analog DNP points current integer or engineering value, or a binary DNP points current
state cannot be performed using the record exchange areas. A DNP Control must be sent directly to
the DNP point, allowing that control operations such as ISaGRAF controlling & Remote Interlock active
are checked for the point control.
Setting of a DNP counter value cannot be performed using the record exchange areas. Pre-setting a
DNP counter value is not supported through DNP controls.
Clearing a DNP counter value cannot be performed using the record exchange areas. A DNP Function
Code 15 (Initialize Data) needs to be sent to the RTU.
7.4.6.4 Restarting the Profiler, Sampler and IEC 60870-5 tasks
Record exchange writes have the potential to impact on the Profiler, Sampler and IEC 60870-5-101 / -
104 Slave tasks.
If the write record exchange is to edit an existing point and the Profile ID is to change, then the Profiler
is flagged for a restart.
If the Write Record Exchange is to edit an existing point with an associated existing Trend Record AND
one of the following attributes is to be modified, then the Sampler is flagged for a restart.
Raw Min
Raw Max
Eng Min
Eng Max
DNP Static Object Type
Trend Inhibit
If the Write Record Exchange is for a TREND record (i.e. Trend REX Write), then the Sampler is flagged
for a restart.
If the Write Record Exchange is to edit an existing point with one of the following attributes to be
modified, then the IEC 60870-5 Slave task is flagged for a restart.
IEC870 ASDU Type
IEC870 Cyclic Scan
IEC870 Information Object Address
Once either service has been flagged for a restart, a 30 second timer is started. If any subsequent write
record exchanges are received by the RTU that may impact on the Profiler, Sampler or IEC 60870-5
Slave task within that 30 seconds, the timer is restarted. Once the timer expires, the appropriate
services are restarted.
7.5 Using Record Exchange to modify configuration in the RTU

The Write Record Exchange process can be used to create and disable points in the RTU. Write record
exchanges are initially processed as point edits. If the point to be edited does not exist, then an attempt
to create the point is undertaken. Disabling configuration points is effected by including attributes point
data class and DNP static object type with the decimal value 21845 (i.e. hexadecimal 0x5555) in the
write record exchange.
Adding & Disabling Points 123

Using Record Exchange with ISaGRAF, Profiler, Sampler & IEC 60870-5 tasks 124
7.5.1 Adding & Disabling Points
Adding Points
The initial step of the write record exchange is to validate the point in the RTU. If the point does not
exist, the configuration point will added to the point database providing one of the following conditions are
met
the requested point type is a user point and the point number is valid (i.e. largest physical point
number < point number < 50000)
the requested point is a configurable system point
the requested point is a valid Remote I/O physical point.
If the point is successfully created, then the point is added to the point database with all attribute values
included in the write record exchange. The record exchange will then return a status as indicated in
Section Notes and Limitations of Writing Database Records 117 . If the point was not successfully
created then the record exchange will return a failure status and the RTU System Error Point will be
written with a value indicating a “point create error” (see the SCADAPack E Operational Reference
Manual).
Disabling Points
The write record exchange can be used to disable configuration points. USER and SYSTEM
configuration points can be disabled, whereas a request to disable physical points result in the point
attributes of the physical point restored to their default values. In this instance the physical point is not
disabled. A configuration point is considered for disabling / restoring only if the following attributes and
values are included in the write record exchange
point data class = 21845 (decimal), i.e., 0x5555 (hex)
DNP static object type = 21845 (decimal), i.e., 0x5555 (hex)
Both of these attributes need to be written with these values for the point to be disabled / restored.
If a point is successfully disabled / restored, any trends associated with the configuration point will also
be deleted, and the record exchange will then return a successful status. If the point is a derived point, it
will be deleted from the point database on the next RTU Restart. If the point was not successfully
disabled / restored then the record exchange will return a status and the System Error Point will be
written with a value indicating a “point delete error” (see the SCADAPack E Operational Reference
manual).
7.5.2 Using Record Exchange with ISaGRAF, Profiler, Sampler & IEC 60870-5 tasks
The dynamic addition and disabling of configuration points using Write Record Exchange has
implications for other system services, e.g. ISaGRAF, Profiler, Sampler and point data processing in
general. The addition or disabling of a given point may well impact on other configuration points, e.g. the
point to be disabled may be an interlock for points mapped to ISaGRAF output boards. These are
managed appropriately by the RTU, e.g. such output points would have their Remote Control Interlock
Point attribute cleared. Implications concerning ISaGRAF, Profiler and Sampler are considered below.
ISaGRAF
It is possible for ISaGRAF to start a given application with ISaGRAF variables (attached to I/O boards)
that are mapped to non-existent points. ISaGRAF correctly processes these variables without the need
to restart the application with the addition of such points to the point database, as a result of write record
exchange. This is the case for point types that can be mapped to input and / or output boards.
The disabling of a point on an ISaGRAF output board, results in that point no longer being processed by
ISaGRAF, and ISaGRAF attempts to control the point are not successful. If a point mapped to an input
board variable is disabled then the ISaGRAF application will still read the point’s current value, though
that point is no longer processed by the Data Processor, therefore the value will no longer change.
It is possible to disable points on a given output board using write record exchange. In this case, the
ISaGRAF application will still run, though all disabled points are no longer processed. If the ISaGRAF
application was to be restarted, then the output board would not open and the ISaGRAF application
would not run.
Profiler, Sampler and IEC 60870-5 Tasks

Record exchange writes have the potential to impact on the Profiler, Sampler and IEC 60870-5 tasks.
See Restarting the Profiler, Sampler and IEC 60870-5 tasks 121 for more information regarding Record
Exchange Writes to existing points.
If a point is either added or disabled via Record Exchange, then both the Profiler, Sampler and IEC
60870-5 tasks are flagged for a restart. Once either service has been flagged for a restart, a 30 second
timer is started. If any subsequent write record exchanges are received by the RTU that may impact on
the Profiler or Sampler within that 30 seconds, the timer is restarted. Once the timer expires, the
appropriate services are restarted.
7.6 Double Status Points

Double status points exist in the RTU as cross-referenced pairs of binary points. Each of the double
status partners exist as configuration points in their own right and therefore record exchange reads can
be carried out on these points independently.
The write record exchange process can be used to either edit, add or disable double status configuration
points. If a write record exchange on a binary point includes a zero value in the double status point
field, or the double status point field was not included in the record exchange, the single point indexed
by the record exchange point number and type is affected only.
The inclusion of the double status point field with a zero value does not remove any previous double
status links.
Editing Double Status Points

If a write record exchange on a binary point includes a non-zero value in the double status point field
(see Section Writing to a Digital Point Record 110 ), then both points will be written with the values
included in the single point write record exchange. I.e. the point indexed by the record exchange point
number and type, and the point indexed by the double status point field. Their double status point
number attributes are set to ‘point’ to each other. Any previous double status partners of either of these
points will have their double status point number attributes cleared.
Adding Double Status Points

If either or both points are non-existent, they will be added to the point database with the attribute values
included in the write record exchange.
Disabling Double Status Points

If a binary configuration point is disabled as a result of a write record exchange (see Section Adding &
Disabling Points 123 [Disabling Points] 123 ), and the double status point number attribute is non-
zero, then the point indexed by the double status point number attribute will also be disabled.
8 RTU System Points

The following sections describe the SCADAPack E System Point allocations:
Binary System Point Map 127
Analog System Point Map 132
String System Point Map 153
BOOTP Configuration Records 155
8.1 Binary System Point Map

The tables below indicate binary system points and whether they are Configurable or not. A Configurable
System Point may be added by the user to the point database and configured to operate in the same
way as Physical or Derived points.
Configurable binary system points are NOT configured by default.
Unconfigured binary system points only allow access to the current state of the system point, where it
may still be referenced via ISaGRAF I/O boards. They cannot be included in DNP3 or IEC poll responses
by directly configuring, though.
Configuring the Configurable system points allows the appropriate attributes to be set for inclusion in poll
responses. Some of the configurable system points are identified as “static poll only”. These particular
points can only be returned in DNP3 class 0 poll responses, i.e. DNP3 events are not supported for the
those points.
Binary System Point Name Start End Point Type

Ran Range
ge
ScratchPad (General use) 5000 50049 Configurable
0
IEC 61131-3 Target/Resource Halted *6.1 130

5010
0
Target/resource 1 Application Halted 5010 Read Only / Configurable
0
Target/resource 2 Application Halted 5010 Read Only / Configurable
1
IEC 61131-3 Target/Resource Started *6.1 130
Target/resource 1 Task Started 5010 Read Only / Configurable

4
Target/resource 2 Task Started 5010 Read Only / Configurable
5
IEC 61131-3 Target/ResourceChecksum *6.1 130
Target/resource 1 Application Incorrect Checksum 5015 Read Only / Configurable

0
Target/resource 2 Application Incorrect Checksum 5015 Read Only / Configurable
1
IEC 61131-3 Validation Resource *6.1 130
Resource Validation Enabled 5016 Read/Write (checkbox)

0
RTU Read Only Config Status *6.2 130

These system points cleared at RTU
startup
RTU Initialised 5020 Read Only / Configurable
0
RTC Time Synchronised 5020 Read Only / Configurable
1
RTC Time Invalid 5020 Read Only / Configurable
2
DNP Protocol Driver Running 5020 Read Only / Configurable
3
Engineering Mode *6.1 130
5020 Read Only / Configurable
4
Local I/O Status *6.1 130
Local I/O Module Failure 5020 Read Only / Configurable

5
Local Input Power Supply Low 5020 Read Only / Configurable
6
Local On Board Battery Low 5020 Read Only / Configurable
7
Local Calibration Parameters Invalid 5020 Read Only / Configurable
8
SCADAPack ES Remote I/O Status *6.3 131
Remote 1 I/O Module Failure 5020 Read Only / Configurable

9
Remote 1 Input Power Supply Low 5021 Read Only / Configurable
0
Remote 1 On Board Battery Low 5021 Read Only / Configurable
1
Remote 1 Calibration Parameters Invalid 5021 Read Only / Configurable
2
Remote 2 I/O Module Failure 5021 Read Only / Configurable

3
Remote 2 Input Power Supply Low 5021 Read Only / Configurable
4
Remote 2 On Board Battery Low 5021 Read Only / Configurable
5
Remote 2 Calibration Parameters Invalid 5021 Read Only / Configurable
6
… 5021 50264 Read Only / Configurable

7
Remote F I/O Module Failure 5026 Read Only / Configurable
5
Remote F Input Power Supply Low 5026 Read Only / Configurable
6
Remote F On Board Battery Low 5026 Read Only / Configurable
7
Remote F Calibration Parameters Invalid 5026 Read Only / Configurable
8
DNP3 Data Concentrator "Ready" 5026 Read Only / Configurable
9
Reference Clock Connected *6.9 131
5027 Read Only / Configurable
0
RTU Read Write Status *6.1 130
Time Zone Modifier 5030 Read / Write / Configurable (static poll

2 only)
Configuration Corrupt 5030 Read Only / Configurable (static poll

3 only)
Stop Data Storage if Full *6.4 131

5030 Read / Write / Configurable (static poll
4 only)
Reserved 5030 50306

5
Analog alarm limit processing mode *6.7 131
7 only)
Exclude Deadband Values *6.11 131

8 only)
Enable v4 Sampler & Profiler compatibility 5030 Read / Write / Configurable (static poll
9 only)
TCP Service Port Disconnect

Range *6.5 131
5052 50524 Write Only
0
Reserved 5052 50529
5
Miscellaneous
Auxiliary DC Output Control (SCADAPack ES only) 5061 Read / Write
0
VLOOP Power Control (SCADAPack 350E and
SCADAPack 357E only)
USB STAT LED Control (SCADAPack 300E only) 5061 Read / Write
1
Modem Port Low-Power mode *6.6 131

5062 50624 Read / Write
0
IEC 60870-5-101 Slave Configurations *6.8 131

5070 50719 Read / Write
0
AGA12 Mixed Mode *6.10 131

5074 Read / Write
0
SCADAPack 300E Series Configuration modes

Also refer to SCADAPack 300E RTU
Hardware manuals.
COM3 Serial Port Power control 50750 Read / Write / Configurable (static poll
only)
12V to 24V DC/DC Converter control 50751 Read / Write / Configurable (static poll
only)
LED Power Always ON control 50752 Read / Write / Configurable (static poll
only)
SCADAPack 300E Series status

Also Refer to SCADAPack 300E RTU
Hardware manuals.
VLOOP Over Current indicator 50760 Read Only
LED Power State indicator 50761 Read Only
*6.1 Refer to the SCADAPack E Operational Reference manual.

*6.2 RTU Status.
RTU Initialized - this system point is set ON during the RTU start-up process, after RTU
system services have been initialized, including start-up initialization
and communication with Remote I/O units (may be used by an
ISaGRAF application to stop controls until the RTU is ready).
RTC Time Synchronized - this system point is set OFF during RTU start-up initialization, and is
set ON by the RTU DNP driver when the Real Time Clock has been
remotely set via DNP3 protocol. This can be used, for example, to
indicate to an ISaGRAF application that the SCADA Master has not yet
synchronized the RTU time after start-up.
RTC Time Invalid - this system point ON indicates that the Real Time Clock does not
contain a valid time. When a valid time is received via DNP3 protocol,
this point is set OFF. This is used internally to stop time operations
from occurring. It may also be used, for example, by an ISaGRAF
application to ignore the RTC value returned in function blocks.
DNP Protocol Driver this system point is set OFF during RTU start-up initialization and is
Running set ON when the RTU DNP driver has completed its initializations. This
point can be used, for example, to indicate to an ISaGRAF application
that the RTU is not ready to send DNP3 peer requests.
*6.3
Refer to the SCADAPack E Operational Reference manual & SCADAPack E Remote I/O Technical
Reference manual.
*6.4
Refer to the SCADAPack E Trend Sampler Technical Reference & SCADAPack E DNP3 Technical
Reference manual.
*6.5 Refer to the SCADAPack E TCP/IP Reference manual
*6.6 Refer to the SCADAPack E Communications Interfaces manual
*6.7 Analog alarm limit processing mode.
Binary System Point
DNP Point Description Comment

50307 Alarm Limit Processing Mode OFF = “Limit Transgress” mode (default)
ON = “At Limit” mode
Refer to the SCADAPack E Data Processing Technical Reference manual for more information.
*6.8 Refer to the SCADAPack E IEC 60870-5-101 Slave Technical Reference manual
*6.9 Refer to the SCADAPack E TCP/IP Technical Reference manual
*6.10 AGA12 Security Mixed Mode Point
Binary System Point

50740 AGA12 Mixed OFF = MIXED mode disabled *
Mode ON = MIXED mode enabled
(exists only in firmware version 7.4-6 and later).
* Only DISABLED state can be written as per AGA12 rules.

Refer to the SCADAPack E Security Technical Reference manual for more information.
*6.11
Binary System Point

50308 Exclude Deadband OFF = Exclude Deadband Values feature inactive (Default).
Values ON = Exclude Deadband Values feature enabled.
(exists only in firmware version 7.73 and later).
This is an application specific parameter that is not normally necessary to use.
Refer to the SCADAPack E DNP3 Technical Reference manual for more information.
8.2 Analog System Point Map

Configurable analog system points are NOT configured by default. Unconfigured analog system points
only allow access to either the current integer value or current engineering value of the system point
(depending on the point type specified in the following table), where it may still be referenced via
ISaGRAF I/O boards, though they can NOT be included in DNP3 poll responses. Configuring these
system points allows the appropriate attributes to be set for inclusion in poll responses.
If the analog system point is NOT configured and is referenced on an ISaGRAF I/O board as an integer
type, the point specified in the following table needs to be either 16-bit Integer or 32-bit Integer.
Similarly if the analog system point is NOT configured and is referenced on an ISaGRAF I/O board as a
real type, the point specified in the following table needs to be Floating Point.
Configuring the analog system point allows ISaGRAF I/O board variable types as either integer or real,
irrespective of the point type specified in the following table.
Some of the configurable system points are identified as “static poll only”. These particular points can
only be returned in DNP3 class 0 poll responses, i.e. DNP3 events are not supported for these points.
Analog System Point Name Start End Point Type

Range Range
RTU Info
RTU Type *6.A 145
50000 16-bit Integer / Read Only /
Configurable *
Operating System Firmware revision 50001 16-bit Integer / Read Only /
Configurable *
Switch Setting 50002 16-bit Integer / Read Only /
Configurable *
Processor board PAL revision 50003 16-bit Integer / Read Only /
Configurable *
Processor board Boot Monitor revision 50004 16-bit Integer / Read Only /
Configurable *
I/O board 1 Firmware revision 50005 16-bit Integer / Read Only /
Configurable *
I/O board 2 Firmware revision 50006 16-bit Integer / Read Only /
Configurable *
* static poll only
RTU Read Write Status

Up Time (Secs) 50010 32-bit Integer / Configurable *
Up Time Delta (0-1000 ms) 50011 32-bit Integer / Configurable *
Reset/Error Reasons Mask *6.B 145
50012 32-bit Integer / Configurable *
Task Watchdogs Mask *6.B 145
Engineering Timer *6.B 145
RTU Restart Count 50016 32-bit Integer / Configurable *
* static poll only
RTU Diagnostic Info *6,B 145
Error Code 50020 32-bit Integer / Configurable
RTU Dynamic System Memory Size 50021 32-bit Integer / Configurable

RTU Dynamic System Memory Free 50022 32-bit Integer / Configurable
Configuration Memory Used 50023 32-bit Integer / Configurable
Number of Files Used 50025 32-bit Integer / Configurable
File System Bytes Used 50026 32-bit Integer / Configurable

File System Bytes Free 50027 32-bit Integer / Configurable
NTP Task State 50028 32-bit Integer / Configurable
IRIG-B time quality (SCADAPack ER - P620 only) 50029 32-bit Integer / Configurable
Configuration
RTU Configuration Major Revision *6.E 147
RTU Configuration Minor Revision *6.E 147
* static poll only
RTU Read Only Status

Input Supply Voltage *6.2.3 50060 Floating Point / Read Only /
(not available on SCADAPack ER model RTU) Configurable
RTU Internal Temperature (Deg. C) 50062 Floating Point / Read Only /
RTU Internal Temperature (Deg. F) 50063 Floating Point / Read Only /
Ethernet MAC addr 1 (High 32-bits) 50080 32-bit Integer / Read Only /
Configurable *
Ethernet MAC addr 1 (Low 16-bits) 50081 32-bit Integer / Read Only /
Configurable *
RTU Serial Number (SCADAPack ES & 50082 16-bit Integer / Read Only /
SCADAPack ER) Configurable
Ethernet MAC addr 2 (High 32-bits) 50083 32-bit Integer / Read Only /
(SCADAPack ES & SCADAPack ER only) Configurable *
Ethernet MAC addr 2 (Low 16-bits) 50084 32-bit Integer / Read Only /
(SCADAPack ES & SCADAPack ER only) Configurable*
CPU ID (Low 32-bits) 50090 32-bit Integer / Read Only /

Configurable*
CPU ID (High 32-bits) 50091 32-bit Integer / Read Only /
Configurable*
Operating System Firmware build number 50093 32-bit Integer / Read Only /
Configurable*
Operating System Firmware service pack number 50095 32-bit Integer / Read Only /
Configurable*
* static poll only
Port Functions *6.D 145
Port 0 Function 50100 16-bit Integer

Port Modes *6.D 145
Port 0 Mode 50110 16-bit Integer


Port Data Rates *6.D 145
Port 0 Data Rate 50120 16-bit Integer

Port 2 Date Rate 50122 16-bit Integer
Port 6 Date Rate 50126 16-bit Integer

Port Formats *6.D 145
Port 0 Format 50130 16-bit Integer


Ethernet Port configuration *6.O 150
Ethernet interface 1 - Functions 50140 16-bit Integer

Enabled IP Services 50141 16-bit Integer
Ethernet interface 2 - Functions (SCADAPack ES & 50142 16-bit Integer
SCADAPack ER)
Port Connection State *6.E 147
Port 0 Connect State 50220 16-bit Integer


DNP3 Configurations *6.F 148
RTU DNP Node Address 50300 16-bit Integer

Reserved 50301 16-bit Integer
Control Arm Select Timeout (secs) 50302 16-bit Integer
Application Layer Confirm Timeout (secs) 50303 16-bit Integer
Time Request Interval (mins) 50304 16-bit Integer
Class 1 Minimum Events 50306 16-bit Integer

Event Notification Delay (secs) 50309 16-bit Integer
Minimum Unsolicited Event Transmit Delay 50310 16-bit Integer

(secs)
Master DNP Node Address 50311 16-bit Integer
Port 0 Data Link Layer Confirm Mode 50312 16-bit Integer

0=Never,1=Sometimes,2=Always
Port 1 Data Link Layer Confirm Mode 50313 16-bit Integer “
Port 0 Channel Receive Timeout (secs) 50322 16-bit Integer


Port 0 Data Link Layer Maximum Retries 50332 16-bit Integer

Application Layer Complete Fragment Timeout 50342 16-bit Integer

(secs)
Application Layer Maximum Attempts 50343 16-bit Integer
Default Startup Unsolicited Event Classes 50344 16-bit Integer
0=No Classes,
+2=Class1, +4=Class2, +8=Class3
DNP3 Master on Port 50345 16-bit Integer
Analog Event Mode 50346 16-bit Integer

0=Multiple, 1=Single
Modem Inactivity Timeout (secs) 50347 16-bit Integer
Modem Send Timer Delay (secs) 50348 16-bit Integer
Remote I/O "Must Poll" Timeout *6.3 131
50349 16-bit Integer
Remote I/O Background Poll Timeout *6.3 131
Modem Tx Message Timeout (secs) 50351 16-bit Integer
Remote I/O Comms Inactivity Timeout *6.3 131
Ethernet DNP3 Data Link Confirm Mode 50354 16-bit Integer

0=Never,1=Sometimes,2=Always
Ethernet DNP3 Channel Receive Timeout (secs) 50355 16-bit Integer
Ethernet DNP3 Data Link Maximum Retries 50356 16-bit Integer
Modem Test Interval (seconds) *6.H 149
Modem DTR Delay (milliseconds) *6.H 149
(max. value is 5000ms)
Unsolicited Response attempts per “Burst” 50359 16-bit Integer
Quiet Time delay (seconds) 50360 16-bit Integer
Master 1 Unsolicited Responses Allowed 50361 16-bit Integer

Max. DNP3 Event Storage 50362 16-bit Integer
Max. = 20,000 for SCADAPack 300E
Max. = 40,000 for SCADAPack ES &
SCADAPack ER
Disable DNP3 Data Concentrator at startup 50363 16-bit Integer
File transfer timeout for revised g70 objects 50367 16-bit Integer
(seconds) (Range 5 to 3600 seconds)
Maximum transmit fragment size (application 50370 16-bit Integer

layer) (Range 1 to 2048 bytes)
Maximum transmit frame size (data link layer) 50371 16-bit Integer
(Range 14 to 292 bytes)
Data Concentrator Update points on successful 50380 16-bit Integer

command (0=don't update, 1=update[default])
Data Concentrator Enable command events on 50381 16-bit Integer
IED control fail (0=don't generate [default],
1=generate)
DNP3 Data Concentrator Secure Authentication 58400 32-bit Integer

response timeout (ms) (Range 100 to 120,000 milliseconds)
DNP3 Slave Secure Authentication reply timeout 58401 32-bit Integer
(ms) (Range 100 to 120,000 milliseconds)
Route Record Previous Destination

Range *6.G 148
(Internal values) 50400 50499 16-bit Integer
DNP ROUTE TABLE Records

Range *6.G 148
50500 51299 16-bit Integer
Route Table AGA12 field *6.G 148
57400 57499 16-bit Integer
IEC 61131-3 Target/Resource 1 Information *6.B

145
Target/resource 1 Application Version 52000 32-bit Integer / Configurable (static poll

only)
Target/resource 1 Application Size 52001 32-bit Integer / Configurable (static poll
only)
Target/resource 1 Application Load Time 52002 32-bit Integer / Configurable (static poll
only)
Target/resource 1 current scan time 52003 32-bit Integer / Configurable (static poll
only)
Target/resource 1 maximum scan time since last 52004 32-bit Integer / Configurable (static poll
reset only)
Target/resource 1 number of cycle overflows 52005 32-bit Integer / Configurable (static poll
only)
Target/resource 1 configured cycle time 52006 32-bit Integer / Configurable (static poll
only)
IEC 61131-3 Target/Resource 2 Information *6.B

145
Target/resource 2 Application Version 52007 32-bit Integer / Configurable (static poll

only)
Target/resource 2 Application Size 52008 32-bit Integer / Configurable (static poll
only)
Target/resource 2 Application Load Time 52009 32-bit Integer / Configurable (static poll
only)
Target/resource 2 current scan time 52010 32-bit Integer / Configurable (static poll
only)
Target/resource 2 maximum scan time since last 52011 32-bit Integer / Configurable (static poll
reset only)
Target/resource 2 number of cycle overflows 52012 32-bit Integer / Configurable (static poll
only)
Target/resource 2 configured cycle time 52013 32-bit Integer / Configurable (static poll
only)
Modbus Slave Configs *6.P 151
Modbus Slave Address 52014 16-bit Integer
DNP3 Event Object Types *6.F 148
Generate Binary Input Event Object 52100 16-bit Integer

Generate Counter Event Object 52101 16-bit Integer
Generate Analog Input Event Object 52102 16-bit Integer
Generate Float Input Event Object 52103 16-bit Integer
Generate Binary Output Event Object 52104 16-bit Integer
Generate Analog / Float Output Event Object 52105 16-bit Integer
Scratchpad (General Use) 52200 52249 32-bit Integer / Configurable
Communications Counters *6.B 145
Total DNP Master 1 Fragments Received 53000 32-bit Integer / Configurable (static poll
only)
Master 1 Unsolicited Fragments Transmitted 53001 32-bit Integer / Configurable (static poll
only)
Master 1 Unsolicited Response Errors 53002 32-bit Integer / Configurable (static poll
only)
Total DNP Master 2 Fragments Received *6.2.2.1 53003 32-bit Integer / Configurable (static poll
only)
Master 2 Unsolicited Fragments Transmitted *6.F 53004 32-bit Integer / Configurable (static poll
148
only)
Master 2 Unsolicited Response Errors *6.F 148
53005 32-bit Integer / Configurable (static poll
only)
Total DNP Master 3 Fragments Received *6.F 148
only)
Master 3 Unsolicited Fragments Transmitted *6.F 53007 32-bit Integer / Configurable (static poll
148
only)
Master 3 Unsolicited Response Errors *6.F 148
only)
Port 0 Communication Counters *6.B 145

53009 53019 32-bit Integer / Configurable (static poll
only)
only)
only)
only)
only)
Ethernet 1 Communication Counters *6.B 145
only)
Ethernet 2 Communication Counters *6.B 145
only)
only)
only)
only)
only)
Telemetry Computer (TC) IDENTIFICATION

NUMBERS
(General Storage for ISaGRAF App)
TC Identification Number 1 53200 16-bit Integer

Network Times *6.H 149
Network Warmup 53210 16-bit Integer

Fixed Tx Delay 53212 16-bit Integer
Max Random Tx Delay 53213 16-bit Integer
Postamble Delay 53214 16-bit Integer
X.29 Parameters
X29 Peer Inactivity Timeout 53230 16-bit Integer
X29 TC Number 53231 16-bit Integer

X29 Status Poll Time 53232 16-bit Integer
X29 Drop DTR Time 53233 16-bit Integer
X29 Tx Message Timeout 53234 16-bit Integer
X29 TC Inactivity Timeout 53235 16-bit Integer
PLC Device Data *6.J 149
ISaGRAF 1 PLC Slave I/O board 1 comm status 53300 16-bit Integer / Read Only
ISaGRAF 1 PLC Slave board 1 data cache age 53301 16-bit Integer / Read Only
… 16-bit Integer / Read Only
ISaGRAF 1 PLC Slave board 60 comm status 53418 16-bit Integer / Read Only
ISaGRAF PLC Slave Output board default 53420 32-bit Integer

“Must Write” time (secs)
… 16-bit Integer / Read Only

ISaGRAF 2 PLC Slave board 14 comm status 53448 16-bit Integer / Read Only
Rate Of Change Timing Parameters *6.K 150
Rate Of Rise Sample Period 53450 Floating Point

Rate Of Rise Clear Time Dead-band (%) 53451 Floating Point
Rate Of Fall Sample Period 53452 Floating Point
Rate Of Fall Clear Time Dead-band (%) 53453 Floating Point
No Change Sample Period 53454 Floating Point
No Change Clear Time Dead-band (%) 53455 Floating Point
Host DNP3 Node Addresses

(IP info for DNP/IP Hosts) *6.M 150
Host DNP3 Address Number 1 53500 16-bit Integer

Host IP Interfaces
(IP info for DNP/IP Hosts) *6.M 150
Host IP Interface 1 53510 16-bit Integer / Read Only

TCP/IP Port Configurations

Port 0 IP Address 54000 32-bit Integer
Port 0 IP Subnet Mask 54010 32-bit Integer


Ethernet 1 IP Address 54020 32-bit Integer

Ethernet 1 IP Subnet Mask 54021 32-bit Integer
Ethernet 2 IP Address (SCADAPack ES & SCADAPack 54039 32-bit Integer
ER)
Ethernet 2 IP Subnet Mask (SCADAPack ES & 54040 32-bit Integer

SCADAPack ER)
PPP DCD delay time (milliseconds) 54041 32-bit Integer

SCADAPack ER - P620 IRIG-B Mode 54042 32-bit Integer
IRIG Disabled = 0
IRIG Standard = 2
IRIG IEEE1344 = 3
TCP/IP Timeout Configurations

TCP Initial Retry Timeout (milliseconds) 54032 32-bit Integer
TCP/IP DNP3 Configurations
DNP3/TCP Keep-Alive Time (secs) 54033 32-bit Integer

Default DNP3 TCP-UDP Port No. 54034 32-bit Integer
Default DNP3 IP Transport *6.L 150
0=UDP, 1=TCP
Data Concentrator DNP3/TCP Keep-Alive Time 54043 32-bit Integer
(secs)
TCP/IP Service Configurations

TCP Service Ports base Port Number 54036 32-bit Integer
TCP Service Ports inactivity timeout (secs) 54037 32-bit Integer
Modbus/TCP server Unit Id 54038 32-bit Integer
SCADAPack ER I/O Card Interface Points

SCADAPack ER I/O Card Configuration *6.F 148
56000 56181 16-bit Integer
SCADAPack ER Detected I/O Card ID Area 56200 56381 16-bit Integer / Read Only /
Configurable
(static poll only)
SCADAPack ER Detected I/O Card Version 56400 56581 16-bit Integer / Read Only /
Configurable (static
poll only)
SCADAPack ER I/O Card Status Area 56600 56781 16-bit Integer / Read Only /
*See SCADAPack E Operations Reference manual f or possible Configurable
v alues
IEC 60870-5-101 104 Slave Configurations *6.Q 57000 57299 16-bit Integer
151
57340 57369
Conitel Slave Configurations *6.S 151

57300 57326 16-bit Integer
AGA12 Security Mode *6.R 151

57600 16-bit Integer / Read Only
AGA12 Performance Counters *6.R 151
only)
DNP3 Event Counters *6.F 148

58000 58033 16-bit Integer / Read Only
IEC 61131-3 System Point 58500 This point has a value of 0 for Target 3
This point has a value of 1 for Target 5
Record Exchange Data *6.F 148
61000 62914 Mixed
RTU Read Write Status
Low Volts Alarm Level 63200 Floating Point

Local Time Offset from UTC (hours) *6.T 151
63201 Floating Point
Remote I/O Global Analog Change Deviation 63202 Floating Point
Ethernet Port Statistics (Not supported by 63250 63268 32-bit Integer

SCADAPack E)
RTU Licensed Features *6.V 151
Licensed Services Bit-mask 63300 32-bit Integer

License Expiry Date (seconds since 1970) 63301 32-bit Integer
DNP3 Additional Master config. points

DNP3 Master 2 Address 63350 16-bit Integer
DNP3 Master 3 Address 63351 16-bit Integer
DNP3 Master 2 Port No. 63360 16-bit Integer
DNP3 Master 3 Port No. 63361 16-bit Integer
DNP3 Master 2 Appl. Confirm Timeout (secs) 63370 16-bit Integer
DNP3 Master 3 Appl. Confirm Timeout (secs) 63371 16-bit Integer

DNP3 Master 2 Min. Unsol. TX Delay (secs) 63380 16-bit Integer
DNP3 Master 3 Min. Unsol. TX Delay (secs) 63381 16-bit Integer
DNP3 Master 2 Quiet Time Delay (secs) 63390 16-bit Integer
DNP3 Master 3 Quiet Time Delay (secs) 63391 16-bit Integer
DNP3 Master 2 Unsol. Allowed 63400 16-bit Integer
DNP3 Master 3 Unsol. Allowed 63401 16-bit Integer
Master 2 DNP3 Local Address 63410 16-bit Integer
Master 3 DNP3 Local Address 63411 16-bit Integer
Master 1 Disable Master Operation at Startup 63420 16-bit Integer
*6.A RTU Type
Model Type Analog System Point 50000 value

SCADAPack 312E -16312
SCADAPack ES - Model A -15855
SCADAPack ES - Model B -15871
SCADAPack ES - Model E -15743
SCADAPack ER - P600 -15870
SCADAPack ER - P620 -14846
*6.B Refer to the SCADAPack E Operational Reference manual.

*6.C Refer to the SCADAPack E Hardware User manual and SCADAPack E Operational Reference
manual.
*6.D PORT Settings

Port Function Values (Analog System Points 50100-50108)
* SCADAPack ER - P620 only
Function Port 0 Port 1 Port 2 Port 3 Port 4 Port 5* Port 6* Port 7* Port 8*
50100 50101 50102 50103 50104 50105 50106 50107 50108
NONE 0 0 0 0 0 0 0 0 0
ISaGRAF 1 1 1 1 1 N/A N/A N/A N/A
Cmd Line 2 2 2 2 2 2 2 2 2
ISaGRAF 2 3 3 3 3 3 N/A N/A N/A N/A
DNP3 9 10 11 12 13 14 15 16 17
PLC Device 19 19 19 19 19 19 19 19 19
PPP/TCPIP 29 30 31 32 33 N/A N/A N/A N/A

Function Port 0 Port 1 Port 2 Port 3 Port 4 Port 5* Port 6* Port 7* Port 8*
50100 50101 50102 50103 50104 50105 50106 50107 50108
ISaGRAF-User 49 50 51 52 53 N/A N/A N/A N/A
Remote I/O 60 61 62 63 N/A N/A N/A N/A N/A
TCP Service 80 81 82 83 84 N/A N/A N/A N/A
Modbus Slave 39 40 41 42 43 44 45 46 47
DNP VT Service 90 91 92 93 94 N/A N/A N/A N/A
IEC 60870-5-103 100 101 102 103 104 105 106 107 108
Master
IEC 60870-5-101 120 121 122 123 124 125 126 127 128
Slave
NTP GPS Receiver 130 131 132 133 134 N/A N/A N/A N/A
Conitel N/A N/A N/A N/A N/A 115 116 117 118
Port Mode Values (50110-50114)
Port Mode Value Comments
RS232 (Rts On) 2
RS422 3 available on Ports 2 and 3 only for SCADAPack ES

available on Ports 2,3,5-8 for SCADAPack ER
RS485 2w 4 available on Ports 1 and 2 for the SCADAPack 300E

available on Ports 2 and 3 only for the SCADAPack ES
Hayes Modem 9
RS232 (RTS Keyed) 11
RS485 4w Master 13 available on Ports 2 and 3 only for SCADAPack ES

RS485 4w Slave 14 available on Ports 2 and 3 only for SCADAPack ES

GPRS 19
RS232 (RTS Off) 20
1xRTT 21
Port Data Rates

(Analog System Points 50120-50124)
Value (bps)
300
600
1200
2400
4800
9600
19200
38400
57600
115200
Port Format Values (50130-50134)
Format Value
8-bit No Parity 0 (default)
8-bit Even Parity 1
8-bit Odd Parity 2
7-bit No Parity* 4
7-bit Even Parity* 5
7-bit Odd Parity* 6
* Not suitable for binary protocols such as DNP3 protocol, MODBUS RTU protocol, etc. Suitable for
User ASCII protocols, for example.
*6.E M ODEM M odes and Status

Modem Mode Values (50200-50204)
Modem Mode Value
Hang-up Enable 0
Hang-up Disable 1
Port Status Values (50210-50214) Port Connection State Values (50220-50224)

Port Status Value Connection State Value
No Modem 0 Modem Connected 1
Modem Failed 1 Modem Free 2
Modem OK 2
*6.F Refer to the SCADAPack E DNP3 Technical Reference manual.
*6.G DNP ROUTE Table
DNP Route Table Records

(100 record rows)
Analog Source Source Source Destin. Destin. Destin. Type / Lifetime
System PORT Start End Start End PORT Status (secs)
Point Node Node Node Node
50500
50508
…….. 0 to 0 to 0 to 0 to 0-32767
65535 65535 65535 65535
51292
Source PORT Values Destination PORT Values Type/Status Values
0--4 = PORT 0--PORT 4 0--4 = PORT 0--PORT 4 0 = Static / Offline
5 = ETHERNET 1 5 = ETHERNET 1 1 = Static / Online
6 = ETHERNET 2 6 = ETHERNET 2
(SCADAPack ES & SCADAPack ER (SCADAPack ES & SCADAPack ER only)
only)
10--13 = PORT 5--PORT 8 10--13 = PORT 5--PORT 8 256 = Dynamic / Offline

(SCADAPack ER - P620 only) (SCADAPack ER - P620 only)
254 = Any Port 257 = Dynamic / Online
255 = Table End 512 = Fixed / Offline
513 = Fixed / Online
Route Record Route Record Route Record AGA12 field *

Previous Destination* Connect No.* (100 record rows)
(100 record rows) (100 record rows)

Analog Previous String Connect Analog Security
System Destination System Number System
Point Com Index Point Point
50400 50300 57400
50401 50301 57401
…….. (Internal …….. ………
Value)
50499 50399 57499
* Each point in these tables corresponds to a record in the DNP Route Table.
Connect Number
Null terminated string, Maximum 25 characters. Default value = Null.
Represents connection number relevant to destination port. e.g. Hayes Modem number, IP
address, etc.
May contain alphanumeric characters & modem control characters (e.g. 0,12345678 = 0
<pause> 12345678, 192.168.0.249 = IP Address).
Valid IP Address Formats:
nnn.nnn.nnn.nnn IP address only: eg. 192.168.0.249
nnn.nnn.nnn.nnn:T use TCP transport eg. 192.168.0.249:T
nnn.nnn.nnn.nnn:U use UDP transport eg. 192.168.0.249:U
nnn.nnn.nnn.nnn:pppppU use UDP port number eg. 192.168.0.249:7001U
AGA12 (Security)
AGA12 Field
0 = None
1 = AGA12 Node
2 = AGA12 Gateway 1
3 = AGA12 Gateway 2
4 = AGA12 Gateway 3
5 = AGA12 Gateway 4
6 = AGA12 Gateway 5
For more information refer to the SCADAPack E Security Technical Reference Manual
*6.H Refer to the SCADAPack E Communication Interfaces Technical Reference manual

*6.J Refer to the SCADAPack E ISaGRAF Technical Reference manual and the SCADAPack E PLC
Device Interface manuals.
*6.K Refer to the SCADAPack E Data Processing Technical Reference manual

*6.L Default DNP3 IP Transport
0 = use UDP transport if not overridden in Route Table Connect Number
1 = use TCP transport if not overridden in Route Table Connect Number
*6.M Refer to the SCADAPack E TCP/IP Technical Reference manual
*6.N IP ROUTE Table

IP Route Table Records
(20 record rows)
Analog Dest IP Subnet Dest Gateway Metric
System Addr Mask Port IP
Point
54100
54105
54195
Destination Port (Interface) Values:

0-4 = PORT 0-4
5 = ETHERNET 1
6 = ETHERNET 2
*6.O Ethernet Configurations

Ethernet Interface Function
The following analog system points determine the primary functions of the Ethernet interfaces
Ethernet Interface 1
Point = 50140. (0 = only Remote I/O, 70 = TCP/IP + Remote I/O)
Ethernet Interface 2
Point = 50142. (0 = only Remote I/O, 72 = TCP/IP + Remote I/O)
Enabled IP Services (Requires Ethernet Function set to “TCP/IP + Remote I/O”).
The following IP Services are enabled when the value of the service is included in the sum of the enabled
IP services system point (50141).
Value IP Service name
0x0001 ISaGRAF/TCP
0x0002 Modbus/TCP Client
0x0004 Modbus/TCP Server
0x0008 Telnet Server
0x0010 FTP Server
0x0020 Not Used
0x0040 BOOTP Server
0x0080 NTP Network Time
0x0100 IEC 60870-5-104 Slave
*6.P Refer to the SCADAPack E Modbus Communication Interfaces manual

*6.Q Refer to the SCADAPack E IEC 60870-5-101 / 104 Slave Technical Reference manual
*6.R AGA12 Security System Points
Analog System Points
DNP Point Point Type Description Comment
57600 Analog AGA12 0 = No Security Enabled

Security Mode 1 = AGA12 Node RTU (non-Gateway)
2 = AGA12 Gateway RTU
57610 – 57616 Analog AGA12 Refer to the SCADAPack E Security

Performance Technical Reference for descriptions
Counters and possible values.
*6.S Refer to the SCADAPack E Conitel Slave Interface manual
*6.T UTC Offset is a float value (in fractions of an hour). For example, a value of 9.5 equates to an offset
of 9 hours, 30 min.
*6.V Licensed Services

System Analog point number 63300 represents a bitmask of the currently licensed services in the RTU.
The following table details the possible “licensed services” bitmask values.
Value RTU Service name

0x00000000 None
0x00000001 AGA Gas Calculations
0x00000002 DNP3 Data Concentrator
0x00000004 Dual Ethernet
0x00000008 ISaGRAF
0x00000010 TCP/IP
0x00000020 Supports Multiple DNP3 Masters
0x00000080 IEC60870-5-103 Data Concentrator
0x00000100 IEC60870-5-101 / 104 Slave
0x00000200 Conitel Slave
0x00000400 AGA12
0x00000800 Authentication SAv2
System Analog point number 63301 represents the expiry date of the license in “seconds since 1970”. A
zero value indicates that there is no expiry date, i.e. time unlimited license.
8.3 String System Point Map
Point Name Start End Point Type Max String Length

Range Range (incl. NUL)
TC PSTN Dial / IP Address String
(General Storage for ISaGRAF
Applications)
General Purpose String 50000 33
IP Address String / General Storage for

ISaGRAF Applications
Host IP Address (IP info for DNP/IP Hosts)

*1 154
Host IP Address 1 50020 Read Only 33
Target/Resource Name *2 154 *5 67

Target/resource 1 Application Name 50100 Read Only 16
Target/resource 2 Application Name 50101 Read Only 16
Configured Resource 1 Name 50110 Read/Write 16
Configured Resource 2 Name 50111 Read/Write 16
Configured Project Name 50120 Read/Write 64
Loaded Project Name 50121 Read Only 64
Workbench Solution File *5 154

50122 Read/Write 255
Modem Initialization String *3 154

Port 0 Modem Initialization String 50200 51
Modem Prefix String *3 154

Port 0 Modem Prefix String 50210 51

GPRS APN String *1 154

Port 0 Modem APN String 50220 51
Route Record Connect No. *3 154
Range 50300 50399 26
BOOTP Configuration Table *4 155
Range 50500 50539 18
Password Authentication Protocol Strings

*1 154
PAP Username 50600 71

PAP Password 50601 71
Device Information
Filename of last applied configuration 50730 255
Device Location 50731 255
Asset Number 50732 32
Device Name 50733 32
Firmware Release Name 50736 Read Only 201
*1 Refer to the SCADAPack E TCP/IP Technical Reference manual

*2 Refer to the SCADAPack E Operational Reference manual
*3 Refer to the SCADAPack E Communication Interface Technical Reference manual
*4 Refer to the BOOTP Configuration Records 155
*5 Refer to the SCADAPack E Configurator User manual
8.4 BOOTP Configuration Records

(20 record rows)
String
System Hardware Address IP Address
Point
50500
50502
… 000054A12104 192.168.1.242
… 00-00-54-A1-21-04
… 00:00:54:A1:21:04
50538
Alternative formats accepted for Hardware Address (Ethernet MAC address)


Configuration Technical Reference Manual

Uploaded by

Copyright:

Available Formats

Configuration Technical Reference Manual

Uploaded by

Document Information

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 Technical Reference Manual

Uploaded by

Copyright:

Available Formats

SCADAPack E Configuration

Part I Configuration Technical 5

5.3.9 Limit Transgression

©2013 Control Microsystems Inc.

Technical Support: The Americas

Technical Support: Europe

Technical Support: Asia

Technical Support: Australia

The addition of this symbol to a Danger or Warning safety label

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

BEFORE YOU BEGIN

Remove tools, meters, and debris from equipment.

Failure to follow these instructions can result in injury or equipment

OPERATION AND ADJUSTMENTS

RTU Start-Up & Configuration Revisions 22

SCADAPack ER I/O Configurations 26

The SCADAPack E RTU supports various point types.

Point Type may be one of the following:

4.2 I/O Numbering

4.2.1 Methodology & System Points

4.2.2 Physical I/O

Physical I/O numbering is subject to the following rules:

4.2.2.1 SCADAPack E Physical I/O Numbering

SCADAPack E Physical I/O Numbering

SCADAPack 300E Physical I/O Numbering

SCADAPack ER Physical I/O Numbering

4.2.2.2 SCADAPack ES Physical I/O Numbering

Main RTU Unit

SCADAPack ES DNP3 I/O Numbering

Model A 1..32 1..16 1..12 1..4 1..32

Model B N/A N/A N/A N/A N/A

Model E 1..16 1..8 1..6 1..2 1..16

Also see SCADAPack E RTU Hardware Manual.

4.2.2.3 SCADAPack ES Remote I/O Units

SCADAPack ES Remote I/O Units

SCADAPack ES Automatic Point Number Assignment

DIGITAL IN DIGITAL OUT ANALOG IN ANALOG OUT COUNTER

101..132 101..116 101..112 101..104 101..132

DIGITAL IN DIGITAL OUT ANALOG IN ANALOG OUT COUNTER

201..232 201..216 201..212 201..204 201..232

4.2.3 User Points

User Point numbering is subject to the following rules:

4.3 RTU Start-Up & Configuration Revisions

Failure to follow these instructions can result in death, serious

RTU Configuration Revisions

CONFIGURATION MAJOR REVISION NO.: System Analog Point 50050

When a Record Exchange modification is made by a Master Station or SCADAPack E Configurator

4.4 Configurations Becoming Active

Point Attributes and Properties Becoming Active

Configurations and ISaGRAF

4.5 SCADAPack E I/O Configurations

There are 2 steps in configuring the SCADAPack E configurations, i.e.

4.6 SCADAPack ER I/O Configurations

Table 4.1: Supported SCADAPack ER I/O Cards

32 Digital Inputs ER-32DI-A 32 (0x20) Yes

16 Relay Output ER-16DO-A 33 (0x21) Yes

16 Analog Inputs ER-16AI-A 34 (0x22) Yes

4 Analog Outputs ER-4AO-A 36 (0x24) Yes

There are 2 major stages in developing the SCADAPack ER configurations, i.e.

Figure 4.1: SCADAPack E Configurator - SCADAPack ER I/O Card Configuration