FieldServer FS-8700-47 Release note

-
A Sierra Monitor Company
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after December 008
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-47 DNP 3.0
Driver Version:
1.03
Document Revision: 14

FS-8700-47 DNP 3.0 Driver Manual Table of Contents
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
TABLE OF CONTENTS
1. DNP 3.0 Driver Description ................................................................................................................ 4
2. Driver Scope of Supply....................................................................................................................... 6
2.1. Supplie by Fiel Server Technologies for this river. ....................................................................6
3. Har ware Connections....................................................................................................................... 7
3.1. Connection Notes ........................................................................................................................... 7
4. Configuring the Fiel Server as a DNP 3.0 Driver Client .................................................................... 8
4.1. Data Arrays.....................................................................................................................................8
4.2. Client Si e Connection Descriptors................................................................................................9
4.3. Client Si e No e Descriptors ......................................................................................................... 9
4.4. Client Si e 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 Fiel Server as a DNP 3.0 Driver Server................................................................. 16
5.1. Server Si e Connection Descriptors ............................................................................................ 16
5.2. Server Si e No e Descriptors ......................................................................................................17
5.3. Server Si e 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 Si e Limitations................................................................................................................. 25
Appen ix A. A vance Topics ...............................................................................................................26
Appen ix A.1. DNP 3.0 Protocol. ......................................................................................................... 26
Appen ix A.2. DNP Driver Functionality ..............................................................................................26
Appen ix A.3. DNP Objects mappe to Fiel Server Data Arrays ....................................................... 26
Appen ix A.4. Channel I le, Master & Slave I le. ............................................................................... 26
Appen ix A.5. DLL Layer Functionality in the Master.......................................................................... 27
Appen ix A.6. App Layer Functionality in the Master ..........................................................................27
Appen ix A.7. Internal In ications, Object 80 an DNP_II .................................................................. 28
A.7.1. Incoming Internal In ications Bytes ..........................................................................................28
A.7.2. Internal In ications reporte in Responses ..............................................................................30
A.7.3. Server_II_Array ......................................................................................................................... 30
A.7.4. Responses to Polls for Object 80 (Internal In ications)............................................................ 31
Appen ix A.8. DNP_Stats .................................................................................................................... 32
Appen ix A.9. DNP 3.0 Data Objects ..................................................................................................33
Appen ix A.10. Controlling the DNP 3.0 Driver’s Function Co e ........................................................36
Appen ix A.11. Controlling the DNP 3.0 Driver’s Qualifier .................................................................. 37
Appen ix A.12. Fiel Server DNP No e Number .................................................................................37
Appen ix A.13. DnpSubType............................................................................................................... 38
Appen ix A.14. Communication Stats ................................................................................................. 38
Appen ix A.15. Link Reset................................................................................................................... 38

FS-8700-47 DNP 3.0 Driver Manual Table of Contents
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
Appen ix A.16. Controlling DA Offsets ................................................................................................39
Appen ix A.17. npIn exStyle ............................................................................................................. 39
Appen ix A.18. Real Time Clock Synchronization............................................................................... 40
Appen ix A.19. Select an Operate..................................................................................................... 42
Appen ix A.20. Multiple requests in a single poll................................................................................. 45
Appen ix B. Driver Error Messages ....................................................................................................... 46

FS-8700-47 DNP 3.0 Driver Manual Page 4 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
1. DNP 3.0 Driver Description
The DNP 3.0 Driver allows the Fiel Server to transfer ata to an from evices over RS-232 or RS-485
using DNP 3.0 Driver protocol. The Fiel Server can emulate either a Server or Client.
The following escription 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, Cana a T2J 7A7

FS-8700-47 DNP 3.0 Driver Manual Page 5 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
• 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).

FS-8700-47 DNP 3.0 Driver Manual Page 6 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
. Driver Scope of Supply
.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 a apter
FS-8700-47 Driver Manual.

FS-8700-47 DNP 3.0 Driver Manual Page 7 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
3. Hardware Connections
The Fiel Server is connecte to the DNP-3.0 evice as shown below.
Configure the DNP-3.0 evice accor ing to manufacturer’s instructions
8917-04 DB25F
Fiel Server
RJ45
Connect to one of the RS-232
Ports on the Fiel Server
P1
18
DNP Device
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 Re
DTR RJ45-06 Black
RTS RJ45-07 DB25F-05 Orange
Tx RJ45-08 DB25F-03 Blue
3.1. Connection Notes
Pinouts an a apters may vary accor ing to the evice being connecte to. Refer to DNP installation
manual for pin connection reference.

FS-8700-47 DNP 3.0 Driver Manual Page 8 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
4. Configuring the FieldServer as a DNP 3.0 Driver Client
For a etaile iscussion on Fiel Server configuration, please refer to the Fiel Server Configuration
Manual. The information that follows escribes how to expan upon the factory efaults provi e in the
configuration files inclu e with the Fiel Server (See “.csv” files supplie with the Fiel Server).
This section ocuments an escribes the parameters necessary for configuring the Fiel Server to
communicate with a DNP 3.0 Driver Server.
The configuration file tells the Fiel Server about its interfaces, an the routing of ata require . In or er to
enable the Fiel Server for DNP 3.0 Driver communications, the river in epen ent Fiel Server buffers
nee to be eclare in the “Data Arrays” section, the estination evice a resses nee to be eclare in
the “Client Si e No es” section, an the ata require from the Servers nee s to be mappe in the
“Client Si e Map Descriptors” section. Details on how to o this can be foun below.
Note that in the tables, * in icates an optional parameter, with the bold legal value being the efault.
4.1. Data Arrays
Section Title
Data_Arrays
Column Title Function Legal Values
Data_Array_Name Provi e name for Data Array Up to 15 alphanumeric characters
Data_Format Provi e ata format. Each ata array can
only take on one format.
FLOAT, BIT, UInt16, SInt16,
Packe _Bit, Byte, Packe _Byte,
Swappe _Byte
Data_Array_Length
Number of Data Objects. Must be larger
than the ata storage area require for
the ata being place in this array.
1-10,000
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

FS-8700-47 DNP 3.0 Driver Manual Page 9 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
4. . Client Side Connection Descriptors
Section Title
Connections
Column Title Function Legal Values
Port Specify which port the evice is connecte to the
Fiel Server P1-P8, R1-R2
1
Bau * Specify bau rate 110 – 115200, stan ar
bau rates only
Parity* Specify parity Even, O , None, Mark,
Space
Data_Bits* Specify ata bits 7, 8
Stop_Bits* Specify stop bits 1
Protocol Specify protocol use DNP
Han shaking* Specify har ware han shaking None
Poll Delay* Time between internal polls 0-32000 secon s, 1
second.
Application*
Versions of the river prior to 1.02a use a ifferent
metho to calculate DA offset. Refer to Appen ix A.16.
It is also possible to use this parameter to control if link
resets are use /require . Refer to Appen ix A.15.
OriginalStyle,
NoLink,
OrigStyle-NoLink
Example
// Client Si e Connections
Connections
Port ,Bau ,Parity ,Protocol ,Han shaking ,Poll_Delay
R1 ,9600 ,None ,DNP ,None ,0.100s
4.3. Client Side Node Descriptors
Section Title
No es
Column Title Function Legal Values
No e_Name Provi e name for no e Up to 32 alphanumeric
characters
No e_ID DNP 3.0 station a ress of physical Server
no e 0-65535
Protocol Specify protocol use DNP
Port Specify which port the evice is connecte to
the Fiel Server P1-P8, R1-R21
Example
// Client Si e No es
No es
No e_Name ,No e_ID ,Protocol ,Port
PLC 1 ,1 ,DNP ,P1
1
Not all ports shown are necessarily supporte by the har ware. Consult the appropriate Instruction
manual for etails of the ports available on specific har ware.

FS-8700-47 DNP 3.0 Driver Manual Page 10 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
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 Up to 32 alphanumeric
characters
Data_Array_Name
Name of Data Array where
ata is to be store in the
Fiel Server
One of the Data Array names
from “Data Array” section
above
Data_Array_Offset Starting location in Data Array 0 to maximum specifie in
“Data Array” section above
Function Function of Client Map
Descriptor R bc, Wrbc, Wrbx
4.4. . Driver Specific Map Descriptor Parameters
Column Title Function Legal Values
The following parameters are use by a number of rivers.
No e_Name Name of No e to fetch ata from
A No e Name specifie in
“Client No e Descriptor”.
Special Map Descriptors are
iscusse in Error!
Reference source not
found..
Length
Length of Map Descriptor. If a request length
is too large the DNP 3.0 river will pro uce a
message an a panic. The maximum length
is a function of the ata object an ata
variation.
1 – 1000
A ress Starting a ress of ata element to be rea 0, 1 , 2 etc
The following parameters apply only to the DNP 3.0 Driver
DnpDataType
Correspon s to the Data Object Types efine
in the DNP ata object Library. A itional
information is provi e in Appen ix A.9
1, 2, 10, 12, 30, 31, 32, 33,
40, 41, 20, 22, 23, 50, 51, 52,
60, 80 - ecimal numbers
DnpDataVari
Correspon s to the Data Object Variant
efine in the DNP ata object Library. Enter
as ecimal number. A itional information is
provi e in Appen ix A.9
0, 1,2,3 etc
Legal values are etermine
by the value of npDataType.
DnpSubType*
Use to tell river which Suffiel of the object
to map to/from the Fiel Server Data Array.
A itional information is provi e in Appen ix
A.10
Value, flags, time1, time2,
combo
DnpFlagBit* Not Use .
DnpQualifier*
This parameter is only require if you nee to
over-ri e the efault qualifier use by the DNP
3.0 river. Refer to Appen ix A.11
Zero, 1, 6, 7, 8, 17h -
hexa ecimal values. For
qualifier 17h specify the
value of npQualifier as 17 in
the Map Descriptor. For
Qualifier zero use the string
“zero”
DnpFunction*
This parameter is only require if you nee to
over-ri e the efault function use by the DNP
3.0 river. Refer to Appen ix A.10
Legal DNP function co es.
Correspon to the function
co e require on ven or’s
implementation table.

FS-8700-47 DNP 3.0 Driver Manual Page 11 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
Column Title Function Legal Values
DnpAssociate*
When class ata is requeste the DNP evice
respon s with ata of multiple types an
variations in one message. One Map
Descriptor is use per ata type - this
parameter is use to link these Map
Descriptors.
Non-zero positive integers.
DnpMultiMsg*
This parameter is use to pro uce 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 npMultiMsg values
are equal will be requeste in a single poll.
Ensure only one is active (r bc for example)
an all the others have the function set to
'Server'. Refer also to Appen ix A.20
0,
positive whole numbers.
By efault Map Descriptors
are not associate with each
other. The efault value of
zero ensures no association.
4.4.3. Timing Parameters
Column Title Function Legal Values
Scan_Interval Rate at which ata is polle >0.1s

FS-8700-47 DNP 3.0 Driver Manual Page 1 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
4.4.4. Map Descriptor Example 1 – Simple Read.
In this example we rea 10 Analog Inputs from a DNP evice. The request is with respect to inputs 20 to 29 an we will place the results of the rea in the ata array calle DA_AI3 in positions 20 to 29. In this example the npSubType is not specifie so the river will report the value of the object. // Client Si e Map Descriptors Map_Descriptors Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,No e_Name ,A ress ,Length ,Scan_Interval , npDataType , npDataVari
A1 ,DA_AI3 ,20 ,R bc ,No e_A ,20 ,10 ,5 ,30 ,1
Rea 10 elements.
This is the name of the no e that we are rea ing. This name must connect to a no e efinition in the CSV file which will contain the a ress of the evice being rea an this in turn shoul connect to a port efinition though which the Fiel Server will
communicate with the DNP evice.
The value of the first analog input rea will be place in position 20 of the ata table (the 21
st
element of the
table.)
Any useful name.
Duplicates are allowe but may make some of the vali ation messages less meaningful.
The results of the rea are place in this ata array.
This Map Descriptor will perform a rea of the DNP evice an the rea will be performe continuously.
Every 5 secon s.
Rea Analog Inputs in the slave evice starting at input in ex 20. Ven or ocumentation will tell you the in ices of the inputs you are intereste in.
DNP Object Type is
Analog Input
DNP Object Variation is 16 Bit Analog Input

FS-8700-47 DNP 3.0 Driver Manual Page 13 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
4.4.5. Map Descriptor Example – Simple Read – Extract the Quality/Status
In this example the status ata rather than the input values are written to the ata array specifie . // Client Si e Map Descriptors Map_Descriptors Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,No e_Name ,A ress ,Length ,Scan_Interval , npDataType , npDataVari , npSubType
A1 ,DA_AI3STAT ,20 ,R bc ,No e_A ,20 ,10 ,5 ,30 ,1 F,lags
4.4.6. Map Descriptor Example 3 – Simple Read Extract Value & Status
In this example we extract both the value an the status using two Map Descriptors. // Client Si e Map Descriptors Map_Descriptors Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,No e_Name ,A ress ,Length ,Scan_Interval , npDataType , npDataVari , npSubType , npAsscoiate
A1 ,DA_AI3 ,20 ,R bc ,No e_A ,20 ,10 ,5 ,30 ,
1
,Value ,1
A2 ,DA_AI3STAT ,20 ,Passive ,No e_A ,20 ,10 ,5 ,30 ,
1
,Flags ,1
The results of the rea are place in this ata array.
Tells the river to write the status byte to the ata array, ignoring the value of the object being rea . You can use value / time1 / time2 / flags / combo as
legal values for this parameter. The efault is value.
Not all objects have these sub
-
fiel s.
DNP Object Type is
Analog Input
The common value for npAssociate ties these two Map Descriptors together an tells the river to use them both to process the response ata.
The status ata is place into a ifferent array from the value ata.
Only one Map Descriptor nee be active. The active Map Descriptor generates the poll. Both the active an passive Map Descriptors are use to process the response.
DNP Object Variation is 16 Bit Analog Input

FS-8700-47 DNP 3.0 Driver Manual Page 14 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
4.4.7. Map Descriptor Example 4 – Reading Class Data
In this example we rea class ata. A class is a structure of ifferent ata types an variations. Ven ors group ata into classes base on the
relationships an importance of the ata. In this example you will see that only one of the Map Descriptors is active – the class ata rea . The remaining passive Map Descriptors are use to process the response from the class ata rea . The response may consist of a number of ata object types an variations an is epen ent on the ven or’s implementation of DNP. Some ven ors allow users to configure what objects constitute a class.
// Class 1 Data Map_Descriptors Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function ,No e_Name ,A ress ,Length , npSubType , npDataType , npDataVari , npQualifier , npAssociate ,timeout Class1-Data ,13.0s ,DA_A3 ,0 ,R bc ,No e_A ,0 ,100 ,value ,60 ,1 ,6 ,1 ,5.0s Map_Descriptors Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Function ,No e_Name ,A ress ,Length , npSubType , npDataType , npDataVari , npAssociate Class1- i ,3.0s ,CL_1 ,0 ,Passive ,No e_A ,0 ,156 ,value ,1 ,0 ,1 Class1- o ,3.0s ,CL_2 ,0 ,Passive ,No e_A ,0 ,9 ,value ,10 ,0 ,1 Class1-co ,3.0s ,CL_3 ,0 ,Passive , No e_A ,0 ,39 ,value ,20 ,0 ,1 Class1-ai-1 ,3.0s ,CL_4 ,0 ,Passive ,No e_A ,0 ,100 ,value ,30 ,0 ,1 Class1-ai-2 ,3.0s ,CL_5 ,0 ,Passive ,No e_A ,100 ,100 ,value ,30 ,0 ,1 Class1-ai-3 ,3.0s ,CL_6 ,0 ,Passive ,No e_A ,200 ,100 ,value ,30 ,0 ,1
4.4.8. Map Descriptor Example 5 – Read an unknown quantity of points (Qualifier 6)
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 an variation. Ensure that there is sufficient length to store all possible ata. // Client Si e Map Descriptors Map-Descriptors Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,No e_Name ,A ress ,Length ,Scan_Interval , npDataType , npDataVari ,DnpQualifier Rea All_AI’s ,DA_AI ,0 ,R bc ,No e_A ,0 ,100 ,5.0s ,30 ,
1
,6
The common value for npAssociate ties these Map Descriptors together an tells the river to use them both to process the response ata.
This Map Descriptor requests class 1 ata from the DNP evice.
Enough space has been reserve for 100 objects. If the response contains more then there will be an error.
The Qualifier of 6 tells the river to request all ata objects.
These Map Descriptors process the ata that the evice returns. If more ata is returne that you have efine Map Descriptors for then it will be aban one .

FS-8700-47 DNP 3.0 Driver Manual Page 15 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
4.4.9. Map Descriptor Example 6 – Read an unknown variation
If the DNP evice oes not ocument the object type variation that it serves, set the variation to zero. The remote evice will respon with its efault variation. The problem is that the response cannot be store using this Map Descriptor because the response will have its variation non- zero. Thus you woul nee 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 an then mo ify the CSV base on information foun in the error message. // Client Si e Map Descriptors Map_Descriptors Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,No e_Name ,A ress ,Length ,Scan_Interval , npDataType , npDataVari ,DnpQualifier Rea All_AI’s ,DA_AI ,0 ,R bc ,No e_A ,0 ,100 ,5.0s ,30 ,
0
,6
With the variation set to zero the remote evice will respon with its efault variation.

FS-8700-47 DNP 3.0 Driver Manual Page 16 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
5. Configuring the FieldServer as a DNP 3.0 Driver Server
For a etaile iscussion on Fiel Server configuration, please refer to the Fiel Server Configuration
Manual. The information that follows escribes how to expan upon the factory efaults provi e in the
configuration files inclu e with the Fiel Server (See “.csv” files provi e with the Fiel Server.)
This section ocuments an escribes the parameters necessary for configuring the Fiel Server to
communicate with a DNP 3.0 Driver Client.
The configuration file tells the Fiel Server about its interfaces, an the routing of ata require . In or er
to enable the Fiel Server for DNP 3.0 Driver communications, the river in epen ent Fiel Server buffers
nee to be eclare in the “Data Arrays” section, the Fiel Server virtual no e(s) nee s to be eclare in
the “Server Si e No es” section, an the ata to be provi e to the Clients nee s to be mappe in the
“Server Si e Map Descriptors” section. Details on how to o this can be foun below.
Note that in the tables, * in icates an optional parameter, with the bold legal value being the efault.
5.1. Server Side Connection Descriptors
Section Title
Connections
Column Title Function Legal Values
Port Specify which port the evice is connecte to the
Fiel Server P1-P8, R1-R2
2
Bau * Specify bau rate 110 – 115200, stan ar bau
rates only
Parity* Specify parity Even, O , None, Mark, Space
Data_Bits* Specify ata bits 7, 8
Stop_Bits* Specify stop bits 1
Protocol Specify protocol use DNP
Han shaking* Specify har ware han shaking None
Example
// Server Si e Connections
Connections
Port ,Bau ,Parity ,Protocol ,Han shaking
P8 ,9600 ,None ,DNP ,None
2
Not all ports shown are necessarily supporte by the har ware. Consult the appropriate Instruction
manual for etails of the ports available on specific har ware.

FS-8700-47 DNP 3.0 Driver Manual Page 17 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
5. . Server Side Node Descriptors
Section Title
No es
Column Title Function Legal Values
No e_Name Provi e name for no e
Up to 32
alphanumeric
characters
No e_ID DNP 3.0 station a ress of physical Server no e 0-65535
Protocol Specify protocol use DNP
Class_Data_Serving_Ctr*l
This parameter can be specifie to configure the
Server to serve change ata only. Refer to
Example 5.3.8 for more information.
Class0; Class1;
Class2; Class3;
Static
Server_II_Array
The name of a Data Array that has previously
been efine in the configuration in the Data
Arrays section. Refer to Error! Reference
source not found..
Max 15 characters
Example
// Server Si e No es
No es
No e_Name ,No e_ID ,
Protocol
Fiel Server ,11 ,DNP
5.3. Server Side Map Descriptors
5.3.1. FieldServer Specific Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name
Name of this Map
Descriptor Up to 32 alphanumeric characters
Data_Array_Name
Name of Data Array
where ata is to be
store in the
Fiel Server
One of the Data Array names from “Data
Array” section above
Data_Array_Offset Starting location in Data
Array
0 to maximum specifie in “Data Array”
section above
Function Function of Client Map
Descriptor
Generally for Server si e no es you will
use the PASSIVE function. The WRBX
function may be use to generate
unsolicite messages.

FS-8700-47 DNP 3.0 Driver Manual Page 18 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
5.3. . Driver Specific Map Descriptor Parameters
Column Title Function Legal Values
No e_Name Name of No e to fetch ata from
A No e Name specifie in
“Client No e
Descriptor”.
Special Map Descriptor’s
use by the DNP 3.0 Driver
are iscusse in Error!
Reference source not
found..
Length
Length of Map Descriptor. If a request length
is too large the DNP 3.0 river will pro uce a
message an a panic. The maximum length
is a function of the ata object an ata
variation being processe .
1 – 1000
A ress Starting a ress of ata element to be rea 0, 1 , 2 etc
The following parameters apply only to the DNP 3.0 Driver
DnpDataType
Correspon s to the Data Object Types efine
in the DNP ata object Library. Enter as
ecimal number. Refer to Appen ix A.9
1, 2, 10, 12, 30, 31, 32, 33,
40, 41, 20, 22, 23, 50,51, 52,
60, 80
DnpDataVari
Correspon s to the Data Object Variant
efine in the DNP ata object Library. Enter
as ecimal number.
When configure as a Server the river can
respon to requests for the so calle ‘Default’
variation. These are polls where the variation
is zero.
To configure the river to be able to respon
to requests for the efault variation then you
must create a MapDesc where the
DNPDataVari=0.
Note that the river consi ers variation=1 as
the efault in most case.
0,1,2,3 etc
Legal values are etermine
by the value of npDataType.
A itional information is
provi e in Appen ix A.9
DnpQualifier*
This parameter is ignore by the river acting
as a Server. The qualifier of the incoming poll
is use to form the response. If the poll
qualifier is not supporte by the river’s
response function then the river respon s
with Qualifier 1. The response function
supports the following qualifiers;
0,1,6,7,8,17,28,
DnpMultiMsg
Simply ensure that that there is a Server MD
for each object requeste . No special actions
are require to configure the Server to
respon to requests for multiple object types.
Refer to Appen ix A.20 for more information.
5.3.3. Timing Parameters
Column Title Function Legal
Values
Sca a_Hol _Timeout
Time Server si e waits before notifying Client that no e is
offline on Fiel Server Client si e. >1.0s

FS-8700-47 DNP 3.0 Driver Manual Page 19 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
5.3.4. Map Descriptor Example 1 – Discrete Data.
In this example the following Map Descriptor will be use allow a remote evice to request iscrete input ata. // Server Si e Map Descriptors Map_Descriptors Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,No e_Name ,A ress ,Length ,Sca a_Hol _Timeout , npDataType , npDataVari
A1 ,DA_DI1 ,0 ,Passive ,No e_A ,0 ,10 ,5 ,1 ,1
5.3.5. Map Descriptor Example – Class Data
Class ata is a composite set of ata comprising ata points from ifferent ata types. In this example the Map Descriptors have been create to serve class 0 ata. Map Descriptors associate with the Class 0 Map Descriptor tell the river which ata to serve as the class ata. When a request is receive it is matche against a Class Map Descriptor. If a matching Map Descriptor is foun the river buil s a response using the ata requeste in the associate Map Descriptors. In this example 10 Digital Inputs an 2 Analog Inputs will be serve as the response. // Server Si e Map Descriptors Map_Descriptors Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,No e_Name ,A ress ,Length ,DnpAssoc , npDataType , npDataVari ServeClass0Data ,DA_Dummy ,0 ,Server ,No e_A ,0 ,1 ,1 ,60 ,0 ServeClass0Data_DI ,DA_DI ,0 ,Server ,No e_A ,0 ,10 ,1 ,1 ,1 ServeClass0Data_AI ,DA_AI ,0 ,Server ,No e_A ,0 ,2 ,1 ,30 ,1
The DNP 3.0 river will use ata from this array to form the response.
This Map Descriptor can respon to a rea /write poll from a remote DNP evice.
This Map Descriptor will be use to process any poll whose objects match an whose a resses fall insi e the a ress an length range specifie by this Map Descriptor.
This is Map Descriptor will process comman s for a DNP Object Type 1 variation 1 Map Descriptor i.e. binary
input.
These are Server Map
Descriptors
’ServeClass0Data’ efines the Map Descriptor use to respon to request for Class 0 Data. (Type=60 vari=0).
The npAssoc fiel forms the association between these Map Descriptors.

FS-8700-47 DNP 3.0 Driver Manual Page 0 of 51
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fiel server.com
Tel: [phone] Fax: [phone] Toll Free: [phone] email: support@fiel server.com
5.3.6. Map Descriptor Example 3 – Class Data (another example)
In this example the Server respon s with a number of non-consecutive binary points. All will work fine except when the Client polls for this ata with qualifier 7. The efault response will be qualifier 7 with implie in ex style 0. The problem is that qualifier 7 tells the Client the number of
objects in the packet, but they are all assume to be a resse sequentially from a ress 0. When the ata is serve , the Client will unpack each portion, thinking that the a ress is zero for each portion an hence the ata will be overwritten. To prevent this a the npIn exStyle parameter with a value of 1 to force the Server to prefix each point of ata with the a ress of the point an thus allow the Client to unpack the ata correctly.
All this can be avoi e by having the Client poll for ata with a qualifier of 1.
// Server Si e Map Descriptors Map_Descriptors Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Location ,Function
,No e_Name ,A ress ,Length ,DNPDataType ,DNPDataVari ,DNPAssociate
Class_0_Data ,DA_DUMMY ,0 ,Server ,RTU ,0 ,1 ,60 ,0 Map_Descriptors Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Location ,Function
,No e_Name ,A ress ,Length ,DNPDataType ,DNPDataVari ,DNPAssociate , npIn exStyle
Class_0_Analogs ,DA_AI_01 ,0 ,Server ,RTU ,1 ,16 ,32 ,1 ,1 ,1 Class_0_Discs_1 ,DA_DI_01 ,0 ,Server ,RTU ,1 ,3 ,2 ,1 ,1 ,1 Class_0_Discs_2 ,DA_PB_01 ,5 ,Server ,RTU ,4 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_3 ,DA_PB_01 ,7 ,Server ,RTU ,5 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_4 ,DA_PB_01 ,9 ,Server ,RTU ,6 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_5 ,DA_PB_01 ,11 ,Passive ,RTU ,7 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_6 ,DA_PB_01 ,13 ,Passive ,RTU ,8 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_7 ,DA_PB_01 ,15 ,Passive ,RTU ,9 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_8 ,DA_PB_01 ,17 ,Passive ,RTU ,10 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_9 ,DA_PB_01 ,27 ,Passive ,RTU ,11 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_10 ,DA_PB_01 ,29 ,Passive ,RTU ,12 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_11 ,DA_PB_01 ,41 ,Passive ,RTU ,13 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_12 ,DA_PB_01 ,43 ,Passive ,RTU ,14 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_13 ,DA_PB_01 ,45 ,Passive ,RTU ,15 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_14 ,DA_PB_01 ,48 ,Passive ,RTU ,16 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_15 ,DA_PB_01 ,49 ,Passive ,RTU ,17 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_16 ,DA_PB_01 ,51 ,Passive ,RTU ,18 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_17 ,DA_PB_01 ,53 ,Passive ,RTU ,19 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_18 ,DA_PB_01 ,55 ,Passive ,RTU ,20 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_19 ,DA_PB_01 ,61 ,Passive ,RTU ,23 ,1 ,2 ,1 ,1 ,1 Class_0_Discs_20 ,DA_PB_01 ,63 ,Passive ,RTU ,24 ,1 ,2 ,1 ,1 ,1