Configuration File Format

SCADAPack E Configuration
File Format
2 SCADAPack E Configuration File Format
Table of Contents
Part I Configuration File Format 3

1 Technical
...................................................................................................................................
Support 3
2 Safety ...................................................................................................................................
Information 4
3 Introduction
................................................................................................................................... 7
3.1 Full & Increm ental ..........................................................................................................................................................
Configuration, & Configuration File Generation 8
3.2 Im pact of Changing ..........................................................................................................................................................
Configuration Online 9
4 Configuration
...................................................................................................................................
File Format 11
4.1 Configuration..........................................................................................................................................................
File Syntax & Execution Output 12
4.1.1 Error and Warning
.........................................................................................................................................................
Messages 13
4.2 RTU Type & Model ..........................................................................................................................................................
Codes 15
4.3 Configuration..........................................................................................................................................................
File Batch Com m ands 17
4.3.1 PC - Create.........................................................................................................................................................
point 18
4.3.2 PE - Edit point.........................................................................................................................................................
& PD - Delete Point 20
4.4 Point Edit Attribute
..........................................................................................................................................................
Mnem onics 21
4.4.1 RQ, LG, & LGT ......................................................................................................................................................... 22
4.4.2 RN, FQ, RCP, .........................................................................................................................................................
RNC, NCP, DE, & TB 24
4.4.3 CTB, OR, UR, .........................................................................................................................................................
ZE, CS, IPN, & CEN 25
4.4.4 RTO, PL, ER, .........................................................................................................................................................
PDC, & TRI 26
4.4.5 AAS, OBT,.........................................................................................................................................................
IPS, DB, RRN, RFN, & DIA 28
4.4.6 CDE, CDT, .........................................................................................................................................................
CRZ, PTC, IOA, AL, & NCN 30
4.4.7 CVAL & ASDU ......................................................................................................................................................... 32
4.4.8 RSC, CYC ......................................................................................................................................................... 33
4.4.9 CTL & PR ......................................................................................................................................................... 34
4.5 Advanced Point ..........................................................................................................................................................
Edit Attribute Mnem onics 36
4.5.1 HTD - Trend .........................................................................................................................................................
Data 37
4.5.2 SLT - Config .........................................................................................................................................................
Lookup Table 38
4.6 Table Form at .......................................................................................................................................................... 39
4.6.1 RT - Route.........................................................................................................................................................
Table 40
4.6.2 PR, PRX, &.........................................................................................................................................................
IA 42
4.6.3 IR & BP ......................................................................................................................................................... 44
4.6.4 RD - Data Concentrator
.........................................................................................................................................................
Remote Devices Table 46
4.6.4.1 5000 Series I/O Modules .........................................................................................................................................
Remote Devices 48
4.6.5 PD - Data Concentrator
.........................................................................................................................................................
Remote Points Table 48
4.6.5.1 Notes for Remote.........................................................................................................................................
Points Table Configuration Entries 50
4.6.6 MR & TC ......................................................................................................................................................... 52
4.6.7 MIO - SCADAPack.........................................................................................................................................................
ER I/O Card Configuration Table 54
4.6.8 CT & PTX ......................................................................................................................................................... 55
4.6.9 IF & HT ......................................................................................................................................................... 57
5 Example...................................................................................................................................
Configuration File 59
Configuration File Format 3
I Configuration File Format
©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 TechnicalSupport@controlmicrosystems.com
Technical Support: Europe

Available Monday to Friday 8:30am – 5:30pm Central European Time
Direct Worldwide +31 (71) 597-1655
Email euro-support@controlmicrosystems.com
Technical Support: Asia

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

Inside Australia 1300 369 233
Email au.help@schneider-electric.com
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
The SCADAPack E RTU Configuration file is a human readable ASCII text file that enables the RTU to
build, modify, or restore the RTU configuration.
The configuration file can be created by a SCADA Master Station, or edited manually with a standard
text editor.
Additionally, a configuration file can be built within the RTU from the current RTU configuration.
The configuration file can be loaded or executed in the RTU in two possible ways, a complete or
incremental configuration. The file format and content is identical for the two configuration techniques,
the differences being the affect upon the RTU configuration. In both cases the configuration file is parsed
to test for a valid format, and if invalid, the configuration will not take place.
The Point Database is locked during execution of a configuration file and cannot be read from while
locked. Execution of the configuration will produce the file config.log, which will have the execution
result, and any errors encountered.
If any warnings or errors are written to the config log, one of the following values will be set in the RTU
Error Code:
Invalid File (1005) - execution not performed with error logged.
Valid File (1006) - execution completed with error or warning logged.
The error code will be set once only per execution.
3.1 Full & Incremental Configuration, & Configuration File Generation

Full Configuration
The RTU will perform a full RTU configuration from a previously loaded configuration file upon receiving
the following command through the RTU Command Line, or via a DNP3 File Exec command:
restart config <filename>
The filename parameter needs to end in .rtu for a full configuration.
A full configuration will disable configurable RTU points currently in the point database and set their Point
Data Class attribute to LOCAL, therefore keeping these points from generating alarms or events.
System points without configurable attributes, however, will not be cleared or altered unless specified in
the configuration file.
The configuration file will be decoded and points will be created as specified in the configuration file.
Points that are not specified will not be created. See the SCADAPack E Configuration Technical
Reference manual for further details on the effect of performing RTU re-configuration.
Incremental Configuration
The RTU will perform an incremental RTU configuration from a previously loaded configuration file upon
receiving the following command through the RTU Command Line, or via a DNP3 File Exec command:
restart config <filename>
The filename parameter needs to end in .inc for an incremental configuration.
An incremental configuration using the configuration file will not affect configuration points in the point
database unless specified within the configuration file. If a Point Delete command is given for a point,
this point will be disabled and have its Point Data Class Attribute set to LOCAL.
Configuration File Generation

The RTU will generate a configuration file for its current configuration upon receiving the following
command through the RTU Command Line, or via a DNP3 File Exec command:
getconfig <filename> [r|c]
The RTU will generate Point Create Commands for User and System Points with configurable attributes,
however, only the non-default attributes will be listed in the configuration file. Additionally, physical points
with non-default values will be listed in the configuration file. Read-Write and Read-Only system points
values will also be generated depending upon the flag set. The example configuration file at the end of
this document has had the comments added by hand. The RTU does not generate comments for
points.
The following combinations of the getconfig command are valid:
getconfig <filename> Configurable points and read-write system points values are written to the file.
getconfig <filename> c Configured points only will be written to the file.
getconfig <filename> r Configured points, read-write and read only system points values will be
written to the file.
3.2 Impact of Changing Configuration Online

Online RTU configuration changes are those changes that are made by writing a Full or
Incremental configuration file to an RTU. Configuration changes may result in the need to
apply one or more of the following restart types (also known as restart levels) to the RTU.
Depending on the method of configuration these may be prompted for or occur automatically,
for example through the SCADAPack E Configurator or through ClearSCADA.
Cold Reset
A cold reset (also known as a cold restart in DNP) is an orderly shutdown and restart of the
RTU and is the equivalent of cycling power to the RTU. Event data that is stored in the
outstation's DNP3 Event Buffer is retained. IEC60870 event data is lost.
A Cold Reset drops the outputs of the outstation. Binary outputs are turned off, and analog
outputs drop to their calibrated zero count (typically 4mA).
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 that would result in the RTU going off-line immediately, and being remotely
unrecoverable. E.g. serial port communication settings including function, mode, baud rates,
Ethernet port mode, IP address.
Other configuration changes that require a Cold Reset to activate include changes to IP
services, I/O module configuration and licence changes.
A Cold Reset causes initialization of data processing for alarm limits, change rates, etc. This
may result in generation of alarms that would normally be suppressed.
Config Restart
Configuration changes made through configuration files require a Config Restart before they
take effect in the RTU. The Config Restart command rebuilds the RTU point database using
the Full or Incremental configuration file information. When an RTU performs a Config
Restart:
New points created in the configuration file using the PC-Create Point command are
added to the RTU point database.
Point properties, or attributes of existing points edited in the configuration file using the
PE - Point Edit command are updated in the RTU point database.
Existing points deleted in the configuration file using the PD - Point Delete command
are removed from the point database.
A config restart command can use either a full configuration (*.rtu) file or an incremental
configuration (*.inc) file.
When the Config Restart uses an incremental file (*.inc) and changes are limited to PC-Point
Create and PE-Point Edit commands that do not use certain attributes then the changes are
applied with only a minimum of disruption to RTU services. The Trend Sampler will be
restarted and points mentioned in the incremental (*.inc) file will be reprocessed but the
remainder of the point database will go untouched. Configuration file changes that include the
following attributes or that go beyond point creation and point edits may result in initialization
of point processing such as alarm limit and change-rate tracking. This may result in
generation of alarms that would normally be suppressed. To avoid re-initialization of data
point processing, restrict online configuration changes to simple point edits, and point
creation. Configuration changes on a point will always result in its No Change alarm being
cleared.
Table 7.1: Point Attributes that Reinitialize Data Point Processing.
PR Profile Number
PDC Point Data Class
HTD Sampler Trend Data
RSC ER I/O Rack, Slot, Channel
CTL Conitel Configuration
IOA IEC60870-5 Information Object Address
ASDU IEC60870-5 ASDU Data Type
CYC IEC60870-5 Cyclic Data
PTC Digital Output Trip Close Partner Point
OBT DNP Static Object Type
Any points that are deleted in a configuration change, and which are currently in use by
ISaGRAF (target) applications, are not fully deleted from the outstation's configuration
until the outstation is Cold Reset.
ISaGRAF Restart
ISaGRAF (target) applications in the outstation are restarted.
An ISaGRAF (target) restart drops any outputs of the outstation that are controlled at the time
the application is restarted. Binary outputs are turned off, and analog outputs drop to their
calibrated zero count (typically 4mA). Points with active interlocks (see Configure an Output
Point or Pulse Action's Interlock Properties) do not drop their outputs.
Profile Restart
The RTU Profiler task is restarted. This causes profile files to be reprocessed and is
performed after new profiles are loaded to the RTU
Warm Reset
The RTU DNP3 driver is restarted. Event data that is stored in the RTU DNP3 Event Buffer is
retained. The DNP3 protocol state is initialized. This results in the RTU reporting "Outstation
Restarted" in the DNP3 Internal Indication status. The RTU may send a startup unsolicited
message and may request a time update from the master station. A Warm Reset on the
DNP3 driver is required to apply changes to the DNP3 protocol settings (e.g. timeouts, link
layer modes, event settings).
IEC60870 restart
The RTU 60870-101 and 104 drivers are restarted. IEC60870 event data is lost. 104 sockets
are disconnected and 101 connections will require a reset link command before
communications resume.
4 Configuration File Format

The format for the configuration file adheres to the following format rules:
Each command is on a separate line
Each edited attribute of an entity is a separate command
Blank lines are allowed
Tab, space and comma characters are treated as white space in a line
In a line, one or more white space characters may precede the command (the command being
one of RC, RE, TE, ... , etc.)
Each command and operand needs to be separated by one or more white space characters
To include white space characters into an operand (e.g. a point comment or dial string) the
whole operand is enclosed in double-quotes, e.g. CO "High lift pump 1"
To include a double-quote character into an operand, two double-quotes are used,
e.g. CO "Press the ""Panic"" button"
Unless occurring within a parameter that is enclosed in double-quotes, a # character preceded
by a white-space character indicates that the rest of the line is not to be processed (E.g.
comments).
A line following a line ending with a backslash \ character is treated as a continuation line
provided the backslash character is preceded by a white-space character.
Lines of text other than comments need to be less than 80 characters. Commands that require
80 characters or more need to use the continuation character previously described. If a line is
greater than 80 characters in length, unless caused by a comment before the 80th character, a
“line too long error” is logged in the configuration log and the characters after the 80th will be
ignored.
Upper and lower case may be used as desired for commands and operands. Where rules
apply, an operand's case is automatically forced when processed.
4.1 Configuration File Syntax & Execution Output

Configuration File Syntax
The syntax for the configuration file commands is listed in the sections for Batch Commands, Point
Attributes, and Tables. The following nomenclature is used to facilitate the syntax description.
Operator mnemonics are shown in bold (e.g. PC, PE, etc.).
Operands are as shown or are enclosed in angular brackets (e.g. <TableName>) in which case
they are substituted with the appropriate values by the user (the angular brackets are not part of
the syntax).
Choices are shown separated by the | character (e.g. Y|N means text string “Y” or “N” are the
only valid values.
Square brackets [] indicate an optional operand.
Configuration File Execution Output

The execution of a configuration file produces a file in the RTU file system called “CONFIG.LOG” which
gives the result of the execution and any errors or warnings encountered. The output file may contain
some of the following error or warning messages proceeded by a line number, if applicable, where the
error occurred.
To view the CONFIG.LOG file, send a TYPE command at the RTU Command Line, or examine the file
after up-loading it via the RTU’s DNP3 communication channel using the SCADAPack E Configurator on
a PC.
4.1.1 Error and Warning Messages
The following error and warning message can result from the RTU activating a configuration file. The
message may appear on the RTU diagnostic stream, or be contained in the config.log configuration log
file.
“Command line too long”
“Non matching TE block”
“Command not found”
“Internal error”
“Failed to create entity”
“Failed to edit entity”
“Failed to delete entity”
“Invalid attribute for point”
“Unknown configuration table”
“Too few parameters”
“Too many parameters”
“Invalid point range”
“Point is read only”
"Invalid Attribute Value"
“Unable to Open file <filename>”
“# Rebuilding Configuration at <time> on <date>”
“# Updating Configuration at <time> on <date>”
“File is valid. Rebuilding Configuration”
“File is valid. Updating Configuration”
“File <filename> is not valid. Rebuild Skipped"
“File <filename> is not valid. Update Skipped"
“Configuration Rebuild Pass”
“Configuration Rebuild Fail”
“Configuration Update Pass”
“Configuration Update Fail”
If an attribute is entered over more than one text line, through the use of a continuation character, and
the value for that attribute is invalid, a command error will also be logged for the remaining values of that
command appearing on each line. For example consider the following command:
PE AI 1 #edit the integer to analog conversion parameter

ER -3.40282e+040 \ # eng min is out of range
3.40282e+038 \ # eng max
-2147483648 \ # raw min
2147483647 # raw max

PDC C1T #set point data class
TE
Even though EngMin is the only attribute that is out of range, and thus invalid, the whole ER command is
unusable. The remaining values of the ER command are on new lines and so will be logged with
command errors. In this example, the PDC command will be processed as valid and the point will have
only the point data class attribute changed. See Create Point and Edit Point commands for more details
on invalid attribute values.
For RTU firmware versions 7.4-4 and later a warning is generated in the config.log file when a point does
not exist only for the first invalid System point encountered per PR or PRX Point Record Table entry in a
configuration file. These warnings are typically benign and are caused by the SCADAPack E
Configurator trying to configure System points that have been added to later versions of firmware to
support new features.
4.2 RTU Type & Model Codes

SCADAPack E Configurator write the RTU Model and RTU Type codes into their config files. This
information is not used by the RTU itself, but is used by the SCADAPack E Configurator to show or hide
some property pages and to present the correct number and types of Physical points for the model of
RTU.
To minimize the impact on older versions of SCADAPack E Configurator software and RTU firmware, the
codes are written with a comment block (i.e. after a ‘#” character). The code identifiers are case
sensitive, but may be written on the same line (respecting the 80 character line limit).
The codes need to occur before the first batch command appears in the file. White space between the
last identifier string character and the code is ignored.
The code identifiers are as follows:
File Version
The code identifier string is “FILE_VER:” (without quotes). This is to identify future versions of the RTU
Configuration File Format. The current version is 1.
RTU Type
The code identifier string is “RTU_TYPE:” (without quotes). This is to identify the major “family” of
supported RTU’s. The valid codes are below:
RTU Type Type Code
Unknown 0
SCADAPack ES 1
SCADAPack ER 2
SCADAPack 350E 4
SCADAPack 357E
SCADAPack 330E 5
SCADAPack 333E
SCADAPack 334E
SCADAPack 337E
SCADAPack 312E 6
SCADAPack 313E
SCADAPack 314E
RTU Model
The code identifier string is “RTU_MODEL:” (without quotes). This is to identify the exact model of
supported RTU. The valid codes are below:
RTU Model Model Code

Unknown 0
SCADAPack ES ‘A’ Model 1
SCADAPack ES ‘B’ Model 2
SCADAPack ES ‘E’ Model 4
SCADAPack ER-P600 10
SCADAPack ER-P620 11
SCADAPack 350E 30
SCADAPack 357E 31
SCADAPack 330E 32
SCADAPack 334E 33
SCADAPack 314E 34
SCADAPack 312E 35
SCADAPack 313E 36
SCADAPack 333E 37
SCADAPack 337E 38
Example File Header

An example config. file header is shown below:
# RTU Generated Configuration File
# Generated at 09:37:05 on 30-11-2007
# FILE_VER: 1 RTU_TYPE: 4 RTU_MODEL: 30
SLT RT #Route Table
TE
4.3 Configuration File Batch Commands

In addition to generic “Create Point”, “Edit Point”, and “Delete Point” commands, the RTU configuration
file permits configuration of Tables for system points, such as the RTU Route Table. The Syntax for
configuration file commands is described in the following sections:
PC - Create Point
PE - Edit Point & PD - Delete Point
4.3.1 PC - Create point
Syntax:
PC [< RTUname >\< PointName > < MasterStationPointType>] <RTUPointType> [DB]
Configuration point attributes # Point attributes
TE # End of Block
Where: MasterStationPointType = AN|IN|ST|DS|RTU + R|D|C
e.g. ANR AND ANC STR STD RTU
and: RTUPointType = DI|DO|AI|AO|CI|DU|AU|DSY|AS
Example:
PC TEST_RTU\ANALOGREAL1 ANR AI # Real Analog Input
PC TEST_RTU\REALOUTPUT1 RTU DO # Digital Output (applicable to RTU only)
PC TEST_RTU\PUMP_RUN_LAMP STR DU # TC Real Input, RTU User Point
PC TEST_RTU\PUMP_RUN_LAMPO RTU DO # RTU Output for LAMP
The optional [< RTUname >\< PointName > < MasterStationPointType>] fields are provided for Master
Station configuration information only. They are ignored by the RTU, and not produced when an RTU
generates a configuration file.
The RTUPointType denotes the point type at the RTU, being one of:
DI = Digital Physical Input
DO = Digital Physical Output
AI = Analog Physical Input
AO = Analog Physical Output
CI = Counter Physical Input
DU = Digital User (derived) point
AU = Analog User (derived) point
DSY = Digital System point
AS = Analog System point
Optional operand DB defines the point as a double status point, which is only valid for digital physical
and digital user point types (DO|DI|DU). Point Create using this operand will require the use of the RN
attribute command with 2 point number arguments for the double status points (See Section RN, FQ,
RCP, RNC, NCP, DE, & TB (RN - Point Number) for more information).
The use of the optional master station fields is Master Station dependent, but useful where the Master
Station can be configured from the same configuration file as the RTU. This format specifies the Master
Station Point Type to be specified first followed by the point type for the RTU. If the point type is RTU
then this point is only applicable to the RTU. The Master Station could ignore this point definition. The
use of both <MasterStationPointType> and <RTUPointType> fields in the point definition permits
independent mapping of RTU and Master Station point types. For example, RTU User and System
Points can be mapped to Master Station “real” points to support outputs to RTU derived points and RTU
system points.
Each Create Point block needs to have a matching end of Block mnemonic (TE) and Point Number (RN)
before another point is created or edited. Point Attributes and Properties are set to the default condition
(except for the Current Point State, or Current Integer and Engineering Values). This is true if the Point
Attributes and Properties are not defined, have insufficient parameters, or have invalid values within the
Point Create block. In addition, attributes with invalid or insufficient parameters are logged as warnings.
Configuration point attributes that are not valid for the point type will be ignored, however Create Point
command without a matching end block will render the configuration file invalid and will not execute. The
operands <RTUname>, <PointName>, and <MasterStationPointType> will be ignored by the RTU and
will not be generated from a configuration generated by the RTU. Configuration point default attributes are
defined in the SCADAPack E Configuration Technical Reference manual.
Current Point State (for Binary points) or Current Integer and Engineering Values (for Analog points) will
be retained if the point already exists in the RTU’s point database.
Note: Create Point deletes Trend Record entries associated with the point, as well as initializing
attributes to default values. Trend configurations must be explicitly redefined as part of the
Create Point command. See Section HTD – Trend Data
4.3.2 PE - Edit point & PD - Delete Point
PE - Edit Point
Syntax:
PE [< RTUname >\< PointName > <MasterStationPointType>] DI|DO|AI|AO|CI|DU|AU|DSY|AS
<pointNumber>
Configuration point attributes # Point attributes
TE # End of Block
The flags denote the point type and number (see Point Create for further details.) Operand
<pointNumber> is required in order to identify the point. Each Edit Point block needs to have a
matching end of Block mnemonic (TE) before the point is edited. Points will be created if they are not
existing. Only attributes defined within the Edit Point block will be altered. Point properties and attributes
not defined, have insufficient parameters, or have invalid values within the Edit Point block will remain
unchanged; attributes with invalid or insufficient parameters, however, will be logged as warnings.
Configuration point attributes that are not valid for the point type will be ignored, however, Edit Point
command without a matching end block will render the configuration file invalid and will not execute. The
operands <RTUname>, <PointName>, and <MasterStationPointType>, will be ignored by the RTU.
Edit Point does not modify Trend Record entries associated with the point, unless explicit trend data
configurations are part of the Edit Point block. Where a Trend Data block is present in the Edit Point
block, existing Trend Records are deleted prior to adding the listed trend data. See Section HTD –
Trend Data. Edit Point will remove associated trend records for a point where an empty Trend Data
block is configured within the Edit Point block.
PD - Delete Point
Syntax:
PD [< RTUname >\< PointName >] DI|DO|AI|AO|CI|DU|AU|DSY|AS <pointNumber>
Point Delete will disable a single point and set the Point Data Class attribute to Local, thus disabling
alarm and event generation on that point. The Point will be deleted from memory when the RTU restarts.
The operands <RTUname> and <PointName> will be ignored by the RTU. The effect on the RTU due to
Deletion of points is described in the SCADAPack E Configuration Technical Reference manual.
Deletion of a double status point will result in both points being deleted. Trend Records associated with
the point are also deleted.
4.4 Point Edit Attribute Mnemonics

The batch mnemonics defined in the following sections edit point attributes.
RQ (Rate of Rise), LG (Limit Alarm/Event Generation), & LGT(Limit Generation Triggered)
RN (Point Number), FQ (Rate of Fall Value), RCP (Period Used for Rate of Rise/Fall), RNC (Rate
of No Change Value), NCP (Period Used for Rate of No Change), DE (Value Deadbnd), & TB
(Time Deadband)
CTB (Clear Time Deadband), OR (Over Range), UR (Under Range), ZE (Zero Threshold), CS
(Change Scan Alarm), IPN (Interlock Point Number), & CEN (Counter Limit Exceeded Point
Number)
RTO (Remote Interlock Timeout), PL (Status Output Configuration/Pulse Length), ER (Integer to
Analog Conversion), PDC (Point Data Class), & TRI (Trend Inhibit)
AAS (Alarm Active State), OBT (DNP Static Object Type), IPS (Invert Point State), DB (Debounce
Time), RRN (Rate of Rise Point Number), RFN (Rate of Fall Point Number), & DIA (Drop Output
on Interlock Active)
CDE (Analog Change Deviation), CRZ (Counter Reset to Zero), PTC (Trip Close Partner Point
Number), IOA (IEC870 Information Object Address), AL (Alarm Limist), & NCN (No Change Point
Number)
CVAL (Point Current Value) & ASDU (IEC870 ASDU Type)
RSC (Rack Slot Channel), CYC (IEC870 Cyclic Scan)
CTL (Continel Slave Configuration) & PR (Profile Number)
4.4.1 RQ, LG, & LGT
RQ - Rate of Rise Value:

RQ <float value>
Sets the rate of rise attribute for analog input and analog derived points.
Default = 100.0
LG - Limit Alarm/Event Generation:

LG <4Lg> <3Lg> <2Lg> <1Lg> <1Hg> <2Hg> <3Hg> <4Hg>
or
LG <Hgt>
Where “g” is one of:
E = Event
A = Alarm
N = None
“E” or “A” sets the Analog Input point’s or Analog Derived point's “Alarm Limit Transgression” attribute to
TRUE for the corresponding alarm limit. “N” sets the attribute to FALSE.
If <Hgt> for a Counter Point is “N”, the Counter limit will be set to zero i.e. no generation
Default for Analog = NNNNNNNN (the 8 limit transgression attributes set to FALSE)
Default for Counter: No default. Alarm Limit for point determines event generation.
LGT - Limit Generation Triggered:

LGT <4Lg> <3Lg> <2Lg> <1Lg> <1Hg> <2Hg> <3Hg> <4Hg> <Qg> <Dg>
or
LGT <Dg> (Binary and Counter point types)
Where “Q” specifies the “Point Quality Change” event type (eg. OverRange/UnderRange), “D” specifies
the Point’s “Current Value” Deviation or “Current State” change event type and “g” is one of:
Y = Triggered Events
N = Buffered Events
“Y” sets a Point’s “Limit Generation Triggered” attribute to TRUE for the corresponding alarm limit, Point
Quality change or Deviation event. This will cause events generated for one of the above reasons to be
“Triggered” type events.
“N” sets the attribute to FALSE, events for the specified alarm limit, Quality Change or Deviation will be
of “Buffered” type.
Default for Analog Point = NNNNNNNNNN (the 8 limit transgression attributes, Point Quality Change and
Deviation set to Buffered).
Default for Counter and Binary Point = N (Change of State events set to Buffered).
For backward compatibility reasons, if the LGT mnemonic is omitted for a Point, the "Point Data
Class" (PDC) Triggered/Buffered setting will determine the setting of the LGT arguments for the Point.
The PDC/LGT mnemonics are not order dependent in the configuration file.
When writing a new RTU configuration file, for backward compatibility reasons, the “Point Data
Class” (PDC) Triggered/Buffered setting (eg. “C1T”, “C1B”) should match the state of the LGT “Current
Value” Deviation or “Current State” change argument (last parameter).
4.4.2 RN, FQ, RCP, RNC, NCP, DE, & TB
RN - Point Number:
Syntax:
RN <number> [pointNumber 2]
This needs to exist for each Point Create block. The second Optional point number is valid only for
double status points. A second point number needs to be greater than the first number. This attribute is
not valid for PE configuration batch commands.
FQ - Rate of Fall Value:

FQ <float value>
Sets the rate of fall attribute for analog input and analog derived points.
Default = 100.0
RCP - Period Used for Rate of Rise/Fall:

RCP <integer>
Sets the Rate of change period for analog input and analog derived points in seconds.
Default = 0
RNC - Rate of No Change Value:

RNC <float>
Sets the No Change Value for analog input and analog dervied points.
Default = 0.0
NCP - Period Used for Rate of No Change:

NCP <integer>
Sets the No Change Time attribute for analog input and analog derived points in seconds.
Default = 0
DE - Value Deadband:
DE <float>
Sets the absolute Value Deadband before Event or Alarm is Cleared for Analog Input and Analog Derived
points.
Negative numbers will be converted to positive numbers.
Default = 0.0
TB - Time Deadband:
TB <integer>
Sets the Time Deadband in seconds before an Alarm or Event is generated for Digital Input, Binary
Derived, Analog Input and Analog Derived points in seconds.
Default = 0
4.4.3 CTB, OR, UR, ZE, CS, IPN, & CEN
CTB - Clear Time Deadband:

CTB <integer>
Sets the Time Deadband out of alarm attribute for digital and analog points in seconds.
Default = 0
OR - Over Range:
OR <float>
Sets the Over Range Limit Attribute for analog input and analog derived points.
Default = FLT_MAX (where FLT_MAX = 3.402823e+038)
UR - Under Range:
UR <float>
Sets the Over Range Limit Attribute for analog input and analog derived points.
Default = -FLT_MAX (where FLT_MAX = 3.402823e+038)
ZE - Zero Threshold:
ZE <float>
Sets the Zero Threshold Limit for analog input and analog derived points.
Default = -FLT_MAX (where FLT_MAX = 3.402823e+038)
CS - Change Scan Alarm:

CS Y|N
Sets the Alarm Inhibit common point attribute. A “Y” signifies Alarm Inhibit is set false, while a “N”
signifies Alarm Inhibit as true.
Default = Y
IPN - Interlock Point Number:

IPN <integer>
Sets the Remote Control Enabled Interlock point number.
Default = 0
CEN - Counter Limit Exceeded Point Number:

CEN <integer>
Sets the binary point number that is set to the Counter Limit Exceeded property (for counter points).
Default = 0
4.4.4 RTO, PL, ER, PDC, & TRI
RTO - Remote Interlock Timeout:

RTO <integer>
Sets the Interlock Alarm Timeout attribute in Seconds.
Default = 600 (ie. 10 minutes)
PL - Status Output Configuration/Pulse Length

PL <integer milliseconds>
Sets the Digital point Output Pulse Time attribute in milliseconds.
Default = 0
ER - Integer to Analog Conversion:

ER <MinEng float> <MaxEng float> <MinRaw integer> <MaxRaw integer>
Sets the Integer to Engineering Values for analog points. Valid for both input and output points. Output
scale specified in the deprecated output point scale mnemonic “OU” is ignored.
Default = 0.0, 100.0, 0, 10000
PDC - Point Data Class:

Syntax:
PDC Master1 [Master2] [Master3]
Where "Master1" is one of:
C0S = Class 0 static
C1T = Class 1 event triggered
C1B = Class 1 event buffered
CL = Local
Where optional parameters "Master2" and "Master3" are one of:

C0 = Class 0 static
C1 = Class 1 event
C2 = Class 2 event
C3 = Class 3 event
CL = Local
Default for Masters = CL
TRI - Trend Inhibit:

TRI Y|N
Sets the Trend Inhibit common point attribute. A “Y” signifies Trend Inhibit is set true, while a “N”
signifies Trend Inhibit is set false.

Default = N
4.4.5 AAS, OBT, IPS, DB, RRN, RFN, & DIA
AAS - Alarm Active State:

AAS <integer>
Sets the Alarm Active state for digital points. If value is non zero, Alarm Active state will be set to true,
otherwise it will be set to false.
Default = 1
OBT - DNP Static Object Type

OBT <object type> <variation>
Sets the DNP Object Type point attribute. Operands <object type> and <variation> are both integer
values.
Default: DI = 1 1; DO = 10 2; DU = 10 1; DSY = 10 1; AI = 30 1; AO 40 1; AU = 30 1;
AS = 30 1; CI = 20 1
IPS - Invert Point State:

IPS Y|N
Sets the Invert Point State for Digital Points. Y signifies true.
Default = N
DB - Debounce Time:
DB <integer>
Sets the debounce time in milliseconds for Physical Digital Input Points.
Default = 0 ms
RRN - Rate of Rise Point Number

RRN <integer>
Sets the binary point number that is set to the Rate of Rise Exceeded property (for analog input and
analog derived points).
Default = 0
RFN - Rate of Fall Point Number:

RFN <integer>
Sets the binary point number that is set to the Rate of Fall Exceeded property (for analog input and
analog derived points).
Default = 0
DIA - Drop Output on Interlock Active:

DIA Y|N
Sets the “Drop Output on Interlock Active” Digital point attribute. A “Y” signifies the attribute is set true,
while a “N” signifies it is set false.
Default = N
4.4.6 CDE, CDT, CRZ, PTC, IOA, AL, & NCN
CDE - Analog Change Deviation:

CDE <integer>
Sets the Change Deviation Event for analog input and analog derived points (value being a float) and
Counter points.
CDT - Analog Event Deviation Type:

CDT <Type>
Where "Type" is one of the following enumerated values:
Percentage of = 0
Span
Absolute = 1
Integration = 2
None = 3
Default = 0
Sets the Event Deviation Type for analog input and analog derived points only. Introduced with firmware
version 7.82.
CRZ - Counter Reset to Zero:

CRZ Y|N
Sets the Counter Reset attribute for integrated points. Operand “Y” signifies the Counter will be reset to
zero upon RTU power-up or Cold-Reset, while “N” signifies the counter will retain the value reached
before power-down.
Default = N
PTC - Trip Close Partner Point Numbers:

PTC <integer>
Sets the Trip Close Partner Point Number attribute for binary points. This attribute is applicable to point
database binary point types except Physical Digital Inputs.
Default = 65535
IOA - IEC870 Information Object Address:

IOA <integer>
This attribute is only applicable to IEC 60870-5-101 and 104 Slave Configurations.
Associates the configuration point number (with a given DNP point number) to a unique Information
Object Address, which is a unique 16-bit object identifier in the IEC 60870-5-101 and -104 protocols.
Default = 0. Valid Range for this field is 0 – 65535.
AL - Alarm Limits:
AL <4Llimit> <3Llimit> <2Llimit> <1Llimit> <1Hlimit> <2Hlimit> <3Hlimit> <4Hlimit>,
or
AL <Limit>
Analog input, Analog derived and Counter Points only. <xxLimit> is a floating-point value for Analog
points and sets the Analog 4 high and 4 low engineering limits. <Limit> is an integer value for Counter
points and sets the High Counter Limit for Counter Points.
The following restrictions apply to the alarm limit values:
4L <= 3L <= 2L <= 1L <= 1H <= 2H <= 3H <= 4H
Default for Analog = -FLT_MAX, -FLT_MAX, -FLT_MAX, -FLT_MAX, -FLT_MAX, -FLT_MAX, -FLT_MAX, -
FLT_MAX (where FLT_MAX = 3.402823e+038), and
Default for Counter = 0 (No Generation)
NCN - No Change Point Number:

NCN <integer>
Sets the No Change property binary point number for analog input and analog derived points.
Default = 0
4.4.7 CVAL & ASDU
CVAL - Point Current Value

CVAL <integer or float value>
The Point Current Value mnemonic is used to set a point’s Current Value or State from within a
configuration file. Valid for DO, AO, DU, AU, DSY and AS RTU point types and can be used within
either a “PC” Point Create or “PE” Point Edit block.
For AO, AU and AS analog RTU point types, the “value” parameter is interpreted according to the point’s
OBT - DNP Static Object Type attribute. If the DNP Static Object type is a floating point type, the
“value” parameter will be interpreted as a float value and will be used to set the point’s Current
Engineering Value. Alternatively, should the DNP Static Object type be an integer point type, the “value”
parameter will be interpreted as an integer value and will be used to set the point’s Current Integer Value.
The following are some examples of the CVAL command:
PC AU # Analog User Float
RN 1000
OBT 30 5
CVAL 123.456
TE
PC AU # Analog User integer object type
RN 1001
OBT 30 1
CVAL 40000
TE
PC DU # Digital User, state set to ‘on’
RN 1000
CVAL 1
TE
PC DU DB # Digital User Double status
RN 1001 1002
OBT 1 2
CVAL 2
TE
For Double Status points, the lowest point no. of the pair will be used for the most-significant bit of the
numeric point value.
ASDU - IEC870 ASDU Type

ASDU <integer>
This attribute is only applicable to IEC 60870-5-101 and -104 Slave Configurations.
Associates the configuration point number (with a given DNP point number) to an ASDU type.
The default values are dependant on the point type, and are listed as follows
Default: DI = 1; DO = 45; DU = 1; DSY = 1;
AI = 11; AO = 49; AU = 11; AS = 11;
CI = 15;
4.4.8 RSC, CYC
RSC – Rack Slot Channel:

RSC <0> <Slot Number> <Channel Number>
This attribute is only applicable to SCADAPack ER Configurations.

Associates the configuration point number (with a given DNP point number) to a physical I/O channel on
the SCADAPack ER rack. The specific I/O channel is uniquely identified by the 3 required fields, i.e. 0,
slot, and channel.
The first field is reserved and should be 0.
The <Slot Number> field specifies which slot (on the specified rack) on which the channel is located.
1 = I/O Card Slot 1
2 = I/O Card Slot 2
... and so on.
Valid Range for this field is 1 – 13.
The <Channel Number> field specifies the individual channel on the specific I/O slot .
1 = the first I/O channel on the I/O card
2 = the second I/O channel on the I/O card
... and so on.
Valid Range for this field is 1 – X. (whereby X = the max. number of channels for the specific card type)
The following is an example of the RSC command:
PC DI # Physical Digital Input Point
RN 232
RSC 0 2 32
TE
This example would associate Physical Digital Input 232 with the 32nd input channel on the DI card
which is located in slot 2 of the local rack.
CYC - IEC870 Cyclic Scan:

CYC Y|N
This attribute is only applicable to IEC 60870-5-101 and 104 Slave Configurations.
Sets the “IEC870 Cyclic” attribute for Analog Points, i.e. the analog point will be included in CYCLIC
scan IEC 60870-5-101 and 104 responses. This attribute is only valid for analog point types. Y signifies
true.
Default = N
4.4.9 CTL & PR
CTL - Continel Slave Configuration

CTL <Station No.> <Group No.> <Function Type> <Conitel Type> <Frame> <Bit> <Opt>
This attribute is only applicable to Conitel Slave configurations on a SCADAPack ER - P620.
Sets the Conitel Slave attributes for the associated point.
The <Function Type> field specifies which function the Conitel Slave will support on the associated
Station/Group combination.
0 = Scan Function
1 = Trip/Close Function
2 = Raise/Lower Function
3 = Analog Setpoint Function
4 = Baker Reset Function
The <Conitel Type> field specifies what Conitel type this point is.
1 = 1-bit binary
2 = 2-bit MCD A-type
3 = 2-bit MCD B-type
4 = 2-bit MCD C-type
5 = 12-bit signed analog
6 = 12-bit unsigned accumulator
7 = 24-bit unsigned accumulator
8 = Trip/Close point
9 = Analog Setpoint
10 = Raise/Lower point
12 = Reset Point
The <Frame> field specifies what Conitel frame this point is located in.
Valid Range for this field is 1 – 31.
The <Bit> field specifies which bit in the associated frame this point is located in.
Valid Range for this field is 0 - 11.
The <Opt> field specifies different attributes depending on the point type.
For a binary point type this represents the SOE ID. Valid Range for this field is 1 - 127.
For a analog setpoint type, this represents the Setpoint A or B. Setpoint A is set a value of 0, and
setpoint B is a value of 1.
PR - Profile Number:
PR <profile number>
Sets the Profile Number, which is a common point attribute, to the value <profile number>.
Default = 0.
4.5 Advanced Point Edit Attribute Mnemonics

The following point edit attribute mnemonics specify advanced trending and communication parameter
configurations:
HTD - Trend Data
SLT - Config Lookup Table
4.5.1 HTD - Trend Data
HTD
[Trend Record 1]
[Trend Record 2]
[…]
[Trend Record 99]
TE
Trend records are defined within the PointCreate (PC) or PointEdit (PE) command block, with each
record defined as follows:
<TrendStatisticType> <TrendTriggerPoint> <TrendPeriod> <Deviation>
Operand CV|AV|MX|MN|CT|STC|RA|SUM|ALC|IG|DR|DV defines the Trend Statistic Type.
Currently supported TrendStatisticType operands are: CV-Current Value, AV-Average Value for Period,
MX- Maximum for Period, MN-Minimum for Period, CT-Counter Change trend, and STC-State Count for
digital (digital CV trend).
The following Trend Statistic Types are not currently supported and will be ignored:
RA - running average, SUM - summation, ALC - alarm count, IG - Integrated, DR - Derivative, DV -
Deviation.
Operand <TrendTriggerPoint> Trend Trigger DNP Binary Point number

Operand <TrendPeriod> Trend Period in seconds, valid range: 1 sec to 231 secs.
Operand <Deviation> Deviation value used for Trend file compression interpreted as an integer
The entire list of trend record information needs to be defined within the one HTD block structure, each
record on a single line. Records are defined from 1 (one) to the number of trend records defined for the
point, up to a maximum of 99 per point. Record numbers cannot be skipped and needs to start at 1.
Records not defined within the HTD block will no longer be sampled. Trend records for Double status
points are defined only once.
The following rules apply to the use of HTD blocks:

Create Point “PC” deletes existing trend records associated with the point and “HTD” block(s)
must be present to reconfigure trends
Edit Point “PE” does not modify existing trend records associated with the point if no “HTD”
block is present within the “PE” block
Edit Point “PE” deletes existing trend records associated with the point if an “HTD” block with no
trend record data is present
Edit Point “PE” deletes existing trend records associated with the point and adds new trend
records where an “HTD” block is present within the “PE” block
4.5.2 SLT - Config Lookup Table
SLT RT|HT|TC|PT|PR [<arguments>]

Table Values #
TE # End of Block
The operand and arguments represent configuration tables within the SCADAPack E RTU.
The Tables defined are as follows:
RT -- Route Table
PR -- System configuration point range
PRX -- System configuration Extended point range
IA -- TCP/IP IP Address Table
IR -- TCP/IP Route Table
BP -- BOOTP Table
RD -- Data Concentrator Remote Devices Table
PD -- Data Concentrator Remote Points Table
HT -- Hayes Modem page
TC -- TC Identification number, X25 address, and PSTN Dial String
PT -- The RTU port configurations
PTX -- The RTU Extended port configurations
These tables are defined in the following section. Invalid tables will be ignored, however, tables without a
matching end block will render the configuration file invalid and will not execute.
4.6 Table Format

The following formats apply to specific RTU data tables:
RT - Route Table
PR (Point Range) , PRX (Point Range Extended), & IA (TCP/IP Address Table)
IR (TCP/IP Route Table) & BP (BOOTP Table)
RD - Data Concentrator Remote Devices Table
PD - Data Concentrator Remote Points Table
MR (Modbus Register/32 bit Analog Point Mapping Table) & TC (TC Address Table)
MIO - SCADAPack ER I/O Card Configuration Table
CT (Group Mapping Configuration Table) & PTX ( RTU Port Configuration Extended)
IF (IEC 60870-5-101 and 104 IOA to Filename Mapping Table) & HT (Hayes Table)
4.6.1 RT - Route Table
< sourceComIndex> < startSourceAddress> < endSourceAddress> <startDestAddress>

< endDestAddress> <destComIndex> “<dialString>” <status> <security>
The above parameters are defined on one line for a static route table entry in the route table and each is
specified as an integer except for the dial string, which is a text string surrounded by double quotes.
After finding the TE command in the configuration file, the next route entry will be set to Table End. The
route table will be completely overwritten if the Route Table is defined in the configuration file.
The <status> field is produced using 2 8-bit fields combined into a single 16-bit number.
The most significant 8 bits are set from the following values:
STATIC = 0
DYNAMIC = 1
FIXED = 2
The least significant 8 bits are set from the following values:
OFFLINE = 0
ONLINE = 1
An empty Route Table block will clear the Route Table, e.g.:
SLT RT
TE
The above entry in the configuration file will clear the route table on both incremental and full
configuration file executions. The route table will not be overwritten if it is not defined in the configuration
file. Consider the following entry in a configuration file:
SLT RT #Route Table
0 0 65535 1 9 1 "dial_string_1" 1 0
1 0 65535 10 19 2 "dial_string_2" 0 0
2 0 65535 20 29 3 "dial_string_3" 513 0
3 0 65535 30 39 4 "dial_string_4" 512 0
4 0 65535 40 49 0 "" "" 1 0
254 0 65535 0 0 0 "" "" 1 0
TE
The above route table entry in the configuration file will produce the following route table in the DNP
Network page of the SCADAPack E Configurator.
A configuration file generated from within the RTU will only write static route table entries to the
configuration file. The following route table will produce the subsequent entry in the configuration file.
SLT RT #Route Table0 0 65535 1 9 1 "dial_string_1" 1 0

4 0 65535 40 49 0 "" 1 0254 0 65535 0 0 0 "" 1 0 TE
The above demonstrates dynamic routes are not generated in the configuration file.
The above route tables are used to demonstrate the method used to write and restore the route table
from the configuration file.
Route Table AGA12 Field

The <AGA12> field is only relevant for RTUs that have been licensed and enabled for AGA12 security
functions.
The AGA12 security level set by this field is applied to routed (or outbound messages). The security field
can be can be set as shown:
The security field values are enumerated as follows for inclusion into the RTU route table:
None = 0
AGA12 Node = 1
AGA12 GW1 = 2
AGA12 GW2 = 3
AGA12 GW3 = 4
AGA12 GW4 = 5
AGA12 GW5 = 6
Consult the SCADAPack E Security Technical Reference manual for more information regarding the
Route Table security settings.
4.6.2 PR, PRX, & IA
PR - Point Range
SLT PR AS|DSY|SS <startRange>
<value> [<value> …]
TE
The Point Range table is used to write a sequential number of Read/Write system point values to the
RTU configuration. The point range table has additional two operands after the table identifier to define
the point type and the start of the point range.
Operand AS|DSY|SS defines one of the following:
AS = system analog point
DSY = system digital point
SS = system string point
Operand <startRange> defines the starting DNP point number of the range. The table needs to have one
or more values before the Table End block. Values need to be separated by a space. The number of
points to write is defined by the number of values in the table. Current firmware versions will log a
message to the “config.log” file for each invalid point encountered. String values need to be enclosed
with double quotes. The following table sets String Points 50000, and 50001 to the strings “string1” and
“string2”.
SLT PR SS 50000
"string1"
"string2"
TE
RTU generated configuration files display the current value of the system points.
PRX - Point Range Extended

SLT PRX AS|DSY|SS <startRange>
<value> [<value> …]
TE
The Point Range Extended table is used to write a sequential number of Read/Write system point values
to the RTU configuration. This table type may replace the “PR” mnemonic described in Section PR, RX,
& IA (Point Range). Unlike the “PR” mnemonic, this command will not stop parsing the configuration
file if an invalid point range is specified. A message will be logged to the “config.log” file for each invalid
point encountered.
This command is useful in allowing new system points to be added to a config. file in a backward-
compatible manner.
IA - TCP/IP Address Table

< commIndex> “<Port IP address>” “<Port Subnet mask >”
The IP Address table allows the user to specify an IP Address and Subnet Mask for an RTU port. This
command modifies only the ports that are defined by operand <commIndex>. For information on the
values defined for these fields, see the SCADAPack E Configuration Technical Reference Manual and
SCADAPack E TCP/IP Technical Reference Manual.
Example IP Address Table:
SLT IA #TCP/IP Port Addresses
0 "192.168.0.1" "255.255.255.0"
1 "192.168.1.1" "255.255.255.0"
E "158.234.186.71" "255.255.255.240"
TE
The configuration file IP Address table contains the Port IP Address and Port Subnet Mask for RTU
Ethernet ports when it is loaded. The table includes any Ethernet ports with IP Addresses and Subnet
Masks of 0.0.0.0. The new Ethernet Address are used when the configuration file is executed.
4.6.3 IR & BP
IR - TCP/IP Route Table

“<Destination IP address>” “<Subnet mask >” <Dest. Port no.> “<Gateway IP Address>”
<Metric>
The above parameters are defined on one line for a static route table entry in the IP Route Table and
each field exists as an text string surrounded by double quotes, except for the Destination Port no. and
Metric fields, which are integer types. The next entry in the IP Route Table after finding the TE
command will be marked as the end of the table. The route table will be completely overwritten if the
Route Table is defined in the configuration file.
An empty IP Route Table block will clear the IP Route Table, e.g.:
SLT IR
TE
The above entry in the configuration file will clear the route table on both incremental and full
configuration file executions. The route table will not be overwritten if it is not defined in the configuration
file. For further information, see the SCADAPack E TCP/IP Technical Reference Manual, “IP Routing”
section.
Example IP Route Table:
SLT IR #TCP/IP Route Table
"192.186.1.0" "255.255.255.0" 2 "192.168.0.1" 1
TE
BP - BOOTP Table
“<Hardware address>” “<IP Address>”
The above parameters are defined on one line for a static BOOTP table entry in the BOOTP Server
configuration table and each field exists as a text string surrounded by double quotes. The BOOTP table
will be completely overwritten if the BOOTP Table is defined in the configuration file.
An empty BOOTP Table block will clear the TCP/IP BOOTP Table, e.g.:
SLT BP
TE
The above entry in the configuration file will clear the BOOTP table on both incremental and full
configuration file executions. The BOOTP table will not be overwritten if it is not defined in the
configuration file. For further information, see the SCADAPack E TCP/IP Technical Reference Manual,
“BOOTP” section.
The “<Hardware address”> field represents an Ethernet MAC address, consisting of 12 hexadecimal
digits, and may be in one of the following formats:
“000054215401”
“00:00:54:21:A4:01”
“00-00-54-21-A4-01”
The “<IP address”> field needs to be in the following format:
“192.168.1.242”
Example TCP/IP BOOTP Table:
SLT BP #BOOTP Table
"00-00-54-21-A4-01" "192.168.1.242"
TE
4.6.4 RD - Data Concentrator Remote Devices Table
When an RD table is written to a configuration file, a PD table needs to be written.
Each line in the Remote Device table follows one of two different formats, depending on the first field,
“Device Type”.
For DNP3, SCADAPack ES Remote I/O and IEC 60870-5-103 Slave Device types, the format is as
follows:
<Device Type> <Device Address> <Poll Type> <Poll Rate 1> <Poll Rate 2> <Poll Rate 3>
<Poll Rate 4> <Appl Layer Timeout> <Analog Status Point Start> <Digital Control Point Start> <Set
Time> <Poll Error Count> <Health Poll Type> <Health Poll Rate> <Multi-frag Support> <Com Port>
For 5000 Series I/O expansion modules, the format is:
<Device Type> <Device Address> <Digital Status Point no.> <Input Filter> <Scan Frequency> <Input
Type Ch. 0><Input Type Ch. 1><Input Type Ch. 2><Input Type Ch. 3><Input Type Ch. 4><Input Type
Ch. 5><Input Type Ch. 6><Input Type Ch. 7><Output Type>
5000 Series I/O Modules Remote Devices
The enumerated values for the RD table “Device Type” field are as follows:
Device Type Value

DNP Slave Device 1
SCADAPack ES Remote I/O Device 2
IEC 60870-5-103 Slave Device 3
5000 Series I/O Modules 10 - 50
The above parameters are defined on one line for a Remote Device entry in the Data Concentrator
Remote Devices Table. The last entry in the Data Concentrator Remote Devices Table is followed by a
TE command. The table will be completely overwritten by the Remote Devices table defined in the
configuration file. This is true for both full and incremental configuration files. If there are no Remote
Devices and Remote Points tables defined, the tables shall remain empty, unless the configuration file is
an incremental file, whereby the tables will remain unchanged.
The Data Concentrator Remote Devices table is directly linked with the Data Concentrator Remote
Points Table described in Section PD – Data Concentrator Remote Points Table.
The relevance of some fields is dependant on the selected Device Type of the corresponding Remote
Device configuration. Where fields are not relevant for a given Device Type, a value of 0 should be
entered. For further information regarding the relationship between the two tables and valid field values,
consult the SCADAPack E Data Concentrator Technical Reference manual.
Example Remote Devices Table:

SLT RD #Remote Devices Table
1 1 1 60 900 65 65 60 41000 41000 1 2 1 120 1 0
TE
The example remote devices table entry in the configuration file will produce the following Remote
Device Configuration in the Data Concentrator page of SCADAPack E Configurator. The entry spans
two screen shots, where the second is the single entry scrolled to the right.
4.6.4.1 5000 Series I/O Modules Remote Devices
The enumerated values for the “Device Type” field for the RD data concentrator remote devices table
SCADAPack E Smart RTU and 5000 Series I/O modules are as follows:
Device Type Value

5304 - 4 Analog Output module 20
5405 - 32 Digital Inputs 27
5411 - 32 Digital Outputs 31
5414 - 16 Digital Inputs 38
5415 - 12 Relay Outputs 39
5505 - 4 RTD (Temperature) Inputs 34
5506 - 8 Analog Inputs 35
5606 - 32DI, 16 Relay Outputs, 8AI, 2AO 36
5608 - 12DI, 6 Relay Outputs 40
5609 - 12DI, 6 Relay Outputs, 4AI 41
5610 - 16DI, 10 Relay Outputs 42
5212 - Processor (SCADAPack 312E, SCADAPack 19
313E, SCADAPack 314E)
357E)
333E, SCADAPack 334E, SCADAPack 337E)
4.6.5 PD - Data Concentrator Remote Points Table
When a PD table is written to a configuration file, an RD table needs to be written.
<Device Number*> <Point Type> <Remote Point No.> <Point Quantity> < Local Point No.> <Element
Index>
The above parameters are defined on one line for a Remote Points entry in the Data Concentrator
Remote Points Table. The last entry in the Data Concentrator Remote Points table is followed by a TE
command. The table will be completely overwritten by the Remote Points table defined in the
configuration file. This is true for both full and incremental configuration files. If there are no Remote
Devices and Remote Points tables defined, the tables shall remain empty, unless the configuration file is
an incremental file, whereby the tables will remain unchanged.
The Data Concentrator Remote Points Table is directly linked with the Data Concentrator Remote
Devices table described in Section RD – Data Concentrator Remote Devices Table. * The <Device
Number> field needs to correspond with the appropriate entry in the Remote Devices table, e.g. a
<Device Number> field value of 1, indicates that this particular Remote Points Table entry relates only to
the 1st entry in the Remote Devices table. For further information regarding the relationship between the
two tables and valid field values, see the SCADAPack E Data Concentrator Technical Reference
manual.
Example Remote Points Table:
SLT PD #DNP Point Map
1 1 1 32 1001 0
1 2 1 16 1041 0
1 3 1 12 1061 0
1 4 1 4 1081 0
1 4 14001 1 1091 0
1 5 1 4 1091
3 3 8492 1 1 7
TE
The above remote points table entries in the configuration file will produce the following Remote Points
Configuration in the Data Concentrator page of SCADAPack E Configurator.
4.6.5.1 Notes for Remote Points Table Configuration Entries
The format and relevance of some of the fields in a Remote Points Table entry depend on the Device
Type of the corresponding entry in the Remote Devices Table. These are discussed in the following
sections
Remote Point Number

The Remote Point Number field is an unsigned 16-bit integer field and it’s format can vary according to
the Device Type of the corresponding Remote Device configuration. The possible formats are
discussed as follows
DNP3 Device Type
The Remote Point Number field is the DNP3 Point Number of the start of the range in the
remote DNP3 slave device.
IEC 60870-5-103 Device Type
The 16-bit Remote Point Number field is broken up into 2 separate 8-bit fields which are
identified as follows
Function Type
Information Number.
OR (if Generic Data Range is selected)
GIN Group
GIN Index
The 8-bits that represent the Function Type form the high byte (most significant bits) of the 16-bit field
and the 8-bits that represent the Information Number form the low byte (least significant bits) of the 16-
bit field. Consider the example where the Remote Point Number field for the last entry is set to 8482
(decimal). This number represented in hexadecimal format is 212C (hex). The Function Type in this entry
is 33 decimal, i.e. 21 (hex) which forms the high byte and the Information Number in this entry is 44
decimal, i.e. 2C (hex) which forms the low byte.
The IEC 60870-5-103 Generic Data ranges use the same format as the Function Type and Information
Number described above.
Element Index
The Element Index field is an 8-bit integer field and is only relevant when the Device Type of the
corresponding Remote Device configuration is set to 60870-5-103. This field is not required for entries
that correspond to other device types. If entered for other device types, the value entered into this field is
ignored. IEC 60870-5-103 point ranges use an Element Index field value of 255 to indicate to the Data
Concentrator that the point is mapped to a Generic Data range.
The SCADAPack E Configurator also uses the Element Index column to indicate a Point Range that is
mapped into an IEC 60870-5-103 Generic Data range.
SCADAPack E Configurator Remote Points Configuration showing Generic Data ranges

4.6.6 MR & TC
MR - Modbus Register/32 bit Analog Point Mapping Table

MR <Analog Point Num> <Point Quantity> < Analog Point Type>
The above parameters are defined on one line for a mapping entry in the Modbus Register / 32-bit Analog
Point Map Table. The last entry in this table is followed by a TE command. The current table will be
completely overwritten by the Modbus Register / 32-bit Analog Point Map table defined in the
configuration file. This is true for both full and incremental configuration files. If there is no Modbus
Register / 32-bit Analog Point Map table defined, the table shall remain empty, unless the configuration
file is an incremental file, whereby the current mapping table will remain unchanged.
Example Modbus Register / 32-bit Analog Point Map Table:
SLT MR #Modbus Register/32-bit Analog Map
2000 4 3
1000 8 4
3000 16 4
4000 4 4
TE
The above mapping entry in the configuration file will produce the following Modbus Register / 32-bit
Analog Point Map table in the Modbus page of the SCADAPack E Configurator.
The mapping entry is only required for mapping the RTU 32-bit point data to the Modbus holding
registers, as shown in the table below.
Consult the SCADAPack E Modbus Communication Interfaces document for more information on the
MR table type and how it is implemented in the RTU.
TC - TC Address Table
<TCnumber> <X25address> <PSTN Number>
The X25 address table lists Telemetry Computer (TC) number (as an integer) with an associated X25
address (string) and a PSTN number (string). There is a facility for four (4) rows of associations. The
table writes from the first row to the last and does not overwrite rows that are not listed. For example the
following table associates TC 3 with X25 address 00111 and PSTN Number 6480100, writing it into the
first row:
SLT TC
3 "00111" "6480100"
TE
PT - RTU Port Configuration

<commIndex> <functionId> <modeId> <baud> <formatId>
The port configuration table modifies only the ports that are defined by operand
<commIndex>.
The commIndex operand format is numeric only.
For more information on the operands, <functionId>, <modeId>, <baud>, and <formatId>, see the
SCADAPack E Configuration Technical Reference Manual.
4.6.7 MIO - SCADAPack ER I/O Card Configuration Table
MIO <0> <Slot Number> <I/O Card Type>

This table format is only applicable to SCADAPack ER configurations.
The MIO table format is used to specify the I/O Card configurations for a SCADAPack ER RTU. The
specific I/O card location is identified by the SLOT field, with the type of I/O card is specified by the I/O
Card Type field.
The first field is reserved and should be zero (0).

The <Slot Number> field specifies which slot in which the I/O Card is to be located.
1 = I/O Card Slot 1
2 = I/O Card Slot 2
... and so on.
The < I/O Card Type> field specifies the I/O card type that is to be located in the slot.
Default = 0. Refer to SCADAPack E Configuration Technical Reference manual for a complete list of
supported card types.
The following is an example of a SCADAPack ER I/O Card Configuration table entry
SLT MIO # SCADAPack ER IO Card Configuration
0 1 33 # 16 channel DO card
0 2 32 # 32 channel DI card
0 3 34 # 16 channel AI card
TE
This example would specify the following SCADAPack ER I/O card configurations:
A ER-16DO-A card located on Slot 1 of the Local Rack
A ER-32DI-A card located on Slot 2 of the Local Rack
A ER-16AI-A card located on Slot 3 of the Local Rack.
4.6.8 CT & PTX
CT - Conitel Group Mapping Configuration Table

CT <Station No.> <Group No.> <Function Type>
This table format is only applicable to SCADAPack ER - P620 configurations that are licensed for
Conitel Slave.
The CT table format is used to specify the Station/Group/Function combinations supported by the
SCADAPack ER - P620 RTU.
The <Station No.> <Group No.> combinations specify the station/group number to simulate as a Conitel
Slave. These numbers are both 4-bits, i.e. each has a valid range of 0-15.
The <Function Type> field specifies which function the Conitel Slave will support on the associated
Station/Group combination.
0 = Scan Function
1 = Trip/Close Function
2 = Raise/Lower Function
3 = Analog Setpoint Function
4 = Baker Reset Function
10 – 41 = Status Register location (this number – 10 gives frame location)
Valid Range for this field is 0 – 4, 10 – 41.
The following is an example of a Conitel Slave Group Mapping table entry
SLT CT #Conitel Group Map

100
2 10 0
111
14 0 2
11 10 3
TE
This example would specify the following Conitel Slave configurations ...
a Scan Fn supported on Station 1 Group 0
a Scan Fn supported on Station 2 Group 10
a Trip/Close Fn supported on Station 1 Group 1
a Raise/Lower Fn supported on Station 14 Group 0
a Setpoint Fn supported on Station 10 Group 11
PTX - RTU Port Configuration Extended

<commIndex> <functionId> <modeId> <baud> <formatId>
The port configuration table modifies only the ports that are defined by operand <commIndex>. The
commIndex operand format is alphanumeric.
Operands <functionId>, <modeId>, <baud>, and <formatId>.
This command is useful in allowing new port types to be added to a configuration file in a backward-
compatible manner. For information on the values defined for these fields, see the SCADAPack E
Configuration Technical Reference manual.

4.6.9 IF & HT
IF - IEC 60870-5-101 and 104 IOA to Filename Mapping Table

IF <Filename> <IOA>
The IF table format is used to specify the IEC Information Object Address (IOA) to filename mapping for
a SCADAPack E RTU. The IOA is uniquely identified by the IOA field, whereas the filename is specified
by the Filename field.
The <Filename.> field specifies the filename to be written to or read from the RTU file system.
It can be any string enclosed in quotation marks with a length of up to 30 characters.
The <IOA> field specifies the IOA that will be used during file transfer for a given filename.
0 = invalid IOA
1-65535 = Range of valid IOA
The following is an example of a IOA Filename mapping Configuration table entry. It is also the default
table.
SLT IF #IOA/File Name mapping

“System.rtk” 60001
“Config.rtu” 60002
“Config.inc” 60003
“Config.log” 60004
“Isa11” 60005
“Isa21“ 60006
“Ntp.conf” 60007
“eNet.lic” 60008
“7xxe586.biz” 60009
“Mon_2xx_586x.bin” 60010
“M386v1xx.bin” 60011
“Readconfig.rtu” 60012
TE
HT - Hayes Table
<commIndex> “<modemInitString>” “<dialPrefix>” <modemMode>
Double-quote characters surround the Modem Initialization and Dial Prefix strings. <CommIndex> and
<modemMode> are integers representing the values defined in DNPConfig. The Hayes Table only
modifies the Comm Index entries that are defined in the table.
The following Hayes Table block in the configuration file will only modify Port 0 and will place empty
strings in the Modem Initialization and Dial Prefix fields and set the mode to Hang-up Enabled:
SLT HT #Hayes Modem Table0 "" "" 0
TE
The remaining communications ports will not be modified. An empty Hayes Table block will therefore
have no affect upon the configuration, regardless of whether an incremental or full execution of the
configuration file is performed.
The RTU will write the entire page to the configuration file if a configuration file is generated from the
RTU.
5 Example Configuration File

The following is an example configuration file 1, 2
#Digital Physical Inputs

PC DI #create a physical Binary Input Point
RN 1 #point number 1
PR 10 #Profile ID 10
CS N #Alarm Inhibit true
AAS 0 #Alarm Active State false
IPS Y #Invert Point State true
DB 20 #Debounce time 20
TE #end point create
PC DI #create a physical Binary Input Point
RN 3 #Point Number 3
PDC C3B #Point Data Class: Class 3 Buffered
TE #end point create
#Digital Physical Outputs

PC DO #Create a physical Binary Output Point
IPN 2000 #interlock point number 2000
RTO 200 #Interlock Timeout 200
TE #end create point
OBT 10 2 #DNP Static Object type 10 variation 2
IPN 2000 #interlock point number 2000
#Digital User Points

PC DU #Create a Binary User Point
RN 2000 #point Number 2000
#Digital System Points

PC DSY #Create a Binary System Point
HTD #define Trend Record start
CV 2000 1 100 #define Trend record 1 for this point
CV 2000 2 100 #define Trend record 2 for this point
TE #end Trend Record
#Analog Physical Inputs

PC AI #Create Physical Analog Input Point
AL 21 22 23 24 25 26 27 28 #limits 4L to 4H
LG A N A N N N N N #Trigger 4L and 2L enabled
RQ 35 #Rate of rise 35
FQ 36 #Rate of Fall 36
RCP 38 #Rate of Change Period 38
RNC 37 # No Change Value 37
RRN 55000 #Rate of Rise exceeded DNP Point Number 55000
RFN 55001 #Rate of Fall exceeded DNP Point Number 55001
NCN 55002 #No Change DNP Point Number 55002
DE 40 #Value Deadband before event or alarm cleared 40
TB 10 #Time Deadband before alarm generated 10
CTB 14 #Time Deadband before alarm cleared 14
OR 33 #Over range value 33
UR 34 #Under range value 34
ZE 41 #Zero Threshold Limit 41
#Analog Physical Outputs

PC AO #Create Physical Analog Output Point
ER 0 1000 0 1000 #Min Raw 0, Max Raw 1000, # Min Engineering. 0, Max Engineering 1000
#Analog User Points

PC AU #Create Analog User Point
#Analog System Points

PC AS #Create Analog System Point
HTD #start Trend Data # This effectively stops trending
TE #end Trend Data # for this point
#Counter Physical Points

PC CI #Create Physical Counter Input Point
AL 25000 #High Counter Limit 25000
CDE 25 #Counter Significant Change Deviation 25
CEN 41248 #Counter Limit exceeded DNP Point Number 41248
SLT RT # Define Route Table
TE #End Route Table
SLT HT #Hayes Modem Table
0 "# IgnoreComment" "" 0 #Comment In String
1 "Double""Quote""" "" 0 #Double Quote character in
#string
2 "" "" 0 #Empty Strings
3 "" "" 0
4 "string with space" "" 0 #String with white-space
TE #end Hayes Table
SLT TC #TC Identification Addresses
1 "1100001001" “96480100” #Addresses of TC1
2 "1100001002" “96485555” #Addresses of TC4
0 "" “” #TC addresses undefined
0 "" “” #TC addresses undefined
TE
SLT PR AS 53210 #Analog System Point range
400 0 100 0 0 #From point number 53210 to 53214
TE #End Point range
1 This configuration is not necessarily an operational configuration file and is presented to facilitate
explanation of configuration file syntax.
2 The comments following the "#" symbol have been added for clarity. The RTU does not generate
comments. For more information see the Configuration File Generation section.

Configuration File Format

Uploaded by

Copyright:

Available Formats

Configuration File Format

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 File Format

Uploaded by

Copyright:

Available Formats

SCADAPack E Configuration

Part I Configuration File Format 3

I Configuration File Format

©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

Failure to follow these instructions can result in injury or equipment

OPERATION AND ADJUSTMENTS

3.1 Full & Incremental Configuration, & Configuration File Generation

Configuration File Generation

3.2 Impact of Changing Configuration Online

layer modes, event settings).

4 Configuration File Format

4.1 Configuration File Syntax & Execution Output

Configuration File Execution Output

4.1.1 Error and Warning Messages

PE AI 1 #edit the integer to analog conversion parameter

-2147483648 \ # raw min

2147483647 # raw max

4.2 RTU Type & Model Codes

RTU Type Type Code

RTU Model Model Code

Example File Header

4.3 Configuration File Batch Commands

4.3.1 PC - Create point

DO = Digital Physical Output

AI = Analog Physical Input

AO = Analog Physical Output

CI = Counter Physical Input

DU = Digital User (derived) point

AU = Analog User (derived) point

DSY = Digital System point

AS = Analog System point

4.3.2 PE - Edit point & PD - Delete Point

4.4 Point Edit Attribute Mnemonics

4.4.1 RQ, LG, & LGT

RQ - Rate of Rise Value:

LG - Limit Alarm/Event Generation:

LGT - Limit Generation Triggered:

4.4.2 RN, FQ, RCP, RNC, NCP, DE, & TB

FQ - Rate of Fall Value:

RCP - Period Used for Rate of Rise/Fall:

RNC - Rate of No Change Value:

NCP - Period Used for Rate of No Change:

4.4.3 CTB, OR, UR, ZE, CS, IPN, & CEN

CTB - Clear Time Deadband:

CS - Change Scan Alarm:

IPN - Interlock Point Number:

CEN - Counter Limit Exceeded Point Number:

4.4.4 RTO, PL, ER, PDC, & TRI

RTO - Remote Interlock Timeout:

PL - Status Output Configuration/Pulse Length

ER - Integer to Analog Conversion:

PDC - Point Data Class:

Where optional parameters "Master2" and "Master3" are one of: