FieldServer FS 8700 47 User Manual

-
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  
Driver Version:  
1.03  
Document Revision: 14  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
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  
FS-8917-04  
FS-8700-47  
UTP cable (7 foot) for RS-232 use  
RJ45 to DB25M connection adapter  
Driver Manual.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
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  
DB25F  
8917-04  
Connect to one of the RS-232  
Ports on the FieldServer  
RJ45  
8
1
P1  
FieldServer  
FieldServer Function From  
Default  
Color  
Rx  
RJ45-01 DB25F-02 White  
RJ45-02 DB25F-04 Brown  
CTS  
DSR  
GND  
GND  
DTR  
RTS  
Tx  
RJ45-03  
Yellow  
RJ45-04 DB25F-07 Green  
RJ45-05  
RJ45-06  
Red  
Black  
RJ45-07 DB25F-05 Orange  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
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  
FLOAT, BIT, UInt16, SInt16,  
Packed_Bit, Byte, Packed_Byte,  
Swapped_Byte  
Provide data format. Each data array can  
Data_Format  
only take on one format.  
Number of Data Objects. Must be larger  
Data_Array_Length than the data storage area required for 1-10,000  
the data being placed in this array.  
Example  
// Data Arrays  
//  
Data_Arrays  
Data_Array_Name  
DA_AI_01  
DA_AO_01  
DA_DI_01  
,Data_Format  
,UInt16  
,UInt16  
,Bit  
,Data_Array_Length  
,200  
,200  
,200  
,200  
DA_DO_01  
,Bit  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
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  
Specify which port the device is connected to the  
FieldServer  
Port  
P1-P8, R1-R21  
110 – 115200, standard  
baud rates only  
Even, Odd, None, Mark,  
Space  
Baud*  
Parity*  
Specify baud rate  
Specify parity  
Data_Bits*  
Stop_Bits*  
Protocol  
Specify data bits  
Specify stop bits  
7, 8  
1
Specify protocol used  
DNP  
Handshaking* Specify hardware handshaking  
None  
0-32000 seconds, 1  
second.  
Poll Delay*  
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. OriginalStyle,  
NoLink,  
Application*  
It is also possible to use this parameter to control if link  
resets are used/required. Refer to Appendix A.15.  
OrigStyle-NoLink  
Example  
// Client Side Connections  
Connections  
Port  
R1  
,Baud ,Parity ,Protocol ,Handshaking ,Poll_Delay  
,9600 ,None ,DNP ,None ,0.100s  
4.3.  
Client Side Node Descriptors  
Section Title  
Nodes  
Column Title  
Function  
Provide name for node  
Legal Values  
Up  
to  
32  
alphanumeric  
Node_Name  
characters  
DNP 3.0 station address of physical Server  
node  
Specify protocol used  
Specify which port the device is connected to  
the FieldServer  
Node_ID  
Protocol  
Port  
0-65535  
DNP  
P1-P8, R1-R21  
Example  
// Client Side Nodes  
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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 10 of 51  
4.4.  
4.4.1.  
Client Side Map Descriptors  
FieldServer Specific Map Descriptor Parameters  
Column Title  
Function  
Legal Values  
Up to 32 alphanumeric  
characters  
Map_Descriptor_Name  
Name of this Map Descriptor  
Name of Data Array where  
data is to be stored in the  
FieldServer  
One of the Data Array names  
from “Data Array” section  
above  
Data_Array_Name  
0 to maximum specified in  
“Data Array” section above  
Data_Array_Offset  
Function  
Starting location in Data Array  
Function of Client Map  
Descriptor  
Rdbc, Wrbc, Wrbx  
4.4.2.  
Driver Specific Map Descriptor Parameters  
Function  
Column Title  
Legal Values  
The following parameters are used by a number of drivers.  
A Node Name specified in  
“Client Node Descriptor”.  
Special Map Descriptors are  
Node_Name  
Name of Node to fetch data from  
discussed  
Reference  
found..  
in  
Error!  
not  
source  
Length of Map Descriptor. If a request length  
is too large the DNP 3.0 driver will produce a  
Length  
message and a panic. The maximum length 1 – 1000  
is a function of the data object and data  
variation.  
Address  
Starting address of data element to be read  
0, 1 , 2 etc  
The following parameters apply only to the DNP 3.0 Driver  
Corresponds to the Data Object Types defined 1, 2, 10, 12, 30, 31, 32, 33,  
DnpDataType in the DNP data object Library. Additional 40, 41, 20, 22, 23, 50, 51, 52,  
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  
60, 80 - decimal numbers  
0, 1,2,3 etc  
Legal values are determined  
by the value of dnpDataType.  
DnpDataVari  
Used to tell driver which Suffield of the object  
to map to/from the FieldServer Data Array.  
Additional information is provided in Appendix combo  
A.10  
Not Used.  
Value, flags, time1, time2,  
DnpSubType*  
DnpFlagBit*  
Zero, 1, 6, 7, 8, 17h -  
hexadecimal values. For  
This parameter is only required if you need to qualifier 17h specify the  
over-ride the default qualifier used by the DNP value of dnpQualifier as 17 in  
DnpQualifier*  
DnpFunction*  
3.0 driver. Refer to Appendix A.11  
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.  
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  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Column Title  
Page 11 of 51  
Function  
Legal Values  
When class data is requested the DNP device  
responds with data of multiple types and  
variations in one message.  
One Map  
DnpAssociate*  
Non-zero positive integers.  
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 0, positive whole numbers.  
associate Map Descriptors for this purpose. All By default Map Descriptors  
DnpMultiMsg* Map Descriptors whose dnpMultiMsg values are not associated with each  
are equal will be requested in a single poll. other. The default value of  
Ensure only one is active (rdbc for example) zero ensures no association.  
and all the others have the function set to  
'Server'. Refer also to Appendix A.20  
4.4.3.  
Timing Parameters  
Column Title  
Scan_Interval  
Function  
Rate at which data is polled  
Legal Values  
>0.1s  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
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  
Specify which port the device is connected to the  
FieldServer  
Legal Values  
P1-P8, R1-R22  
Port  
110 – 115200, standard baud  
rates only  
Baud*  
Specify baud rate  
Parity*  
Specify parity  
Even, Odd, None, Mark, Space  
Data_Bits*  
Specify data bits  
7, 8  
Stop_Bits*  
Protocol  
Specify stop bits  
1
Specify protocol used  
DNP  
Handshaking* Specify hardware handshaking  
None  
Example  
// Server Side Connections  
Connections  
Port  
P8  
,Baud ,Parity ,Protocol ,Handshaking  
,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: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 17 of 51  
Legal Values  
5.2.  
Server Side Node Descriptors  
Section Title  
Nodes  
Column Title  
Function  
Provide name for node  
Up  
to  
32  
Node_Name  
alphanumeric  
characters  
Node_ID  
DNP 3.0 station address of physical Server node 0-65535  
Specify protocol used DNP  
This parameter can be specified to configure the Class0;  
Class_Data_Serving_Ctr*l Server to serve changed data only. Refer to Class2;  
Protocol  
Class1;  
Class3;  
Example 5.3.8 for more information.  
Static  
The name of a Data Array that has previously  
been defined in the configuration in the Data  
Server_II_Array  
Max 15 characters  
Arrays section.  
Refer to Error! Reference  
source not found..  
Example  
// Server Side Nodes  
Nodes  
Node_Name ,Node_ID ,Protocol  
FieldServer ,11 ,DNP  
5.3.  
5.3.1.  
Server Side Map Descriptors  
FieldServer Specific Map Descriptor Parameters  
Column Title  
Function  
Legal Values  
Name of this Map  
Descriptor  
Name of Data Array  
where data is to be  
stored in the  
Map_Descriptor_Name  
Data_Array_Name  
Data_Array_Offset  
Function  
Up to 32 alphanumeric characters  
One of the Data Array names from “Data  
Array” section above  
FieldServer  
Starting location in Data 0 to maximum specified in “Data Array”  
Array  
section above  
Generally for Server side nodes you will  
use the PASSIVE function. The WRBX  
function may be used to generate  
unsolicited messages.  
Function of Client Map  
Descriptor  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 18 of 51  
5.3.2.  
Driver Specific Map Descriptor Parameters  
Column Title  
Function  
Legal Values  
A Node Name specified in  
“Client  
Special  
Node  
Map  
Descriptor”.  
Descriptor’s  
Node_Name  
Name of Node to fetch data from  
used by the DNP 3.0 Driver  
are discussed in Error!  
Reference  
source  
not  
found..  
Length of Map Descriptor. If a request length  
is too large the DNP 3.0 driver will produce a  
Length  
message and a panic. The maximum length 1 – 1000  
is a function of the data object and data  
variation being processed.  
Address  
Starting address of data element to be read  
0, 1 , 2 etc  
The following parameters apply only to the DNP 3.0 Driver  
Corresponds to the Data Object Types defined 1, 2, 10, 12, 30, 31, 32, 33,  
DnpDataType in the DNP data object Library. Enter as  
decimal number. Refer to Appendix A.9  
Corresponds to the Data Object Variant  
defined in the DNP data object Library. Enter  
as decimal number.  
40, 41, 20, 22, 23, 50,51, 52,  
60, 80  
When configured as a Server the driver can  
respond to requests for the so called ‘Default’  
variation. These are polls where the variation  
0,1,2,3 etc  
Legal values are determined  
by the value of dnpDataType.  
is zero.  
DnpDataVari  
To configure the driver to be able to respond  
to requests for the default variation then you  
must create a MapDesc where the  
DNPDataVari=0.  
Additional information is  
provided in Appendix A.9  
Note that the driver considers variation=1 as  
the default in most case.  
This parameter is ignored by the driver acting  
as a Server. The qualifier of the incoming poll  
is used to form the response. If the poll  
qualifier is not supported by the driver’s  
response function then the driver responds  
DnpQualifier*  
with Qualifier 1. The response function  
supports the following qualifiers;  
0,1,6,7,8,17,28,  
Simply ensure that that there is a Server MD  
for each object requested. No special actions  
DnpMultiMsg are required to configure the Server to  
respond to requests for multiple object types.  
Refer to Appendix A.20 for more information.  
5.3.3.  
Timing Parameters  
Legal  
Values  
Column Title  
Function  
Time Server side waits before notifying Client that node is  
offline on FieldServer Client side.  
Scada_Hold_Timeout  
>1.0s  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 25 of 51  
5.4.  
Server Side Limitations  
The DNP 3.0 Server can only parse a single poll per message. This means that a single message  
cannot contain more than one read request - You cannot read two different objects types/variations in  
a single read request. The same limitation applies to write commands sent the Server.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Appendix A. Advanced Topics  
Page 26 of 51  
Appendix A.1.  
DNP 3.0 Protocol.  
The DNP 3.0 protocol is complex and not all the features are implemented by this driver.  
The application layer performs a large set of potential functions, each of which can request its  
own app layer confirmation transaction and many of which include a separate response  
transaction.  
The app layer messages are wrapped and unwrapped by the data link layer which can ask for  
DLL layer ack's and confirmations.  
The protocol provides for unsolicited messages.  
The protocol defines and allows a huge set of data object & variations to be handled.  
Not all DNP devices (slaves) provide all functions, data objects....  
Appendix A.2.  
DNP Driver Functionality  
The DNP master driver has been developed to provide the functionality a FieldServer Technologies  
Client requires in communicating with a DNP slave device as well as additional functionality and data  
object handling. The DNP master driver is to be considered as DNP Subset Level 1 implementation  
as defined in DNP V3.00 Subset Definitions Doc Number P009-0IG.SUB  
The DNP slave driver has been developed to test the master driver and may NOT be considered a  
DNP slave driver as defined in the DNP subset definitions.  
Appendix A.3.  
DNP Objects mapped to FieldServer Data Arrays  
DNP objects consist of values and additional information such as quality, control and status bits as  
well as time information.  
The DNP driver allows this additional data to be extracted and mapped into the indicated data array.  
For example, the DNP master driver can read 10 analog inputs with status flags and put the 10  
values in consecutive order in one data array and the 10 status bytes in another data array.  
Control of this functionality is achieved by setting up the CSV file correctly. If not specified the DNP  
driver extracts data values and discards the additional data.  
Appendix A.4.  
Channel Idle, Master & Slave Idle.  
The following notes describe the internal architecture of the driver and do not affect the way that the  
driver is used or configured.  
The Driver is implemented using the channel idle. The channel idle function is called in the master  
mux but must be regarded as processing the channel (independently of the master or slave).  
Chan Idle  
processes all incoming bytes,  
looks for complete messages,  
From a DLL layer point of view parses the message and responds  
Signals the master or slave app layer that there is an coming message  
Signals master if there is an app layer response  
Signals slave if there is an app layer request(read/write) or unsolicited message.  
Looks for master or slave app layer signals to process an outgoing message  
Maintains a list of nodes & node status (in terms of link reset)  
Slave Idle  
Looks for signals from chan idle that a message has been received  
Parses message from an app layer point of view.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 27 of 51  
If required sets flags for  
Map Descriptor matching,  
fetch/store function calls  
and/or response function call  
Signals Chan idle the outgoing app layer message needs to be processed.  
Looks for signals from chan idle that a message has been received  
Processes Map Descriptors and forms read/write messages  
Master Idle  
Signals Chan idle the outgoing app layer message needs to be processed.  
Appendix A.5.  
DLL Layer Functionality in the Master  
The DNP Primer provided by dnp.org describes the DLL layer requests for confirmation as optional  
and suggests that it is not often employed. Our driver never asks for DLL layer confirmations. Thus  
the DLL layer functions as a mere wrapper/unwrapper layer. It wraps user data with a header and  
CRC's but does not perform node-node confirmations.  
The only DLL layer functions which have been implemented are send and respond with user data and  
link reset. The slave DNP driver will not respond until a link reset has been performed. The DNP  
master driver sends a Link Reset request when a Map Descriptor requests data from an un-reset  
node. The link resetting is performed on a node-node link.  
Appendix A.6.  
App Layer Functionality in the Master  
The App layer provides over 40 app layer functions, confirmations and responses and allows for  
handling of a huge number of data objects.  
1. Read  
2. Write  
3. Select  
App  
Layer 4. Operate  
Functions  
6. Direct Operate with no Ack (limited)  
8. Direct Freeze with no Ack (limited)  
129. Response  
130. Unsolicited. (Slave Driver can parse these messages.)  
The Slave indicates its internal state by appending internal indication bytes to the  
app layer header of each response. Thus it can report that it is faulty, corrupted or  
unable to process the request. If it can’t find a matching Map Descriptor it sets the  
internal indication bit used to indicate that the data object parameters specified  
cannot be parsed.  
Internal  
Indications  
You can configure a Server node to respond with the internal indications bytes that  
are extracted from a Data Array allowing you to control them. For more  
information, refer to Error! Reference source not found..  
The app layer contains a Qualifier Byte used to control indexing for data objects.  
The DNP 3.0 Driver only handles Qualifiers 00, 01, 07, 08, 17, 28. Qualifier 6 is  
supported with limitations.  
App  
Qualifier  
Layer  
The DNP 3.0 (master) Driver never asks for an App Layer Confirmation. The DNP  
3.0 Slave Driver is capable of responding to an app layer request for confirmation  
(to allow it to process an unsolicited message which may ask for confirmation.)  
App  
Confirmation  
Layer  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 28 of 51  
Appendix A.7.  
Internal Indications, Object 80 and DNP_II  
The driver can store the Internal Indications Bits found in incoming messages and it is possible to  
control the values of the internal indication bytes sent in responses. In addition, the driver can be  
configured to respond to the Poll for Object 80 (Internal Indications)  
A.7.1.  
Incoming Internal Indications Bytes  
This driver can expose data from the most recently consumed message and additional diagnostic  
information using a special Map Descriptor called “DNP_ii” (DNP Internal Indications)  
The following example shows the configuration of this Map Descriptor. Only one of these Map  
Descriptors may be configured per FieldServer.  
Nodes  
Node_Name  
Null_Node  
,Protocol  
,DNP  
Data_Arrays  
Data_Array_Name  
DNP_DIAG  
,Data_Format  
,UINT32  
,Data_Array_Length  
,100  
Map_Descriptors  
Map_Descriptor_Name  
dnp-ii  
,Data_Array_Name,  
,Node_Name  
,Null_Node  
,DNP_DIAG  
,
The following data is stored in the Data Array DNP_DIAG.  
Array  
Element  
Contents  
The first byte of the Internal indication reported by a DNP device as found in the most  
recently received message.  
Only messages complete enough to warrant parsing will cause this item to be  
updated.  
0
1
DNP devices only contain internal indication bytes when the message is an application  
layer response type message. Typically this includes all responses to data  
queries/writes as well as unsolicited messages.  
The 2nd byte of the response internal indication.  
Bit zero is the least significant bit.  
A one (1) in the bit position indicates the described state.  
Bit  
#
Explanation  
First Byte  
All stations message received  
Set when a request is received with the destination address of the all stations address (ffff  
hexadecimal).  
Cleared after next response (even if response to global request is required)  
Bit  
0
Used to let the master station know that a Broadcasted message was received by this station.  
Class 1 data available  
Bit  
1
Set when data that has been configured as Class 1 data is ready to be sent to the master  
Master station should request this class data from the Outstation when this bit is set in a  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 29 of 51  
Bit  
#
Explanation  
response  
Class 2 data available  
Bit Set when data that has been configured as Class 2 data is ready to be sent to the master  
2
Master station should request this class data from the Outstation when this bit is set in a  
response  
Class 3 data available  
Bit Set when data that has been configured as Class 3 data is ready to be sent to the master  
3
Master station should request this class data from the Outstation when this bit is set in a  
response  
Time-synchronization required from the master. The master synchronizes the time by writing  
Bit the Time and Date object to the Outstation.  
4
Cleared when the time is set by the master. This bit is also cleared when the master explicitly  
writes a 0 into this bit of the Internal Indication object of the Outstation.  
Set when some or all of the Outstation's digital output points are in the Local state. That is,  
Bit the Outstation's control outputs are NOT accessible through the DNP protocol.  
5
Clear when the Outstation is in the Remote state. That is, the Outstation's control outputs are  
accessible through the DNP protocol.  
Device trouble  
Set when an abnormal condition exists at the Outstation. The device profile for a given device  
states the conditions that affect this bit.  
This should only be used when the state can not be described by a combination of one or  
more of the other IIN bits.  
Bit  
6
Device restart  
Bit Set when the user application at the Outstation restarts.  
7
Cleared when the master explicitly Writes a 0 into this bit of the Internal Indications object in  
the Outstation.  
Second Byte  
Bit  
0
Function code not implemented  
Requested object(s) unknown. The Outstation does not have the specified objects or there  
are no objects assigned to the requested class. This indication should be used for debugging  
purposes and usually indicates a mismatch in device profiles or configuration problems.  
Parameters in the qualifier, range or data fields are not valid or out of range. This is a catch-all  
for application request formatting errors. This indication should be used for debugging  
purposes and usually indicates configuration problems.  
Bit  
1
Bit  
2
Event buffer(s), or other application buffers have overflowed. For example, COS/SOE buffers  
Bit have overflowed. The master should attempt to recover as much data as possible and  
3
indicate to the user that their may be lost data. The appropriate error recovery procedures  
should be initiated by the user.  
Bit  
4
Request understood but requested operation is already executing.  
Set to indicate that the current configuration in the Outstation is corrupt and that the master  
Bit application layer should inform the user of this exception. The master may download another  
5
configuration to the Outstation. Note that sometimes a corrupt configuration will disable an  
Outstation, making it impossible to communicate this condition to a master station.  
Bit  
6
Bit  
7
Reserved for use by agreement, currently always returned as zero (0).  
Reserved for use by agreement, currently always returned as zero (0).  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 30 of 51  
A.7.2.  
Internal Indications reported in Responses  
The Internal Indications (IIN) field is a two-octet field that follows the function code in all  
responses. When a request cannot be processed due to formatting errors or unavailable data,  
the IIN is always returned with the appropriate bits set.  
A.7.3.  
Server_II_Array  
This parameter only applies to Server/responding nodes.  
If specified the driver validates that the Data Array exists. If it doesn’t then Error 78 is printed.  
The driver uses the 1st two elements to form the Internal Indications bytes of all normal responses  
(responses where the driver is able to respond to the poll). The driver does not modify these  
bytes when building the response but sends the values exactly as found in the Data Array.  
If a poll for unknown and/or unsupported objects/devices is received, the driver builds the internal  
indications bytes itself. They cannot be controlled using this parameter.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 32 of 51  
Appendix A.8.  
DNP_Stats  
In addition to the standard FieldServer communication statistics described in the FieldServer  
Configuration Manual the DNP 3.0 Driver can expose some driver statistics by writing to a data array  
called “DNP_STATS”  
The following example shows how this special Map Descriptor can be configured. Only one of these  
Map Descriptors may be specified per FieldServer.  
Nodes  
Node_Name  
Null_Node  
,Protocol  
,DNP  
,Node_ID  
,100  
Data_Arrays  
Data_Array_Name  
DNP_STATS  
,Data_Format  
,UINT32  
,Data_Array_Length  
,100  
Map_Descriptors,  
Map_Descriptor_Name  
dnp-stats  
,Data_Array_Name,  
,DNP_STATS,  
,Node_Name  
,Null_Node  
The driver stores the following data in the data array EGD_STATS.  
Array  
Contents  
Element  
1
2
3
4
5
6
7
8
DRV_DLL_CLIENT_SENDS_MSG  
DRV_DLL_CLIENT_SENDS_BYTES  
DRV_DLL_SERVER_SENDS_MSG  
DRV_DLL_SERVER_SENDS_BYTES  
DRV_DLL_CLIENT_RCVS_MSG  
DRV_DLL_CLIENT_RCVS_BYTES  
DRV_DLL_SERVER_RCVS_MSG  
DRV_DLL_SERVER_RCVS_BYTES  
DNP_UPD_TMO  
9
10  
11  
12  
12  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
26  
27  
28  
29  
DNP_UPD_PROTO  
DNP_UPD_NOISE  
DNP_UPD_CHECK  
DNP_UPD_STATION  
DNP_UPD_LENGTH  
DNP_UPD_EXCEPT  
DNP_UPD_STREAMING  
DNP_UPD_FUNCTION  
DNP_UPD_PREMATURE  
DNP_UPD_IC_TIMEOUT  
DNP_UPD_NAK  
DNP_UPD_OVERRUN  
DNP_UPD_HOLD_TIMEOUTS  
DNP_UPD_NODE_OFFLINE  
DNP_UPD_NO_SLAVE  
DNP_UPD_NO_START  
DNP_UPD_SCADA_BYTES_RECD  
DNP_UPD_SCADA_BYTES_SENT  
DNP_UPD_SCADA_MSG_SENT  
DNP_UPD_SCADA_MSG_RECD  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 33 of 51  
Array  
Element  
Contents  
30  
31  
32  
33  
34  
35  
36  
37  
38  
39  
40  
41  
DNP_NOT_OK  
DNP_UPD_RESET_RQD  
DNP_UPD_CANT_RESET  
DNP_UPD_NO_NODES  
DNP_UPD_RESET_FAILED  
DNP_UPD_MAST_DEBUG_MSG  
DNP_UPD_MAST_PARSE_ERR  
DNP_UPD_SLAVE_PARSE_ERR  
DNP_UPD_MAPD_TOO_SHORT  
DNP_UPD_TOO_MANY_BYTES3  
DNP_DIAGNOTIC_GENERATOR  
DNP_UPD_LINK_RESET_DONE  
DNP_UPD_LINK_RESET_DONE_BY_MST  
Increments once each time a link reset ack is sent by a master  
DNP_UPD_LINK_RESET_DONE_BY_SRV  
Increments once each time a link reset ack is sent by a slave.  
DNP_UPD_LINK_STATUS_STATE  
42  
43  
44  
Result of most recent link status poll are stored here. 1=Busy, 2=Available, 0=Not  
Update  
Appendix A.9.  
DNP 3.0 Data Objects  
The DNP 3.0 Driver acting as a Client will produce a single message fragment. A message fragment  
may contain a maximum of 249 bytes, some of which constitute overhead. The DNP 3.0 driver will  
panic if the message fragment is too long. Reduce the length and add another Map Descriptor to poll  
additional items. This limitation does not apply when the DNP 3.0 driver processes a response from  
a query as the driver can process multi fragment responses.  
The list of data objects supported and the functions used to access the objects is defined on the  
Driver Fact Sheet which may be obtained from FieldServer Technologies. The table is known as a  
DNP 3.0 Implementation Table.  
The table below lists the objects and variations that be used in the Map Descriptors. The DNP 3.0  
Driver supports all the objects with some exceptions. The exceptions are noted by indicating the  
revision number of the driver prior to them being supported or by indicating that the object is not  
supported with the NS annotation.  
Default Variations are designated with a *. Not all Data Types have a default variation. The default  
variation will be returned when a Client polls for variation zero (default). Server configurations require  
a Map Descriptor with variation zero to be defined in the CSV file before the driver can respond with  
the default variation data.  
Object  
Variation.  
Ex  
Description  
1
1
1
2
2
2
2
0
1*  
2
0
1*  
2
Binary Input - All Variations  
Binary Input  
Binary Input with Status  
Binary Input Change - All Variations  
Binary Input Change without Time  
Binary Input Change with Time  
3
Binary Input Change with Relative Time  
3
Increments by one each time a response message isn’t sent because the number of elements to  
respond with requires too many bytes to fit in a message.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 34 of 51  
Object  
10  
10  
12  
12  
12  
12  
20  
20  
20  
20  
20  
20  
20  
20  
20  
21  
21  
21  
21  
21  
21  
21  
21  
21  
21  
21  
21  
21  
22  
22  
22  
22  
22  
22  
22  
22  
22  
23  
23  
23  
23  
23  
23  
23  
23  
23  
30  
30  
30  
30  
30  
31  
31  
31  
Variation.  
Ex  
Description  
1*  
2
0
1*  
2
3
0
1*  
2
3
4
5
6
7
8
0
1*  
2
3
4
Binary Output  
Binary Output Status  
NS  
Control Descriptor - All Variations  
101a Control Relay Output Descriptor  
NS  
NS  
Pattern Control Descriptor  
Pattern Mask  
Binary Counter - All Variations  
32-Bit Binary Counter  
16-Bit Binary Counter  
32-Bit Delta Counter  
16-Bit Binary Counter  
32-Bit Binary Counter without Flag  
16-Bit Binary Counter without Flag  
32-Bit Delta Counter without Flag  
16-Bit Delta Counter without Flag  
Frozen Counter - All Variations  
32-Bit Frozen Counter  
16-Bit Frozen Counter  
32-Bit Frozen Delta Counter  
16-Bit Frozen Delta Counter  
5
6
7
8
32-Bit Frozen Counter with Time of Freeze  
16-Bit Frozen Counter with Time of Freeze  
32-Bit Frozen Delta Counter with Time of Freeze  
16-Bit Frozen Delta Counter with Time of Freeze  
32-Bit Frozen Counter without Flag  
16-Bit Frozen Counter without Flag  
32-Bit Frozen Delta Counter without Flag  
16-Bit Frozen Delta Counter without Flag  
9
10  
11  
12  
0
1*  
2
3
4
5
6
101a Counter Change Event - All Variations  
101a 32-Bit Counter Change Event without Time  
101a 16-Bit Counter Change Event without Time  
101a 32-Bit Delta Counter Change Event without Time  
101a 16-Bit Delta Counter Change Event without Time  
101a 32-Bit Counter Change Event with Time  
101a 16-Bit Counter Change Event with Time  
101a 32-Bit Delta Counter Change Event with Time  
101a 16-Bit Delta Counter Change Event with Time  
101a Frozen Counter Event - All Variations  
101a 32-Bit Frozen Counter Event without Time  
101a 16-Bit Frozen Counter Event without Time  
101a 32-Bit Frozen Delta Counter Event without Time  
101a 16-Bit Frozen Delta Counter Event without Time  
101a 32-Bit Frozen Counter Event with Time  
101a 16-Bit Frozen Counter Event with Time  
101a 32-Bit Frozen Delta Counter Event with Time  
101a 16-Bit Frozen Delta Counter Event with Time  
Analog Input - All Variations  
7
8
0
1*  
2
3
4
5
6
7
8
0
1*  
2
3
4
0
1*  
3
32-Bit Analog Input  
16-Bit Analog Input  
32-Bit Analog Input without Flag  
16-Bit Analog Input without Flag  
Frozen Analog Input - All Variations  
32-Bit Frozen Analog Input  
32-Bit Frozen Analog Input with Time of Freeze  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 35 of 51  
Object  
31  
31  
31  
32  
32  
32  
32  
32  
33  
33  
33  
33  
33  
40  
40  
40  
41  
41  
41  
50  
50  
50  
51  
51  
51  
52  
52  
52  
60  
60  
60  
60  
60  
70  
80  
81  
82  
83  
83  
90  
100  
100  
100  
101  
101  
101  
Variation.  
Ex  
Description  
16-Bit Frozen Analog Input with Time of Freeze  
32-Bit Frozen Analog Input without Flag  
16-Bit Frozen Analog Input without Flag  
Analog Change Event - All Variations  
32-Bit Analog Change Event without Time  
16-Bit Analog Change Event without Time  
32-Bit Analog Change Event with Time  
16-Bit Analog Change Event with Time  
Frozen Analog Event - All Variations  
32-Bit Frozen Analog Event without Time  
16-Bit Frozen Analog Event without Time  
32-Bit Frozen Analog Event with Time  
16-Bit Frozen Analog Event with Time  
Analog Output Status - All Variations  
32-Bit Analog Output Status  
4
5
6
0
1
2
3
4
0
1*  
2
3
4
0
1*  
2
0
1
2
0
1*  
2
0
1*  
2
0
1*  
2
0
1*  
2
3
4
1
1
1
1
1
2
1
1
2
3
1
2
3
16-Bit Analog Output Status  
Analog Output Descriptor - All Variations  
32-Bit Analog Output Descriptor  
16-Bit Analog Output Descriptor  
101a Time and Date - All Variations  
101a Time and Date  
101a Time and Date with Interval  
101a Time and Date CTO - All Variations  
101a Time and Date CTO  
101a Unsynchronized Time and Date CTO  
NS  
Time Delay - All Variations  
Time Delay Coarse  
1.03b4  
1.03b4 Time Delay Fine  
1.03b4  
Class 0 Data  
Class 1 Data  
Class 2 Data  
Class 3 Data  
NS  
File Identifier  
1.03iB Internal Indications  
NS  
NS  
NS  
NS  
NS  
NS  
NS  
NS  
NS  
NS  
NS  
Storage Object  
Device Profile  
Private Registration Object  
Private Registration Object Descriptor  
Application Identifier  
Short Floating Point  
Long Floating Point  
Extended Floating Point  
Small Packed Binary-Coded Decimal  
Medium Packed Binary-Coded Decimal  
Large Packed Binary-Coded Decimal  
4 See notes in Appendix A.10 for function code 23.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 36 of 51  
Appendix A.10. Controlling the DNP 3.0 Driver’s Function Code  
When a write Map Descriptor is found by the DNP 3.0 Driver it will use the DNP protocol’s write  
function to write data to the DNP device. If the DNP device’s vendor requires that an alternative DNP  
function be used, use the keyword dnpFunction in the Map Descriptor and specify the function that  
the vendor requires (provided that it is in the list of functions implemented by this driver.)  
Example: To set a Control Relay Output Descriptor’s state in a SEL-351A relay you cannot use a  
write function. The vendor requires you use functions 3, 4, 5 or 6. Select the appropriate function and  
specify it as the value of the dnpFunction parameter.  
In some cases the DNP 3.0 driver will change the default function automatically. This will be  
reported in the error log.  
The dnpFunction parameters may have any legal DNP protocol function. The function must be  
specified as a decimal value.  
Function  
Value for  
Client Supports Server Supports  
dnpFunction  
Confirm  
Read  
Write  
Select  
0
1
2
3
4
5
6
7
8
9
10  
11  
12  
13  
14  
23  
Yes  
Yes  
Yes  
Yes5  
Yes5  
Yes5  
Yes5  
Yes  
Yes  
Yes  
Yes5  
Yes5  
Yes5  
Yes5  
Operate  
Direct Operate  
Direct Operation with no Ack  
Immediate freeze  
Immediate freeze with no Ack  
Freeze Clear  
Freeze Clear with no Ack  
Freeze Time  
Freeze Time with No Ack  
Cold Restart  
Limited*  
Limited*  
Warm Restart  
Delay Measurement  
Yes  
Yes  
When the Function #23 (Delay Measurement) is used the following two notes apply:  
1. When the driver is configured as a Client, the configuration must also specify the dnpDataType  
parameter set to Object 52 (Time Delay Objects) and the dnpDataVari parameter to variation 2  
(Time Delay Fine ). The driver reads the single object from the Server. The address parameter is  
ignored.  
2. When the driver is configured to serve a response to a poll with application function #23 then the  
configuration must have a Server Map Descriptor with dnpDataType parameter set to Object 52  
(Time Delay Objects) and dnpDataVari parameter set to variation 2 (Time Delay Fine ). The  
address parameter is ignored as the poll is for a single object. The driver responds by serving  
data from the Data Array element specified on the Server Map Descriptor – most DNP 3.0 RTU  
devices respond by reporting the number of milliseconds between receiving the 1st bit of the poll  
and sending the 1st bit of the response.  
5
There are limitations to the Select and Operate Functionality. Refer to Appendix A.19 for more  
information.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 37 of 51  
Appendix A.11. Controlling the DNP 3.0 Driver’s Qualifier  
The protocol uses a qualifier in the application layer part of a message to indicate how data must be  
packed in the message. The DNP 3.0 Driver as a Client will default to use a Qualifier of 1. The  
qualifier is used internally by the driver and is of no concern unless the DNP protocol has been  
implemented to require the use of qualifiers other then 1. In this case it is possible to change the  
driver’s default value by specifying the dnpQualifier parameter. For example, to address a Control  
Relay Output Descriptor object in a Multlin 489 Generator management relay, the vendor data sheet  
indicates that only qualifiers 17 and 28 may be used.  
When the driver is configured as a Server then the dnpQualifier parameter specified in the CSV file is  
not used. The qualifier of the requesting poll is used in interpreting the request and forming the  
response. The driver accepts poll’s that have the DNP qualifier set to 6 which effectively requests the  
Server to send back all objects of the type requested. The driver’s support for this qualifier is limited  
by the length of the response message. The response must fit in one 255 byte message. The  
number of objects contained in the response message (and hence the length of the response) is  
controlled by the length parameter. We have found lengths in the upper range 10 to 30 successful.  
As a Server, if configured to serve ‘changed’ data the driver may choose the qualifier itself as the data  
object may be non sequential. See 5.3.8.  
Appendix A.12. FieldServer DNP Node Number  
The FieldServer’s DNP node number is set in the CSV file. In the following example the node is set to  
22.  
FieldServer  
Title  
B1  
,System_Node_ID  
,22  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Appendix A.13. DnpSubType  
Page 38 of 51  
DNP objects often contain more than one element of information, e.g. Object 30, variation 1 is a 32-  
bit analog input. When the DNP device is polled for data for this object the device returns a data  
structure which contains a 32 bit value for the input and an 8 bit status byte indicating the input’s  
quality. Alternatively the FieldServer defaults to the value subtype.  
By using the value or flags in the field for dnpSubType you could have the FieldServer extract the  
value or the status byte and place them in the data array associated with the Map Descriptor. In this  
example it would have made no sense to try and extract a time as there is no time field associated  
with object 30, variation 1.  
Permitted Values  
Value  
Flags  
Description  
The driver extracts the value of the object being read.  
The driver extracts the quality/status byte of the object.  
The driver extracts the time field from the object.  
The driver extracts a second time field from the object if the object has more  
than one.  
Time1  
Time2  
Used with a write Map Descriptor with the dnpFunction set to 5 (Direct  
Operation with no Ack). The driver uses multiple consecutive elements from  
the data array to build the write command.  
When used with Object 12 Variation 1.  
Combo  
The 1st array element is used as a byte to fill in the control code field.  
The 2nd array element is used as a byte to fill in the count field.  
The 3rd array element is used as a UINT32 to fill in the on time field.  
The 4th array element is used as a UINT32 to fill in the off time field.  
The status field is always set to zero.  
(NB - only valid with  
Object 12, Variation  
1;  
Object 41, Variation  
1 & 2)  
When used with Object 41 Variation 1 & 2  
The 1st array element is used as a INT32 (variation 1) or INT16 (variation2)  
to fill in the requested value field.  
The 2nd Array Element is used as a byte to fill in the control status field. (See  
the definition of object 12 for a description of this field.)  
Appendix A.14. Communication Stats  
The driver counts bytes on the connection and messages on the Map Descriptors. Thus if a Map  
Descriptor is used to generate a poll then the transmit messages increment and when a response is  
received, its received messages will increase. The byte count of these messages will be counted on  
the connection and not on the Map Descriptor. The connection also counts messages and bytes that  
form connection related messages such as link resets, confirms, acks, naks….  
Appendix A.15. Link Reset  
The Link Reset message forms part of the Data Link layer of the DNP 3.0 protocol. It is used to  
establish and check a connection. When configured as a Client, the driver sends a Link Reset and  
waits for the Server to respond before starting data transfer. When configured as a Server, the driver  
will not respond to messages until the remote Client has sent a Link Reset. The following example  
configuration will override this default behavior.  
Example  
// Server Side Connections  
Connections  
Port  
P8  
,Baud  
,9600  
,Parity  
,None  
,Protocol  
,DNP  
,Application  
,NoLink  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 39 of 51  
Appendix A.16. Controlling DA Offsets  
Versions of the driver prior to 1.02a used a method to calculate DA offsets that was not consistent  
with the general FieldServer model. This was corrected in versions 1.02a and later. To retain the old  
offset calculation, specify the ‘Application’ parameter on the connection.  
Use either ‘OriginalStyle’ or ‘OrigStyle-NoLink’ (to overwrite Link Reset).  
Example  
// Server Side Connections  
Connections  
Port  
P8  
,Baud  
,9600  
,Parity  
,None  
,Protocol  
,DNP  
,Application  
,OriginalStyle  
Appendix A.17. dnpIndexStyle  
Normally the Server responds to requests for data using the same qualifier as the poll. Use this  
parameter on a Server Map Descriptor to override the indexStyle of the qualifier in the response.  
Refer to Section 5.3.6 for an example.  
Supported  
1
2
objects are prefixed with a one byte index  
objects are prefixed with a two byte index  
Unsupported  
3
4
5
6
objects are prefixed with a four byte index  
objects are prefixed with a one byte object size  
objects are prefixed with a two byte object size  
objects are prefixed with a three byte object size  
Others  
Unknown.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 42 of 51  
Appendix A.19. Select and Operate  
As a Client  
The DNP 3.0 Driver Client can send select, operate and direct operate messages to a Server device.  
The commands can be sent to Analog Output Blocks, Relay Control Blocks and Pattern Control  
Blocks. The responses from these commands contain status information on whether the command  
was accepted or rejected. The driver can store this status information so that is it available to another  
protocol.  
When using these commands it is important to remember that the driver is not a DNP 3.0 device and  
is only capable of transferring data from one protocol to another. The driver does not understand the  
context of these commands. For example, the driver can send the select command but will not  
resend the command if an operate command failed because the select arm timer had expired.  
Another example, is when you send an operate command to a control relay, the driver sends the  
relay a block of data that is extracted from a Data Array. It is the content of this block that tells the  
relay what to do. Because the driver doesn’t understand the command but simply sends a block of  
data it is necessary to ensure the block of data has been formatted correctly.  
The driver does not check the echoed data objects contained in the response. The DNP 3.0  
specification requires that a DNP 3.0 device should.  
Analog Output Block  
Depending on the variation selected the driver sends a 16 or 32 bit signed value with a status byte  
(Status byte sent is always equal to zero).  
If the active Map Descriptor used to send a select or operate command has the DA_Float_Name  
parameter specified with the name of a Data Array then the driver stores the status byte extracted  
from the response message in this secondary Data Array at the same offset specified with the  
“Data_Array_Offset” parameter.  
Control Relay Block (Object=12)  
The following 5 fields are sent with the command to operate such an object:  
Field  
Description  
Control  
Code  
This field indicates the control function to perform. The applicability of this code will  
depend on the type of hardware used in the end device.  
This field indicates the number of times that the control operation should be performed  
in succession.  
Count  
This field specifies the amount of time the digital output is to be turned on (may not  
apply to all control types).  
This field specifies the amount of time the digital output is to be turned off (may not  
apply to all control types).  
On-time  
Off-time  
Status  
Byte  
This is always sent with a value of zero.  
By default the driver grabs one item from the Data Array specified on the Map Descriptor. It uses this  
value for the control code, sets the count field to 1 and sets the time and status fields to zero.  
If the “dnpSubType” is specified with a value of “Combo” then the driver will extract 4 consecutive  
values from the Data Array specified on the Map Descriptor. These values are used to complete the  
‘Control Code’, ‘Count’, ‘On-Time’ and ‘Off-Time’ fields in the message.  
If the active Map Descriptor used to send a select or operate command has the “DA_Float_Name”  
parameter specified with the Name of a Data Array then the driver stores the status byte extracted  
from the response message in this secondary Data Array at the same offset specified with  
“Data_Array_Offset” parameter. If the “DA_Bit_Name” parameter is specified then the driver stores  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 43 of 51  
the control code extracted from the response and if the “DA_Byte_Name” is specified then the driver  
stores the count field extracted from the response.  
Pattern Control Block  
Object 12 variations 2 & 3 are not supported by the driver.  
As a Server  
The DNP 3.0Driver Server can accept and process Select and Operate commands sent by a remote  
Client with limitations as discussed in the notes below.  
The commands can be sent to Analog Output Blocks, Relay Control Blocks and Pattern Control  
Blocks. The driver executes or rejects the commands on these data objects, returning a response  
which contains an echo of the poll with the status byte of each data object modified to report the  
success or failure.  
The driver is intended to transfer data from one protocol to another. The driver does not make the  
FieldServer behave like a typical DNP 3.0 device such as a protective relay. For these reasons the  
driver cannot implement all the actions implied by the Select and Operate commands. For example:  
The driver cannot queue commands. The driver cannot use the on and off time fields. The driver  
only understands the ‘Latch On and “Latch Off’ command codes. The driver cannot understand the  
attribute bits of the control code field such as the clear and reset attribute flags.  
All Commands  
When one of the select, operate and direct operate commands are received, the driver sends a  
response which contains internal indication status bytes as well as en echo of the data objects being  
commanded. Each data object that can be commanded with one of the commands has a status byte  
field trailing the block of data sent with the object. The Server modifies the status byte that is echoed  
back.  
The driver sends 1 of 4 possible status byte responses.  
0
2
4
6
Command Accepted  
Command rejected because object was not previously selected.  
Command rejected because the command code is not supported by the driver.  
Command Rejected, Hardware problem. The driver sends this response when the driver is not  
able to process the command correctly. It does not mean that the FieldServer hardware is  
malfunctioning.  
Select Command  
This command is used to select data objects for an ‘Operate’ Command. If possible the driver marks  
the data objects as selected when the select command is received. If not possible, the driver  
assumes the objects are selected at all times. Many DNP 3.0 devices implement an ‘Arm’ timer that  
clears the select flag when it times out. This driver does not implement this timer but relies on a  
remote device using another protocol to implement the ‘Arm’ timer if it so requires. The remote  
device can clear the select flag by writing a zero to the Data Array element at any time.  
If the Server Map Descriptor used to define the Server data object to be selected/operated has the  
“DA_Bit_Name” parameter specified, the driver uses this Data Array location to set the select flag by  
setting the value to ‘1’. If the secondary Data Array is not specified then the select command is  
accepted and the point is considered to be permanently selected.  
The driver sends responses with the status byte modified to report the success/failure of the  
command.  
Operate Command  
Once selected, data objects can be operated. If the secondary Data Array is specified using the  
“DA_Bit_Name” parameter, the driver looks in the Data Array and if the value is non-zero the point is  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 44 of 51  
considered to be selected and the operation can proceed. If the value is zero, the driver rejects the  
command. If the secondary Data Array is not specified, the port is considered to be permanently  
selected.  
The driver supports the following Control Codes  
Code Operation Supported  
0
Null  
No  
1
2
3
4
Pulse On  
Pulse Off  
Latch On  
Latch Off  
No  
No  
Yes  
Yes  
5-15  
Undefined N/A  
‘Direct Operate’ and ‘Direct Operate with No Acknowledgement’ Commands  
The driver does not check if the data object had previously been selected. The supported Control  
Codes are described above.  
Analog Output Block  
When a ‘Select’ command is received the driver sets the select flag in a secondary Data Array  
defined by the “DA_Bit_Name” parameter, if available. When any of the operate commands are  
received the driver stores the value sent with the command in the Data Array defined on the Map  
Descriptor.  
Control Relay Block (Object=12)  
If the Control Code is supported the driver does the required action.  
The driver supports the following Control Codes  
Code Operation Supported  
0
Null  
Not Supported  
1
2
3
4
Pulse On  
Pulse Off  
Latch On  
Latch Off  
Not Supported  
Not Supported  
Driver sets Data Array value to ‘1’  
Driver sets Data Array value to ‘0’  
5-15  
Undefined N/A  
If the “DA_Bit_Name” parameter is specified then the driver stores the control code as extracted from  
the command and if the “DA_Byte_Name” is specified then the driver stores the count field, extracted  
from the command message.  
Pattern Control Block  
Object 12 variations 2 & 3 are not supported by the driver.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Page 46 of 51  
Appendix B. Driver Error Messages  
Error Message  
Explanation  
DNP:#1 Err. Unknown object=%d  
variation=%d for resp.  
DNP:#2 Err. Unknown object=%d  
variation=%d for store.  
DNP:#3 FYI. No nodes to  
process.  
The driver is polling for or responding to a poll for a data object and  
variation that is not supported. See Appendix A.9 for a table of  
supported objects.  
No DNP 3.0 nodes have been defined in the configuration. The  
configuration file is probably invalid. 6.  
DNP:#4 Err. Link Reset node %d  
failed. (Send a Link Reset Rqst  
before polling.)  
A Client must send a ‘Link Reset Request’ message to this driver  
before it can respond to a poll.  
Many DNP 3.0 Servers time out the link and the connection must  
be reestablished with a ‘Reset Link Rqst’ message. This driver  
doesn’t do this. This message is printed when the link has timed out  
and a poll is received. The message indicates that this behavior is  
ok.  
DNP:#5 FYI. Slave=%d happy  
with link. No reset Rqst.  
DNP:#6 FYI. Node=%d requires a A Client must send a ‘Link Reset Request’ message to this driver  
reset before it can respond. before it can respond to a poll.  
DNP:#7. Err. Too many polls with When the driver receives too many polls without a link reset request  
no reset request.  
then this message is printed and the driver panics.  
The driver cannot reset the link for the node reported in the  
message because the node number is too large. Change the Client  
to poll for a smaller node number.6  
DNP:#8 Err. Cant reset node=%d  
(Max=%d)  
DNP:#9 Err. Unknown  
dnpSubType=<%s>  
DNP:#11 FYI. Master Node  
Address=%d  
Valid values are provided in Appendix A.3. The driver uses ‘value’  
as default if the keyword is not recognized.  
The driver is reporting the Node_ID of the Client node. This  
message is for information only.  
DNP:#12 FYI. DEBUG Message  
being sent.  
You should never see this message. Check the configuration file for  
an illegal DNPDatatype.6  
This message is for information only. When writing to a DNP  
device the message contains a function code which may be  
overwritten by specifying the DNPfunction in the CSV file. When  
DNPfunction has not been specified, the default function is used  
and this message is printed. When writing to a relay output the  
driver uses function code=5 (Direct act with no ack). When writing  
to a Counter the driver uses function code=8 (Immed freeze with no  
ack).  
DNP:#13 FYI. Write function  
overwritten. MD=<%s>  
DNP:#14 FYI. Length truncated to When using DNP qualifier 17, the maximum value for Map  
255 for MD=<%s>  
Descriptor Length is 255. The driver has truncated the request 6  
The qualifier is invalid. Appendix A.11 has a list of valid Qualifiers.6  
DNP:#15a Err. Cant understand  
index portion of qualifier.  
Qual=0x%02x for MD=<%s>  
DNP:#16 Err. Previous Poll not An attempt was made to start a new poll before the previous one  
completed  
completed. A poll might consist of multiple transactions of multiple  
fragments and therefore could take several seconds. Take a log  
and send with the problem description and the configuration file to  
FST Tech support.  
DNP:#17. Err. Previous Write not  
completed  
DNP:#18 FYI. Cmd completed but  
no (event) data to store.  
DNP:#18 FYI. Cmd completed but  
no (diag) data to store.  
These messages are printed when the polls for data return with no  
data. This can be normal if there are no events/ diagnostic data in  
the remote device. This message is for information only.  
6 Edit the CSV file, download to the FieldServer and reset the FieldServer.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Error Message  
Page 47 of 51  
Explanation  
DNP:#20 FYI. Node Indicates that This message is for information only. It is printed when a remote  
Event Buffers Have Overflowed.  
DNP:#21 FYI. Length=%d invalid.  
Setting to %d.  
device reports that its event buffers have overflowed.  
DNP:#23 FYI. Store rqsted but no A poll for data contained a response with no data. This can be  
Data. valid, e.g. you request Change Data and there isn’t any.  
DNP:#25 FYI. Slave Cant use You cannot use a qualifier of 6 when configuring a Server. See  
Qual=6. for Md=<%s>  
Appendix A.11 for a list of valid qualifiers. 7  
DNP:#27 Err. Slave: Too many  
bytes=%s to send. Reduce  
message length  
Change the Map Descriptor length so that the message contains  
fewer data bytes. 7  
The driver does not support this qualifier when processing response  
from a remote DNP device. Configure the device to use a different  
qualifier.7  
DNP:#29 Err. Cant process this  
qualifier (%d)  
DNP:#30 FYI. Data to store but A message has been received from a remote DNP device but the  
no mapDesc found. driver has not been configured to store this data.  
DNP:#31 Resp. data contained Some responses (Class Data) contain multiple data types. The  
obj=%d vari=%d. MD rqd for driver could not find a Map Descriptor to store some of the data.  
storage.  
Refer to Section 4.4.7 to correct the problem. 7  
The driver can only store data from messages where the data  
elements are indexed in a supported style. Take a log and send  
with your configuration file to FST Tech Support.  
DNP:#32 Err. Cant store for index  
style %d  
DNP:#33 Err. Qty items + array  
offset > end array. md=<%s>  
Cant store all. qty/max= %d/%d  
DNP:#35 Err. Relay Output.  
Status data array too short.  
DNP:#36 Err. Relay Output.  
Status data array too short.  
DNP:#37 Err. Relay Output.  
Bridge cant implement action  
code  
You need to make the data array longer (and/or the length of the  
Map Descriptor.) 7  
The Data Array designated with e DA_Byte_Name parameter in the  
CSV file is too short. 7  
The driver only supports ‘Latch On’ and ‘Latch Off’ and Relay  
output actions. Reconfigure the remote device to use a different  
relay action.  
DNP:#38 Err. Storage Method  
Unknown. (%d)  
Take a log and send the log and configuration file to FST Tech  
Support.  
DNP:#40 Err. Abandoned data  
store. Too many data object  
types.  
The DNP 3.0 driver can process a max of 20 different data objects  
when storing class data. Reconfigure the remote device for fewer  
data objects in the class requested.  
DNP:#41 Err. MD=<dnp-ii> is too  
short. Rqd=%d  
8
DNP:#41 Err. MD=<dnp-stats> is  
too short. Rqd=%d  
DNP:#42 FYI. You could have  
used a MD called <dnp-ii> to  
expose diagnostic info.  
Error! Reference source not found. and 0 contain additional  
information.  
DNP:#42 FYI. You could have  
used a MD called <dnp-stats> to  
expose diagnostic info.  
DNP:#43a Err. Diagnostic #3. Call If any variation of MSG #43 is printed, take a log and call Tech  
Support.  
support.  
The configuration file has suppressed the requirement for link reset.  
If this corresponds to your expectation then you can safely ignore  
this message, If not, see Appendix A.15  
DNP3:#44 FYI. Link Reset  
Suppressed. Port=%d  
7 Edit the CSV file, download to the FieldServer and reset the FieldServer.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Error Message  
Page 48 of 51  
Explanation  
If the destination address is 0xFFFF (=65535) then this message is  
printed. The address 0xFFFF is the broadcast address and the  
driver cannot process broadcasts. Configure the node which sent  
the broadcast message to send a specific message to the  
FieldServer. 8  
We have also seen that this message gets printed when the  
‘System_Station_Address’ has not been specified. Appendix A.12  
has more information.  
DNP:#45 Err. Dest  
Address=%d=Broadcast  
Address." , dest_station  
DNP:#45 Err. Perhaps the  
System_Station_Address has not  
been specified."  
A message was received by the Server side for a Node that has not  
been defined (as a DNP node).  
DNP:#46 Err. Server received a  
poll for unknown node=%d  
Either this message wasn’t intended for the FieldServer or the  
configuration requires review. You may need to add a new Server  
side node and Server side Map Descriptors to solve this problem.  
The driver cannot process the function code indicated when the  
message comes from a responder. If this message occurs rarely  
then assume it is the result of an occasional corrupt message. If  
you are concerned or if it occurs frequently then take a log and  
contact Tech Support.  
DNP:#49 Err. Cant process  
func=0x%x from a responder  
DNP:#50 Err. Cant process  
func=0x%x from an initiator  
DNP:#51 Err. Node_ID=%d Valid  
Range=0-65535  
Illegal Node_ID used. The Node ID refers to the DNP 3.0 Station  
Address. Refer to sections 4.3 and 5.2.  
The message reports that the driver has been set to a mode where  
DNP3:#52a FYI. OriginalStyle DA it will use the DA offsetting style present in the driver prior to  
offset use.  
version 1.02a. If this is consistent with your configuration, the  
message may be ignored.  
A response to a poll contained no data. This is possible when, for  
DNP3:#53 FYI. Mast App Parse - example, you poll for event or change data and no events/changes  
NO DATA, returning early  
have occurred since the last poll. This message is printed for  
information purposes only  
DNP3:#53b FYI. Class Rqst  
returned no data.  
As per #53 but pertains exclusively to polls for class data.  
A message was received by the Server side and the application  
layer function code isn’t supported by this driver. You could  
reconfigure the Client not to send this message,  
DNP:#54 Err. App Layer  
Func=%#x not recognized.  
When you create MD’s to serve Class Data the dnpAssoc field must  
have non-zero values. More information is provided in section  
5.3.58  
DNP:#55 Err. To serve class data  
set the DNPAssoc value non-zero  
To serve Class data you need a Map Descriptor matching the class  
data request and a number of associated Map Descriptors to tell  
the driver what data forms part of the class data set. More  
information is provided in section 5.3.58  
DNP:#56 Err. No MDs associated  
with the class MD=%s  
DNP:#57 FYI. You could have  
used a MD called <dnp-stats> to  
expose diagnostic info.  
Error! Reference source not found. and 0 contain additional  
information.  
The driver found that a response message was addressed to a  
node different from the polling node. Take a log and report to Tech  
support.  
DNP3:#58 Err. Response  
Dest=%d != Master=%d  
The response message originated from a node different to the  
polled node. If the Node_ID reported is not in the list of nodes in  
your configuration, take a log and report the problem to Tech  
Support. If this message is printed rarely, it may have resulted from  
an occasional corrupt message.  
DNP3:#59 Err. Response  
Unknown Src_Id=%d  
8 Edit the CSV file, download to the FieldServer and reset the FieldServer.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Error Message  
Page 49 of 51  
Explanation  
Some DNP messages contain too much data to be sent in one  
message. Such messages are split into multiple frames and  
reassembled on the receiving side. Each frame has a sequence  
number. If frames are received out of sequence this message is  
printed. Typically, once one frame is found out of sequence the  
remaining frames may be flagged as errors too. A consequence of  
this message is the loss of the complete message. If this message  
is printed rarely, you could assume that it is a consequence of  
occasional corruption. If it is printed often then take a log and call  
Tech support.  
DNP3:#60 Msg Frame  
abandoned. Frames out of seq.  
Exp=%d Rcvd=%d. TP=%#d  
When the DNPfunction parameter is omitted on a Map Descriptor  
used to read data the driver assumes that the intended  
DNPfunction is ‘read’. However in some case the driver knows that  
for certain Objects the function must be changed and does this  
automatically. This message gives a heads. No action is required  
from you.  
DNP3:#61 FYI. Read func  
changed Now=%s. MD=<%s>  
The Server side of the driver can only process messages which poll  
DNP3:#62 Err. Rejected msg with for one class of data at a time. Re-configure your Client and try  
multiple polls.  
again. This message is obsolete. Only driver version 1.03i and  
older produce the message. Read Appendix A.20 for more info.  
To serve class data the parameter dnpAssociate must be specified  
on all associated Map Descriptors and the value of the parameter  
must be non-zero.9  
DNP3:#64 Err. To serve class  
data set the DNPAssoc value  
non-zero  
DNP3:#65 Err. There are no MD  
associated with the class MD=%s  
Refer to Section 5.3.5. 9  
DNP3:#63a Err. Cant open %s for If any of these messages are printed call tech support. An internal  
poll from log  
DNP3:#63b Err. Cant read 1st  
line of %s  
diagnostic specific to QA testing has been activated. It is possible  
for the driver to send a message that is found in a log file instead of  
the configured poll to test the Server side of the driver. Script S4085  
provides an example. The Client side MD name must have '.log in  
the name and the driver opens that file and sends the 1st line (only)  
as a single message. The line is expected to have hex bytes  
delimited by space or square brackets.  
DNP3:#63c FYI. Sending  
message from log file=%s  
The Server side of the driver does not support the indicated  
index_style. Refer to Appendix A.17. Reconfigure your Client to  
use a different qualifier and try again9  
DNP3:#66 Err. Index Style=%d  
not supported.  
This message confirms that the Server has been configured to  
serve ‘changed’ data only. Thus, only data whose value has  
changed by some dead band since the last poll for class data will  
be served. You can safely ignore this message if it confirms your  
expectations. If not then review your configuration.  
DNP3:#67 FYI Serve 'changed'  
data only. Class=%d  
When the Server serves class data and when configured to serve  
only ‘changed’ data then the Server may change the qualifier of the  
response from the default or configured qualifier because the points  
being served in the response may not be sequential. You may  
ignore this message as it does not report an error. It is printed to  
draw your attention to the fact that the master should be configured  
to receive a response that uses a different qualifier.  
DNP3:#68 FYI. Class Data  
Served with Qualifier=%#x  
Each time that the Server sets the internal indication bit to signal  
the master station that a time update is required this message is  
printed. You can safely ignore it if it confirms your expectations.  
Refer to Appendix A.18.  
DNP3:#69 FYI. Server signals  
Client=%d to time synch  
9 Edit the CSV file, download to the FieldServer and reset the FieldServer.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Error Message  
Page 50 of 51  
Explanation  
The Server has been configured to serve ‘changed’ data only. In  
reviewing the data, the driver could not find the dead band needed  
to make a decision about whether the data has changed or not.  
Refer to Section 5.3.10 for an example showing configuration  
requirements. 10  
DNP3:#70 Err No COV  
DeadBand for DA=%s Off=%d  
Each time that the Server sets bit 4 of byte 1 of the internal  
indication field in the response message the Client driver will print  
this message. It alerts you to the fact that the Server device  
expects to be sent the time and to have the master reset the flag.  
Refer to Appendix A.18 for more information on how to configure  
the master to respond to this request. If you don’t care about the  
Server’s time then ignore this message without consequence.  
The driver attempted to auto-create a Map Descriptor to send the  
time to a Server device that has requested a Real Time Clock  
"DNP3:#71 FYI. Client observes:  
Server rqsts time synch  
DNP3:#72 Err. Heading not equal Update. The attempt failed and the time was not sent. To resolve  
to keywords  
this error refer to Appendix A.18 and review your configuration. If  
you cannot see a problem, capture a log and send the log with the  
configuration to FieldServer Tech Support.  
You can safely ignore this message. It confirms that the Client side  
DNP3:#73 FYI. Time Synch MD of the driver, saw a request for a time update and auto-created a  
Created  
MD to send the time to the Server device. Read Appendix A.19 for  
more information.  
DNP3:#74 Err. Ana Output Blk.  
No Operate because no select.  
Obj=%d"  
DNP3:#75 FYI. Relay Output. No  
place to store select. Obj=%d"  
DNP3:#76 Err. Relay Output. No  
Operate because no select.  
Obj=%d  
Analog Output Blocks and Relay Blocks must be selected before  
they can be operated. The driver needs a place to store the select  
flag. This is done using a Secondary Data Array specified with the  
DA_Bit_Name parameter. If not specified then the point is  
assumed to be selected all the time. Errors #75 and #77 can safely  
be ignored. If a point has secondary storage defined to store the  
select flag then the driver checks the select flag has been set when  
an operate command has been received. If not set then the  
message #74 or #76 is printed. These errors can be avoided by  
having the remote master send a select command first. Refer to  
Appendix A.19 for more information.  
DNP3:#77 FYI. Ana Output Blk.  
No place to store select. Obj=%d"  
The configuration contains the Node parameter ‘Server_II_Array’  
but when the driver looked for the Data Array specified it could not  
find it. The Data Array must be defined before this parameter is  
used. If the Data Array cannot be found then the driver responds  
as if it had not been specified at all.  
DNP3:#78 Err. Node_ID=%d II  
Array=%s doesn’t exist.  
The driver prints this message once and then suppresses it. It  
draws your attention to the fact that one or more Server nodes has  
the node parameter ‘Server_II_Array’ specified and that the  
DNP3:#79 FYI. Node=%d Using Internal Indications bytes in the response will not be built by the  
DA=%s for II  
driver but will rather be extracted from two consecutive data array  
elements. Offsets 0 and 1 are always used. If this message is  
consistent with your expectations then ignore it otherwise review  
your configuration  
To auto-create a Map Descriptor to send the time to the Server  
device the driver required the configuration to have a Data Array  
called ‘DNP3_RTC_NODEx’ where x is the Server device station  
address. Refer to Appendix A.18 for more information10  
DNP3:#80 FYI. Time Synch  
requires DA=%s  
10 Edit the CSV file, download to the FieldServer and reset the FieldServer.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  
FS-8700-47 DNP 3.0 Driver Manual  
Error Message  
Page 51 of 51  
Explanation  
The driver does not support message fragment acknowledgements.  
Please configure your client software not to request them. This  
message is printed each time we receive a message with CON flag  
set in the Application control flag.  
DNP3:#85  
acknowledgements  
supported.  
Err.  
Fragment  
not  
"CON  
If set to one (1) in a received message, indicates the  
sending application is expecting a confirmation from the receiving  
application of the reception of the fragment. An application function  
code zero (0) is used in the confirmation message." Extract from  
the DNP3 spec.  
DNP3:#86 Err. Index style=%d is The driver supports qualifiers with an index style of 0, 1 or 2. Index  
not supported. Support 0,1,2. styles 3,4,5,6 are not supported. The only way to work around this  
Reformat your request qualifier.  
is to reconfigure the client software to poll using different qualifiers.  
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com  
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]  

HP Hewlett Packard Hewlett Packard Computer Monitor LA2206X User Manual
Hanns G HG 216DPB User Manual
Gigabyte 7VT600 RZ C User Manual
EVGA 132 LF E653 KR User Manual
Electrolux Air O Convect 6GN User Manual
Dell YKDNM User Manual
Cisco Systems CP7970GRF User Manual
Asus V8170 User Manual
Asus Computer Hardware Z87WS User Manual
Adesso AKB 530UB User Manual