FS-8700-47 - DNP 3.0

Up one level

Text Box: Driver Version: 1.03

FieldServer Driver - Serial

FS-8700-47

DNP 3.0

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

• 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).

Connection Information

Connection type:	RS-485 (RS-232 with converter) (Half-Duplex)
Baud Rates:	All Standard Baud Rates
Data Bits:	7, 8
Stop Bits:	0,1
Parity:	None, Even, Odd
Multidrop Capability	None, RTS/CTS

Devices tested

Device	Tested (FACTORY, SITE)
Schweitzer Engineering Laboratories SEL351A.	FACTORY
Multilin Generator Management Relay	FACTORY
Energyline 5800 IntelliTeam	FACTORY
ASE2000 Test Software	FACTORY
Televent Oasys Scada	SITE

DNP V3.00 DEVICE PROFILE DOCUMENT

Vendor Name : FieldServer Technologies

Device Name : FS-X40 and FS-X20 Series

Highest DNP Level Supported:

For Requests 1

For Responses: 1

Device Function:

þ Master þ Slave

Notable objects, functions and or qualifiers supported in addition to the highest DNP Levels Supported.

Although the highest level implemented is level 1 there are very few functions and objects that have not been implemented that would allow classification as level 2 compliance. These exceptions include some functions on the analog output objects, no processing of the time delay objects, setting internal indications and no handling of object type 101.

In addition to being compliant with most level 2 requirements the FieldServer can parse a greater number of qualifiers than are required for level 2 compliance.

The attached table indicates the objects, object variations, functions and qualifiers that can be processed.

Maximum Data Link Frame Size (Octets)

Transmitted: 242

Received: 292

Maximum Application Fragment Size

Transmitted: 242

Received: 2048

Maximum Data Link Re-Tries

p None

þ Fixed at 3

p Configurable

Maximum Application Layer Retries

þ None

p Fixed

p Configurable

Requires Application Layer Confirmation

þ Never

p Always

p When reporting event data

p When sending multi-fragment responses (Slaves Only)

p Sometime _____________________________________________________

p Configurable ___________________________________________________

Timeouts while waiting for:

Data Link Confirm :

p None p Fixed at ____ p Variable þ Configurable (Use timeout param in CSV file.)

Complete App Fragment:

p None p Fixed at ____ p Variable þ Configurable (Use timeout param in CSV file.)

App Confirm:

p None p Fixed at ____ p Variable þ Configurable (Use timeout param in CSV file.)

Complete App Response:

p None p Fixed at ____ p Variable þ Configurable (Use timeout param in CSV file.)

Sends / Executes Control Operations

Write Binary Outputs:

p Never þ Always p Sometimes þConfigurable (May Over-ride default)

Select/Operate :

þ Never pAlways p Sometimes pConfigurable (May Over-ride default)

Direct Operate:

þ Never pAlways pSometimes pConfigurable (May Over-ride default)

Direct Operate No Ack