SYS600 - DNP V3.00 Master Protocol

MicroSCADA Pro
SYS 600 *9.1

DNP V3.00 Master Protocol
Configuration Manual
1MRS751860-MEN MicroSCADA Pro SYS 600 *9.1
Issued: 26.03.2003 DNP V3.00 Master Protocol
Version: D/25.02.2005
1. About this manual .....................................................................5

1.1. Copyrights .....................................................................................5
1.2. Trademarks ...................................................................................5
1.3. General .........................................................................................5
1.4. Use of symbols ..............................................................................6
1.5. Related documents .......................................................................7
1.6. Document revisions .......................................................................7
2. Safety information .....................................................................9
2.1. Backup copies ...............................................................................9
2.2. Fatal errors ....................................................................................9
3. Instructions ..............................................................................11
3.1. Installation ...................................................................................11
3.2. Configuration ...............................................................................11
3.2.1. Base system configuration ...............................................11
3.2.2. Communication system configuration ..............................14
3.2.2.1. DNP V3.00 link layer ..........................................15
3.2.2.2. Link layer attributes ............................................16
3.2.2.3. DNP V3.00 application layer ..............................25
3.3. After configuration .......................................................................39
3.4. How to test the configuration .......................................................40
3.5. Serial cable wiring diagram .........................................................40
4. Technical description .............................................................43
4.1. Introduction .................................................................................43
4.1.1. DNP V3.00 protocol .........................................................43
4.1.2. Level of implementation ...................................................43
4.2. Communication ...........................................................................44
4.2.1. Protocol converter ............................................................45
4.2.2. Communication modes ....................................................45
4.2.3. Handshaking ....................................................................45
4.2.4. DNP V3.00 in LAN/WAN ..................................................46
4.2.5. Addressing .......................................................................46
4.2.6. Internal indications ...........................................................47
4.2.7. Device communication attributes .....................................48
4.3. Configuring data polling ..............................................................51
4.3.1. Input data .........................................................................53
4.3.2. Status of output objects ...................................................56
4.3.3. Output data ......................................................................57
4.3.3.1. Command handling in DNP V3.00 protocol .......57
4.3.3.2. Data commands .................................................57
4.3.3.3. Application and system commands ....................60
©Copyright 2005 ABB Oy, Substation Automation Products, Vaasa, FINLAND 3

SYS 600 *9.1 MicroSCADA Pro 1MRS751860-MEN

4.4. Signal engineering ...................................................................... 61

4.5. Status codes ............................................................................... 61
4.6. Device profile .............................................................................. 65
5. Appendix. Configuration Examples ...................................... 75
6. Index ........................................................................................ 79
4
1. About this manual
1.1. Copyrights
The information in this document is subject to change without notice and should not
be construed as a commitment by ABB Oy. ABB Oy assumes no responsibility for
any errors that may appear in this document.
In no event shall ABB Oy be liable for direct, indirect, special, incidental or
consequential damages of any nature or kind arising from the use of this document,
nor shall ABB Oy be liable for incidental or consequential damages arising from
use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written
permission from ABB Oy, and the contents thereof must not be imparted to a third
party nor used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license
and may be used, copied, or disclosed only in accordance with the terms of such
license.
Copyright © 2005 ABB Oy
All rights reserved.
1.2. Trademarks
Registrations and trademarks used in this document include:
Windows: Registered trademark of Microsoft Corporation.
1.3. General
This manual provides thorough information on the use of DNP V3.00 Master
Protocol. It describes how to configure the base system and the communication
system to establish communication to a DNP V3.00 slave.
In addition to this configuration, the base system might be needed for other
communication tasks, such as process communication. For further information on
this subject, refer to the Application Objects and System Objects manuals. The DNP
V3.00 slave needs to be configured as well.
DNP V3.00 master

DNP V3.00 master protocol is mainly used for upper level communication between
SYS 600 and a substation control system as illustrated in Fig. 1.3.-1. This protocol
can also be used for communication between a SYS 600 and for example a remote-
controlled line disconnector.
5

Fig. 1.3.-1 DNP Master sees the Substation Control System (SCS) as an DNP
slave
1.4. Use of symbols

This publication includes information and caution symbols where it is appropriate
to point out safety related or other important information. It also points out useful
hints for the reader. The corresponding symbols should be interpreted as follows:
Caution icon indicates important information or warning related to

the concept discussed in the text. It might indicate the presence of a
hazard, which could result in corruption of software or damage to
equipment/property.
Information icon alerts the reader to pertinent facts and conditions.
6
1.5. Related documents
Name of the manual MRS number

DNP V3.00 Slave Protocol manual 1MRS751861-MEN
System Configuration manual 1MRS751846-MEN
System Objects manual 1MRS751847-MEN
Application Objects manual 1MRS751848-MEN
The following documents of the DNP V3.00 protocol are available via the DNP
Users Group:
DNP V3.00 DATA LINK LAYER

DNP V3.00 APPLICATION LAYER
DNP V3.00 DATA OBJECT LIBRARY
DNP V3.00 TRANSPORT FUNCTIONS
DNP V3.00 SUBSET DEFINITIONS
1.6. Document revisions
Version Revision number Date History

A 4.0 Document created
B 4.0 26.03.2003 Autodialling and PP, OT, IA, LT attributes added
Attributes SD, PS, RM, DC updated
Section 4.2.4 added
C 9.0 30.06.2004 Document updated
D 9.1 25.02.2005 New revision number
7
2. Safety information
This chapter gives information about the prevention of hazards.
2.1. Backup copies

We suggest that you take backup copies before making any changes, especially the
ones that might have side effects. Software and data need to be copied to another
place, usually to a CD or a backup tape. A writable CD and DAT tape are commonly
used.
Backup copying makes it easier to restore the application software in case of a disk
crash or any other serious failure when stored data is lost. Therefore, it is
recommended that backup copies are taken regularly.
There should be at least two system backup copies and two application copies. A
new backup is copied over the oldest backup. This way the latest version is always
available, even if the backup procedure fails.
Detailed information on how to take backup copies should be delivered to the
customer with the application.
System backup
Usually a system backup is taken after the application is made. A backup should be
taken again when changes are made to the MicroSCADA system. For example, if
the driver configuration or the network set-up is changed.
Application backup
An application backup is taken simultaneously with the system backup after the
application is made. A backup should be taken again when changes are made to the
application. For example, if pictures or databases are edited or new pictures are
added.
2.2. Fatal errors

A fatal error is an error that causes a break-down or a locked situation in the
MicroSCADA program execution.
Handling
In case of a fatal error:
1. Write down the possible MicroSCADA error messages.
2. Shut down the MicroSCADA main program. If this cannot be done in the
MicroSCADA Control Panel, try to end the task in Windows Task Manager.
Shutting down the base system computers by switching off the

power might damage the files.
3. In Windows, the data kept in the main memory at the moment of a fatal error is
placed in the drwtsn32.log file. It is placed in a system folder, for example,
WINNT. Analyse and copy the data in this file.
4. Restart the system.
9

Report the program break-down together with the possible MicroSCADA error
messages and the information from drwtsn32.log file to the MicroSCADA supplier.
Status codes
Error messages in SCIL are called status codes. A list of status codes and short
explanations can be found in the Status Codes manual.
10
3. Instructions
Communication
In MicroSCADA, DNP V3.00 master protocol is implemented only in the PC-NET
software. PC-NET unit communicates over an INTEGRATED link and via the serial
ports of the base system computer. Setting the attributes of MicroSCADA system
objects can modify the communication parameters.
The base system considers each DNP V3.00 master device as a station that has been
created to a line of a NET unit. Each DNP V3.00 station works as a protocol
converter that converts data between the internal protocol of MicroSCADA and
DNP V3.00 protocol.
3.1. Installation
Software requirements
The following software is required:
• MicroSCADA 8.4.3 Software or later
• Operating system - Windows
Install the software as described in their respective manuals. The installation of
MicroSCADA 8.4.3 software is described in the Installation an Commissioning
manual.
Revision information
The information given in this document is valid for MicroSCADA revision 8.4.4.
With the following limitations the information is valid in older revisions:
• Dial-up was implemented in revision 8.4.4
3.2. Configuration
The configuration can be divided into two parts:
• Base system configuration
• Communication system configuration
Configuration can be made either by using the System Configuration Tool or by
using SCIL statements. The following sections show how to make the configuration
by using SCIL. For more information on the System Configuration Tool, refer to the
System Configuration Manual.
3.2.1. Base system configuration
Introduction
Each base system has a set of objects that specify the base system and its
environment, hardware and software, as well as the physical and logical connections
of the base system and its applications.
11

The base system objects are defined with SCIL commands in the
SYS_BASCON.COM file, which is executed every time the base system is started.
Except for a few limitations, you can also define and modify the base system objects
any time when MicroSCADA is running. During the operation, the base system
objects are in the primary memory of the base system computer.
DNP V3.00 master protocol is implemented in the PC-NET software, which means
that an INTEGRATED link must be used. When an integrated link is used, the base
system and PC-NET use services provided by the operating system for exchanging
information. DNP V3.00 master protocol uses the station type 30 with DNP process
database interface.
Configuration steps
To configure SYS_BASCON.COM:
1. Define the base system.
2. Define a link.
3. Define a node.
4. Define a monitor.
5. Define an application.
6. Define the station type.
7. Define the DNP V3.00 stations.
The definitions are made in the example below using the old SYS_BASCON.COM
template. If a new (revision 8.4.2 or later) template is used, the INTEGRATED link
and the node for the PC-NET is created by the System Configuration Tool and need
not to be included in SYS_BASCON.COM. For more information on the system
objects, see the System Objects manual.
Example of SYS_BASCON.COM
The following is an example of the SYS_BASCON.COM file for communication
with DNP V3.00 master protocol. An application DNP_TEST is defined. In this
example two DNP V3.00 master stations are configured.
;***************************************************************************
;
; SYS_BASCON.COM
; BASE SYSTEM CONFIGURATION TEMPLATE
;
;***************************************************************************
#CREATE SYS:B = LIST(-

SA = 209,- ;STATION ADDRESS OF BASE SYSTEM
ND = 9,- ;NODE NUMBER OF BASE SYSTEM
DN = 3,- ;DEFAULT NET NODE NUMBER
DS = "RTU",- ;STA TYPES: E.G. STA,RTU,SPA,REX
FS = "NEVER") ;FILE SYNCH CRITERIA:
;NEVER,MAINT,SET,CHECKPOINT,ALWAYS
;***************************************************************************
;
; COMMUNICATION LINKS
#CREATE LIN:V = LIST(- ;REQUIRES THE PC-NET PROGRAM

LT = "INTEGRATED",-
SC = "\SC\PROG\PC_NET\PC_NETS.EXE") ;STARTUP COMMAND
#CREATE LIN3:B = %LIN
12
;***************************************************************************
;
; COMMUNICATION NODES
#CREATE NOD:V = LIST(-

LI = 3,-
SA = 203)
#CREATE NOD3:B = %NOD
;***************************************************************************
;
; PRINTERS
;***************************************************************************
;
; MONITORS
#LOOP_WITH I = 1..5
#CREATE MON'I':B = LIST(-
TT = "LOCAL",- ;TRANSLATION TYPE
DT = "X") ;X MONITOR
@MON_MAP(%I) = -1
#LOOP_END
#LOOP_WITH I = 6..10
#CREATE MON'I':B = LIST(-
DT = "VS") ;VISUAL SCIL MONITOR
@MON_MAP(%I) = -1
#LOOP_END
;***************************************************************************
;
; APPLICATIONS
#CREATE APL:V = LIST(-

NA = "DNP_TEST",- ;NAME OF APPLICATION DIRECTORY
AS = "HOT",- ;APPLICATION STATE: COLD,WARM,HOT
HB = 2000,- ;HISTORY BUFFER SIZE)
RC = VECTOR("FILE_FUNCTIONS_CREATE_DIRECTORIES"),-
AP = (1,2),-
MO = %MON_MAP,- ;MONITOR MAPPING
PR = (1,2,3)) ;PRINTER MAPPING
#CREATE APL1:B = %APL
;***************************************************************************
; STATION TYPES
#SET STY30:BCX = "DNP"
;***************************************************************************
; STATIONS
;*** NET 3 stations ***
#CREATE STA:V = LIST(-

TT = "EXTERNAL",-
ST = "DNP",-
ND = 3,-
TN = 1)
#CREATE STA1:B = %STA
13

#CREATE STA:V = LIST(-

TT = "EXTERNAL",-
ST = "DNP",-
ND = 3,-
TN = 2)
#CREATE STA2:B = %STA
;***************************************************************************
3.2.2. Communication system configuration
Introduction
• Each NET unit contains a set of system objects, which specify line properties,
connected devices etc. These objects can be created, modified and deleted by
SCIL, and setting the attributes of the objects can change the properties. This
communication system configuration is usually done by using command
procedures.
Access to the attributes can be one of the following:
• Read-only:The attribute can only be read. There are still a few exceptions in
which the values can be reset.
• Write-only: The attribute can only be written (set).
• Read, conditional write: The attribute can be both read and written, but the
object must be set out of use (IU = 0) before writing.
• No limitations: The attribute can be both read and written without limitations.
The implementation of DNP V3.00 master protocol in MicroSCADA can be divided
into two layers: link layer and application layer. Both of these layers have a specific
functionality and a set of attributes of their own. The link layer corresponds to a line
of a NET unit and the application layer corresponds to a station configured to the
line.
The purpose of the communication system configuration is to:
• Create all the system objects needed to establish communication between the
master and the slave.
• Adjust the values of the system object attributes to match the physical
communication channel and the properties of the master station.
Setting the attribute values

All the line and station attributes have sensible default values but the value of each
attribute must be checked against the requirements of the actual communication
system. The attribute values depend on:
• The physical communication media (for example leased telephone line, radio
link, power line carrier), which affects in particular the attributes of the DNP
V3.00 line, such as the baud rate and parity.
• The network topology used (point-to-point, multi-drop), which affects for
example the link type.
• The size (number of stations) of the system, which affects especially the timeout
parameters; the slower the media and larger the system, the longer timeouts are
needed.
14
• The master system, which affects both the line and station attributes, and also the
message types used.
When making the DNP V3.00 connection, an agreement about the used
communication parameters should be made with the supplier or owner of the master
system.
Network topologies
The implementation of the DNP V3.00 protocol in MicroSCADA supports direct
and serial bus topologies. The direct topology (point-to-point) can be a direct
physical cable from point-to-point or a two-node radio, or modem network. The
serial bus topology (multi-drop) is commonly made up of many modems with their
outputs/inputs tied together, or by using a star-coupler. These network topologies are
illustrated in Fig. 3.2.2.-1.
Fig. 3.2.2.-1 Point-to-point and serial bus topologies

The DNP V3.00 link layer supports the multiple-master, multiple-slave and peer-to-
peer communication methods. In peer-to-peer communication, all the stations act as
slave data links and collisions are possible as no station has a higher priority and all
of them can transmit spontaneously. MicroSCADA uses random delay of
retransmission as a collision avoidance method.
3.2.2.1. DNP V3.00 link layer

The line process of a NET unit performs the functions of the link layer. The purpose
of the link layer is to send and receive messages with external devices using DNP
V3.00 protocol. By using DNP V3.00 terminology this means that the data link layer
provides transfer of Link Service Data Units (LSDU) across the physical link.
LSDUs are user data fragments small enough to fit to the FT3 frame format. The
15

application layer of a NET unit is responsible for assembling and disassembling

messages into LSDUs. The link layer provides frame synchronization and link
control.
According to DNP V3.00 documentation, the link layer performs the following
functions:
• Exchange of LSDUs between peer DNP V3.00 data links
• Error notification to data link user
• Sequencing of LSDUs
• Prioritized LSDU delivery
• Quality LSDU delivery
• Performing message retries
• Synchronzing and handling of the Frame Count Bit in the control word
• Setting and clearing the Data Flow Control bit based on buffer availability
• Packing user data into the defined frame format and transmitting the data to the
physical layer
• Unpacking the frames that are received from the physical layer into user data
• Controlling all aspects of the physical layer
• Responding to all valid frames (function codes) received from the physical layer
Link layer attributes

The following attributes can be used for configuring DNP V3.00 master lines in
MicroSCADA.
IU In Use
Indicates whether the line is in use (value 1) or not in use (value 0).
Data type: Integer
Value: 0 or 1
Index range: 1...8 (NET line numbering)
Default value: 0
Access: No limitations
LD Local Address
The IP address which is locally used. The setting of this attribute is necessary when
the computer has multiple IP addresses and it is defined which address the master
line must use. Not more than one master line can be created per IP address. The
setting of this attribute must be done before the line has been taken into use for the
first time.
Value: String containing a valid IP address, max 29 characters.
Access: Read, write
This attribute accepts the IP address in form:
#SET NET1:SLD1=”62.236.144.120”
16
PO Protocol
The data transfer protocol used on the line. The line is defined to the NET by setting
this attribute. By setting the attribute to 0 the line definition including all the line
attributes are deleted.
Data type: Integer
Value: 0...43
43 = value with DNP V3.00 master protocol
Access: Read, conditional write
SD System Device Name

Associates the NET line numbers of PC-NET with the device names of the physical
channels of serial ports.
By default, line number 1 is connected to COM1, line 2 to COM2 and so on. By
using the SD attribute, it is possible to override these default values. This may be
necessary if COM ports are used as NET lines or if, for example, a RocketPort card
is used.
Data type: Text
Value: See above
When using DNP V3.00 over LAN, the SD attribute defines the used connection
type. Possible types are TCP and UDP.
#SET NET’NET’:SSD’LINE’ = “TCP” ;line uses TCP connection
#SET NET’NET’:SSD’LINE’ = “UDP” ;line uses UDP connection
PS Buffer Pool Size

Specifies the number of message buffers reserved for the line. Each buffer can
contain one message. Buffers from this pool are also allocated for SYS-NET
transmission from the STA object of DNP type. If the lengths of APDUs from the
slave station are at their maximum value (2048 bytes), do not use smaller PS values
than the default one. Each buffer is capable of sending about 12 objects to the base
system.
With Object=1 Variation=1, one buffer may send 250 objects to base
system.
Data type: Integer

Value: 1...250
Default value: 180
17

BR Baud Rate
Transmission rate used on the line.
Data type: Integer
Value: 1...19200
Unit: Bits / s
Default value: 1200
PY Parity
Specifies the parity check (if any) used for the characters transferred on the line.
Data type: Integer
Value: 0 = no parity check
1 = odd parity
2 = even parity
Default value: 2
RD Receiver Data Bit Count

Specifies the number of data bits in each received character.
Data type: Integer
Value: 5, 6, 7 or 8
Unit: Data bits
Default value: 8
SB Stop Bits
Specifies the number of stop bits attached to each transmitted character.
Data type: Integer
Value: 1 or 2
Unit: Stop bits
Default value: 1
18
TD Transmitter Data Bit Count

Specifies the number of data bits in each transmitted character.
Data type: Integer
Value: 5, 6, 7 or 8
Unit: Data bits
Default value: 8
PD Poll Delay
Delay (in milliseconds) between test function of link commands. The purpose of this
command is to ensure that the communication to the slave is open. If this attribute is
set to zero, the test function of link command is not sent.
Data type: Integer
Value: 0... 5535
Unit: Milliseconds
Default value: 500
PP Polling Period
The polling frequency of suspended stations. This attribute specifies how often the
suspended stations of the line are polled with the link initialization message. PP
value is the value of transmitted messages before a new link initialization message
is sent. Each suspended station has a counter of its own, which means that the
sending may take place more often, if there are more than one suspended station. If
all the stations are suspended, the value of PP is meaningless. Value PP=1 may be
used, but is not recommended.
Value: Integer, 1..255
Indexing: Line number
Default: 10
ML Maximum Message Length

Maximum length of a data link fragment (LPDU). This length is the amount of user
data without checksums.
Data type: Integer
Value: 50...249
Unit: Octets
19

Default value 230

XR Maximum Random Delay for Retransmission

Random transmission delay is a simple collision avoidance method used in DNP
V3.00 lines. When unsolicited responses are enabled for slave stations on a multi-
drop line, there is a possibility that several slave devices send messages at the same
time. This message collision is seen as timeout in a slave station since the master is
not responding. The XR attribute limits the possibility that two devices retransmit
messages at the same time.
This attribute can also be used for setting the priorities of the slave stations: the
station with the smallest retransmission delay has the highest priority.
Data type: Integer
Value: 0...65535
Unit: Milliseconds
Default value: 0
DE CTS Delay
Time delay (in milliseconds) between the activation of the RTS signal (Request to
Send) and the start of a new transmission.
Data type: Integer
Value: 0...65535
Unit: Milliseconds
Default value 50
TW Transmission Wait Delay

Specifies the transmission delay in milliseconds, that is the time that the NET must
wait after receiving a CTS (Clear to Send) signal until starting the transmission of a
message.
Data type: Integer
Value: 0...65535
Unit: Milliseconds
Default value: 5
20
HT Header Timeout
Specifies the maximum waiting time in milliseconds within which the first byte of
a link layer response should have been received after the transmission of a message.
If no response has been received within this time, new attempts are performed the
number of times specified by the Enquiry Limit. If still no response is obtained, the
station is suspended.
Data type: Integer
Value: 0...65535
Unit: Milliseconds
Default value: 2000
OT Connecting Timeout
The maximum time of the TCP ‘connect’-operation. This attribute is only used in
the master. The value of this attribute depends on the speed of the LAN, the remote
station and possible routers between MicroSCADA and the substation. It should be
smaller than the HT attribute of the line but it should be big enough to enable reliable
reconnecting of the substation. In a multi-drop configuration, a too big value may
cause communication disturbances, if some of the stations are not available.
Value: 0... 60000
Unit Milliseconds
Access: Read, write
Default: 500 ms
TI Response Timeout
The time in seconds that the DNP V3.00 link waits for the end of the link layer
response.
Data type: Integer
Value: 0...255
Unit: Seconds
Default value: 2
RK RTS Keep Up Padding Characters

The number of padding characters (null characters) inserted to the end of telegram
to delay the passivation of the RTS (Request To Send) signal.
Data type: Integer
Value: 0...255
21

Default value: 0
RI Receive Interrupt Enable Delay

Defines the delay in milliseconds after which the receiver of a NET line is enabled
after a message has been issued.
Data type: Integer
Value: 0...255
0 = receiver is always enabled
Unit: Milliseconds
Default value: 0
EN Enquiry Limit
Specifies the maximum number of times that a message is retransmitted after a
timeout.
Data type: Integer
Value: 1...10
Default value: 1
SG Modem Signal
An attribute for direct supervision and control of the state of the modem signal. The
attribute applies to all protocols. It is used for diagnostics and testing.
Data type: Integer
Value: 0 = Passive signal
1 = Active signal
Index range: 100 * line no + signal no. Signal no. 5 = CTS, 8 = DCD,
20 = DTR
Access: Read-only
MI Message Identification
Object address of system messages.
Data type: Integer
Value: 1...32760
Default value: 6000 + (100 * NET number) + line number
22
MS Message Application
The number of the application that is the receiver of the system messages generated
by the line.
Data type: Integer
Value: 1...32
Default value: 1
Example:
In the example of SYS_BASCON.COM earlier in this chapter, the number of the
message application is 1.
LK Link Type
The type of data link connection used on the line:
Data type: Integer
Value: 14: Collision detection in use, transmission when the Data
Carrier Detect (DCD) signal of the line is not set.
15: No collision detection, Data Carrier Detect (DCD) signal is
handled as in other protocols.
Default value: 15
LA Link Layer Confirmations Enabled

Determines whether the link layer confirmations are in use (value 1) or not in use
(value 0).
Data type: Integer
Value: 0 or 1
Default value: 1
DC Diagnostic Counters
The line protocols gather statistical information about the events on the lines by
incrementing a number of diagnostic counters. All the major events and error
situations of the communication have their own counters.
When accessing diagnostic counters, the attribute is indexed according to the
formula:
100 * (line number) + (diagnostic counter number)
23

DNP V3.00 master protocol supports the following counters:

1. Transmitted telegrams
2. Failed transmissions
4. Transmitted commands
5. Transmitted replies
11. Received messages
12. Parity errors
13. Overrun errors
14. Check sum errors
15. Framing errors
16. Buffer overflow errors
20. TCP connect
21. TCP accept
22. TCP close
Data type: Integer
Value: 0...30000
Index range: See above
Access: Read-only, the values can be reset
OM Operating Mode
A bit pattern, which defines the operating mode of the line.
Data type: Integer
Value: 0..65535 (see below)
Index range: 1..8 (NET line numbering)
Default value: 0
Bit 1: When this bit is 1, only one application layer command from the
connected STA objects may be active at any time. This
configuration is useful when the collision detection is not done
by the hardware. The poll intervals defined with DP attribute,
will define the interval the STA object is ready to transmit the
poll. When multiple stations are connected, the real polling
interval may be longer. When this bit is 0, the command’s
transmission is not related with the state of the other STA objects
connected to a line (default). This mode of operation can be used
in systems with collision detection and in the LAN
configurations.
Bit 2: When this bit is 1, the transmission of the "Test function for link"
frame is disabled. This configuration may be useful when the
collision detection is not done by the hardware. When this bit is
0, the transmission of the "Test function for link" frame is
enabled as a default.
Example:
The 'one command mode' is used when OM is given a value 2^1=2.
24
3.2.2.2. DNP V3.00 application layer

The main purpose of the application layer is protocol conversion between DNP
V3.00 and the internal protocol of MicroSCADA. The application layer also takes
care of the application level communication with the slave.
STA objects created in a NET unit perform the functions of the application layer.
Several STA objects of the DNP V3.00 device type are allowed on the same line.
Some application layer attributes are used for configuration of the station, others are
used for device communication. The configuration attributes are presented in this
chapter and the device communication attributes in Chapter 4. By using the device
communication attributes you can send messages and, for example, synchronize the
slaves on the line.
Application layer attributes

The following attributes can be used for configuring the DNP V3.00 master stations
in MicroSCADA.
IU In Use
Indicates whether the station is in use (value 1) or not in use (value 0).
Data type: Integer
Value: 0 or 1
Default value: 0
LI Line Number
The number of the NET line the station is connected to.
Data type: Integer
Value: 1...8
Default value: 1
Setting this attribute is not needed when the station is created by

using the DV attribute.
SA Slave Address
The station address of the DNP V3.00 slave.
Data type: Integer
Value: 0...65534
Example:
In the example of the communication system configuration, the slave addresses are
1 and 2.
25

MA Master Address
The station address of the master station. In DNP protocol, this is the source address
of each request from the master.
If multiple station objects are connected to the same line, the value of the last
connected object is used. This means that all station objects connected to line are
using the same MA value.
Data type: Integer
Value: 0...65534
IA Internet Address
The IP address or the hostname of the remote host. The connection is established
with a device in this address using port number 20000. The line must have been
taken into use at least once before writing to this attribute. If routers/firewalls are
used, it must be ensured that the defined port number is left open for connection.
Value: Any string, max 29 characters
Access: Read/write
This attribute accepts the IP address in form:
#SET STA1:SIA=”62.236.144.120”
or as an alias name:
#SET STA1:SIA=”GRACE”
When an alias name is used, it must be defined in the TCP host file:
%windir\system32\drivers\etc\hosts.
There is one exception in the usage of the IA attribute. When operating as a DNP
V3.00 master in the UDP mode and there is more than one STA objects, that is the
configuration is a multi-drop configuration, a unique local port number must be
defined for the other station but the first one. This is done in the following way:
;first sta uses local port 20000
#SET STA1:SIA=”62.236.144.120”
;second STA uses local port 19999

#SET STA2:SIA=”19999>62.236.144.121”
;third STA uses local port 19998

#SET STA3:SIA=”19998>62.236.144.122”
The local port numbers are freely selectable, but they are not allowed to be used by
any other application.
AL Allocation
Allocates the station to an application. When the AL attribute has the value 1, the
station is reserved by the application specified by the AS attribute. All the
spontaneous messages from the station are sent to this application.
26
Data type: Integer

Value: 0 or 1
AS Allocating Application
Specifies the allocating application of the station (see the AL attribute). The
allocating application gets all the spontaneous process data from the station. This
application is also the only one that is allowed to set the device communication
attributes
Data type: Integer
Value: 0...32, 0 = no application
Note that when the AL attribute is set to 0, AS also gets
the value 0.
Access: Read-only
MI Message Identification
Object address of system messages.
Data type: Integer
Value: 1...32760
Default value: 30000 + STA object number
MS Message Application
The number of the application, that is the receiver of the system messages generated
by the station.
Data type: Integer
Value: 1...32
Default value: 1
Example:
In the example of SYS_BASCON.COM earlier in this chapter, the number of the
message application is 1.
SE System Messages Enabled

Specifies whether the system messages generated by the NET and related to the
station are sent to applications (value 1) or not (value 0). By using this attribute, it is
possible to disable the system messages related to the station.
Data type: Integer
Value: 0 or 1
Default value: 1
27

IL Information Address Length

The length of data object address (index) used in the DNP V3.00 messages.
Data type: Integer
Value: 1 or 2
Unit: Octets
Default value: 2
PC Process Data Confirmation

By setting the value of this attribute to 0, application level confirmations can be
disabled and by setting the value to 1, the confirmations can be enabled.
Data type: Integer
Value: 0 or 1
Default value: 1 (application level confirmations enabled)
AR Application Message Data Retries

The maximum number of retransmissions of an application data fragment (APDU).
Data type: Integer
Value: 0...5
Default value: 0
ML Maximum Message Length

The maximum length of an application data fragment (APDU).
Data type: Integer
Value: 249...2048
Unit: Octets
Default value: 2048
CA Command Address
The object address of bit stream process object in the MicroSCADA process
database, where unidentified messages are sent. If the value of the CA attribute is 0,
the unidentified messages are not sent and the bit stream object is not updated.
28
Data type: Integer

Value: 0...65534
Default value: 0
The unit number of the bit stream process object must be the same as
the STA object number of the master station.
PT Pulse Length for Control Relay Output Block

The length of the pulse used in the output commands of the control relay.
Data type: Integer
Value: 1…4294967295
Indexing: 0 = Pulse Off time
1 = Pulse On time
Unit: Milliseconds
Default value: 0
DR Direction
States if the DNP V3.00 master station acts as the station A (primary station) or
station B (secondary station).
Data type: Integer
Value: 0 or 1
Default value: 1 (primary station)
EO Event Offset
The address offset between the process objects for static data and events with the
same DNP V3.00 address (index). The address of the event process object is the
address of the process object for static data added with the value of this attribute. If
both static data and events are wanted to be received by the same process object, this
attribute must be set to 0.
Data type: Integer
Value: 0…65535
Default value: 0
29

RM Running Mode
Consists of a set of flags that control the behaviour and functionality of the DNP
V3.00 master station. Each flag is one bit of this attribute. The bits are as follows
(bits 0 and 1 used by the DNP V3.00 slave stations are left out):
Bit 1: When this bit is 1, consequent application layer response timeouts set
the station to suspended state and the corresponding process objects are
set to invalid state. The first application layer response within timeout
sets the station object state back to OK. This configuration may be
needed with the command mode defined by the line attribute OM, bit
1. The limit of the consequent timeouts is defined with the line attribute
EN, that is the same value, which is used if the link layer responses are
waited. When this bit is 0, application layer timeouts do not set the
station to suspended state, only an informative status message 13915
DNPC_RESPONSE_TIMEOUT is transmitted in this situation. This is
the default mode of operation.
Bit 2: Sending static data poll at zero (OK) status. When this bit is 0, a static
data (class 0) poll request is always sent when the object status of the
DNP master station gets the value zero, for example when set in use or
after a suspension. When this bit is 1, static data poll is not sent
automatically at zero status.
Bit 3: Automatic reset of RESTART bit. When this bit is 0, the master station
resets the RESTART bit of the internal indications bit of the slave
station after this bit has been set by the slave. When this bit is 1 the
RESTART bit is not reset.
Bit 4: When this bit is 0, automatic time synchronization of the slave is
enabled in master mode. If the slave sets the synchronization required
bit of internal indications (bit 1.4), MicroSCADA performs the
synchronization automatically. When this bit is 1, an automatic
synchronization of the slave is disabled in the master mode. The master
does not send a synchronization message to the slave at all.
Data type: Integer
Value: 1...65535
DC Diagnostic Counters
The values of the diagnostic counters which the NET unit keeps for the station. The
counters have the following meaning:
1. Suspension information (0 = OK, 1 = suspended)
2. Suspension counter
3. Transmitted data messages
4. Transmitted command messages
5. Transmitted confirmation messages
6. Received data messages
7. Received command messages
8. Received confirmation messages
9. Received unknown messages
30
10. APDU in queue length

11. APDU out queue length
12. TSDU in queue length
13. TSDU out queue length
14. WAIT CONFIRM queue length
15. SYS transition queue length
16. Confirmation transition queue length
17. Select transition queue length
18. Free APDUs queue length
19. Free events queue length
20. Free SYS transitions queue length
21. WAIT RESPONSE queue length
22. Unsolicited enabled bitmask
23. WAIT RESPONSE timeouts
24. WAIT CONFIRM timeouts
25. LINK CONFIRM timeouts
26. SYS transition timeouts
27. APDU receive timeouts
28. Delayed scm timeouts
29. Select timeouts
30. Cf write timeouts
31. Commanded station address
32. TCP connects
Data type: Integer
Value: 1...65535
Index range: 1...32
Access: Read-only, the values can be reset
LT Last Transaction number

The NET unit has a buffer for storing the last data messages received from the
process objects. Using the LT attribute, the last transmitted transaction number can
be read, and a forced retransmission of the latest transactions to the application can
be started.
Data type: Integer
Value: When read: Integer. The last transaction number of the last data
message, which the NET unit has forwarded to the application
(the application from where the read command is issued).
When written: Integer. A transaction number. All the stored
transactions above this number (if any) are transmitted to the
application.
Access: Not preconfigurable, otherwise no limitations.
Example:
The transactions occurred after the last received transaction are transmitted to the
application that issues the command:
#SET NET1:SLT = NOD1:BLT
31

OS Object Status
The current object status of the DNP V3.00 master station. When value 1 is written
to this attribute, the slave station retransmits its current status code.
Data type: Integer
Value: 0 or 1
IN Internal Indications
The current value of the internal indications of the DNP V3.00 master station. See
the DNP V3.00 protocol documentation for details of the internal indications.
Data type: Integer
Value: 0...65535
Access: Read-only
CT Confirmation Timeout
The maximum time in seconds that the master station waits for an application layer
confirmation from the slave.
Data type: Integer
Value: 0...600
Unit: Seconds
Default value: 10
AT Application Response Timeout

The time in seconds within which the application layer response from the slave must
be completed. This is the maximum time from the beginning of the first fragment of
the response to the end of the last fragment of the response.
Data type: Integer
Value: 0...600
Unit: Seconds
Default value: 30
TT Transport Layer Timeout

The maximum time in seconds that the transport layer is allowed to assemble one
application message fragment.
Data type: Integer
Value: 0...600
Unit: Seconds
32
Default value: 10
ST SYS Waiting Time

The maximum time in milliseconds that the master station waits for a reply from the
base system.
Data type: Integer
Value: 0...60000
Unit: Milliseconds
Default value: 5000
MT Maximum Delayed Response Time

The maximum time that the master station waits for a response to a command
request from the slave.
Data type: Integer
Value: 0...600
Unit: Seconds
Default value: 15
RT Reply Time-out
The maximum time in seconds that the DNP V3.00 application layer waits for a
reply from the slave.
Data type: Integer
Value: 0...600
Unit: Seconds
Default value: 10
Autodialling attributes
MicroSCADA provides support for the Autocaller functionality for the DNP V3.00
master protocol. An Autocaller is a modem with functions for automatic dial-up.
The dial-up can be initiated by the DNP V3.00 master or the DNP V3.00 slave.
The Autocaller must use the AT (Hayes) command set. Note that when using odd or
even parity, the modem must support 11-bit word length. In some cases, this feature
must be enabled by using the AT commands. Please refer to the documentation of
the modem in use for further details.
33

The following Autocaller attributes are valid for the DNP V3.00 master lines:
AC Autocaller Enabled
The AC attribute states whether an Autocaller is connected to the line (value 1) or
not (value 0).
Data type: Integer
Value: 0 or 1
Default value: 0
AS Autocaller State
This attribute indicates the state of the Autocaller.
Data type: Integer
Value: 0...4
0 = IDLE, ready to make a call
1 = CONNECTED, transmission is activated
2 = BUSY, Autocaller is dialling
3 = INITIAL, Autocaller is uninitialized
4 = CONFIGURE, the IU attribute of the line is set to 0
Default value: 0
Access: Read-only
CL Connection Time Limited

This attribute determines whether a time limit has been set to the connection (value
1) or not (value 0). The maximum duration of the connection is determined by the
CT attribute.
Data type: Integer
Value: 0 or 1
Default value: 0
CT Connection Time
The maximum time that a connection is allowed to last. This attribute is significant
only if time limiting is activated (CL = 1).
Data type: Integer
Value: 1...255
Unit: Seconds
Default value: 0
34
CN Connection
The CN attribute is used for dialling devices from the NET and for breaking
telephone connections.
A call to a station or workstation is initiated by writing the phone number to the CN
attribute. The NET unit then commands the autodialling modem to dial the number.
The success of the dialling is reported as a system message. Writing an empty string
to CN breaks the connection. When dialling a station, the link address of the station
should be given at the end of the phone number string, preceded by the letter "S".
This option is normally used to increase the communication performance on
multidrop lines.
Data type: Text
Value: Text string of maximum 25 characters
Default value: Empty text string
Example:
#SET NET1:SCN5 = "123456789S11"
CS Connected Station
The link address of the station a NET unit is communicating with.
Data type: Integer
Value: 0...65535
0 = Autocaller not defined or no communication
Default value: 0
Access: Read-only
DD Radio Disconnection Delay

Delay between the last data transfer and line disconnection.
Data type: Integer
Value: 1...255
Unit: Seconds
Default value: 0
MC Modem Command
Using this attribute, a modem can be controlled directly from SCIL with the AT/
Hayes commands. When an AT command is written to the MC attribute, it is
transmitted to the modem on the line. The response from the modem is read using
the same attribute.
Data type: Text
Value: Text string, an AT/Hayes command
35

Default value: 0
Example:
#SET NET1:SMC3 = ("AS0?")'
PC Pulse Dialling
This attribute determines the dialling principle used.
Data type: Integer
Value: 0 = tone dialling
1 = pulse dialling
Default value: 0
RC Remote Calls Enabled

The RC attribute states whether remote calls are enabled on a line, that is if the NET
unit can be called from the stations connected to the line in question.
Data type: Integer
Value: 0 = remote calls not enabled
1 = remote calls enabled
Default value: 0
RW Radio Connection Wait Time

Normally, the DCD (Data Carrier Detect) signal is used to indicate an active
connection. However, there are cases where this is not possible, for example on
radiotelephone lines using half-duplex links. The RW attribute defines the waiting
time in seconds in such a situation: from the finishing of the dialling until the
transmission is started.
Data type: Integer
Value: 0...255
Unit: Seconds
Default value: 0
SR Autocaller AT S Register
The S registers used by the Autocallers follow the AT (Hayes) de facto standard.
All the Autocallers which use the AT command set have a number of S registers.
The number of registers used and the meaning of the individual registers slightly
varies from one Autocaller model to another. The contents of the S registers are
therefore not described in this document. Please refer to the modem manuals.
36
Using the SR attribute, the S registers number 2, 6, 7, 8, 9, 10, 11 and 12 are

accessed. By using the MC attribute (see above), other S registers can also be
accessed. The S registers 11 and 12 cannot be set.
Data type: Integer
Value: See the modem manuals
Indexing: Seconds
Access: 100 * line number + register number
Example:
The S register number 6 of line 2 in NET1 is set = 4:
#SET NET1:SSR206 = 4
Example of communication system configuration

The following SCIL procedure makes the communication system configuration
which is related to the base system configuration example presented earlier in this
document. The procedure creates a DNP V3.00 slave line and two stations on this
line.
;***************************************************************************
; INPUT PARAMETERS
@NET = 3 ; NODE NUMBER OF THE PC-NET

@LINE = 1 ; LINE NUMBER
@STATIONS = VECTOR(1,2) ; MASTER STATION NUMBERS
@SLAVE_STATIONS = VECTOR(1,2) ; SLAVE STATION NUMBERS
@APPLIC = 1
;***************************************************************************
; CREATE A DNP V3.00 LINE TO NET
#IF NET'NET':SPO'LINE'==0 #THEN #BLOCK

#SET NET'NET':SPO'LINE' = 36 ;DNP V3.00 master
#SET NET'NET':SSD'LINE' = "COM1" ;system device name
#SET NET'NET':SMS'LINE' = %APPLIC ;message application
#SET NET'NET':SMI'LINE' = %LINE+(6000+(%NET*100) ;message identifier
#SET NET'NET':SBR'LINE' = 9600 ;baud rate
#SET NET'NET':SPY'LINE' = 2 ;parity
#SET NET'NET':SRD'LINE' = 8 ;receive bit count
#SET NET'NET':STD'LINE' = 8 ;transmit bit count
#SET NET'NET':SSB'LINE' = 1 ;stop bit count
#SET NET'NET':SLK'LINE' = 14 ;link type (coll. detection in use)
#SET NET'NET':SPS'LINE' = 20 ;buffer pool size
#SET NET'NET':SML'LINE' = 249 ;maximum message length (bytes)
#SET NET'NET':SXR'LINE' = 0 ;max. random delay for retransm.(ms)
#SET NET'NET':SDE'LINE' = 50 ;CTS delay (ms)
#SET NET'NET':STW'LINE' = 0 ;transmission wait delay (ms)
#SET NET'NET':SHT'LINE' = 2000 ;header timeout (ms)
#SET NET'NET':STI'LINE' = 2 ;response timeout (ms)
#SET NET'NET':SRK'LINE' = 0 ;RTS keep up padding characters
#SET NET'NET':SRI'LINE' = 0 ;receiver disabling time (ms)
#SET NET'NET':SPD'LINE' = 5000 ;polling delay (ms)
#SET NET'NET':SEN'LINE' = 3 ;retransmission limit
#SET NET'NET':SLA'LINE' = 1 ;link layer conf. enabled
#BLOCK_END
;***************************************************************************
; CREATE DNP V3.00 STATIONS TO NET
#LOOP_WITH I = 1..LENGTH(%STATIONS)
37

@STA=%STATIONS(%I)
@SLAVE = %SLAVE_STATIONS(%I)
#SET NET'NET':SDV(30) = (%STA,%LINE);create station to line
#SET STA'STA':SIU = 0 ;set station out of use
#SET STA'STA':SAL = 1 ;allocation
#SET STA'STA':SAS = %APPLIC ;allocating application
#SET STA'STA':SMI = 30000 +%STA ;message identification
#SET STA'STA':SMS = %APPLIC ;message application
#SET STA'STA':SSE = 1 ;system messages enabled
#SET STA'STA':SSA = %SLAVE ;slave address
#SET STA'STA':SMA = %STA ;master address
#SET STA'STA':SIL = 2 ;info address length (bytes)
#SET STA'STA':SCA = 32000 ;command address
#SET STA'STA':SPC = 0 ;process data confirmation
#SET STA'STA':SAT = 30 ;appl. response timeout (s)
#SET STA'STA':SRT = 10 ;reply timeout (s)
#SET STA'STA':SST = 5000 ;SYS waiting time (ms)
#SET STA'STA':SCT = 10 ;confirmation timeout (s)
#SET STA'STA':STT = 10 ;transport layer timeout (s)
#SET STA'STA':SDR = 1 ;direction
#SET STA'STA':SAR = 0 ;appl. message data retries
#SET STA'STA':SML = 2048 ;max. message length
#SET STA'STA':SPT0 = 0 ;pulse off time
#SET STA'STA':SPT1 = 0 ;pulse on time
#SET STA'STA':SEO = 0 ;event offset
#SET STA'STA':SRM = 0 ;running mode
#SET STA'STA':SIU = 1 ;set station in use
#LOOP_END
; Set line in use

#SET NET'NET':SIU'LINE' = 1
The second example is for a DNP V3.00 master line with dial-up and two DNP
V3.00 stations.
;***************************************************************************
; INPUT PARAMETERS
@NET = 3 ; NODE NUMBER OF THE PC-NET

@LINE = 1 ; LINE NUMBER
@STATIONS = VECTOR(1,2) ; MASTER STATION NUMBERS
@SLAVE_STATIONS = VECTOR(1,2) ; SLAVE STATION NUMBERS
@APPLIC = 1
;***************************************************************************
; CREATE A DNP V3.00 LINE TO NET
#IF NET'NET':SPO'LINE'==0 #THEN #BLOCK

#SET NET'NET':SPO'LINE' = 36 ;DNP V3.00 master
#SET NET'NET':SSD'LINE' = "COM1" ;system device name
#SET NET'NET':SMS'LINE' = %APPLIC ;message application
#SET NET'NET':SMI'LINE' = %LINE+(6000+(%NET*100));message identifier
#SET NET'NET':SBR'LINE' = 9600 ;baud rate
#SET NET'NET':SPY'LINE' = 2 ;parity
#SET NET'NET':SRD'LINE' = 8 ;receive bit count
#SET NET'NET':STD'LINE' = 8 ;transmit bit count
#SET NET'NET':SSB'LINE' = 1 ;stop bit count
#SET NET'NET':SLK'LINE' = 14 ;link type (coll. detection in use)
#SET NET'NET':SPS'LINE' = 20 ;buffer pool size
#SET NET'NET':SML'LINE' = 249 ;maximum message length (bytes)
#SET NET'NET':SXR'LINE' = 0 ;max. random delay for retransm.(ms)
#SET NET'NET':SDE'LINE' = 50 ;CTS delay (ms)
#SET NET'NET':STW'LINE' = 0 ;transmission wait delay (ms)
#SET NET'NET':SHT'LINE' = 2000 ;header timeout (ms)
#SET NET'NET':STI'LINE' = 2 ;response timeout (ms)
#SET NET'NET':SRK'LINE' = 0 ;RTS keep up padding characters
38
#SET NET'NET':SRI'LINE' = 0 ;receiver disabling time (ms)

#SET NET'NET':SPD'LINE' = 5000 ;polling delay (ms)
#SET NET'NET':SEN'LINE' = 3 ;retransmission limit
#SET NET'NET':SLA'LINE' = 1 ;link layer conf. enabled
#BLOCK_END
;*************** Configure Autocaller *************************************
#SET NET'NET':SCL'LINE' = 0 ;connection time limited
#SET NET'NET':SCT'LINE' = 0 ;connection time
#SET NET'NET':SDD'LINE' = 0 ;radio disc. delay
#SET NET'NET':SPU'LINE' = 0 ;pulse dialing
#SET NET'NET':SRC'LINE' = 0 ;remote calls enabled
#SET NET'NET':SRW'LINE' = 0 ;radio connecton wait time
;***************************************************************************
; CREATE DNP V3.00 STATIONS TO NET
#LOOP_WITH I = 1..LENGTH(%STATIONS)
@STA=%STATIONS(%I)
@SLAVE = %SLAVE_STATIONS(%I)
#SET NET'NET':SDV(30) = (%STA,%LINE) ;create station to line
#SET STA'STA':SIU = 0 ;set station out of use
#SET STA'STA':SAL = 1 ;allocation
#SET STA'STA':SAS = %APPLIC ;allocating application
#SET STA'STA':SMI = 30000 +%STA ;message identification
#SET STA'STA':SMS = %APPLIC ;message application
#SET STA'STA':SSE = 1 ;system messages enabled
#SET STA'STA':SSA = %SLAVE ;slave address
#SET STA'STA':SMA = %STA ;master address
#SET STA'STA':SIL = 2 ;info address length (bytes)
#SET STA'STA':SCA = 32000 ;command address
#SET STA'STA':SPC = 0 ;process data confirmation
#SET STA'STA':SAT = 30 ;appl. response timeout (s)
#SET STA'STA':SRT = 10 ;reply timeout (s)
#SET STA'STA':SST = 5000 ;SYS waiting time (ms)
#SET STA'STA':SCT = 10 ;confirmation timeout (s)
#SET STA'STA':STT = 10 ;transport layer timeout (s)
#SET STA'STA':SDR = 1 ;direction
#SET STA'STA':SAR = 0 ;appl. message data retries
#SET STA'STA':SML = 2048 ;max. message length
#SET STA'STA':SPT0 = 0 ;pulse off time
#SET STA'STA':SPT1 = 0 ;pulse on time
#SET STA'STA':SEO = 0 ;event offset
#SET STA'STA':SRM = 0 ;running mode
#SET STA'STA':SIU = 1 ;set station in use
#LOOP_END
; Set line in use

3.3. After configuration

For each input signal received from the DNP V3.00 slave the process database
should contain a process object whose value changes after process data is received.
There should also be an output process object for each command. You should also
create the bit stream process object that receives unrecognized DNP V3.00 messages
from the slave.
Besides the configuration of the base system and the communication system, you
also need to configure the DNP V3.00 slave.
39

3.4. How to test the configuration

When the slave and master stations have been physically tested and the
configuration has been completed, the connection and configuration can be tested
based on the following methods:
• Clear to Send (CTS) and Data Carrier Detect (DCD) signals. With the DNP
V3.00 master protocols both of these signals should be active in the slave end of
the line as follows:
• When collision detection is not in use (the LK attribute of the line is 15),
Carrier Detect signal is always active and Clear to Send signal is active when
the master station is transmitting.
• When collision detection is in use (the LK attribute of the line is 14), Clear to
Send signal is active when the master station is transmitting, and the master
station transmits only when the Carrier Detect signal is inactive, that is no other
station on the line is transmitting.
• Diagnostic counters. When the communication between the slave and the master
is running properly and data is moving on the line, the diagnostic counters
indicating the number received/transmitted data messages should be
incrementing.
• Object status. The OS attribute of the DNP V3.00 slave station should be 0.
• By connecting a serial line analyser to the DNP V3.00 line.
3.5. Serial cable wiring diagram

When connecting the DNP V3.00 slave to a MicroSCADA DNP V3.00 master using
a direct serial cable, the wiring illustrated by Fig. 3.5.-1 or Fig. 3.5.-2 should be
used depending on whether collision detection is used (the LK attribute of the line
is 14) or not (the LK attribute of the line is 15).
When connecting several slaves and masters to one line when collision detection is
used, a more sophisticated connection is needed. The connections should be made
in a way that when the Request to Send signal of any master or slave is set as an
indication that the station is transmitting, the Carrier Detect signal of all stations
should be set.
40
Fig. 3.5.-1 Serial cable wiring diagram when collision detection is not used
Fig. 3.5.-2 Serial cable wiring diagram when collision detection is used
41
4. Technical description
4.1. Introduction
4.1.1. DNP V3.00 protocol

The Distribute Networks Protocol (DNP) V3.00 is a standard-based communication
protocol designed for electric utility, water, oil & gas and security systems. DNP is
hardware-independent and works with a variety of networks enabling
communication between substation computers, Remote Terminal Units (RTUs),
Intelligent Electronic Devices (IEDs) and master stations over serial or LAN-based
systems.
DNP is designed according to the Enhanced Protocol Architecture (EPA) and it
specifies the following Open Systems Interconnection (OSI) layers:
• Physical layer
• Data link layer
• Transport layer
• Application layer
The DNP transport layer is actually a pseudo-transparent layer that provides
minimum message assembly and disassembly. The purpose of the transport layer is
to provide support for application messages larger than the frame length of the data
link.
The physical layer can be any bit-serial physical layer, for example RS-232 C, RS-
485 or fibre transceiver. In MicroSCADA, the communication takes place using the
serial port(s) of the base system computer by using the RS-232 C interface.
4.1.2. Level of implementation

DNP V3.00 has three subset levels from 1 to 3, which each include a specific subset
of DNP message types and functionality. In MicroSCADA the DNP V3.00 protocol
has been implemented according to the Subset Level 2 of the protocol (DNP 3.00–
L2) as presented in Table 4.6.-3.
Each DNP V3.00 message contains a function code that describes the purpose of the
messages. The function codes in the Table 4.1.2-1 are supported in MicroSCADA:
Table 4.1.2-1 The function code describes the purpose of the message
Code Function Description
Transfer Function Codes
0 Confirm Message Fragment confirmation.

No response.
1 Read Request objects from outstation.
Respond with requested objects.
2 Write Store specified objects to outstation.
Respond with status of operation.
Control Function Codes
43

Code Function Description

3 Select Select the output point of outstation.
Respond with status of control point.
4 Operate Set the output that has previously been
selected.
5 Direct operate Set the output directly.
6 Direct operate, no ack Set the output directly.
No response.
Freeze Function Codes
7 Immediate Freeze Copy the specified objects to freeze buffer.

8 Immediate Freeze, no ack Copy the specified objects to freeze buffer.
No response.
9 Freeze and Clear Copy the specified objects to freeze buffer and
clear objects.
10 Freeze and Clear, no ack Copy the specified objects to freeze buffer and
clear objects. No response.
Application Control Function Codes
13 Cold Restart Perform desired reset sequence.

Respond with a time object.
14 Warm Restart Perform desired partial reset operation.
Respond with a time object.
Time Synchronization Function Codes
23 Delay Measurement Perform propagation delay measurement.
Response Function Codes
0 Confirm Message fragment confirmation.

129 Response Response to requested message.
130 Unsolicited Message Spontaneous message without request.
For more details about the implementation of DNP V3.00 protocol in

MicroSCADA, see the device profile in the end of this document.
4.2. Communication
This section gives a more detailed description of the implementation of the DNP
V3.00 master protocol in MicroSCADA, describing also the attributes that can be
used for device communication. Examples of how to exchange data between the
master and the slave are also given in this section along with information of the DNP
status codes.
44
4.2.1. Protocol converter

Each DNP V3.00 slave station configured on a line of a NET unit acts as a protocol
converter between the DNP V3.00 protocol and a base system. An internal protocol
of MicroSCADA is used in communication between the MicroSCADA nodes, for
example, between a base system and a NET unit.
In DNP, there are basically two kinds of data: static data and event data. Static data
in DNP is called class 0 data. Event data can have three different classes or priorities:
1 (high priority), 2 (medium priority) and 3 (low priority). In DNP terminology static
data objects are called by their data type, for example binary input and analog input.
Corresponding events are called by adding “change” to the static data object, for
example “binary input change” and “analog change”.
Both the static and event data, can be sent from the slave to the master in two ways:
1. The master polls it cyclically or when needed
2. It is sent to the master spontaneously as unsolicited messages
A combination of these two ways is also possible. From this point of view DNP
V3.00 implements both the balanced and unbalanced transmission procedures.
4.2.2. Communication modes

A communication mode describes how messages are sent between the DNP V3.00
master and the slave by polling or by means of unsolicited messages, or by both
methods. The following four cases can be identified:
• Quiescent Operation. In this mode the master does not poll the slave, all the
communication is based on unsolicited (spontaneous) report-by-exception
messages. The master can send application layer confirmations to the slave.
• Unsolicited Report-by-Exception Operation. The communication is basically
unsolicited but the master occasionally sends integrity polls for Class 0 data to
verify that its database is up-to-date.
• Polled Report-by-Exception Operation. The master frequently polls for event
data and occasionally for Class 0 data.
• Static Report-by-Exception Operation. The master polls only for Class 0 data or
the specific data it requires.
When connecting MicroSCADA to a DNP V3.00 slave or slaves, the operation
mode of the slaves should be identified and the configuration of the DNP line and
station in MicroSCADA, especially the data polling, should be modified to fit the
communication mode in question. This is described in detail in Section 4.3.
4.2.3. Handshaking
By default, NET sends spontaneous “test function of link” messages to the DNP line
in order to check that the communication link is open. The message is sent at
intervals specified by the PD attribute of the line. If the DNP V3.00 slave does not
acknowledge this message, the communication will not be established.
Sending the “test function of link” messages can be disabled by setting both the PD
and LA attributes of the line to zero. It must be noted that in this case the state of the
communication link is not supervized at regular intervals.
45

4.2.4. DNP V3.00 in LAN/WAN

The DNP V3.0/LAN protocol is used in LAN and WAN networks to connect central
stations and outstations to each other. Since the stations use an open TCP/IP
interface as a connection to the network, the structure and the characteristics of the
network used will be invisible to the application. The transferred data messages are
equal to the ones used in the serial line based on the DNP V3.00 protocol. When
operating as a DNP V3.00 master, MicroSCADA is the client-end of the connection.
MicroSCADA is able to keep several connections to controlled stations open at the
same time. In the TCP mode, multiple DNP V3.00 master lines may be created in
the same computer. In the UDP mode, only one DNP V3.00 master or slave line may
be created. The connection type is defined with line attribute SD. Host internet
address (server) is defined with the station attribute IA. Configuration examples for
LAN connection are given in the Appendix. Configuration Examples.
4.2.5. Addressing
In the DNP V3.00 protocol each link layer message has two addresses: SOURCE
address indicates from which station the message is coming and DESTINATION
address tells which station the message is going to. When configuring a DNP V3.00
master station in MicroSCADA, the MA (Master Address) attribute should be equal
to the SOURCE address and the SA (Slave Address) equal to the DESTINATION
address.
In DNP V3.00 terminology a data point address is called index. Several data points
of the different data object type, for example binary input and analog input, can have
the same index. An individual data point is thus identified with the combination of
data object type and index.
Since in MicroSCADA the process object addresses are unique within one
application, the different data object types are separated into index ranges by giving
each data object type an address offset. Thus the addresses of two process objects of
different types will not overlap even if the corresponding DNP V3.00 indices are
equal. The address (OA attribute) of a process object is calculated as follows:
OA = OFFSET + INDEX
The address offsets used in MicroSCADA are calculated as follows:
OFFSET = (2^24)* DATA_OBJECT_TYPE
Address offset for different data object types are given in Table 4.2.5-1.
Table 4.2.5-1 Address offsets of data object types

Data Object Type Process Object Type Offset
Binary input Binary input, double binary indication 16777216
Binary input change
Binary output status Binary input 167772160
Control relay output block Binary output 201326592
Binary counter Pulse counter 335544320
Counter event
Frozen counter Pulse counter 352321536
Frozen counter event
Analog input Analog input 503316480
Analog change
46
Table 4.2.5-1 Address offsets of data object types

Data Object Type Process Object Type Offset
Analog output status Analog input 671088640
Analog output block Analog output 687865856
The object type double binary indication reserves two addresses.
By default, a static data object and the corresponding event has the same address.
The static data object type always determines the address offset. If static data and
events are wanted to be received in separate process objects, it can be achieved by
giving the EO (Event Offset) attribute a non-zero. In this case the addresses of the
static data object and the corresponding event is calculated as follows:
STATIC_OA = OFFSET + INDEX
EVENT_OA = OFFSET + INDEX + STAn:SEO
The process object address of an analog input process object with index 1255
would be:
OA = 503316480 + 1255 = 503317735
When using the Process Object Tool of the MicroSCADA base tools, the due
address offset is added automatically and the address given in the tool is the index.
The size of the address range (one or two bytes) is determined by the IL (Information
Address Length) attribute of the DNP V3.00 master station.
4.2.6. Internal indications

Each response message sent by the slave contains a two-octet field called internal
indications, which indicates the current state of the slave device. This information
can be used for monitoring the state of the slave or for troubleshooting purposes.
The internal indications sent by the DNP V3.00 slave can be read by using the IN
attribute of the DNP V3.00 master station. The bits of the internal indications are as
presented in Table 4.2.6-1.
Table 4.2.6-1 Bits of the internal indications

Octet Bit Description
1 0 All stations message received
1 1 Class 1 data available
1 4 Time-synchronization required from the master
1 5 Some or all of the Outstation's digital output points are in local state
1 6 Device trouble
1 7 Device restart
2 0 Function code not implemented
2 1 Requested object(s) unknown
2 2 Parameters in the qualifier, range or data fields are not valid or out of
range
47

Table 4.2.6-1 Bits of the internal indications

Octet Bit Description
2 3 Event buffer(s), or other application buffers overflow
2 4 Request understood but the requested operation is already executing
2 5 The current configuration in the slave is corrupt
2 6 Currently always returned as zero (0)
2 7 Currently always returned as zero (0)
For example, if the value of the IN attribute is 144 = 0000000010010000, it means
that the slave should be synchronized (octet 1, bit 4) and the slave device has
restarted (octet 1, bit 7).
4.2.7. Device communication attributes
GI General Interrogation
By using the GI attribute a request for all static (class 0) data can be made. This
corresponds to a general interrogation command used in other protocols.
Data type: Integer
Value: 1
Access: Write only
SY Synchronize
The SY attribute is used to make an accurate time synchronization of DNP V3.00
stations. No time arguments are needed since the time sent in the synchronization
message is taken from the internal clock of MicroSCADA. Stations can be
synchronized one by one or by using a broadcast synchronization message, which
synchronizes all the stations configured on a DNP V3.00 line.
By using the “do the first delay” measurement option (FUNC = 2), the
synchronization can be corrected with the delay of the application layer of the slave.
This can be done by sending a command to the slave to measure its delay. This
information is then used for correcting the actual synchronization.
Data type: Vector
Value: (FUNC, [BRO])
Description of the vector parameters:
FUNC: Function code as follows:
1 = direct time setting
2 = time setting with preceding delay measurement
3 = time setting using func 24, record current time
BRO: Broadcast, determines whether the synchronization message is a
broadcast message (value 1) or not (value 0). If omitted, value 0
is assumed. Brodcast is not currently supported with FUNC
value 3.
48
CO Command Out
The CO attribute can be used for generating command messages,that is requests, to
DNP V3.00 slave stations. All kinds of commands can be generated. The data
content of the command is given as transparent data octet by octet. It must be noted
that the user is responsible for the validity of the data content. For more information,
please refer to the DNP V3.00 standards listed in Chapter 2.
Data type: Vector
Value: (FNC, [TYPE, VAR, QUAL, [TDT]])
Access: Write-only
FNC: Function code of the command, integer
TYPE: Data object type of the command, integer
VAR: Variation of the command, integer
QUAL: Qualifier of the command, integer
TDT: The set of information objects of the command as integers. Each
integer corresponds to one octet in the DNP V3.00 message.
Example:
;direct 16-bit analog output block command to index 100
#SET STA1:SCO=(5, 41, 2, 23, 1, 100, 255, 255, 255)
FZ Freeze Counters
The FZ attribute can be used for freezing the binary counters of the DNP V3.00
slave.
Data type: Integer
Value: 7 = immediate freeze
8 = immediate freeze, no acknowledgement
9 = freeze and clear
10 = freeze and clear, no acknowledgement
Access: Write-only
DP Data Point
By using the DP attribute the user can configure the data polling of the DNP V3.00
master station.
Data type: Vector
Value: When writing:
Index 0: vector (PI, NUM)
Other indices: vector (PI, TYPE, VAR, FIRST, LAST)
When reading:
Index 0: vector (PI, NUM, STATUS, TIME)
Other indices: vector (PI, TYPE, VAR, FIRST, LAST,
STATUS, TIME)
49

Index range: 0...50

0 = event poll
1…50 = freely defined polls
PI: Polling interval as hundreds of milliseconds (0,1s).
Setting this parameter to zero will stop the poll.
NUM: Number of events to be polled. Value 0 = all events.
TYPE: Data object type to be polled, integer.
VAR: Variation of to be polled, integer. Value 0 = all variations.
FIRST: Lower limit of the index range. If 0, all data points with the given
data object type and variation are polled.
LAST: Upper limit of the index range, integer. If 0, all data points with
the given data object type and variation are polled.
STATUS: The result of the polling as a bit mask. The bits of the STATUS
parameter are as in the table below.
TIME: Time left to the next request.
Table 4.2.7-1 Bits of the STATUS parameter

Bit Description
0 Data not polled yet
1 No connection to the slave
2 Response timeout
6 Device trouble
8 Function code not implemented in the slave
9 Requested object(s) unknown, that is requested data does not exist in the slave
10 Parameters in the qualifier, range or data fields are not valid or they are out of
range
11 Event buffer(s), or other application buffers overflow
12 Request understood but requested operation is already executing
13 Current configuration in the slave is corrupt
For example, if the value of the status parameter is 512 = 0001000000000, the
parameter error bit (bit 10) is set.
Data object types and variations supported by MicroSCADA are listed in Table
4.1.2-1. It is possible to poll all static data (class 0) and events (classes 1…3) by
using the DP attribute by setting the TYPE parameter to 60 and variation to class
number + 1.
50
The following examples illustrate the use of the DP attribute.

;1,5 second event poll, all events
#SET STA1:SDP0 = (15,0)
;2 second poll for binary inputs, all variations, all objects

#SET STA1:SDP1 = (20,1,0,0,0)
;3 second poll for 32-bit analog inputs (var 3) with index 100…500
#SET STA1:SDP1 = (30,30,3,100,500)
4.3. Configuring data polling

DNP V3.00 protocol provides versatile possibilities for data polling: data can be
polled based on the data object type, variation, index range, class and count. It can
also be polled, with certain restrictions, based on a combination of these parameters.
The way data polling is executed is also different in DNP V3.00 protocol compared
to many other protocols. While for example in IEC 60870-5-101 polling is fixed and
standard background operation, the data polls, or requests, are application level
messages in DNP V3.00 protocol and they can be configured in a different way in
each DNP V3.00 master device. For this reason MicroSCADA does not send any
cyclical data polls by default; requests must be configured by using the DP attribute
of the DNP V3.00 master station. The only automatic poll is a request for static
(class 0) data when the device gets OK status, that is at start-up or after a
communication disturbance, unless this feature is disabled by the RM (Running
Mode) attribute of the DNP V3.00 master station.
Another dimension of the data polling is the fact that some DNP V3.00 slaves are
able to send some or all of their data as unsolicited, or spontaneous, messages while
some slave devices require all the data to be polled. One example could be a device
that sends all the binary events as unsolicited messages while all static data, binary
and analog, must be requested by the master. In this case polling the binary events
would be unnecessary and cause unneeded transmissions on the DNP V3.00 line.
All the facts mentioned above lead to the conclusion that it is very important to
configure the data polling of the DNP V3.00 master according to the functionality
of the slave or slaves, otherwise decreased performance or missing data may be the
result.
The following examples give instructions how to configure data polling for the four
different communication modes listed in Section 4.2.2. These are only examples, in
each project the data polling must be matched to the actual slave device. The
implementation of the slave can be checked from the device profile or other
documentation of the slave.
Quiescent operation
All the communication is based on unsolicited messages; no data polling is needed.
In this case no configuration by using the DP attribute is needed. The automatic class
0 poll at OK status can be disabled by using the RM attribute of the DNP V3.00
master station.
51

Unsolicited report-by-exception operation

Communication is basically unsolicited, only integrity poll is needed.
Cyclical integrity poll for static (class 0) data can be configured as follows:
;request class 0 data every 5 minutes
#SET STA1:SDP1 = (3000,60,1,0,0)
Polled report-by-exception operation

Event data (classes 1…3) is polled frequently and static data occasionally.
This poll configuration can be made as follows:
;request all events every 2 seconds
#SET STA1:SDP0 = (20,0)
;request class 0 data every 20 seconds

#SET STA1:SDP1 = (200,60,1,0,0)
Events can be polled also class by class:

;request class 1..3 data every 2 seconds
#SET STA1:SDP2 = (20,60,2,0,0)
#SET STA1:SDP3 = (20,60,3,0,0)
#SET STA1:SDP4 = (20,60,4,0,0)
Static report-by-exception operation

The master polls only for Class 0 data or the specific data it requires.
This poll configuration can be made as follows:
;request binary inputs every 5 seconds
#SET STA1:SDP1 = (50,1,0,0,0)
;request analog inputs and binary counters every 15 seconds

#SET STA1:SDP2 = (150,30,0,0,0)
#SET STA1:SDP3 = (150,20,0,0,0)
Another example shows how to poll a certain variation or index range:

;request binary inputs with status (var 2) every 5 seconds
#SET STA1:SDP1 = (50,1,2,0,0)
;request analog inputs with index 1…100 and 150…200 every 15 seconds
#SET STA1:SDP2 = (150,30,0,1,100)
#SET STA1:SDP3 = (150,20,0,150,200)
;request binary counters every 15 seconds

#SET STA1:SDP3 = (150,20,0,0,0)
All cyclical data polling must be configured by using the DP

attribute. The time intervals of the data polls should be set in a way
that it is possible to issue other commands in between the
consecutive polls.
In the quiescent operation mode static data is sent to the master as

unsolicited messages only at start-up and when the status of a data
point changes. Besides these situations, data must be sent as change
events or by means of polling.
52
4.3.1. Input data

Input data, such as binary inputs and analog inputs, are received in input process
objects. Table 4.3.1-1 lists the process object attributes that are updated when a
message is received from a DNP V3.00 slave.
Table 4.3.1-1 Process object attributes updated from a DNP message

Attribute Values Description
OV - Value of the information object. Data type depends on the
data object type.
OS 0…10 Object status, calculated from the bits of the flag byte and the
internal indications.
QL 0…255 Flag byte of the data object.
IV 0, 1 On-line bit of the flag byte.
NT 0, 1 Communication lost bit of the flag byte.
BL 0, 1 Chatter filter bit of the flag byte. Only with binary objects.
SB 0, 1 Local forced and remote forced bits of the flag byte.
OR 0, 1 Overflow bit of the qualifier. Only with analog objects.
OF 0, 1 Roll-over bit of the flag byte Only with binary counter objects.
RT Time Time tag of the information object (time-tagged data), or
system time (non-time-tagged data).
RM 0…999 Milliseconds of the information object (time-tagged data), or
system time (non-time-tagged data).
In DNP V3.00 there are variations with and without flag, that is status information.
The status of a data object is indicated by using a flag byte that consists of eight bits,
each of which represent a property of the data object. The bits used depend on the
data object type and are shown in Table 4.3.1-2. The attributes that are updated being
based on the flag byte are shown in Table 4.3.1-1.
Table 4.3.1-2 Bits of the flag byte

Bit Description Pobj. type
On-line The on-line bit indicates that the binary input point has All
been read successfully. If this field is set to off-line, the
state of the digital point may not be correct.
Restart The restart bit indicates that the field device which All
originated the data object is currently restarting. This can
be the device reporting this data object.
Communication The communication lost bit indicates that the device All
lost reporting this data object has lost communication with the
originator of the data object.
Remote forced The remote forced data bit indicates that the state of the All
data binary input has been forced to its current state at a
device other than the end device.
Local forced The local forced data bit indicates that the state of the All
data binary input has been forced to its current state at the
end device.
Chatter filter The chatter filter bit indicates that the binary input point Binary input
has been filtered in order to remove unneeded transitions
in the state of the point.
53

Table 4.3.1-2 Bits of the flag byte

Bit Description Pobj. type
Roll-over When set, the roll-over bit indicates that the accumulated Pulse counter
value has exceeded the last reported recordable. The
counter value has been reset to 0 upon the roll-over and
counting has resumed as normal. This bit is cleared
when the counter value (plus the roll-over state) is
reported.
Over range The out of range field indicates that the digitized signal or Analog input
calculation has exceeded the value range.
The internal indications parameter sent by the DNP V3.00 slave contains a status
bit which the slave can use to indicate that it needs synchronization and the time
stamps it is sending may be invalid. The value of the OS (Object Status) attribute of
an input process object is calculated from the bits of the flag byte and the internal
indications as in the following:
if “off-line” then (*on-line bit set*)
OS = 1
Elseif “communication lost” then)(*communication lost bit set*)
OS = 2
Elseif “Timesync required bit set in IIN” then(*need time bit of IIN set*)
OS = 3
Else
OS = 0
The following sections give a brief description of each MicroSCADA input process
object type and the corresponding DNP V3.00 data object types.
By default, both static data objects and events with the same index are received in
the same process object. If these are to be separated, it can be done by using the EO
(Event Offset) attribute of the DNP V3.00 master station.
Events in DNP V3.00 protocol can be sent in one of the following three ways:
• Without time. This kind of an event does not contain a time stamp and it can be
considered as a notification of a change in the value of the static data point.
• With time. This kind of an event contains a time coded as milliseconds from 1
January 1970 00:00:00.000.
• With relative time. Relative time means that first the slave sends a base time
object and the events sent after the base time contain a timestamp relative to the
base time.
Analog inputs
Analog inputs and analog change events are received in DNP V3.00 analog input
process objects. The data object types and variations listed in Table 4.3.1-3 are
supported by MicroSCADA.
Table 4.3.1-3 Analog input data object types and variations

Obj Var Description Value
30 1 32-bit analog input S32
30 2 16-bit analog input S16
30 3 32-bit analog input without flag S32
30 4 16-bit analog input without flag S16
32 1 32-bit analog change event without time S32
54
Table 4.3.1-3 Analog input data object types and variations

32 2 16-bit analog change event without time S16
In DNP V3.00 analog values are integers, value ranges are as follows:
S16 = signed 16-bit integer = -32768…32767
S32 = signed 32-bit integer = - 2147483648…2147483647
Single and double indications

DNP V3.00 protocol has a somewhat exceptional approach to handling of binary
data. Binary data in a DNP V3.00 application is considered as a sequence of bits and
it is up to the application to decide how they are used (as single or double indications
or even as a bit mask).
MicroSCADA supports binary input and double binary input process objects for
DNP. A binary input is a one-bit signal and a double binary is a two-bit signal whose
bits are two binary inputs with consecutive indices (DNP addresses). These two bits
can be sent from the DNP V3.00 slave in separate messages and the connection to
one process object is done internally in MicroSCADA. The following data object
types and variations are supported:
Table 4.3.1-4 Binary input data object types and variations

Obj Var Description
1 1 Binary input.
1 2 Binary input with status.
2 1 Binary input change without time.
2 2 Binary input change with time.
2 3 Binary input change with relative time.
Each DNP V3.00 double binary input object reserves two

consecutive addresses in the MicroSCADA process database. This
should be taken into account when giving addresses.
The Alarm Delay must be used when receiving double point information in
MicroSCADA. This is because two bits are received in two different messages and
there may be a delay between them. To prevent faulty values, a small alarm delay
must be added to the process object. See the attribute definition of the AD process
object in the Application Objects manual.
Both bits of a DNP V3.00 double binary input object must be

updated by static data, for example by a class 0 request, before the
object is updated by a change event.
55

Pulse counters
Pulse counters are termed binary counters in DNP V3.00 protocol. Counters can be
either of 16-bit or 32-bit. DNP V3.00 protocol has also a data object type called
frozen counter, which is a binary counter frozen to the value it had when the master
sent a freeze counters command. This way a snapshot of the counters can be
provided.
Binary counters and counter events are received by DNP V3.00 pulse counter
process objects. Frozen counters are received by DNP frozen binary counter process
objects. MicroSCADA supports the data object types and variations listed in Table
4.3.1-5.
Table 4.3.1-5 Binary counter data object types and variations

20 1 32-bit binary counter U32
20 2 16-bit binary counter U16
20 3 32-bit delta counter U32
20 4 16-bit delta counter U16
20 5 32-bit binary counter without flag U32
20 6 16-bit binary counter without flag U16
20 7 32-bit delta counter without flag U32
20 8 16-bit delta counter without flag U16
21 1 32-bit frozen counter U32
21 2 16-bit frozen counter U16
21 9 32-bit frozen counter without flag U32
21 10 16-bit frozen counter without flag U16
22 1 32-bit counter change event without time U32
22 2 16-bit counter change event without time U16
Value ranges are as follows:

U16 = unsigned 16-bit integer = 0…65535
U32 = unsigned 32-bit integer = 0…4294967295
4.3.2. Status of output objects

DNP V3.00 provides data object types for the status of binary and analog output
objects. These data objects indicate the value and status of the corresponding output
objects and can be requested as any other data from the slave. The following data
object types and variations are supported:
Table 4.3.2-1 Data object types and variations for status of output objects
Object Variation Description
10 2 Binary Output Status
40 1 32-bit Analog Output Status
Status of an output object is the status of a binary or analog output

object of the DNP V3.00 slave, not the DNP V3.00 master.
56
4.3.3. Output data
4.3.3.1. Command handling in DNP V3.00 protocol
Requests and responses

Messages from the master to the slave are called requests in DNP V3.00 protocol. A
request can be, for example, a request for data or a latch relay command. The slave
replies to a request with a response that can contain, for example, the requested user
data or the status of a command.
Unlike in some other protocols in DNP V3.00 all data polling is handled by
application layer requests. Since only one request can be open, that is waiting for a
response, at a time, a new request cannot be issued before the previous request has
received its response or a time-out has occurred. This means that if, for example, a
data poll configured by using the DP attribute is waiting for a response, a command
sent from SCIL is not issued until the handling of the poll is completed.
Overlapping requests are handled in MicroSCADA as follows: if a new request is
issued from SCIL while another is waiting for the response, execution of SCIL is
paused until the previous request is completed or the time defined by the MT
(Maximum Delayed Response Time) expires. The latter results in the status
DNPC_ANOTHER_COMMAND_ALREADY_PENDING.
By default, MicroSCADA sends a clock synchronization request, a

reset restart bit request and class 0 data request when the DNP V3.00
master station gets OK status, for example at start-up. While these
requests are open, no commands can be issued from SCIL.
4.3.3.2. Data commands
Object commands
Object commands , such as switching device open/close commands, tap changer
raise/lower commands, are sent as control relay output block messages. This
message is a multi-purpose command that contains the following control functions:
• Latching commands
• Momentary relay commands
• Breaker or transformer tap commands (pulse operation
The first two commands are usually used for setting and latching output relays and
the third for tripping and closing breakers, or raising and lowering tap changers.
Object commands are usually select-before-execute commands.
The data object type of the analog output block is 12 and its variation is 1. The
implementation in MicroSCADA has the following limitations:
• The CLEAR and QUEUE fields of the command are always 0. This means that
MicroSCADA does not support queued commands.
• The COUNT field of the command is always 1. This means that the command is
executed only once.
• The STATUS field of the command is set to 0.
57

Control relay output messages are sent by setting a list to a DNP V3.00 Control
Relay Block process object or by using the CO attribute of the DNP V3.00 station.
The unit number (UN attribute) of the output process object must be the same as the
STA object number of the corresponding DNP V3.00 master station.The address
(index) of the process object must also be equal to the address of the command in
the DNP V3.00 slave. Process Object Tool automatically adds the due offset to the
DNP index.
The values of the attributes set to the list depend on the control function and are
presented in the following three tables. A few examples are given for each control
function.
Table 4.3.3.2-1 Process object attributes included in a control relay output

command
SE - If a select command is sent, the parameter list is set to the SE
attribute. Otherwise not included.
TY 3, 4, 5, 6 Function code of the command, 3 = select, 4 = execute, 5 =
direct operate, 6 = direct operate, no ack
QL 0, 1, 2 Qualifier of the command, 0 = momentary relay operation, 1 =
latching operation, 2 = pulse operation
OV 0, 1 Direction of the command, 0 = OFF/TRIP/RAISE, 1 = ON/
CLOSE/LOWER
Examples:
;select, latch ON
#SET 'LN':PSE'IX' = LIST(OV=1,QL=1,TY=3)
;operate, latch OFF

#SET 'LN':POV'IX' = LIST(OV=0,QL=1,TY=4)
;direct, relay ON
;direct, no ack, relay OFF

;select, trip breaker

#SET 'LN':PSE'IX' = LIST(OV=0,QL=2,TY=3)
;operate, close breaker

Analog setpoints
Analog setpoints are sent analog output block messages to the DNP V3.00 slave.
The data object type of the analog output block is 41. MicroSCADA implementation
supports the 16-bit variation 2 whose value range is –32768…32767. The unit
number (UN attribute) of the output process object must be the same as the STA
object number of the corresponding DNP V3.00 master station, and the address of
the process object must be equal to the address of the command in the DNP V3.00
slave. The Process Object Tool automatically adds the due offset to the DNP V3.00
index.
58
Analog output block messages are sent by setting a list to a process object of the type
DNP V3.00 analog output block. The attributes included in the list are presented in
Table 4.3.3.2-2. Setpoint commands are usually direct commands.
Table 4.3.3.2-2 Process object attributes included in a control relay output

command
OV -32767..32767 Value.
TY 3,4,5,6 Function code of the command: 3 = select, 4 =
operate, 5 = direct operate, 6= direct operat- no ack.
The following examples illustrate the use of the analog output block command.
;select, value 100
#SET 'LN':P'IX' = LIST(OV=100,TY=3)
;execute, value 100

;direct, value 200

Response to a data command

The DNP V3.00 slave sends a corresponding response to each control relay output
block and analog output block request containing information about the status of the
execution of the command. This response message updates an analog input process
object with the UN attribute equal to the STA object number of the DNP V3.00
master station and OA equal to 209715200 + DNP V3.00 address (index) of the
corresponding output process object. This applies only to object commands. For
analog setpoints the offset for the command response indication is 696254464
(= 41.5 * 2^24). The process object for the response information can be created as
an DNP V3.00 command termination object by using the Process Object Tool,
which will automatically add the due address offset. Note that the index given in the
Process Object Tool is the index of the command.The values of the OV attribute of
the response process object have the following meaning:
Table 4.3.3.2-3 Values of the process object receiving response to a

command
Value Description
0 Request accepted or initiated.
1 Request not accepted, the time between select and operate was too long.
2 No previous select message.
3 Request not accepted because of a formatting error.
4 Control operation is not supported for this point.
5 Request not accepted because the point is already active.
6 Request not accepted because of control hardware problems.
128 Response timeout.
Values 0…6 are sent by the slave and value 128 is set by MicroSCADA after a time
determined by the MT attribute of the DNP V3.00 master station has expired while
waiting for a response from the slave.
59

4.3.3.3. Application and system commands
Restart commands
DNP V3.00 protocol has two restart commands; cold restart and warm restart. When
receiving a cold restart command, the DNP V3.00 slave should perform a complete
reset sequence to its application level. Warm restart should launch only a partial
reset sequence.
Both restart commands can be sent by using the CO attribute of the DNP V3.00
master station as shown in the following examples:
;send cold restart command
#SET STA1:SCO = VECTOR(13)
;send warm restart command

#SET STA1:SCO = VECTOR(14)
Time synchronization
DNP V3.00 slaves can be synchronized by using the SY attribute of the DNP V3.00
master station. Synchronization can take place station by station or as a broadcast
message which synchronises all the stations on the line. It is possible to first measure
the delay caused by the application layer of the slave and use this delay to correct
the actual synchronization. The synchronization send automatically when the master
station gets the OK status, if not prevented by the RM attribute, is always a message
corrected with the measured delay.
Examples:
;send synch to station 1, no broadcast, no delay measurement
#SET STA1:SSY = (1,0)
;send synch broadcast to the line of station 1, include delay measurement

#SET STA1:SSY = (2,1)
Freeze Counters command

DNP V3.00 protocol provides a function, which can be used to freeze the binary
counters of a slave, that is they can be copied to another buffer in the slave. These
frozen counters have the same indices (DNP V3.00 addresses) as the original
counters but a different data object type and they can be requested independently.
The Freeze Counters function provides a snapshot of the binary counters of the DNP
V3.00 slave in a specific moment of time.
The Freeze Counters command has two options:
• Immediate freeze, which only freezes the counters.
• Freeze and clear, which both freezes the counters and resets the values of the
original counters.
Both these options can be sent with or without a request for acknowledgement from
the slave.
The Freeze Counters command can be sent by using the FZ attribute of the DNP
V3.00 master station as shown in the next examples.
;immediate freeze
#SET STA1:SSZ = 7
60
;freeze and clear, no ack

#SET STA1:SSZ = 10
Binary counters and frozen counters have different data object type
and thus different address offsets in MicroSCADA, which means
that a binary counter and a frozen counter cannot be received in the
same process object.
4.4. Signal engineering

The term signal engineering means the engineering needed for establishing the
communication to the DNP V3.00 slave station. Signal engineering is made after the
system configuration is completed and the process database needed for the process
communication is ready. We recommend using the LIB 5xx application libraries for
creating the process database.
The following steps are taken when making signal engineering for DNP V3.00:
1. Make a list of all signals that are to be transferred between the master and the
slave. Include the data object type, variation and address of the static data
object. If an event is to be sent, include also data object type, variation, class and
delta of the event.
2. Determine the communication mode, that is whether polling or unsolicited
messages are used for sending the data to the master, based on the information
about the behaviour of the slave device.
3. Configure data polling based on the communication mode.
4. Test each signal.
4.5. Status codes

The following status codes are defined for DNP V3.00 slave protocol. Some typical
reasons for some of the status codes are also given.
Status codes are sent as system messages, which can be received by analog input
project objects with a unit number (UN) 0 and an object address (OA) as determined
by the MI attribute of the line or station.
Link layer status codes

17650 DGTP_REMOTE_LINK_CONTINUOUSLY_BUSY
The Data Flow Control (DFC) bit of the messages from the slave is set
for more than 15 seconds.
17651 DGTP_TIMEOUT_WHILE_TRANSMITTING
The DCD or CTS signal or the end of transmitted message is not
received in correct time. The DE attribute controls the CTS waiting
time and the TI attribute controls the message time. The DCD waiting
time is constant.
17652 DGTP_TIMEOUT_WHILE_WAITING_RESPONSE
Timeout while waiting for an acknowledgement to a request.
17654 DGTP_LINK_NOT_READY
The application level sends a command before the communication
between the master and the slave is established.
61

17655 DGTP_REMOTE_STATION_BUSY
The Data Flow Control bit of the messages from the slave is set for too
long.
17656 DGTP_REMOTE_STATION_NOT_RESPONDING
The master does not receive a reply from the slave.
17657 DGTP_LINE_STARTED
The line has been set in use by using the IU attribute.
17658 DGTP_LINE_STOPPED
The line has been set out of use by using the IU attribute.
17659 DGTP_RECEIVER_OUT_OF_BUFFERS
Internal software error.
17670 DGPC_ILLEGAL_ATTRIBUTE_VALUE
The value written to one of the line attributes is incorrect.
17700 DCPC_INVALID_ATTRIBUTE_VALUE
The value written to one of the line attributes is of wrong data type.
Application layer status codes

13901 DNPC_INVALID_ATTRIBUTE_VALUE
The value set to an attribute of a DNP V3.00 station is out of range.
13902 DNPC_INVALID_INDEX_RANGE
The index range used when accessing an attribute of a DNP V3.00
station is incorrect.
13903 DNPC_INVALID_ATTRIBUTE
The STA object attribute used is not valid for DNP V3.00 master
protocol.
13905 DNPC_MESSAGE_BUFFER_FULL
13906 DNPC_MESSAGE_FILLING_ERROR
13907 DNPC_UNKNOWN_OBJECT_TYPE
13909 DNPC_SC_DATA_OVERFLOW
13910 DNPC_DEVICE_SUSPENDED
The DNP V3.00 station is in the suspended state. The reason for this
could be that the link is not properly established (for example incorrect
cable wiring) or the slave station does not respond.
13911 DNPC_MESSAGE_SENDING_ERROR
Internal software error. The device status is set to this value if the
message sending has failed. The sending may fail due to, for example,
an error in the physical communication link.
13912 DNPC_REMOTE_DEVICE_REPLIES_WITH_NACK
The DNP V3.00 slave station responses with a negative
acknowledgement.
13913 DNPC_LINE_NOT_READY
A command is sent to a line with a non-established communication.
62
13914 DNPC_OUT_OF_BUFFERS
13915 DNPC_RESPONSE_TIMEOUT
The time determined by the RT attribute (first APDU) or RT+AT
attributes (last APDU) has expired while waiting for a response from
the slave.
13916 DNPC_CONFIRMATION_TIMEOUT
The time determined by the CT attribute has expired while waiting for
a confirmation from the slave.
13918 DNPC_DEVICE_STOPPED
The station has been set out of use by using the IU attribute.
13919 DNPC_DEVICE_STARTED
The station has been set to use by using the IU attribute.
13920 DNPC_UNEXPECTED_OV_VALUE
The value set to the OV attribute of an output process object is not
valid.
13921 DNPC_ERROR_IN_ACP
13924 DNPC-NET_BUFFER_ERROR
13926 DNPC_INTERNAL_ERROR
13927 DNPC_LINK_LINE_DOES_NOT_EXIST
The line to which the DNP V3.00 station is created is incorrect (not a
DNP V3.00 line).
13933 DNPC_INVALID_QL_VALUE
The qualifier defined in the output process object is invalid.
13934 DNPC_UNEXPECTED_TYPE_IN_SUBITEM
13935 DNPC_UNSUPPORTED_OV_TYPE
The data type of value set to the OV attribute of an output process
object is not valid.
13936 DNPC _APDU_SCAN_ERROR
13937 DNPC_UNKNOWN_VARIATION
The variation received from the slave is not supported.
13938 DNPC_ACP_MESSAGE_FULL
13940 DNPC_ALLOCATION_FAILED
13941 DNPC_BACKGROUND_POLL_ACTIVE
A command was issued while the DNP V3.00 master station was
waiting for a response to a data poll request.
13942 DNPC_PREVIOUS_CMD_STILL_ACTIVE
A command was issued while the DNP V3.00 master station was
waiting for a response to the previous command.
63

13943 DNPC_POLL_NOT_DEFINED
A poll has not been defined for the index used when reading the SD
attribute.
13944 DNPC_ANOTHER_COMMAND_ALREADY_PENDING
This status is returned when one command from SCIL is already
waiting to be sent (MT-timer is on) and the user issues a new command
from SCIL. This situation is possible only when parallel execution of
the SCIL procedures is possible.
64
4.6. Device profile

Table 4.6.-1 The device profile that describes the implementation of DNP V3.00 master protocol in
MicroSCADA
DNP V3.00
DEVICE PROFILE DOCUMENT
Vendor Name: ABB Oy Substation Automation Products
Device Name: MicroSCADA revision 9.1
Highest DNP Level Supported: Device Function:
For Requests: Subset Level 2 [x] Master [ ] Slave

For Responses: Subset Level 2
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels Supported
(the complete list is described in the attached table):
Additions to level 2 are shaded in the accompanying implementation tables.
Maximum Data Link Frame Size (octets): Maximum Application Fragment Size (octets):
Transmitted: <292 Transmitted: <250 (Single fragments only)

Received: (must be 292) Received : 2048
Maximum Data Link Re-tries: Maximum Application Layer Re-tries:
[ ] None [ ] None
[ ] Fixed at _______________________
[x] Configurable, range 0 to 10, line attribute EN [x] Configurable, range 0 to 5, STA attribute AR
Requires Data Link Layer Confirmation:
[ ] Never
[ ] Always
[ ] Sometimes. If 'Sometimes', when? ______________________________________________
[x] Configurable, line attribute LA
Requires Application Layer Confirmation:
[ ] Never
[ ] Always (not recommended)
[ ] When reporting Event Data (Slave devices only)
[ ] When sending multi-fragment responses (Slave devices only)
[ ] Sometimes. If 'Sometimes', when? ______________________________________________
[x] Configurable, STA attribute PC
65

Timeouts while waiting for:
Data Link Confirm

[ ] None [ ] Fixed at _________ [ ] Variable [x] Configurable, line attribute HT
Complete Appl. Fragment

[ ] None [ ] Fixed at _________ [ ] Variable [x] Configurable, STA attribute TT
Application Confirm
[ ] None [ ] Fixed at _________ [ ] Variable [x] Configurable, STA attribute CT
Complete Appl. Response

[ ] None [ ] Fixed at _________ [ ] Variable [x] Configurable, STA attribute AT
Others:
Retransmission after a collision, STA attribute XR (random delay if collision detection used).
Complete data link frame: line attribute TI
Response to a request: STA attribute RT (first APDU), STA attribute AT (last APDU).
Sends/Executes Control Operations:
WRITE Binary Outputs

[x] Never [ ] Always [ ] Sometimes [ ] Configurable
SELECT/OPERATE
[ ] Never [ ] Always [ ] Sometimes [x] Configurable, process object
attribute TY
DIRECT OPERATE
attribute TY
DIRECT OPERATE - NO ACK
attribute TY
Count > 1
Pulse On
attribute QL
Pulse Off
attribute QL
Latch On
attribute QL
66
Latch Off
attribute QL
Queue
Clear Queue
FILL OUT THE FOLLOWING ITEM FOR MASTER DEVICES ONLY:
Expects Binary Input Change Events:
[x] Either time-tagged or non-time-tagged for a single event

[ ] Both time-tagged and non-time-tagged for a single event
[ ] Configurable (attach explanation)
67

Supported function codes

Table 4.6.-2 Supported function codes, (* = CO attribute is needed )
CODE FUNCTION DESCRIPTION Supported
Transfer Function Codes
0 Confirm Message fragment confirmation Yes

No response
1 Read Request objects from outstation Yes
Respond with requested objects
2 Write Store the specified objects to outstation Yes
Respond with status of operation
Control Function Codes
3 Select Select the output point of outstation Yes

Respond with status of control point
4 Operate Set the output that has previously been selected Yes
5 Direct operate Set the output directly Yes
6 Direct operate Set the output directly Yes
- no ack No respond
Freeze Function Codes
7 Immediate Freeze Copy the specified objects to freeze buffer Yes

8 Immediate Freeze Copy the specified objects to freeze buffer Yes
-no ack No respond
9 Freeze and Clear Copy the specified objects to freeze buffer and clear objects Yes
10 Freeze and Clear Copy the specified objects to freeze buffer and clear objects Yes
-no ack No respond
11 Freeze with time Copy the specified objects to freeze buffer at specified time No
12 Freeze with time Copy the specified objects to freeze buffer at specified time No
-no ack No respond
Application Control Function Codes
13 Cold Restart Perform the desired reset sequence Yes

Respond with a time object
14 Warm Restart Perform the desired partial reset operation Yes
Respond with a time object
15 Initialise Data to Defaults Initialise the specified data to default No
Respond with the status of operation
16 Initialise Application Prepare the specified application to run No
17 Start Application Start the specified application to run No
18 Stop Application Stop the specified application to run No
68
CODE FUNCTION DESCRIPTION Supported
Configuration Function Codes
19 Save configuration Save the configuration No

20 Enable Unsolicited Enable Unsolicited Messages Yes (*)
Messages Respond with status of operation
21 Disable Unsolicited Disable Unsolicited Messages Yes (*)
Messages Respond with status of operation
22 Assign Class Assign specified objects to a class Yes (*)
Time Synchronization Function Codes
23 Delay Measurement Perform propagation delay measurement Yes

24 Record current time Used in a network application to allow the Master station and the Yes
Out station to record their time at the same instant
Response Function Codes
0 Confirm Message fragment confirmation Yes

129 Response Response to requested message Yes
130 Unsolicited Message Spontaneous message without request Yes
69

Supported objects:
Table 4.6.-3 Supported objects
REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Codes Qual Codes Func Codes Qual Codes

Obj Var Description
(dec) (hex) (dec) (hex)
1 0 Binary Input - All Variations 1, 22 00, 01, 066

1 1 Binary Input 1 00,01,06 129, 130 00, 01
1 2 Binary Input with Status 1 00,01,06 129, 130 00, 01
2 0 Binary Input Change - All Variations 1 06,07,08
2 1 Binary Input Change without Time 1 06,07,08 129, 130 17, 28
2 2 Binary Input Change with Time 1 06,07,08 129, 130 17, 28
2 3 Binary Input Change with Relative Time 1 06,07,08 129, 130 17, 28
10 0 Binary Output – All Variations 1 00,01,06
10 1 Binary Output
10 2 Binary Output Status 1 00,01,06 129, 130 00, 01
12 0 Control Block – All Variations
12 1 Control Relay Output Block 3, 4, 5, 6 17, 28 129 echo of
request
12 2 Pattern Control Block 5, 6 17, 28 129 echo of
request
12 3 Pattern Mask 5, 6 00,01 129 echo of
request
20 0 Binary Counter - All Variations 1, 7, 8, 9, 10, 00,01,06
22
20 1 32-Bit Binary Counter 1 00,01,06 129, 130 00, 01
20 2 16-Bit Binary Counter 1 00,01,06 129, 130 00, 01
20 3 32-Bit Delta Counter 1 00,01,06 129, 130 00, 01
20 4 16-Bit Delta Counter 1 00,01,06 129, 130 00, 01
20 5 32-Bit Binary Counter without Flag 1 00,01,06 129, 130 00, 01
20 6 16-Bit Binary Counter without Flag 1 00,01,06 129, 130 00, 01
20 7 32-Bit Delta Counter without Flag 1 00,01,06 129, 130 00, 01
20 8 16-Bit Delta Counter without Flag 1 00,01,06 129, 130 00, 01
21 0 Frozen Counter - All Variations 1,22 00,01,06
21 1 32-Bit Frozen Counter 1 00,01,06 129, 130 00, 01
21 2 16-Bit Frozen Counter 1 00,01,06 129, 130 00, 01
21 3 32-Bit Frozen Delta Counter 1 00,01,06 129, 130 00, 01
21 4 16-Bit Frozen Delta Counter 1 00,01,06 129, 130 00, 01
21 5 32-Bit Frozen Counter with Time of Freeze
21 6 16-Bit Frozen Counter with Time of Freeze
21 7 32-Bit Frozen Delta Counter with Time of Freeze
21 8 16-Bit Frozen Delta Counter with Time of Freeze
70
REQUEST RESPONSE
OBJECT

Obj Var Description
21 9 32-Bit Frozen Counter without Flag 1 00,01,06 129, 130 00, 01
21 10 16-Bit Frozen Counter without Flag 1 00,01,06 129, 130 00, 01
21 11 32-Bit Frozen Delta Counter without Flag
21 12 16-Bit Frozen Delta Counter without Flag
22 0 Counter Change Event - All Variations 1 06,07,08
22 1 32-Bit Counter Change Event without Time 1 06,07,08 129, 130 17, 28
22 2 16-Bit Counter Change Event without Time 1 06,07,08 129, 130 17, 28
22 3 32-Bit Delta Counter Change Event without Time 1 06,07,08 129, 130 17, 28
22 4 16-Bit Delta Counter Change Event without Time 1 06,07,08 129, 130 17, 28
22 5 32-Bit Counter Change Event with Time
22 6 16-Bit Counter Change Event with Time
22 7 32-Bit Delta Counter Change Event with Time
22 8 16-Bit Delta Counter Change Event with Time
23 0 Frozen Counter Event - All Variations 1 06,07,08
23 1 32-Bit Frozen Counter Event without Time 1 06,07,08 129, 130 17, 28
23 2 16-Bit Frozen Counter Event without Time 1 06,07,08 129, 130 17, 28
23 3 32-Bit Frozen Delta Counter Event without Time 1 06,07,08 129, 130 17, 28
23 4 16-Bit Frozen Delta Counter Event without Time 1 06,07,08 129, 130 17, 28
23 5 32-Bit Frozen Counter Event with Time
23 6 16-Bit Frozen Counter Event with Time
23 7 32-Bit Frozen Delta Counter Event with Time
23 8 16-Bit Frozen Delta Counter Event with Time
30 0 Analog Input - All Variations 1,22 00, 01, 06
30 1 32-Bit Analog Input 1 00,01,06 129, 130 00, 01
30 2 16-Bit Analog Input 1 00,01,06 129, 130 00, 01
30 3 32-Bit Analog Input without Flag 1 00,01,06 129, 130 00, 01
30 4 16-Bit Analog Input without Flag 1 00,01,06 129, 130 00, 01
31 0 Frozen Analog Input - All Variations
31 1 32-Bit Frozen Analog Input
31 2 16-Bit Frozen Analog Input
31 3 32-Bit Frozen Analog Input with Time of Freeze
31 4 16-Bit Frozen Analog Input with Time of Freeze
31 5 32-Bit Frozen Analog Input without Flag
31 6 16-Bit Frozen Analog Input without Flag
32 0 Analog Change Event - All Variations 1 06,07,08
32 1 32-Bit Analog Change Event without Time 1 06,07,08 129,130 17,28
32 2 16-Bit Analog Change Event without Time 1 06,07,08 129,130 17,28
71

REQUEST RESPONSE
OBJECT

Obj Var Description
32 3 32-Bit Analog Change Event with Time
32 4 16-Bit Analog Change Event with Time
33 0 Frozen Analog Event - All Variations
33 1 32-Bit Frozen Analog Event without Time
33 2 16-Bit Frozen Analog Event without Time
33 3 32-Bit Frozen Analog Event with Time
33 4 16-Bit Frozen Analog Event with Time
40 0 Analog Output Status - All Variations 1 00, 01, 06
40 1 32-Bit Analog Output Status 1 00, 01, 06 129,130 00,01
40 2 16-Bit Analog Output Status 1 00, 01, 06 129, 130 00, 01
41 0 Analog Output Block - All Variations
41 1 32-Bit Analog Output Block 3, 4, 5, 6 17, 28 129 echo of
request
41 2 16-Bit Analog Output Block 3, 4, 5, 6 17, 28 129 echo of
request
50 0 Time and Date - All Variations
50 1 Time and Date 2 07
quantity = 1
1 07 129 07
quantity = 1 quantity = 1
50 2 Time and Date with Interval
51 0 Time and Date CTO - All Variations
51 1 Time and Date CTO 129, 130 07,
quantity=1
51 2 Unsynchronized Time and Date CTO 129, 130 07,
quantity=1
52 0 Time Delay - All Variations
52 1 Time Delay Coarse 129 07,
quantity=1
52 2 Time Delay Fine 129 07,
quantity=1
60 1 Class 0 Data 1 06
60 2 Class 1 Data 1 06,07,08
20, 21, 22 06
60 3 Class 2 Data 1 06,07,08
20, 21, 22 06
60 4 Class 3 Data 1 06,07,08
20, 21, 22 06
70 1 File Identifier
80 1 Internal Indications 1 00,01
72
REQUEST RESPONSE
OBJECT

Obj Var Description
2 00
index=7
81 1 Storage Object
82 1 Device Profile
83 1 Private Registration Object
83 2 Private Registration Object Descriptor
90 1 Application Identifier
100 1 Short Floating Point
100 2 Long Floating Point
100 3 Extended Floating Point
101 1 Small Packed Binary-Coded Decimal
101 2 Medium Packed Binary-Coded Decimal
101 3 Large Packed Binary-Coded Decimal
No Object 13
No Object 23
Explanations:
• Obj. is the data object type.
• Var. is the variation.
• Func. is the function code of the message.
• Qual. is the qualifier code of the message in hexadecimal.
• Echo means that the response is the request mirrored.
TCP/UDP additions for LAN/WAN network
MicroSCADA LAN/WAN DNP uses the default IP address provided by the
operating system.
A created DNP Slave line reserves a port number
2501+linenumber
for its internal use.
In TCP/IP mode (connection-oriented), the connection is established to port
20000
of the slave device. The slave device accepts connections from this port only. Only
one connection to each master station is established at the same time. The IP address
of the master is configured with the IA attribute of the station object, and the
connection is established only if the address of the incoming is ‘connect’.
73

In UDP/IP mode (connectionless) all data is sent and received through port
20000
The slave device must receive messages from this port only. All messages which are
sent by the slave device must be sent to this port of master. The IP address of the
slave is configured with the IA attribute of the station object. The multidrop
configuration requires redefinition of local ports though all communication goes
through port 20000. This configuration has been explained in the description of the
IA attribute.
Example topologies:
DNP Master Line Line SD="TCP" ; connection oriented mode;

STA1 connect made to port 20000 of each IP-address
STA2 Station 1 IA="62.236.145.119"
STA3 Station 2 IA="62.236.145.120"
IP 62.236.145.130 Station 3 IA="62.236.145.121"
MicroSCADA LAN/WAN
Station 1 (IED, RTU) Station 2 (IED, RTU..) Station 3 (IED, RTU..)
IP-address IP-address IP-address

62.236.145.119 62.236.145.120 62.236.145.121
Listens port 20000 Listens port 20000 Listens port 20000
MicroSCADA_TCP_a
Fig. 4.6.-1 MicroSCADA as DNP3.0 TCP master in multidrop environment
DNP Master Line Line SD="UDP" ; connectionless mode;

STA1 messages to port 20000 of each IP-address
STA2 Station 1 IA="62.236.145.119" ;port 20000 default - all;
STA3 messages uses this port
IP 62.236.145.130 Station 2:SIA="19999>62.236.145.120" ; 19999 reserved
Station 3:SIA="19998>62.236.145.121" ; 19998 reserved
MicroSCADA LAN/WAN
Station 1 (IED, RTU) Station 2 (IED, RTU..) Station 2 (IED, RTU..)

IP-address IP-address IP-address
62.236.145.119 62.236.145.120 62.236.145.121
Uses port 20000 Uses port 20000 Uses port 20000
MicroSCADA_UDP_a
Fig. 4.6.-2 MicroSCADA as DNP3.0 UDP master in multidrop environment
74
Appendix. Configuration Examples

One station in TCP mode
@NET=2
@STA=1
@LINE=1
#SET NET'NET':SPO'LINE'=43
#SET NET'NET':SDV(30)=('STA','LINE')
#SET NET'NET':SSD'LINE'="TCP"
#SET NET'NET':SEN'LINE'=3
#SET NET'NET':SMS'LINE'='NET'
#SET NET'NET':SPD'LINE'=0
#SET NET'NET':SHT'LINE'=300
#SET NET'NET':STI'LINE'=4
#SET NET'NET':SLA'LINE'=1
#SET NET'NET':SPS'LINE'=190
#SET NET'NET':SLK'LINE'=15
#SET NET'NET':SIU'LINE'=1
#SET STA'STA':SAL=1
#SET STA'STA':SDR=1
#SET STA'STA':SSA=1
#SET STA'STA':SIA="GRACE"
#SET STA'STA':SMA=10
#SET STA'STA':STT=25
#SET STA'STA':SCT=10
#SET STA'STA':SRT=30
#SET STA'STA':SAT=60
#SET STA'STA':SPC=1
#SET STA'STA':SRM=28
#SET STA'STA':SIU=1
Multiple stations in TCP mode

@NET=2
@STA=1
@LINE=1
#SET NET'NET':SDV(30)=(2,'LINE')
#SET NET'NET':SSD'LINE'="TCP"
#SET NET'NET':SPP'LINE'=3
#SET STA'STA':SAL=1
#SET STA'STA':SDR=1
#SET STA'STA':SSA=1
#SET STA'STA':SIA="62.236.144.120"
75

#SET STA'STA':SPC=1
#SET STA'STA':SIU=1
@STA=2
#SET STA'STA':SAL=1
#SET STA'STA':SDR=1
#SET STA'STA':SSA=2
#SET STA'STA':SIA="62.236.144.120"
#SET STA'STA':SPC=1
#SET STA'STA':SIU=1
@STA=3
#SET STA'STA':SAL=1
#SET STA'STA':SDR=1
#SET STA'STA':SSA=3
#SET STA'STA':SIA="62.236.144.122"
#SET STA'STA':SPC=1
#SET STA'STA':SIU=1
One station in UDP mode

@NET=2
@STA=1
@LINE=1
#SET NET'NET':SSD'LINE'="UDP"
#SET STA'STA':SAL=1
#SET STA'STA':SDR=1
#SET STA'STA':SSA=1
#SET STA'STA':SIA="62.236.144.120"
76
#SET STA'STA':SPC=1
#SET STA'STA':SIU=1
Multiple stations in UDP mode

@NET=2
@STA=1
@LINE=1
#SET NET'NET':SSD'LINE'="UDP"
#SET NET'NET':SPP'LINE'=3
#SET STA'STA':SAL=1
#SET STA'STA':SDR=1
#SET STA'STA':SSA=1
#SET STA'STA':SIA="20000>62.236.144.120"
#SET STA'STA':SPC=1
#SET STA'STA':SIU=1
@STA=2
#SET STA'STA':SAL=1
#SET STA'STA':SDR=1
#SET STA'STA':SSA=2
#SET STA'STA':SIA="19999>62.236.144.121"
#SET STA'STA':SPC=1
#SET STA'STA':SIU=1
@STA=3
77

#SET STA'STA':SAL=1
#SET STA'STA':SDR=1
#SET STA'STA':SSA=3
#SET STA'STA':SIA="19998>62.236.144.122"
#SET STA'STA':SPC=1
#SET STA'STA':SIU=1
78
6. Index
A
AC ............................................................................................................. 34
Address offset ........................................................................................... 46
AL ....................................................................................................... 26, 27
Allocating Application ............................................................................. 27
Allocation ................................................................................................. 26
Analog
Change events ..................................................................................... 54
Inputs .................................................................................................. 54
Output block ....................................................................................... 58
Setpoints ............................................................................................. 58
APDU ........................................................................................... 17, 28, 63
Application Layer Attributes .................................................................... 25
Application Message Data Retries ........................................................... 28
Application Response Timeout ................................................................ 32
AR ....................................................................................................... 28, 65
AS ....................................................................................................... 27, 34
AT ................................................................................................. 32, 63, 66
AT command ...................................................................................... 33, 35
Autocaller AT S Register ......................................................................... 36
Autocaller Enabled ................................................................................... 34
Autocaller State ........................................................................................ 34
B
Baud Rate ................................................................................................. 18
Binary
Counters .............................................................................................. 56
Data ..................................................................................................... 55
Input .................................................................................................... 55
BR ............................................................................................................. 18
Buffer Pool Size ....................................................................................... 17
C
CA ............................................................................................................. 28
CL ............................................................................................................. 34
Classes .................................................................................... 45, 47, 69, 72
CN ............................................................................................................. 35
CO ....................................................................................................... 49, 60
Cold restart ............................................................................................... 60
Collision ....................................................................................... 40, 41, 66
Command Address ................................................................................... 28
Command Out .......................................................................................... 49
Communication modes ............................................................................. 45
Configuration ............................................................................................ 11
Confirmation Timeout .............................................................................. 32
79

Connected Station .................................................................................... 35

Connecting Timeout ................................................................................. 21
Connection ............................................................................................... 35
Connection Time ...................................................................................... 34
Connection Time Limited ........................................................................ 34
Control relay output block ....................................................................... 57
Counter events .......................................................................................... 56
CS ............................................................................................................. 35
CT ................................................................................................. 32, 34, 66
CTS ........................................................................................ 20, 22, 40, 61
D
Data Point ................................................................................................. 49
Data point address .................................................................................... 46
Data polling .............................................................................................. 51
DC ...................................................................................................... 23, 30
DCD ....................................................................................... 22, 23, 40, 61
DCD signal ............................................................................................... 36
DD ............................................................................................................ 35
DE ............................................................................................................ 20
Delay measurement .................................................................................. 48
DESTINATION address .......................................................................... 46
DFC .......................................................................................................... 61
Diagnostic Counters ........................................................................... 23, 30
Direction ................................................................................................... 29
DNP V3.00 slave protocol ....................................................................... 11
Double binary input .................................................................................. 55
DP ....................................................................................................... 49, 52
DR ............................................................................................................ 29
DV ............................................................................................................ 25
E
EN ...................................................................................................... 22, 65
Enhanced Protocol Architecture (EPA) ................................................... 43
Enquiry Limit ........................................................................................... 22
EO ................................................................................................ 29, 47, 54
Event data ..................................................................................... 45, 52, 65
Event Offset .............................................................................................. 29
F
Fatal error ................................................................................................... 9
Flag byte ................................................................................................... 53
Freeze and clear ........................................................................................ 60
Freeze Counters .................................................................................. 49, 60
Function code ........................................................................................... 43
FZ ....................................................................................................... 49, 60
80
G
General Interrogation ................................................................................ 48
GI .............................................................................................................. 48
H
Handshaking ............................................................................................. 45
Header Timeout ........................................................................................ 21
Hostname .................................................................................................. 26
HT ....................................................................................................... 21, 66
I
IA ........................................................................................................ 26, 46
IL ........................................................................................................ 28, 47
Immediate freeze ...................................................................................... 60
IN ........................................................................................................ 32, 47
In Use .................................................................................................. 16, 25
Index ............................................................................................. 29, 46, 52
Information Address Length ..................................................................... 28
Input data .................................................................................................. 53
Intelligent Electronic Devices (IEDs) ...................................................... 43
Internal Indications ............................................................................. 32, 47
Internet Address ........................................................................................ 26
IP address .................................................................................................. 26
IU .................................................................................................. 16, 25, 34
L
LA ....................................................................................................... 23, 65
LI .............................................................................................................. 25
Line Number ............................................................................................. 25
Link Layer Attributes ............................................................................... 16
Link Layer Confirmations Enabled .......................................................... 23
Link Service Data Units (LSDU) ............................................................. 15
Link Type ................................................................................................. 23
LK ....................................................................................................... 23, 40
LPDU ........................................................................................................ 19
LT ............................................................................................................. 31
M
MA ...................................................................................................... 26, 46
Master Address ......................................................................................... 26
Maximum Delayed Response Time ......................................................... 33
Maximum Message Length ................................................................ 19, 28
Maximum random delay for retransmission ............................................. 20
MC ...................................................................................................... 35, 37
Message Application .......................................................................... 23, 27
Message Identification ........................................................................ 22, 27
MI ................................................................................................. 22, 27, 61
ML ...................................................................................................... 19, 28
81

Modem Command .................................................................................... 35

Modem Signal .......................................................................................... 22
MS ...................................................................................................... 23, 27
MT ............................................................................................................ 33
Multi-drop network topology ................................................................... 15
Multiple stations ................................................................................. 75, 77
N
NET .................................................................................................... 30, 45
Network topologies .................................................................................. 15
No limitations ........................................................................................... 14
O
OA ............................................................................................................ 46
Object commands ..................................................................................... 57
Object Status ............................................................................................ 32
Offset .................................................................................................. 29, 58
One station ............................................................................................... 75
Open Systems Interconnection (OSI) ....................................................... 43
OS ....................................................................................................... 32, 54
OT ............................................................................................................ 21
Output data ............................................................................................... 57
OV ...................................................................................................... 58, 59
P
Parity ........................................................................................................ 18
PC ................................................................................................. 28, 36, 65
PD ............................................................................................................. 19
Physical layer ........................................................................................... 43
PO ............................................................................................................. 17
Point-to-point network topology .............................................................. 15
Poll Delay ................................................................................................. 19
Polled Report-by-Exception Operation .............................................. 45, 52
Polling Period ........................................................................................... 19
PP ............................................................................................................. 19
Priorities ................................................................................................... 45
Process Data Confirmation ....................................................................... 28
Protocol .................................................................................................... 17
Protocol converter .................................................................................... 45
PS ............................................................................................................. 17
PT ............................................................................................................. 29
Pulse counters ........................................................................................... 56
Pulse Dialing ............................................................................................ 36
Pulse Length ............................................................................................. 29
PY ............................................................................................................. 18
Q
QL ............................................................................................................ 58
82
Quiescent Operation ................................................................................. 45

R
Radio Connection Wait Time ................................................................... 36
Radio Disconnection Delay ...................................................................... 35
RC ............................................................................................................. 36
RD ............................................................................................................. 18
Read, conditional write ............................................................................. 14
Read-only ................................................................................................. 14
Receive Interrupt Enable Delay ................................................................ 22
Receiver Data Bit Count ........................................................................... 18
Remote Calls Enabled .............................................................................. 36
Remote host .............................................................................................. 26
Remote Terminal Units (RTUs) ............................................................... 43
Reply Time-out ......................................................................................... 33
Request ..................................................................................................... 57
Response Timeout .................................................................................... 21
Restart bit ............................................................................................ 30, 57
Restart commands .................................................................................... 60
RI .............................................................................................................. 22
RK ............................................................................................................. 21
RM ................................................................................................ 30, 51, 60
RT ....................................................................................................... 33, 66
RTS ........................................................................................................... 21
Running Mode .......................................................................................... 30
RW ............................................................................................................ 36
S
SA ....................................................................................................... 25, 46
SB ............................................................................................................. 18
SCS ............................................................................................................. 5
SD ....................................................................................................... 17, 46
SE ....................................................................................................... 27, 58
Slave Address ........................................................................................... 25
SOURCE address ..................................................................................... 46
Spontaneous data ...................................................................................... 27
SR ............................................................................................................. 36
ST ............................................................................................................. 33
Static data ................................................................................................. 45
Static Report-by-Exception Operation ............................................... 45, 52
Status codes .............................................................................................. 10
Application Layer ............................................................................... 61
Link Layer .......................................................................................... 61
Stop Bits ................................................................................................... 18
Subset levels ....................................................................................... 43, 65
SY ....................................................................................................... 48, 60
Synchronise .............................................................................................. 48
83

SYS 600 ..................................................................................................... 5

SYS Waiting Time ................................................................................... 33
SYS_BASCON.COM .............................................................................. 12
System Device Name ............................................................................... 17
System Messages Enabled ....................................................................... 27
System objects .......................................................................................... 14
T
TCP mode ................................................................................................. 75
TD ............................................................................................................ 19
Test function of link ................................................................................. 45
TI ........................................................................................................ 21, 66
Time synchronisation ............................................................................... 60
Transmission Wait Delay ......................................................................... 20
Transmitter Data Bit Count ...................................................................... 19
Transport layer ......................................................................................... 43
Transport Layer Timeout ......................................................................... 32
TT ....................................................................................................... 32, 66
TW ............................................................................................................ 20
TY ............................................................................................................ 58
U
UDP mode .......................................................................................... 76, 77
UN ...................................................................................................... 58, 59
Unsolicited messages ............................................................................... 45
Unsolicited Report-by-Exception Operation ............................................ 45
V
Variation ................................................................................................... 73
W
Warm restart ............................................................................................. 60
Wiring ................................................................................................ 40, 62
Write-only ................................................................................................ 14
X
XR ...................................................................................................... 20, 66
84
1MRS751860-MEN EN 02.2005
ABB Oy
Substation Automation Products
P.O. Box 699
FI-65101 Vaasa
FINLAND
Tel. +358 10 22 11
Fax. +358 10 224 1094
www.abb.com/substationautomation

SYS600 - DNP V3.00 Master Protocol

Uploaded by

Copyright:

Available Formats

SYS600 - DNP V3.00 Master Protocol

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SYS600 - DNP V3.00 Master Protocol

Uploaded by

Copyright:

Available Formats

MicroSCADA Pro

SYS 600 *9.1

1. About this manual .....................................................................5

©Copyright 2005 ABB Oy, Substation Automation Products, Vaasa, FINLAND 3

DNP V3.00 Master Protocol

4.4. Signal engineering ...................................................................... 61

1. About this manual

DNP V3.00 master

DNP V3.00 Master Protocol

1.4. Use of symbols

Caution icon indicates important information or warning related to

Information icon alerts the reader to pertinent facts and conditions.

1.5. Related documents

Name of the manual MRS number

DNP V3.00 DATA LINK LAYER

1.6. Document revisions

Version Revision number Date History

2.1. Backup copies

2.2. Fatal errors

Shutting down the base system computers by switching off the

DNP V3.00 Master Protocol

3.2.1. Base system configuration

DNP V3.00 Master Protocol

#CREATE SYS:B = LIST(-

#CREATE LIN:V = LIST(- ;REQUIRES THE PC-NET PROGRAM

#CREATE NOD:V = LIST(-

#CREATE APL:V = LIST(-

#SET STY30:BCX = "DNP"

;*** NET 3 stations ***

#CREATE STA:V = LIST(-

DNP V3.00 Master Protocol

#CREATE STA:V = LIST(-

3.2.2. Communication system configuration

Setting the attribute values

Fig. 3.2.2.-1 Point-to-point and serial bus topologies

3.2.2.1. DNP V3.00 link layer

DNP V3.00 Master Protocol

application layer of a NET unit is responsible for assembling and disassembling

Link layer attributes

SD System Device Name

PS Buffer Pool Size

Data type: Integer

DNP V3.00 Master Protocol

RD Receiver Data Bit Count

TD Transmitter Data Bit Count

ML Maximum Message Length

DNP V3.00 Master Protocol

Default value 230

XR Maximum Random Delay for Retransmission

TW Transmission Wait Delay

RK RTS Keep Up Padding Characters

DNP V3.00 Master Protocol

RI Receive Interrupt Enable Delay

LA Link Layer Confirmations Enabled

DNP V3.00 Master Protocol

DNP V3.00 master protocol supports the following counters:

3.2.2.2. DNP V3.00 application layer

Application layer attributes

Setting this attribute is not needed when the station is created by

;* NET 3 stations *

;* Configure Autocaller ***********************