FieldServer FS-8700-47 User Manual

Driver Version:

1.03

-

A Sierra Monitor Company

Driver Manual

(Supplement to the FieldServer Instruction Manual)

FS-8700-47 DNP 3.0

APPLICABILITY & EFFECTIVITY

Effective for all systems manufactured after December 2008

Document Revision: 14

FS-8700-47 DNP 3.0 Driver Manual Table of Contents

TABLE OF

1.

DNP 3.0 Driver Description ................................................................................................................4

2.

Driver Scope of Supply....................................................................................................................... 6

2.1. Supplied by FieldServer Technologies for this driver. .................................................................... 6

3.

Hardware Connections....................................................................................................................... 7

3.1. Connection Notes ...........................................................................................................................7

4.

Configuring the FieldServer as a DNP 3.0 Driver Client .................................................................... 8

4.1. Data Arrays..................................................................................................................................... 8

4.2. Client Side Connection Descriptors................................................................................................ 9

4.3. Client Side Node Descriptors .........................................................................................................9

4.4. Client Side Map Descriptors .........................................................................................................10

4.4.1. FieldServer Specific Map Descriptor Parameters .................................................................10

4.4.2. Driver Specific Map Descriptor Parameters .......................................................................... 10

4.4.3. Timing Parameters ................................................................................................................ 11

4.4.4. Map Descriptor Example 1 – Simple Read. ..........................................................................12

4.4.5. Map Descriptor Example 2 – Simple Read – Extract the Quality/Status .............................. 13

4.4.6. Map Descriptor Example 3 – Simple Read Extract Value & Status ...................................... 13

4.4.7. Map Descriptor Example 4 – Reading Class Data ................................................................ 14

4.4.8. Map Descriptor Example 5 – Read an unknown quantity of points (Qualifier 6) ..................14

4.4.9. Map Descriptor Example 6 – Read an unknown variation .................................................... 15

5.

Configuring the FieldServer as a DNP 3.0 Driver Server................................................................. 16

5.1. Server Side Connection Descriptors ............................................................................................16

5.2. Server Side Node Descriptors ......................................................................................................17

5.3. Server Side Map Descriptors........................................................................................................ 17

5.3.1. FieldServer Specific Map Descriptor Parameters .................................................................17

5.3.2. Driver Specific Map Descriptor Parameters .......................................................................... 18

5.3.3. Timing Parameters ................................................................................................................ 18

5.3.4. Map Descriptor Example 1 – Discrete Data. ......................................................................... 19

5.3.5. Map Descriptor Example 2 – Class Data ..............................................................................19

5.3.6. Map Descriptor Example 3 – Class Data (another example)................................................ 20

5.3.7. Map Descriptor Example 4 – Default Variation (Variation zero) ........................................... 21

5.3.8. Map Descriptor Example 5 - Class_Data_Serving_Ctrl ........................................................ 22

5.3.9. Map Descriptor Example 5 – Serving Objects which have a time field................................. 24

5.3.10. Map Descriptor Example 6 – Unsolicited Messages ............................................................. 24

5.4. Server Side Limitations................................................................................................................. 25

Appendix A. Advanced Topics ...............................................................................................................26

Appendix A.1. DNP 3.0 Protocol. .........................................................................................................26

Appendix A.2. DNP Driver Functionality .............................................................................................. 26

Appendix A.3. DNP Objects mapped to FieldServer Data Arrays .......................................................26

Appendix A.4. Channel Idle, Master & Slave Idle. ............................................................................... 26

Appendix A.5. DLL Layer Functionality in the Master ..........................................................................27

Appendix A.6. App Layer Functionality in the Master .......................................................................... 27

Appendix A.7. Internal Indications, Object 80 and DNP_II ..................................................................28

A.7.1. Incoming Internal Indications Bytes .......................................................................................... 28

A.7.2. Internal Indications reported in Responses .............................................................................. 30

A.7.3. Server_II_Array .........................................................................................................................30

A.7.4. Responses to Polls for Object 80 (Internal Indications)............................................................ 31

Appendix A.8. DNP_Stats ....................................................................................................................32

Appendix A.9. DNP 3.0 Data Objects ..................................................................................................33

Appendix A.10. Controlling the DNP 3.0 Driver’s Function Code ........................................................ 36

Appendix A.11. Controlling the DNP 3.0 Driver’s Qualifier .................................................................. 37

Appendix A.12. FieldServer DNP Node Number ................................................................................. 37

Appendix A.13. DnpSubType............................................................................................................... 38

Appendix A.14. Communication Stats ................................................................................................. 38

Appendix A.15. Link Reset................................................................................................................... 38

CONTENTS

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-47 DNP 3.0 Driver Manual Table of Contents

Appendix A.16. Controlling DA Offsets ................................................................................................ 39

Appendix A.17. dnpIndexStyle .............................................................................................................39

Appendix A.18. Real Time Clock Synchronization............................................................................... 40

Appendix A.19. Select and Operate..................................................................................................... 42

Appendix A.20. Multiple requests in a single poll................................................................................. 45

Appendix B. Driver Error Messages .......................................................................................................46

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-47 DNP 3.0 Driver Manual Page 4 of 51

1. DNP 3.0 Driver Description

The DNP 3.0 Driver allows the FieldServer to transfer data to and from devices over RS-232 or RS-485
using DNP 3.0 Driver protocol. The FieldServer can emulate either a Server or Client.

The following description of DNP is from the DNP User Group internet site.∗

“The development of DNP was a comprehensive effort to achieve open, standards-based interoperability
between substation computers, RTUs, IEDs (Intelligent Electronic Devices) and master stations (except
inter-master station communications) for the electric utility industry. Also important was the time frame
and the need for a solution to meet today's requirements. As ambitious an undertaking as this was, we
are reaching this objective.

DNP is based on the standards of the International Electrotechnical Commission (IEC) Technical
Committee 57, Working Group 03 who have been working on an OSI 3 layer "Enhanced Performance
Architecture" (EPA) protocol standard for telecontrol applications. DNP has been designed to be as close
to compliant as possible to the standards as they existed at time of development with the addition of
functionality not identified in Europe but needed for current and future North American applications (e.g.
limited transport layer functions to support 2K descriptor transfers for IEDs, RF and fiber support).
Recently DNP 3.0 was selected as a Recommended Practice by the IEEE C.2 Task Force; RTU to IED
Communications Protocol.

Feature Rich
DNP offers flexibility and functionality that go far beyond conventional communications protocols. Among
its robust and flexible features DNP 3.0 includes:

• Output options

• Secure configuration/file transfers

• Addressing for over 65,000 devices on a single link

• Time synchronization and time-stamped events

• Broadcast messages

• Data link and application layer confirmation

DNP 3.0 was originally designed based on three layers of the OSI seven-layer model: application layer,
data link layer and physical layer. The application layer is object-based with objects provided for most
generic data formats. The data link layer provides for several methods of retrieving data such as polling
for classes and object variations. The physical layer defines most commonly a simple RS-232 or RS-485
interface.

DNP 3.0 is very efficient for a layered protocol while ensuring high data integrity.

Suits Any SCADA/EMS Environment

Because DNP 3.0 is based on the IEC 870-5 requirements, DNP is suitable for application in the entire
SCADA/EMS environment. This includes RTU to IED communications, master to remote
communications, and even peer-to-peer instances and network applications.

Being an object-based application layer protocol, DNP 3.0 has the flexibility to support multiple operating
modes such as poll-response, polled report-by-exception, unsolicited responses and peer-to-peer. It
permits multiple masters and encourages distributed intelligence.
Users can expect many benefits from using DNP. In the short term:

• Interoperability between multi-vendor devices

• Fewer protocols to support in the field

• reduced software costs

• No protocol translators needed

∗

DNP Users Group, PO Box 43075 DVPO, Calgary, AB, Canada T2J 7A7

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-47 DNP 3.0 Driver Manual Page 5 of 51

• Shorter delivery schedules

• Less testing, maintenance and training

• Improved documentation

• Independent conformance testing

• Support by independent users group and third-party sources (e.g. test sets, source code).

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-47 DNP 3.0 Driver Manual Page 6 of 51

2. Driver Scope of Supply

2.1. Supplied by FieldServer Technologies for this driver.

FieldServer Technologies Part# Description

FS-8915-10 UTP cable (7 foot) for RS-232 use
FS-8917-04 RJ45 to DB25M connection adapter
FS-8700-47 Driver Manual.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-47 DNP 3.0 Driver Manual Page 7 of 51

3. Hardware Connections

The FieldServer is connected to the DNP-3.0 device as shown below.
Configure the DNP-3.0 device according to manufacturer’s instructions

DNP Device

8917-04

DB25F

Connect to one of the RS-232

Ports on the FieldServer

RJ45

18

FieldServer

P1

FieldServer Function From Default Color

Rx RJ45-01 DB25F-02 White
CTS RJ45-02 DB25F-04 Brown
DSR RJ45-03 Yellow
GND RJ45-04 DB25F-07 Green
GND RJ45-05 Red
DTR RJ45-06 Black
RTS RJ45-07 DB25F-05 Orange
Tx RJ45-08 DB25F-03 Blue

3.1. Connection Notes

Pinouts and adapters may vary according to the device being connected to. Refer to DNP installation
manual for pin connection reference.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-47 DNP 3.0 Driver Manual Page 8 of 51

4. Configuring the FieldServer as a DNP 3.0 Driver Client

For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration
Manual. The information that follows describes how to expand upon the factory defaults provided in the
configuration files included with the FieldServer (See “.csv” files supplied with the FieldServer).

This section documents and describes the parameters necessary for configuring the FieldServer to
communicate with a DNP 3.0 Driver Server.

The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to
enable the FieldServer for DNP 3.0 Driver communications, the driver independent FieldServer buffers
need to be declared in the “Data Arrays” section, the destination device addresses need to be declared in
the “Client Side Nodes” section, and the data required from the Servers needs to be mapped in the
“Client Side Map Descriptors” section. Details on how to do this can be found below.

Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.

4.1. Data Arrays

Section Title

Data_Arrays

Column Title Function Legal Values

Data_Array_Name Provide name for Data Array Up to 15 alphanumeric characters

Data_Format

Data_Array_Length

Example

// Data Arrays
//
Data_Arrays
Data_Array_Name ,Data_Format ,Data_Array_Length
DA_AI_01 ,UInt16 ,200
DA_AO_01 ,UInt16 ,200
DA_DI_01 ,Bit ,200
DA_DO_01 ,Bit ,200

Provide data format. Each data array can
only take on one format.

Number of Data Objects. Must be larger
than the data storage area required for
the data being placed in this array.

FLOAT, BIT, UInt16, SInt16,
Packed_Bit, Byte, Packed_Byte,
Swapped_Byte

1-10,000

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-47 DNP 3.0 Driver Manual Page 9 of 51

4.2. Client Side Connection Descriptors

Section Title

Connections

Column Title Function Legal Values

Port

Baud* Specify baud rate

Parity* Specify parity

Data_Bits*

Stop_Bits*

Protocol

Handshaking* Specify hardware handshaking

Poll Delay*

Application*

Example

// Client Side Connections

Specify which port the device is connected to the
FieldServer

Specify data bits

Specify stop bits

Specify protocol used DNP

Time between internal polls

Versions of the driver prior to 1.02a used a different
method to calculate DA offset. Refer to Appendix A.16.

It is also possible to use this parameter to control if link
resets are used/required. Refer to Appendix A.15.

P1-P8, R1-R21

110 – 115200, standard
baud rates only
Even, Odd, None, Mark,
Space

7, 8

1

None
0-32000 seconds, 1
second.

OriginalStyle,
NoLink,
OrigStyle-NoLink

Connections
Port ,Baud ,Parity ,Protocol ,Handshaking ,Poll_Delay
R1 ,9600 ,None ,DNP ,None ,0.100s

4.3. Client Side Node Descriptors

Section Title

Nodes

Column Title Function Legal Values

Node_Name Provide name for node

Node_ID

Protocol Specify protocol used DNP

Port

Example

// Client Side Nodes

DNP 3.0 station address of physical Server
node

Specify which port the device is connected to
the FieldServer

Up to 32 alphanumeric
characters

0-65535

P1-P8, R1-R21

Nodes
Node_Name ,Node_ID ,Protocol ,Port
PLC 1 ,1 ,DNP ,P1

1

Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction

manual for details of the ports available on specific hardware.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-47 DNP 3.0 Driver Manual Page 10 of 51

4.4. Client Side Map Descriptors

4.4.1. FieldServer Specific Map Descriptor Parameters

Column Title Function Legal Values

Map_Descriptor_Name Name of this Map Descriptor

Name of Data Array where

Data_Array_Name

Data_Array_Offset Starting location in Data Array

Function

data is to be stored in the
FieldServer

Function of Client Map
Descriptor

Up to 32 alphanumeric
characters
One of the Data Array names
from “Data Array” section
above
0 to maximum specified in
“Data Array” section above

Rdbc, Wrbc, Wrbx

4.4.2. Driver Specific Map Descriptor Parameters

Column Title Function Legal Values

The following parameters are used by a number of drivers.

A Node Name specified in
“Client Node Descriptor”.

Node_Name Name of Node to fetch data from

Length of Map Descriptor. If a request length
is too large the DNP 3.0 driver will produce a

Length

Address Starting address of data element to be read 0, 1 , 2 etc
The following parameters apply only to the DNP 3.0 Driver

DnpDataType

DnpDataVari

DnpSubType*

DnpFlagBit* Not Used.

DnpQualifier*

DnpFunction*

message and a panic. The maximum length
is a function of the data object and data
variation.

Corresponds to the Data Object Types defined
in the DNP data object Library. Additional
information is provided in Appendix A.9
Corresponds to the Data Object Variant
defined in the DNP data object Library. Enter
as decimal number. Additional information is
provided in Appendix A.9
Used to tell driver which Suffield of the object
to map to/from the FieldServer Data Array.
Additional information is provided in Appendix
A.10

This parameter is only required if you need to
over-ride the default qualifier used by the DNP

3.0 driver. Refer to Appendix A.11

This parameter is only required if you need to
over-ride the default function used by the DNP

3.0 driver. Refer to Appendix A.10

Special Map Descriptors are
discussed in Error!

Reference source not
found..

1 – 1000

1, 2, 10, 12, 30, 31, 32, 33,
40, 41, 20, 22, 23, 50, 51, 52,
60, 80 - decimal numbers

0, 1,2,3 etc
Legal values are determined
by the value of dnpDataType.

Value, flags, time1, time2,
combo

Zero, 1, 6, 7, 8, 17h ­hexadecimal values. For
qualifier 17h specify the
value of dnpQualifier as 17 in
the Map Descriptor. For
Qualifier zero use the string
“zero”
Legal DNP function codes.
Correspond to the function
code required on vendor’s
implementation table.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FS-8700-47 DNP 3.0 Driver Manual Page 11 of 51

positive whole numbers.

Column Title Function Legal Values

When class data is requested the DNP device
responds with data of multiple types and

DnpAssociate*

DnpMultiMsg*

variations in one message. One Map
Descriptor is used per data type - this
parameter is used to link these Map
Descriptors.
This parameter is used to produce a single
message with a request for multiple object
types. Assign positive whole numbers to
associate Map Descriptors for this purpose. All
Map Descriptors whose dnpMultiMsg values
are equal will be requested in a single poll.
Ensure only one is active (rdbc for example)
and all the others have the function set to
'Server'. Refer also to Appendix A.20

Non-zero positive integers.

0,

By default Map Descriptors
are not associated with each
other. The default value of
zero ensures no association.

4.4.3. Timing Parameters

Column Title Function Legal Values

Scan_Interval Rate at which data is polled >0.1s

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

DNP Object

Variation is 16

Bit Analog Input

DNP Object Type is

Analog Input

Read Analog Inputs in

the slave device starting

at input index 20.

Vendor documentation

will tell you the indices of

the inputs you are

interested in.

This is the name of the node that we

Read 10 elements.

are reading. This name must connect

to a node definition in the CSV file

which will contain the address of the

device being read and this in turn

should connect to a port definition

though which the FieldServer will

This Map

Descriptor will

perform a read of

the DNP device

and the read will

be performed

continuously.

element of the

st

The value of the

first analog input

read will be placed

The results of the

read are placed in

this data array.

in position 20 of

table.)

the data table (the

21

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

4.4.4. Map Descriptor Example 1 – Simple Read.

Duplicates are

allowed but may

make some of the

validation

messages less

Any useful name.

FS-8700-47 DNP 3.0 Driver Manual Page 12 of 51

In this example we read 10 Analog Inputs from a DNP device. The request is with respect to inputs 20 to 29 and we will place the results of the

read in the data array called DA_AI3 in positions 20 to 29. In this example the dnpSubType is not specified so the driver will report the value of

the object.

// Client Side Map Descriptors

Map_Descriptors

Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Address ,Length ,Scan_Interval ,dnpDataType ,dnpDataVari

A1 ,DA_AI3 ,20 ,Rdbc ,Node_A ,20 ,10 ,5 ,30 ,1

meaningful.

,Value ,1

,Flags ,1

The common value for dnpAssociate

ties these two Map Descriptors

together and tells the driver to use

them both to process the response

data.

Tells the driver to write the status byte to the data

array, ignoring the value of the object being read.

You can use value / time1 / time2 / flags / combo as

legal values for this parameter. The default is value.

DNP Object Variation is

16 Bit Analog Input

Only one Map Descriptor need be active. The

active Map Descriptor generates the poll. Both

the active and passive Map Descriptors are

used to process the response.

DNP Object Type is

Analog Input

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

4.4.5. Map Descriptor Example 2 – Simple Read – Extract the Quality/Status

The results of the

read are placed in

this data array.

FS-8700-47 DNP 3.0 Driver Manual Page 13 of 51

In this example the status data rather than the input values are written to the data array specified.

// Client Side Map Descriptors

Map_Descriptors

Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Address ,Length ,Scan_Interval ,dnpDataType ,dnpDataVari ,dnpSubType

A1 ,DA_AI3STAT ,20 ,Rdbc ,Node_A ,20 ,10 ,5 ,30 ,1 F,lags

4.4.6. Map Descriptor Example 3 – Simple Read Extract Value & Status

The status data is

placed into a different

array from the value

data.

In this example we extract both the value and the status using two Map Descriptors.

// Client Side Map Descriptors

Map_Descriptors

Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Address ,Length ,Scan_Interval ,dnpDataType ,dnpDataVari ,dnpSubType ,dnpAsscoiate

A1 ,DA_AI3 ,20 ,Rdbc ,Node_A ,20 ,10 ,5 ,30 ,

A2 ,DA_AI3STAT ,20 ,Passive ,Node_A ,20 ,10 ,5 ,30 ,

,6

The Qualifier of 6 tells the driver

to request all data objects.

The common value for dnpAssociate ties these Map

Descriptors together and tells the driver to use them both to

process the response data.

This Map Descriptor requests class 1 data from the DNP device.

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

4.4.7. Map Descriptor Example 4 – Reading Class Data

These Map Descriptors process the data that the device returns. If more

data is returned that you have defined Map Descriptors for then it will be

abandoned.

relationships and importance of the data. In this example you will see that only one of the Map Descriptors is active – the class data read. The

remaining passive Map Descriptors are used to process the response from the class data read. The response may consist of a number of data

object types and variations and is dependent on the vendor’s implementation of DNP. Some vendors allow users to configure what objects

constitute a class.

FS-8700-47 DNP 3.0 Driver Manual Page 14 of 51

In this example we read class data. A class is a structure of different data types and variations. Vendors group data into classes based on the

// Class 1 Data

Map_Descriptors

Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Address ,Length ,dnpSubType ,dnpDataType ,dnpDataVari ,dnpQualifier ,dnpAssociate ,timeout

Class1-Data ,13.0s ,DA_A3 ,0 ,Rdbc ,Node_A ,0 ,100 ,value ,60 ,1 ,6 ,1 ,5.0s

Map_Descriptors

Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Address ,Length ,dnpSubType ,dnpDataType ,dnpDataVari ,dnpAssociate

Class1-di ,3.0s ,CL_1 ,0 ,Passive ,Node_A ,0 ,156 ,value ,1 ,0 ,1

Class1-do ,3.0s ,CL_2 ,0 ,Passive ,Node_A ,0 ,9 ,value ,10 ,0 ,1

Class1-co ,3.0s ,CL_3 ,0 ,Passive , Node_A ,0 ,39 ,value ,20 ,0 ,1

Class1-ai-1 ,3.0s ,CL_4 ,0 ,Passive ,Node_A ,0 ,100 ,value ,30 ,0 ,1

Class1-ai-2 ,3.0s ,CL_5 ,0 ,Passive ,Node_A ,100 ,100 ,value ,30 ,0 ,1

Class1-ai-3 ,3.0s ,CL_6 ,0 ,Passive ,Node_A ,200 ,100 ,value ,30 ,0 ,1

4.4.8. Map Descriptor Example 5 – Read an unknown quantity of points (Qualifier 6)

Enough space has been reserved for 100 objects. If the response contains more then

there will be an error.

In this example the qualifier has been set to 6. This is the qualifier the protocol uses to request all possible points of a particular object type and

variation. Ensure that there is sufficient length to store all possible data.

// Client Side Map Descriptors

Map-Descriptors

Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Address ,Length ,Scan_Interval ,dnpDataType ,dnpDataVari ,DnpQualifier

ReadAll_AI’s ,DA_AI ,0 ,Rdbc ,Node_A ,0 ,100 ,5.0s ,30 ,

,6

With the variation set to zero the remote device will respond

with its default variation.

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

4.4.9. Map Descriptor Example 6 – Read an unknown variation

FS-8700-47 DNP 3.0 Driver Manual Page 15 of 51

If the DNP device does not document the object type variation that it serves, set the variation to zero. The remote device will respond with its

default variation. The problem is that the response cannot be stored using this Map Descriptor because the response will have its variation non-

zero. Thus you would need to make a Server Map Descriptor for each possible variation. A better strategy is to experiment. Use the single Map

Descriptor below, wait for the error and then modify the CSV based on information found in the error message.

// Client Side Map Descriptors

Map_Descriptors

Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Address ,Length ,Scan_Interval ,dnpDataType ,dnpDataVari ,DnpQualifier

ReadAll_AI’s ,DA_AI ,0 ,Rdbc ,Node_A ,0 ,100 ,5.0s ,30 ,

FS-8700-47 DNP 3.0 Driver Manual Page 16 of 51

5. Configuring the FieldServer as a DNP 3.0 Driver Server

For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration
Manual. The information that follows describes how to expand upon the factory defaults provided in the
configuration files included with the FieldServer (See “.csv” files provided with the FieldServer.)

This section documents and describes the parameters necessary for configuring the FieldServer to
communicate with a DNP 3.0 Driver Client.

The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order
to enable the FieldServer for DNP 3.0 Driver communications, the driver independent FieldServer buffers
need to be declared in the “Data Arrays” section, the FieldServer virtual node(s) needs to be declared in
the “Server Side Nodes” section, and the data to be provided to the Clients needs to be mapped in the
“Server Side Map Descriptors” section. Details on how to do this can be found below.

Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.

5.1. Server Side Connection Descriptors

Section Title

Connections

Column Title Function Legal Values

Port

Baud* Specify baud rate

Parity* Specify parity
Data_Bits*

Stop_Bits*

Protocol

Handshaking* Specify hardware handshaking

Example

// Server Side Connections

Specify which port the device is connected to the
FieldServer

Specify data bits

Specify stop bits

Specify protocol used DNP

P1-P8, R1-R22

110 – 115200, standard baud
rates only
Even, Odd, None, Mark, Space

7, 8

1

None

Connections
Port ,Baud ,Parity ,Protocol ,Handshaking
P8 ,9600 ,None ,DNP ,None

2

Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction

manual for details of the ports available on specific hardware.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com

Tel: [phone] Fax: [phone] Toll Free: [phone] email: [e-mail]