FieldServer FS-8700-47 instruction manual DNP 3.0 Driver Description

Page 4

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: support@fieldserver.com

Page 3 Page 5
Image 4
Page 3 Page 5
Contents Driver Manual FS-8700-47 DNP Table of Contents FS-8700-47 DNP 3.0 Driver Manual Table of Contents DNP 3.0 Driver Description Page FS-8700-47 DNP 3.0 Driver Manual Hardware Connections Connection NotesConfiguring the FieldServer as a DNP 3.0 Driver Client Data ArraysClient Side Connection Descriptors Client Side Node DescriptorsDriver Specific Map Descriptor Parameters Timing Parameters Map Descriptor Example 1 Simple Read Map Descriptor Example 3 Simple Read Extract Value & Status Map Descriptor Example 4 Reading Class Data Map Descriptor Example 6 Read an unknown variation Configuring the FieldServer as a DNP 3.0 Driver Server Server Side Connection DescriptorsServer Side Node Descriptors Driver Specific Map Descriptor Parameters Map Descriptor Example 1 Discrete Data Map Descriptor Example 2 Class DataMap Descriptor Example 3 Class Data another example RTUMap Descriptor Example 4 Default Variation Variation zero Map Descriptor Example 5 ClassDataServingCtrl AnaInputs Map Descriptor Example 6 Unsolicited Messages Server Side Limitations Appendix A. Advanced Topics Appendix A.1. DNP 3.0 Protocol Appendix A.2. DNP Driver FunctionalityAppendix A.3. DNP Objects mapped to FieldServer Data Arrays Appendix A.4. Channel Idle, Master & Slave IdleAppendix A.5. DLL Layer Functionality in the Master Appendix A.6. App Layer Functionality in the MasterAppendix A.7. Internal Indications, Object 80 and Dnpii Incoming Internal Indications BytesPage Internal Indications reported in Responses ServerIIArrayResponses to Polls for Object 80 Internal Indications Appendix A.8. DNPStats DnpstatsAppendix A.9. DNP 3.0 Data Objects Counter Change Event All Variations See notes in Appendix A.10 for function code FS-8700-47 DNP 3.0 Driver Manual Appendix A.11. Controlling the DNP 3.0 Driver’s Qualifier Appendix A.12. FieldServer DNP Node NumberAppendix A.13. DnpSubType Appendix A.15. Link ResetAppendix A.14. Communication Stats Appendix A.16. Controlling DA Offsets Appendix A.17. dnpIndexStyleAppendix A.18. Real Time Clock Synchronization DatimePage Appendix A.19. Select and Operate Page Page Appendix A.20. Multiple requests in a single poll Appendix B. Driver Error Messages Page Page Page FYI
Top Page Image Contents