DNP3 Master Protocol

7/24/2019 DNP3 Master Protocol

1/44

DNP3 Master Protocol


2/44

Documentation for Cybectec part number P-SMPR-0201

The information in this document applies to software version 3.0or later and is subject to change withoutnotice.

Quebec City

730 Commerciale StreetSuite 200Saint-Jean-Chrysostome, QuebecCanada G6Z 2C5Phone: 418-834-0009Fax: 514-227-5256

Montreal

1290 St. Denis StreetSuite 400Montreal, QuebecCanada H2X 3J7Phone: 514-845-6195Fax: 514-227-5256


3/44

Revision History

Version Date Author Comments

4 2007-02-27 Johanne Lavalle Cooper integration, no major changes for version 4.Tx during SBO default changed to no checkmark.

3 2007-01-15 Jonathan Fortier Added support for Qualifier Code 0x27

2 2006-07-11 Frdric Vallires Test mode function.

1 2006-01-20 Rmi Dutil No major changes with respect to version 2.0.


4/44


5/44

Contents

Tables ............................................................................................................................................. iii

1. Introduction ............................................................................................................................. 1

2.

Features.................................................................................................................................... 2

2.1 Communication .....................................................................................................................22.2 Interoperability...................................................................................................................... 2

2.2.1 DNP3 Device Profile................................................................................................. 32.2.2 Implementation Table.............................................................................................. 6

2.3 Device Data Retrieval........................................................................................................... 102.4 Device Control..................................................................................................................... 10

2.4.1 Analog output control operations ............................................................................ 102.4.2 Binary output control operations............................................................................. 10

2.4.2.1 OPEN/CLOSE operations using two PULSE points..................................... 11

3. Configuration Settings ........................................................................................................... 123.1 General Settings.................................................................................................................. 12

3.2

Redundancy Settings ........................................................................................................... 15

3.3 Analog Input Settings .......................................................................................................... 183.4 Binary Input Settings ........................................................................................................... 183.5 Counter Input Settings......................................................................................................... 183.6 Frozen Counter Input Settings .............................................................................................. 193.7 Analog Output Settings ........................................................................................................ 193.8 Binary Output Settings......................................................................................................... 193.9 Comma-Separated Values File Format ................................................................................... 21

3.9.1 General Settings Line Definition.............................................................................. 213.9.2 Redundancy Settings Line Definition ....................................................................... 223.9.3 Switched Connection Settings Line Definition........................................................... 233.9.4 Switched Connection Schedule Settings Line Definition ............................................. 24

3.9.5

Analog Input Line Definition ................................................................................... 25

3.9.6 Binary Input Line Definition.................................................................................... 253.9.7 Counter Input Line Definition.................................................................................. 263.9.8 Frozen Counter Input Line Definition....................................................................... 273.9.9 Analog Output Line Definition................................................................................. 293.9.10 Binary Output Line Definition.................................................................................. 30

4. Implementation Details ......................................................................................................... 314.1 Startup Sequence ................................................................................................................ 314.2 Scan Process....................................................................................................................... 31

4.2.1 Automated operations based on internal indications ................................................. 324.2.2 Automated operations based on events................................................................... 334.2.3 Scheduled operations............................................................................................. 34

4.3 Listen Mode ........................................................................................................................ 34

5. Troubleshooting ..................................................................................................................... 36

DNP3MASTER PROTOCOL I


6/44


7/44

Tables

Table 2-1 Communication Features .................................................................................. 2

Table 2-2 Device Profile .................................................................................................... 5

Table 2-3 Implementation Table ...................................................................................... 9

Table 2-4

Variation of object 41 used for analog output control operations ................. 10

Table 2-5 Binary output control functions based on configuration................................ 11

Table 3-1 General Settings ............................................................................................. 14

Table 3-2 Redundancy Settings ...................................................................................... 17

Table 3-3 Analog Input Settings..................................................................................... 18

Table 3-4 Binary Input Settings...................................................................................... 18

Table 3-5 Counter Input Settings ................................................................................... 18

Table 3-6 Frozen Counter Input Settings ....................................................................... 19

Table 3-7

Analog Output Settings................................................................................... 19

Table 3-8 Binary Output Settings ................................................................................... 20

Table 3-9 General Settings Line Definition..................................................................... 22

Table 3-10 Redundancy Settings Line Definition.............................................................. 23

Table 3-11 Switched Connection Settings Line Definition................................................ 24

Table 3-12 Switched Connection Schedule Settings Line Definition ................................ 24

Table 3-13 Analog Input Line Definition........................................................................... 25

Table 3-14 Binary Input Line Definition ........................................................................... 26

Table 3-15 Counter Input Line Definition......................................................................... 27

Table 3-16 Frozen Counter Input Line Definition ............................................................. 28

Table 3-17 Analog Output Line Definition ........................................................................ 29

Table 3-18 Binary Output Line Definition ......................................................................... 30

Table 4-1 Automated operations based on internal indications..................................... 33

Table 5-1 Troubleshooting.............................................................................................. 36

DNP3MASTER PROTOCOL III


8/44


9/44

1. Introduction

This manual provides the information required to install and set up a DNP3 master protocolcomponent on a Cybectec SMP gateway.

The DNP3 master protocol component is used to retrieve data from any device compatible withthe DNP3 protocol definition. It can also be used to control such a device.

You need to be familiar with the SMP gateway environment, master protocol concepts, and theDNP3 protocol specification before proceeding with this document. You can obtain thisinformation by reading the following documents:

Master Protocol Common Concepts, GUI-00316-00018-T, Cybectec.

SMP Gateway User Manual, GUI-00316-00001-T, Cybectec.

DNP V3.00 Data Link Layer(P009-0PD.DL), Harris Corporation.

DNP V3.00 Transport Functions(P009-0PD.TF), Harris Corporation.

DNP V3.00 Application Layer(P009-0PD.APP), Harris Corporation.

DNP V3.00 Data Object Library(P009-0BL), Harris Corporation.

DNP V3.00 Subset Definitions(P009-0IG.SUB), DNP Users Group.

Transporting DNP V3.00 over Local and Wide Area Networks, DNP Users Group, 1998.

DNP3MASTER PROTOCOL 1


10/44

2. Features

This chapter outlines the features provided by the DNP3 master protocol component.

2.1 Communication

The following communication features are available when connecting devices to the SMPhardware:

Feature Comment

Serial Ports The DNP3 protocol component supports RS-232, RS-422 and RS-485 interfaces at bit rates up to 115200 bps.

Multidrop Multiple instances of the DNP3 protocol component can share asingle serial port, as long as different addresses are used to identifythe devices and as long as the devices support such a feature.

PassthruConnections

The DNP3 protocol component allows for passthru connections.Note that it is necessary to suspend link activity to establish such a

connection.Listen Mode Requires a single serial port. Since DNP3 application layer responses

are self-explanatory, there is no need to know the associatedrequest.

TCP/IP The DNP3 protocol component supports TCP/IP communication.Although the DNP Users Group recommends using TCP port 20000for DNP devices, any other port number can be used if theassociated slave device supports the port number.

Modem The DNP3 protocol component supports modem connections, ineither permanent or switched mode.

Link Redundancy This protocol component can be configured to use 2 differentcommunication links to communicate with the same device.

Hot Standby This protocol component can be configured to synchronize all itsdata and scanning states between 2 SMP gateways in a redundantsetup.

Table 2-1 Communication Features

2.2 Interoperability

This section, in conjunction with chapter 3,the DNP 3.0 Basic 4 Document Set, and the DNPSubset Definitions Document, provides complete information on how to communicate with theDNP3 master component via the DNP3 protocol.

The implementation of the DNP3 master is fully compliant with DNP V3.00 Subset Definition Level2, contains many Subset Level 3 features, and contains some functionality even beyond SubsetLevel 3.

2 DNP3MASTER PROTOCOL


11/44

2.2.1 DNP3 Device Profile

The following table provides a Device Profile Document in the standard format defined in theDNP V3.00 Subset Definitions Document. While it is referred to in the DNP V3.00 SubsetDefinitions as a Document, it is actually one of three components that make up aninteroperability guide. The other two components are:

the Implementation Table, provided in section 2.2.2;

a description of the configuration settings, which you can find in chapter 3.

Together, these three components make up a complete interoperability and configuration guidefor the DNP3 master protocol component.

DNP V3.00DEVICE PROFILE DOCUMENT

(See also the Implementation Table, in section 2.2.2)

Vendor Name: Cybectec Inc.

Device Name: DNP3 Master for Cybectecs SMP Gateway

Highest DNP Level Supported:

For Requests: Level 2

For Responses: Level 2

Device Function:

Master

Slave

Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels Supported (thecomplete list is described in the attached table):

For static (non-change-event) object requests, request qualifier codes 00 and 01 (start-stop) aresupported, in addition to request qualifier code 06 (no range or all points).

16-bit and 32-bit Analog Change Events with Time may be requested.

The read function code for Object 50 (Time and Date), variation 1, is supported.

Maximum Data Link Frame Size (bytes):

Transmitted: 292

Received: 292

Maximum Application Fragment Size (bytes):

Transmitted: 2048

Received: 2048

Maximum Data Link Retries:

NoneFixed at _______________________

Configurable from 0 to 255, default value set

to 2.

Maximum Application Layer Retries:

None

Configurable from 0 to 255, default

value set to 2.



12/44

Requires Data Link Layer Confirmation:

Never

Always

Sometimes

Configurable between one of the following:

- Never (default);

- Always;

- Sometimes (for multi-frame fragments).

Requires Application Layer Confirmation:

Never

Always

When reporting Event Data

When sending multi-fragment responsesSometimes

Configurable

Timeouts while waiting for:

Data Link Confirm None Fixed at ____ Variable Configurable from 0 to 31days, in ms (default valueset to 3000 ms)

Complete Appl. Fragment None Fixed at ____ Variable Configurable

Application Confirm None Fixed at ____ Variable Configurable

Complete Appl. Response None Fixed at ____ Variable Configurable, from 0 to 31days, in ms (default valueset to 3000 ms)



13/44

Executes Control Operations*:

WRITE Binary Outputs Never Always Sometimes Configurable

SELECT/OPERATE Never Always Sometimes Configurable (see section 3.1)

DIRECT OPERATE Never Always Sometimes Configurable (see section 3.1)

DIRECT OPERATE - NO ACKNever Always Sometimes Configurable

Count > 1 Never Always Sometimes Configurable

Pulse On Never Always Sometimes Configurable

Pulse Off Never Always Sometimes Configurable

Latch On Never Always Sometimes Configurable

Latch Off Never Always Sometimes Configurable

Queue Never Always Sometimes Configurable

Clear Queue Never Always Sometimes Configurable

*The execution of control operations may be enabled/disabled.

Expects Binary Input Change Events:

Either time-tagged or non-time-tagged for a single event

Both time-tagged and non time-tagged for a single event

Configurable

Table 2-2 Device Profile



14/44

2.2.2 Implementation Table

The following table identifies the variations, function codes and qualifiers supported by the DNP3master component in both request and response messages.

Text shaded as Subset Level 3 indicates Subset Level 3 functionality (beyond Subset Level 2),

and text shaded as beyond Subset Level 3 indicates functionality beyond Subset Level 3.

OBJECTREQUEST

(Component may send)RESPONSE

(Component will parse)

ObjectNumber

VariationNumber

DescriptionFunction

Codes (dec)Qualifier

Codes (hex)Function Codes

(dec)Qualifier Codes

(hex)

1 0 Binary Input (variation 0 is used torequest default variation).

1 (read) 00, 01 (start-stop)06(no range, or all)

1 1 Binary Input 1 (read) 00, 01 (start-stop)06(no range, or all)

129 (response) 00, 01 (start-stop)17, 28 (index)27 (index)

1 2 Binary Input with Status 1 (read) 00, 01 (start-stop)06(no range, or all)


2 0 Binary Input Change (variation 0 isused to request default variation).

1 (read) 06(no range, or all)07, 08(limited qty)

2 1 Binary Input Change without Time. 1 (read) 06(no range, or all)07, 08(limited qty)

129 (response)130 (unsol. resp)

17, 28 (index)27 (index)

2 2 Binary Input Change with Time. 1 (read) 06(no range, or all)07, 08(limited qty)



2 3 Binary Input Change with RelativeTime.




10 0 Binary Output Status (variation 0 isused to request default variation).


10 2 Binary Output Status 1 (read) 00, 01 (start-stop)06(no range, or all)


12 1 Control Relay Output Block 3 (select)4 (operate)5 (direct op)6 (dir. op, noack)

17, 28 (index) 129 (response) echo of request

20 0 Binary Counter (variation 0 is used torequest default variation).

1 (read)7 (freeze)8 (freeze noack)9 (freeze clear)10(frz. cl. noack)

00, 01 (start-stop)06(no range, or all)

20 1 32-Bit Binary Counter 1 (read)7 (freeze)8 (freeze noack)9 (freeze clear)10(frz. cl. noack)



20 2 16-Bit Binary Counter 1 (read)7 (freeze)8 (freeze noack)9 (freeze clear)10(frz. cl. noack)



20 3 32-Bit Delta Counter 1 (read)

7 (freeze)8 (freeze noack)9 (freeze clear)10(frz. cl. noack)

00, 01 (start-stop)

06(no range, or all)

129 (response) 00, 01 (start-stop)


20 4 16-Bit Delta Counter 1 (read)7 (freeze)8 (freeze noack)9 (freeze clear)10(frz. cl. noack)





15/44

OBJECTREQUEST



ObjectNumber

VariationNumber

DescriptionFunction




(hex)

20 5 32-Bit Binary Counter without Flag. 1 (read)7 (freeze)8 (freeze noack)9 (freeze clear)10(frz. cl. noack)



20 6 16-Bit Binary Counter without Flag. 1 (read)7 (freeze)8 (freeze noack)9 (freeze clear)10(frz. cl. noack)



20 7 32-Bit Delta Counter without Flag. 1 (read)7 (freeze)8 (freeze noack)9 (freeze clear)10(frz. cl. noack)



20 8 16-Bit Delta Counter without Flag. 1 (read)7 (freeze)8 (freeze noack)9 (freeze clear)10(frz. cl. noack)



21 0 Frozen Counter (variation 0 is used to

request default variation).

1 (read) 00, 01 (start-stop)


21 1 32-Bit Frozen Counter 1 (read) 00, 01 (start-stop)06(no range, or all)


21 2 16-Bit Frozen Counter 1 (read) 00, 01 (start-stop)06(no range, or all)


21 9 32-Bit Frozen Counter without Flag. 1 (read) 00, 01 (start-stop)06(no range, or all)


21 10 16-Bit Frozen Counter without Flag. 1 (read) 00, 01 (start-stop)06(no range, or all)


22 0 Counter Change Event (variation 0 isused to request default variation).


22 1 32-Bit Counter Change Event without

time.

1 (read) 06(no range, or all)

07, 08(limited qty)

129 (response)

130 (unsol. resp)

17, 28 (index)

27 (index)22 2 16-Bit Counter Change Event without

time.1 (read) 06(no range, or all)

07, 08(limited qty)129 (response)130 (unsol. resp)


30 0 Analog Input (variation 0 is used torequest default variation).


30 1 32-Bit Analog Input. 1 (read) 00, 01 (start-stop)06(no range, or all)


30 2 16-Bit Analog Input. 1 (read) 00, 01 (start-stop)06(no range, or all)


30 3 32-Bit Analog Input without Flag. 1 (read) 00, 01 (start-stop)06(no range, or all)


30 4 16-Bit Analog Input without Flag. 1 (read) 00, 01 (start-stop)


129 (response) 00, 01 (start-stop)


30 5 Short Floating Point Analog Input. 1 (read) 00, 01 (start-stop)06(no range, or all)


32 0 Analog Change Event (variation 0 isused to request default variation).


32 1 32-Bit Analog Change Event withoutTime.




32 2 16-Bit Analog Change Event withoutTime.






16/44

OBJECTREQUEST



ObjectNumber

VariationNumber

DescriptionFunction




(hex)

32 3 32-Bit Analog Change Event with Time. 1 (read) 06(no range, or all)07, 08(limited qty)



32 4 16-Bit Analog Change Event with Time. 1 (read) 06(no range, or all)07, 08(limited qty)



32 5 Short Floating Point Analog ChangeEvent.




32 7 Short Floating Point Analog ChangeEvent with Time.




40 0 Analog Output Status (variation 0 isused to request default variation).


40 1 32-Bit Analog Output Status. 1 (read) 00, 01 (start-stop)06(no range, or all)


40 2 16-Bit Analog Output Status. 1 (read) 00, 01 (start-stop)06(no range, or all)


40 3 Short Floating Point Analog OutputStatus.

1 (read) 00, 01(start-stop)06(no range, or all)


41 1 32-Bit Analog Output Block. 3 (select)4 (operate)5 (direct op)6 (dir. op, noack)


41 2 16-Bit Analog Output Block. 3 (select)4 (operate)5 (direct op)6 (dir. op, noack)


41 3 Short Floating Point Analog OutputBlock.

3 (select)4 (operate)5 (direct op)6 (dir. op, noack)


50 0 Time and Date 1 (read) 00, 01 (start-stop)06(no range, or all)

129 (response) 00, 01 (start-stop)07 (limited qty=1)17, 28 (index)27 (index)

50 1 Time and Date 1 (read)2 (write)

00, 01 (start-stop)06(no range, or all)07 (limited qty=1)08 (limited qty)17, 28 (index)

129 (response) 00, 01 (start-stop)07 (limited qty=1)17, 28 (index )27 (index)

51 1 Time and Date CTO. 129 (response) 07 (limited qty)(qty = 1)

51 2 Unsynchronized Time and Date CTO. 129 (response) 07 (limited qty)(qty = 1)

52 1 Time Delay Coarse 129 (response) 07 (limited qty)(qty = 1)

52 2 Time Delay Fine 129 (response) 07 (limited qty)(qty = 1)

60 0 Class 0, 1, 2, and 3 Data 1 (read)20(enbl. unsol.)21(dsbl. unsol.)


60 1 Class 0 Data 1 (read) 06(no range, or all)

60 2 Class 1 Data 1 (read)20(enbl. unsol.)21(dsbl. unsol.)

06(no range, or all)07, 08(limited qty)





70 1 File Identifier 2 (write) 1b (free-format) 129 (response) 1b (free-format)

80 1 Internal Indications 2 (write) 00 (start-stop) (index must =7)

No Object (function code only). 13 (cold restart)

No Object (function code only). 14(warm restart)



17/44

OBJECTREQUEST



ObjectNumber

VariationNumber

DescriptionFunction




(hex)

No Object (function code only). 23 (delay meas.)

Table 2-3 Implementation Table



18/44

2.3 Device Data Retrieval

Application layer class 0/1/2/3 data read requests are used to retrieve data objects from thedevice. The data objects obtained are then transformed to standard analog or binary data types,as specified by the configuration settings (see chapter 3 for further details on configuration),published on the system, and made available to slave components.

All static data and without-time event data are time-stamped by the system on reception. Forevent data reported with time, the object time is preserved.

2.4 Device Control

Analog and binary output points may be configured to allow device control. The DNP Select(FC3), Operate(FC 4) and Direct Operate(FC 5) application layer requests are used to send controlrequests to devices. Usage of Select/Operateand/or Direct Operate control requests is on apoint-by-point basis, and is dictated by the Select Required setting (see sections 3.7 and 3.8).

When an Operate or a Direct Operate requestis successfully confirmed by the remote device, theDNP3 master component sends an operate feedback poll request, to obtain the state of all pointsthat may potentially have changed during the output control operation. The operate feedbackpoll request is actually a Readrequest for data class 1/2/3.

2.4.1 Analog output control operations

For analog output control operations, the variation used for object 41 Analog Output Block,depends on the Output Controlsetting of each analog output point.

Output Control Object 41 Variation

32-Bit Value 1 32-Bit Analog Output Block

16-Bit Value 2 16-Bit Analog Output Block

Float Value 3 Short Floating-Point Analog Output Block

Table 2-4 Variation of object 41 used for analog output control operations

2.4.2 Binary output control operations

Binary output control operations use object 12 variation 1 Control Relay Output Block. TheControl Code field is set in accordance with DNP Technical Bulletin 9701-002 Control RelayOutput Block Minimum Implementation, and the function performed depends on the ControlType setting of each binary output point.

Control Type Function

Not supported Any control operation requested on this point will be refused.

Latch ON/OFF The output point is controlled using DNP Latch ON/OFFfunctions.

An OPEN request ends in a Latch OFFoperation, and a CLOSErequest ends in a Latch ONoperation.

PULSE requests are not supported.

Trip/Close The output point is controlled using DNP Trip/Closefunctions.

PULSE requests are not supported.

Pulse The output point is controlled using DNP Pulsefunctions.



19/44

Control Type Function

OPEN/CLOSE requests are not supported.

Pulse, Open The output point is controlled using DNP Pulsefunctions.

All system requests (OPEN/CLOSE*, PULSE) are allowed.

*See section 2.4.2.1 for a description of the management ofOPEN/CLOSE requests on open/close pairs.

Pulse, Close The output point is controlled using DNP Pulsefunctions.

All system requests (OPEN/CLOSE*, PULSE) are allowed.

*See section 2.4.2.1.

Table 2-5 Binary output control functions based on configuration

2.4.2.1 OPEN/CLOSE operations using two PULSE points

The DNP3 master component provides a mechanism by which slave components can operate twoPULSE points using system OPEN/CLOSE requests. Two points are associated to form an

open/close pair, one member handling OPEN requests and the other, CLOSE requests.Open/close pair configuration is described in section 3.8.

Thus, OPEN/CLOSE requests on any of these two points will result in a PULSE controlfunction being sent to the remote device on the point that handles the requestedoperation. Note that even in this case, a PULSE execute type of operation on any point of anopen/close pair is translated into the PULSE ON control function on the same point.



20/44

3. Configuration Settings

This chapter enumerates the configuration settings to be specified for each DNP3 master protocolinstance. Cybectecs SMP Configsoftware is generally used to define these settings.

Only the settings specific to the DNP3 protocol are described here. The settings common to allmaster protocol components are described in the Cybectec document entitled Mas er ProtocolCommon Concepts.

t

3.1 General Settings

Every instance of a master protocol component contains general settings, which set the generalbehavior of the component. The following table shows the general settings that are specific tothe DNP3 master protocol.

Setting Description

Link Address The DNP data link address of this DNP3 master protocol instance.This address must be unique for each instance that uses a particularmultidrop link.

Range: 0 to 65,534

Default value: 1

Slave Link Address The DNP data link address of the remote device with which thisDNP3 master instance is communicating.

Range: 0 to 65,535

Default value: 1

Class 0123 PollCycle

Time interval, in milliseconds, after which the DNP3 master will senda read request for Class 0, Class 1, Class 2 and Class 3 data (staticI/O point value and change event).

If you set this value to 0, the request will not be sent cyclically.

Range: 0 to 2,147,483,647 ms

Default value: 3,600,000 ms (1 hr)

Class 0 Poll Cycle Time interval, in milliseconds, after which the DNP3 master will senda read request for Class 0 data (static I/O point value).


Range: 0 to 2,147,483,647 ms

Default value: 0

Class 1 Poll Cycle Time interval, in milliseconds, after which the DNP3 master will send

a read request for Class 1 data (report by exception/change event).


Range: 0 to 2,147,483,647 ms

Default value: 0

Class 2 Poll Cycle Time interval, in milliseconds, after which the DNP3 master will senda read request for Class 2 data (report by exception/change event).




21/44

Setting Description

Range: 0 to 2,147,483,647 ms

Default value: 0



Range: 0 to 2,147,483,647 ms

Default value: 0

Class 123 Poll Cycle Time interval, in milliseconds, after which the DNP3 master will senda read request for Class 1, Class 2 and Class 3 data (report byexception/change event).


Range: 0 to 2,147,483,647 ms

Default value: 5,000 ms

Clock Sync A checkmark indicates that the DNP3 master can synchronize theslave station clock. If you put a checkmark, clock synchronizationoperations may be initiated in two different ways:

Automatically, when IIN1-4 (clock synchronization required) isset in any response received from the slave device.

Cyclically, based on the value of the Clock Sync Cyclesetting (ifnot 0).

Range: checkmark / no checkmark

Default value: checkmark

Clock Sync Cycle Time interval, in milliseconds, after which the DNP3 master will senda clock synchronization request to the slave device, if allowed (seeClock Sync).


Range: 0 to 2,147,483,647 ms

Default value: 30 secs

Unsolicited Report If you put a checkmark, the DNP3 master will send an enableunsolicited response request (for class 1/2/3) on startup of theremote slave.


Default value: no checkmarkLink Sync If you put a checkmark, the DNP3 master begins the link-up

sequence with a Read IIN request. This request, which has noimpact on the master or the device, allows the DNP3 master tosynchronize the link with the device. This feature is relevant whenusing serial links, and when the SMP gateway is in a redundantconfiguration.


Default value: no checkmark



22/44

Setting Description

Link ConfirmationMode

Data link layer confirmation mode used by the DNP3 master.

Range: NeverNo confirmation for any frame.

SometimesConfirmation requested for multi-framefragments only.

AlwaysConfirmation requested for all frames.

Default value: Never

Link ConfirmationTimeout

The number of milliseconds to wait for a remote device data linklayer confirmation of the last frame sent, before attempting anyretries (only if frame sent with confirm requested). Measured afterthe last byte of the data frame sent.

A 0 value causes an immediate timeout.

Range: 0 to 2,147,483,647 ms


Link Max Retries The number of attempts to re-transmit a data link frame that wasnot confirmed by the remote device (only if frame sent with confirmrequested).

Range: 0 to 255

Default value: 2

Applic Max Retries The number of attempts to re-transmit an application layer request,when no response is received from the remote device during the

application response timeout interval (seeApplic ResponseTimeout).

Range: 0 to 255

Default value: 2

Applic ResponseTimeout

The number of milliseconds to wait for a remote device to respondto an application layer request. Measured after the last byte of thedata frame sent.

Range: 100 to 300,000 msDefault value: 3,000 ms

Tx During SBO A checkmark specifies that data can be transmitted to the remote

device between the selection and the operation of a control outputpoint.



Table 3-1 General Settings



23/44

3.2 Redundancy Settings

Each instance of this master protocol component contains redundancy settings, which set thegeneral behavior of the redundancy component. The following table shows the redundancysettings that are specific to the DNP3 protocol component.

Setting Description

Link 1 Test Interval The delay, in milliseconds, between two complete link test requestson link 1.

Range: 0 to 300,000 ms


Link 2 Test Interval The delay, in milliseconds, between two complete link test requestson link 2.

Range: 0 to 300,000 ms


Link Address The DNP data link address of this DNP3 master protocol instance.

This address must be unique for each instance that uses a particularmultidrop link.

Range: 0 to 65,534

Default value: 1

Slave Link Address The DNP data link address of the remote device with which thisDNP3 master instance is communicating.

Range: 0 to 65,535

Default value: 1

Class 0123 Poll

Cycle

Time interval, in milliseconds, after which the DNP3 master will send

a read request for Class 0, Class 1, Class 2 and Class 3 data (staticI/O point value and change event).


Range: 0 to 2,147,483,647 ms

Default value: 3,600,000 ms (1 hr)

Class 0 Poll Cycle Time interval, in milliseconds, after which the DNP3 master will senda read request for Class 0 data (static I/O point value).


Range: 0 to 2,147,483,647 ms

Default value: 0Class 1 Poll Cycle Time interval, in milliseconds, after which the DNP3 master will send



Range: 0 to 2,147,483,647 ms

Default value: 0

Class 2 Poll Cycle Time interval, in milliseconds, after which the DNP3 master will send



24/44

Setting Description



Range: 0 to 2,147,483,647 ms

Default value: 0



Range: 0 to 2,147,483,647 ms

Default value: 0

Class 123 Poll Cycle Time interval, in milliseconds, after which the DNP3 master will senda read request for Class 1, Class 2 and Class 3 data (report byexception/change event).


Range: 0 to 2,147,483,647 ms


Clock Sync A checkmark indicates that the DNP3 master can synchronize theslave station clock. If you put a checkmark, clock synchronizationoperations may be initiated in two different ways:

Automatically, when IIN1-4 (clock synchronization required) isset in any response received from the slave device.

Cyclically, based on the value of the Clock Sync Cyclesetting (ifnot 0).



Clock Sync Cycle Time interval, in milliseconds, after which the DNP3 master will senda clock synchronization request to the slave device, if allowed (seeClock Sync).


Range: 0 to 2,147,483,647 ms

Default value: 30 secs

Unsolicited Report If you put a checkmark, the DNP3 master will send an enableunsolicited response request (for class 1/2/3) on startup of the

remote slave.Range: checkmark / no checkmark


Link Sync If you put a checkmark, the DNP3 master begins the link-upsequence with a Read IIN request. This request, which has noimpact on the master or the device, allows the DNP3 master tosynchronize the link with the device. This feature is relevant whenusing serial links, and when the SMP gateway is in a redundantconfiguration.



25/44

Setting Description




Data link layer confirmation mode used by the DNP3 master.

Range: NeverNo confirmation for any frame.

SometimesConfirmation requested for multi-framefragments only.

AlwaysConfirmation requested for all frames.

Default value: Never


The number of milliseconds to wait for a remote device data linklayer confirmation of the last frame sent, before attempting any

retries (only if frame sent with confirm requested). Measured afterthe last byte of the data frame sent.

A 0 value causes an immediate timeout.

Range: 0 to 2,147,483,647 ms


Link Max Retries The number of attempts to re-transmit a data link frame that wasnot confirmed by the remote device (only if frame sent with confirmrequested).

Range: 0 to 255

Default value: 2

Applic Max Retries The number of attempts to re-transmit an application layer request,when no response is received from the remote device during theapplication response timeout interval (seeApplic ResponseTimeout).

Range: 0 to 255

Default value: 2


The number of milliseconds to wait for a remote device to respondto an application layer request. Measured after the last byte of thedata frame sent.

Range: 100 to 300,000 msDefault value: 3,000 ms

Table 3-2 Redundancy Settings



26/44

3.3 Analog Input Settings

Each instance of the master protocol component may contain several analog input points. Analoginput settings tell the component how to process data retrieved from the device. The followingtable shows the analog input settings that are specific to the DNP3 master protocol.

Setting Description

Index Logical index that identifies the point.

Range: 0 to 65,535

Default value: 0

Table 3-3 Analog Input Settings

3.4 Binary Input Settings

Each instance of the master protocol component may contain several binary input points. Binaryinput settings tell the component how to process data retrieved from the device. The followingtable shows the binary input settings that are specific to the DNP3 master protocol.

Setting Description

Type Type of binary input point.

Range: NormalUsual binary input point type.

Time sync statusBinary input point used to qualify thetimestamp of reported transitions.When set to 0, the reported timestampshave a synchronized status.When set to 1, the reported timestampshave a non-synchronized status.

Default value: Normal


Range: 0 to 65,535

Default value: 0

Table 3-4 Binary Input Settings

3.5 Counter Input Settings

Each instance of the master protocol component may contain several counter input points.Counter input settings tell the component how to process data retrieved from the device. The

following table shows the counter input settings that are specific to the DNP3 master protocol.

Setting Description


Range: 0 to 65,535

Default value: 0

Table 3-5 Counter Input Settings



27/44

3.6 Frozen Counter Input Settings

Each instance of the master protocol component may contain several frozen counter input points.Frozen counter input settings tell the component how to process data retrieved from the device.The following table shows the frozen counter input settings that are specific to the DNP3 masterprotocol.

Setting Description


Range: 0 to 65,535

Default value: 0

Table 3-6 Frozen Counter Input Settings

3.7 Analog Output Settings

Each instance of the master protocol component may contain several analog output points.Analog output settings tell the component how to control the device. The following table shows

the analog output settings that are specific to the DNP3 master protocol.

Setting Description


Range: 0 to 65,535

Default value: 0

Select Required A checkmark indicates that the output point is controlled with aSelect/Opera eapplication layer request. If you do not put atcheckmark, the output point will be controlled with a Direct Operaterequest.

Range: checkmark / no checkmarkDefault value: checkmark

Output Control The data type used for the output control object that is sent to theslave device when a control output operation occurs.

Range: 16-bit value32-bit valueFloating-point value

Default value: 32-bit value

Table 3-7 Analog Output Settings

3.8 Binary Output Settings

Each instance of the master protocol component may contain several binary output points. Binaryoutput settings tell the component how to control the device. The following table shows thebinary output settings that are specific to the DNP3 master protocol.

Setting Description




28/44

Setting Description

Range: 0 to 65,535

Default value: 0

Select Required A checkmark indicates that the output point is controlled with aSelect/Opera eapplication layer request. If you do not put at

checkmark, the output point will be controlled with a Direct Operaterequest.



Control Type Output control operations supported for this point, i.e., operationsthat can be forwarded to the remote device.

Pulse, Openand Pulse, Closesupport pulse operations, and allowslave protocol components to perform open/close operations on thepoint. The point has to be configured as a member of an open/closepair, and there has to be another point in the same pair, which isconfigured in a complementary way, that is: one Pulse, Openpoint and one Pulse, Close point.

The two points of an open/close pair are linked together using theOpen/Close Pairfield, so they do not have to be consecutive.

Open/close operations can be performed on either point of the pair,giving the same results. An open operation results in a pulseoperation on the Pulse, Open point of the pair, and a closeoperation results in a pulse operation on the Pulse, Close point ofthe pair. See section 2.4 - Device Control.

Force Pulse supports open, close and pulse operations on the point.A pulse is always transmitted to the device, regardless of which

request was received.

Range: Not SupportedLatch ON/OFFTrip/ClosePulsePulse, OpenPulse, CloseForce Pulse

Default value: Not Supported

Open/Close Pair Indicates the number of the open/close pair, if supported. Used to

combine two pulse points to allow open/close operations on eitherof the two points.

Note: Only two points can use the same Open/Close pair number.

Range: 0 not assigned1 to 65,535 pair number

Default value: 0

Table 3-8 Binary Output Settings



29/44

3.9 Comma-Separated Values File Format

Using SMP Config, you can import or export a CSV (Comma-Separated Values) file containingyour SMP gateway configuration. This section describes the format to be used in defining thevarious DNP3 master protocol settings.

See the document entitled SMP Config CSV Format Definition, to familiarize yourself with the CSV

file format.

3.9.1 General Settings Line Definition

Description: Defines the general settings for each instance of the DNP3 master protocol.

Type: A single line of data with a unique name.

Setting Description

Line Identifier Must be MDGP.

Master Name See the CSV-specific general settings, in the Master P otocolrCommon Conceptsdocument.

Device Prefix See General Settings in the Master Pro ocol Common Conceptstdocument.

Listen Mode See General Settings in the Master Pro ocol Common Conceptstdocument.

Link Address See General Settings in this document.

Slave Link Address See General Settings in this document.

Scan Priority See General Settings in the Master Pro ocol Common Conceptstdocument.

Control Enabled See General Settings in the Master Pro ocol Common Conceptstdocument.


See General Settings in this document.

Class 0 Poll Cycle See General Settings in this document.





Clock Sync See General Settings in this document.

Clock Sync Cycle See General Settings in this document.

Unsolicited Report See General Settings in this document.



Allowed values: 0: Never1: Sometimes2: Always

Link Confirmation See General Settings in this document.



30/44

Setting Description

Timeout

Link Max Retries See General Settings in this document.

Applic Max Retries See General Settings in this document.



Selection Timeout See General Settings in the Master Pro ocol Common Conceptstdocument.

Tx During SBO See General Settings in this document.

Notify When Ready See General Settings in the Master Pro ocol Common Conceptstdocument.

Delay Between Tx See General Settings in the Master Pro ocol Common Conceptstdocument.

Link Sync See General Settings in this document.

Test Mode Point See General Settings in the Master Pro ocol Common Conceptstdocument.

Test Mode Type See General Settings in the Master Pro ocol Common Conceptstdocument.

Hot-StandbySupport

See General Settings in the Master Pro ocol Common Conceptstdocument.

Add Prefix To LogicalPoints Only

Indicates if the Device Prefix is added to the logical points only or ifit is added to each point.


Default value: no checkmarkTable 3-9 General Settings Line Definition

3.9.2 Redundancy Settings Line Definition

Description: Defines the redundancy settings for each instance of the DNP3 masterprotocol.


Setting Description

Line Identifier Must be MDRD.


Enabled See "Redundancy Settings" in the Mas er Pro ocol Commont tConceptsdocument.

Link 1 Preferred See "Redundancy Settings" in the Mas er Pro ocol Commont tConceptsdocument.

Link 1 Test Interval See "Redundancy Settings" in this document.



31/44

Setting Description

Link 2 Test Interval See "Redundancy Settings" in this document.

Link Address See "Redundancy Settings" in this document.

Slave Link Address See "Redundancy Settings" in this document.

Scan Priority See Redundancy Settings in the Mas er Pro ocol Commont tConceptsdocument.


See "Redundancy Settings" in this document.

Class 0 Poll Cycle See "Redundancy Settings" in this document.





Clock Sync See "Redundancy Settings" in this document.

Clock Sync Cycle See "Redundancy Settings" in this document.

Unsolicited Report See "Redundancy Settings" in this document.

Link Confirmation

Mode


Allowed values: 0: Never1: Sometimes2: Always



Link Max Retries See "Redundancy Settings" in this document.

Applic Max Retries See "Redundancy Settings" in this document.



Selection Timeout See Redundancy Settings in the Mas er Pro ocol Commont tConceptsdocument.

Delay Between Tx See General Settings in the Master Pro ocol Common Conceptstdocument.

Link Sync See "Redundancy Settings" in this document.

Table 3-10 Redundancy Settings Line Definition

3.9.3 Switched Connection Settings Line Definition

Description: Defines the switched connection settings for each instance of the DNP3master protocol.




32/44

Setting Description

Line Identifier Must be MDSW.


Enabled See Switched Connection Settings in the Master Pro ocol Commont

Conceptsdocument.

Accept IncomingConnections

See Switched Connection Settings in the Master Pro ocol CommontConceptsdocument.

Force Init See Switched Connection Settings in the Master Pro ocol CommontConceptsdocument.

Max Retries See Switched Connection Settings in the Master Pro ocol CommontConceptsdocument.

Retry Delay See Switched Connection Settings in the Master Pro ocol CommontConceptsdocument.

Urgent ConnectionsTimeout


Inactivity Timeout See Switched Connection Settings in the Master Pro ocol CommontConceptsdocument.

Control InactivityTimeout


Max Comm Timeout See Switched Connection Settings in the Master Pro ocol CommontConceptsdocument.

Table 3-11 Switched Connection Settings Line Definition

3.9.4 Switched Connection Schedule Settings Line Definition

Description: Defines the switched connection schedule settings for each instance of theDNP3 master protocol.


Setting Description

Line Identifier Must be MDSC.


Start Time See Switched Connection Schedule Settings in the Master Protocol

Common Conceptsdocument.

Stop Time See Switched Connection Schedule Settings in the Master ProtocolCommon Conceptsdocument.

Comm Cycle See Switched Connection Schedule Settings in the Master ProtocolCommon Conceptsdocument.

Table 3-12 Switched Connection Schedule Settings Line Definition



33/44


34/44

Setting Description


Name See Binary Input Settings in the Mas er Pro ocol Commont tConceptsdocument.

Description See Binary Input Settings in the Mas er Pro ocol Commont t

Conceptsdocument.Type See the CSV-specific binary input settings, in the Master Protocol


DNP3 BI Type See "Binary Input Settings" in this document.

Allowed values: 0: Physical or logical input point1: Internal indication2: Time synchronization status input

point

Index See Binary Input Settings in this document.

Inverted Polarity See Binary Input Settings in the Mas er Pro ocol Commont t

Conceptsdocument.

Disabled See Binary Input Settings in the Mas er Pro ocol Commont tConceptsdocument.

Persistent See Binary Input Settings in the Mas er Pro ocol Commont tConceptsdocument.

Monitor Activity See Binary Input Settings in the Mas er Pro ocol Commont tConceptsdocument.

Table 3-14 Binary Input Line Definition

3.9.7 Counter Input Line DefinitionDescription: Defines DNP3 counter input points.

Type: One line of data per counter input point, up to a maximum of 65,535 linesper instance of the DNP3 protocol.

Setting Description

Line Identifier Must be MDCI.


Name See Analog Input Settings in the Mas er Protocol Commont

Conceptsdocument.Description See Analog Input Settings in the Mas er Protocol Commont

Conceptsdocument.

Index See Counter Input Settings in this document.

Scale See Analog Input Settings in the Mas er Protocol CommontConceptsdocument.

Offset See Analog Input Settings in the Mas er Protocol Commont



35/44

Setting Description

Conceptsdocument.

SMP Deadband See Analog Input Settings in the Mas er Protocol CommontConceptsdocument.

Units See CSV Unit Definition in the Master Protocol Common Concep st

document.Disabled See Analog Input Settings in the Mas er Protocol Commont

Conceptsdocument.

Persistent See Analog Input Settings in the Mas er Protocol CommontConceptsdocument.

Monitor Activity See Analog Input Settings in the Mas er Protocol CommontConceptsdocument.

Comm Deadband See Analog Input Settings in the Mas er Protocol CommontConceptsdocument.

Table 3-15 Counter Input Line Definition

3.9.8 Frozen Counter Input Line Definition

Description: Defines the DNP3 frozen counter input points.

Type: One line of data per frozen counter input point, up to a maximum of 65,535lines per instance of the DNP3 protocol.

Setting Description

Line Identifier Must be MDFCI.


Name See Analog Input Settings in the Mas er Protocol CommontConceptsdocument.

Description See Analog Input Settings in the Mas er Protocol CommontConceptsdocument.

Index See Frozen Counter Input Settings in this document.

Scale See Analog Input Settings in the Mas er Protocol CommontConceptsdocument.

Offset See Analog Input Settings in the Mas er Protocol CommontConceptsdocument.

SMP Deadband See Analog Input Settings in the Mas er Protocol CommontConceptsdocument.

Units See CSV Unit Definition in the Master Protocol Common Concep stdocument.

Disabled See Analog Input Settings in the Mas er Protocol CommontConceptsdocument.

Persistent See Analog Input Settings in the Mas er Protocol CommontConceptsdocument.



36/44


37/44


38/44


39/44

4. Implementation Details

4.1 Startup Sequence

The protocol component goes through the following steps on startup:

Parses the configuration file. Initializes the various logs, traces and statistics.

Creates all I/O points and marks them as invalid (communications failure).

Initializes the communications link.

Starts the scan cycle.

If any of these steps fail, system startup is aborted.

4.2 Scan Process

The protocol component manages the device polling cycle using the following principles:

The protocol is full duplex.

The remote device may send an unsolicited response at any time if this feature is supportedand the device is configured to do so.

There is a response to each application layer request.

DNP3 response processing complies with the DNP technical specifications. Since this topic goesbeyond the scope of this document, it will not be described here. Refer to the DNPdocumentation for additional information on the topic.

The DNP3 response processing rules are as follows:

In addition to the DNP rules, an application layer response is valid only if it arrives within the

configured application response timeout delay. All objects and their variations are supported (see section 2.2.2 "Implementation Table"for

the complete listing of all supported objects and variations).

The same request is re-issued if the reception status is incorrect, up to the number ofconfigured retry counts. For output control requests, only Select requests may be re-issued.

Whatever the reason, the link is reset from scratch if too many consecutive bad receptionsare received, too many being the number of configured retry counts.

Link initialization occurs under the following circumstances:

The SMP is being restarted.

The communications link is being reset due to too many consecutive errors of any type.

The communications link is being reset due to a control request on a logical binary outputpoint.

The initialization sequence is as follows:

Perform an integrity poll (data class 0/1/2/3 read request).

Perform a clock synchronization operation (a delay measurement request, followed by a writetime request), if enabled through configuration.



40/44

Once the link has been initialized, and as long as it remains active, a regular scanningprocess is used on a continuous basis. Note that the link is not considered active until a validresponse to a data class 1/2/3/0 read request is received from the device.

The regular scanning process is as follows:

If the last sent request failed and must be retried, send it again.

If the previous application layer response contains IINs that require a special operation,

perform the operation (see section 4.2.1).

If an event requiring a special operation occurs, perform the operation (see section 4.2.2).

If a scheduled operation is ready to be performed, carry out the operation (see section4.2.3).

The scanning process may be interrupted at any time, if there are output control requests.

If the normal scanning process is abandoned to cause a link reset, all I/O points are taggedas being defective due to a communications failure. Analog, binary and counter input pointsbecome valid again on an individual basis only when valid I/O data is received from thedevice. Analog and binary output points become valid again as soon as the link is consideredactive.

4.2.1 Automated operations based on internal indications

Each application response that the DNP3 master receives from the remote device contains a 16-bit information field, called Internal Indications (IIN). This field contains essential information onthe status of the remote device. Consult the document entitled DNP V3.00 Application Layersection 3.6, for a more detailed description of the bits contained in this field.

,

Depending on the state of each bit, the DNP3 protocol component may perform the automatedoperations described below.

Internal Indication Bit Related Operation

IIN 1-0 All station messagesreceived N/A

IIN 1-1 Class 1 data available If this bit is set, the protocol component performs a changeevent poll (Class 1/2/3 read request).



IIN 1-4 Time synchronizationrequired

If this bit is set, the protocol component synchronizes theremote device clock (if clock synchronization is allowed viathe configuration).

IIN 1-5 Local mode If this bit is set and then cleared, the protocol componentperforms an integrity poll (Class 0 read request).

IIN 1-6 Device trouble N/A

IIN 1-7 Device restart If this bit is set, the protocol component sends a clearrestart request to the remote device.

If the bit is set in a null unsolicited response, the protocolcomponent sends an enable/disable unsolicited response



41/44

Internal Indication Bit Related Operation

request, depending on the unsolicited responseconfiguration.

IIN 2-0 Function code notimplemented

N/A

IIN 2-1 Requested object(s)unknown N/A

IIN 2-2 Invalid parameter N/A

IIN 2-3 Event buffer overflow If this bit is set, the protocol component performs anintegrity poll (Class 0 read request).

IIN 2-4 Request alreadyexecuting

N/A

IIN 2-5 Configuration corrupted N/A

IIN 2-6 Reserved N/A

IIN 2-7 Reserved N/A

Table 4-1 Automated operations based on internal indications

All internals indication bits are available as statistics for diagnostic purposes. These statisticalfields are updated each time remote device IINs are reported. See section 5 - Troubleshooting.

4.2.2 Automated operations based on events

Other automated operations may be performed based on events that occur during the DNP3master operation cycle. These events and their related automated operations are described in thefollowing table.

Events Related operation

Reception of an unsolicitedresponse from the remotedevice

If unsolicited responses are disabled through configuration,the protocol component sends a disable unsolicitedresponse request.

If the response is a null unsolicited response and IIN 1-7device restart is set, the protocol component sends anenable/disable unsolicited response request, depending onthe unsolicited report configuration.

Clock synchronization Before sending a clock synchronization request to theremote device, the DNP3 master automatically performs adelay measurement operation to adjust the time to whichthe remote device will be synchronized.

Response timeout The protocol component performs an integrity poll (Class1/2/3/0 read request) after the timeout delay (waiting for aresponse from the remote device) expires.

Table 4-1 Automated operations based on events



42/44

4.2.3 Scheduled operations

Scheduled operations are performed cyclically. The cycle for each operation is set throughconfiguration. The operations that can be scheduled are described in the following table.

Operation Description

Integrity poll Sends a class 0 or class 0/1/2/3 read request to the remotedevice.

Change event poll Sends a class 1/2/3 read request to the remote device.

Clock synchronization Performs delay measurement and clock synchronization ofthe remote device.

Freeze all counter inputs Sends an immediate freeze request to the remote device.

On reception of the response to this request, the DNP3master sends a freeze feedback polling request (class 1/2/3data, counters and frozen counters).

Freeze and clear all counter

inputs

Sends a freeze and clear request to the remote device.

On reception of the response to this request, the DNP3master sends a freeze feedback polling request (class 1/2/3data, counters and frozen counters).

Table 4-2 Scheduled Operations

It is important to note that the normal scanning sequence may be interrupted by output controloperations, depending of the Tx During SBOgeneral setting value. When this parameter is set to0, the scanning process is momentarily suspended after a successful Select request, until anassociated Operate request is sent, or until the selection timer expires. This feature is required tointeract with special devices that automatically recall any selected point when a request, otherthan an appropriate Operate request, follows the Select request.

4.3 Listen Mode

The DNP3 master component can be configured to operate as a spy on a serial link, i.e., in listenmode. The following restrictions apply:

Control output operations are disabled.

Communication link failures are detected using the inactivity timeout mechanism of the datalink layer. Thus, if no valid data link layer frames are received during the inactivity timeoutperiod, the communications link is reset, with all the consequences that this implies.

The inactivity timeout is obtained from the following calculation:

InactivityTimeout(ms)

=

Cycle of

the fastestconfiguredrequest(ms)

+ ( (

Application

layerconfigured

retry number

+ 1 ) *

Application

layerconfigured

timeout (ms)

)

If there is no request configured, which is not recommended, the inactivity timeoutmechanism is disabled and link failures cannot be detected.



43/44

Remember that the basic idea in using a master protocol component in listen mode is to spy onanother link that already controls the acquisition cycle with the RTU. Thus, the instance used inlisten mode should have a configuration that is compatible with the information that is exchangedon the primary link, so that a request timeout on one side will reflect as an inactivity timeout onthe other side, at approximately the same time.



44/44

5. Troubleshooting

The following table enumerates solutions to common problems experienced with the DNP3master protocol component.

Problem Solution

The SMP gateway isnot communicatingwith my device.

This problem can be due to one of the following:

One of the reasons discussed in the Troubleshooting sectionof the Master Protocol Common Conceptsdocument.

All requests in the scanning cycle are disabled (the cycle is setto 0). At least one request must be enabled (cycle greater than0) in your general settings.

Device addressing problem: The slave link address configuredin the general settings does not match the one configured inthe device.

The link to my devicekeeps resetting.

This problem can be due to one of the following:

One of the reasons discussed in the Mas er Protocol CommontConceptsdocument.

Reception timeout problem: The reception timeout configuredin the general settings is too small.

Table 5-1 Troubleshooting

DNP3 Master Protocol

Documents

Transcript of DNP3 Master Protocol