Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

DNP V3.00 and IEC 60870-5-101 IMPLEMENTATIONS IN INTELLIGENT ELECTRICAL DEVICES (IEDs)
OSullivan Neil; Mikli, Lauri. NU-LEC PTY LTD

1. Summary
This paper looks at a manufacturers slave implementation of both DNP V3.00 and IEC60870-5-101 communications protocol in intelligent electrical devices (IEDs) and makes a comparison of the advantages and disadvantages from the perspective of this manufacturer.

2.Introduction
Rationalisation and privatisation in the global electrical distribution industry is forcing utilities to consider new ways to optimise their business from both a performance and cost perspective. Utilities are increasingly required to meet the performance criteria set by the regulators of these newly privatised companies. This is making remote control and automation of their distribution networks a real necessity if they are to meet these requirements. Distribution utility regulators are tending to apply several benchmarked criteria and performance indicators on electricity distribution utilities. These performance criteria directly reflect how profitable a utility is and also form the basis for their regulation. This manufacturer recognised this trend almost a decade ago and began developing a range of pole mounted Intelligent Electronic Devices (IEDs) with a range of features and functionality designed to help the modern electricity utility meet these criteria. This paper discusses the two main open architecture protocols to emerge from the proprietary communications era. Of these two, DNP was largely influenced by North and South America, together with the African and Asian regions, while 60870-5-101 has been heavily influenced by the European community. Both of these protocols are specified, developed and controlled by regulatory committees to ensure they allow Page 1 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

inter-operability between different implementors equipment. These regulatory groups are the DNP V3.00 User Group and International Electrotechnical Commission (IEC) 60870-5 Technical Committee 57 Working Group 03.

3.Reporting Model
Whilst this paper looks at slave implementations of these protocols it is important to choose the protocol network topology which best supports the electricity utilitys needs. Points to consider are the communications medium, network topology and whether continuous polling or report by exception / unsolicited reporting is required. One example of this is a situation where a utility wants to control and monitor their entire population of IEDs but dont have the necessary bandwidth or VHF/UHF radio coverage to use continuous polling under all system conditions. To get around this limitation they may want to utilise a combination cellular, satellite or dialup landline to communicate with remote IEDs. At present the best solution would be to use DNPs balanced transmission, report by exception communications. 60870-5-101 does support balanced transmission, report by exception communications but it is limited to point to point communications only. It would not be suitable for the above multi-drop, multiple communications media situations.

Page 2 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

4.Protocol Architecture
Both DNP and 60870-5-101 use a simplified 3 layer version of the Open System Interconnection (OSI) 7 layer reference model known as the Enhanced Performance Architecture (EPA). It is important to know this basic design in order to understand the various terminology and principles involved with using either protocol.

Layer 7 6 5 4 3 2 1 Application Presentation Session Transport Network Link Physical OSI Reference Model 4.1 Physical Layer <=> <=> Link Physical Enhanced Architecture Model Performance (DNP Transport) <=> Application

The physical layer refers to the physical media over which the protocol is transmitted. This is usually a physical medium such as RS-232, RS-485 or V23 FSK using media such as fibre, radio or satellite. Examples of its functions are handling the state of the media (eg collision detection) and transmission controls (eg RTS/CTS) to ensure synchronisation successful transfer of data. Currently both protocols are in the process of developing standards of behaviour for each protocol on networks such as Ethernet.

Page 3 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

4.2

Link Layer

The link layer provides a logical link between the sender and receiver of data. It also provides mechanisms to determine and overcome, physical layer error characteristics such as noise. The 60870-5-1 standard defines four different frame types for the link layer. Both protocols make use of one of these. 60870-5-1 Frame Type Hamming Distance (error bits) IEC60870-5-101 DNP V3.00 FT1.2 FT3 4 6 8 bit checksum 16 bit CRC Security Maximum Length (bytes) 255 255

As can be seen in the table above, both protocols transmit identical maximum length messages but the DNP protocol has a higher hamming distance. This means that with DNP two more single bit errors must occur than in 60870-5-101 before a corrupted message will be mistakenly identified as a healthy message. The frame type determines the link level functions and characteristics available for each protocol: Message start and end identification bytes Destination and Source Addressing (up to 65534 addresses for DNP and a varying address field size for IEC which allows for up to 16777215 addresses). Message Length Information Error detection using Cyclic Redundancy Checking (CRC) and Checksums Link services. These include message handling abilities such as: 1. Reset link 2. Reset user application 3. Link level Send/Confirm service 4. Link Status Requests

Page 4 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

4.3

DNP Pseudo-Transport Layer

The DNP protocol varies from the EPA 3 layer model by adding a fourth layer - a pseudo-transport layer. The pseudo-transport layer segments application layer messages into multiple link messages and provides a segment tracking mechanism. 60870-5-101 limits the size of its application layer messages to that of the link layer (255 bytes) and hence does not require transport layer fragmentation. 4.4 Application Layer

The application layer builds messages based on the need for, or the availability of, user data. Once messages are built, they are passed down to the data link layer and eventually communicated over the physical layer. The application layer uses function codes to indicate the purpose, or requested operation, of the message. The functions include: Reporting - Polled report by exception, Unsolicited Responses Time Synchronisation Read/Write message identification Digital Control Commands eg Select before Operate, Direct Operate Freeze and Clear commands for counters Time-stamped events Data Groups/classes

5. DNP V3.00 Subset Levels

The DNP protocol was designed as a generic SCADA data protocol and by its nature therefore contains a very large suite of data object types. Historically it was possible for both a master vendor and an IED vendor to claim support for the DNP protocol without the devices being able to fully communicate with one another. For example, one implementation might process analogs using one type of DNP analog object format, which is specifically applicable to its implementation, while the other device may be using another analog format. No data transfer is possible despite both devices using valid DNP data formats. To combat this problem, and preserve the open standards philosophy, the DNP User Group defined three levels of implementation Page 5 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

that established a minimum set of behavioural rules and data objects types supported by a device. The size and nature of the device determines the appropriate level that should be supported by the vendor. 60870-5-101 does not have any predefined subsets. It relies solely on interoperability tables that we will explain later. 5.1 Level 1 This is the simplest implementation of DNP. It is intended for use between a master station or data concentrator and a small end device (eg. Meter, relay or capacitor bank controller). The input and output points of the slave devices are typically local to the device. 5.2 Level 2 This level of implementation defines a slightly larger subset of DNP features than the Level 1 implementation. It is intended to be used between a master station or data concentrator and either a large IED or a small Remote Terminal Unit (RTU). Like level 1 implementations, the input and output points of the slave device would be local to the device. The functionality available in the Nu-Lec Optimised Family of products require Level 2 functionality. 5.3 Level 3 This level of implementation is the largest subset of DNP. It does not cover all DNP features but does contain the majority of useful, popular items. It is intended for use between a master and a medium size slave device (e.g. RTU, Data Concentrator). There are not yet many slaves with full level 3 compliance in the market place. The input and output points in level 3 implementations are both local and remote. Remote points are usually obtained via serial links to external devices.

6. IEC 60870-5-101 and its companion standards.

From these writers perspective, there appears to be much confusion in relation to IEC companion standards 60870-5-101 and 60870-5-103. We believe some of this

confusion arises because DNP3 is specified in three levels and anyone who Page 6 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

understands DNP naturally assumes 60870-5-101 has a similar set of levels and subset level functionality. This is not the case. The 60870-5-103 companion standard is an extension, not a subset, of the 60870-5-101 standard and is designed for specific use in data interchange between protection equipment and a substation control system. The 60870-5 standard for Transmission Protocols consists of five basic parts (608705-1 to 5) and a set of companion standards (eg 60870-5-101 and 103). The diagram below highlights the roles of each part in defining 60870-5.
User Telecontrol Process Layer IEC 60870-5-101 Basic Telecontrol Tasks IEC 60870-5-5 Basic Application Functions Application Layer IEC 60870-5-4 Definition and Coding of Application Information Elements IEC 60870-5-3 General Structure of Application Data Datalink Layer Physical Layer IEC 60870-5-2 Link Transmission Procedures IEC 60870-5-1 Transmission Frame Format IEC 60870-5-103 Informative Interface of Protection Equipment

EPA Model The 60870-5-101 Companion Standard for Basic Telecontrol Tasks defines a set of data types and services, as detailed in 60870-5-1 to 5, that are suitable for telecontrol systems eg a substation control system. These data types are generic and include data such as single and double binary point statuses and commands, counters, analogs and set-points. The 60870-5-103 Companion Standard for the Informative Interface of Protection Equipment includes more detail than 60870-5-101. It extends the set of data types and services by defining specific data types formats and communication behaviour for distance protection, transformer differential protection and line differential protection. These data types can include combined digital and analog data like currents, voltages, fault indications and disturbance data. Page 7 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

7. Device Interoperability
To aid end users with the integration of devices, and early identification of problems such as the one outlined in the DNP subset section, both protocols have incorporated detailed compliance tables in their standards. These tables provide a standard format for easy checking of the functions and data types supported by an implementation. The DNP protocol breaks down its compliance tables into two parts. The Device Profile document defines compliance with various application and link layer issues such as implementation level and deviations from the basic level criteria. The Implementation Table defines the data objects and message types supported by the device. An example of a Level 2 DNP V3.00 Device Profile for the Nu-lec N Series Recloser is located in Appendix A. Its companion implementation table is given in Appendix B. The 60870-5-101 refers to its compliance tables as its Interoperability Statement. It contains information about the devices support of all EPA layers. This information includes data such as supported network configuration, transmission details, link transmission procedure, and implemented data objects. An example of an 60870 Interoperability Statement for the Nu-lec N Series Recloser is given in Appendix C.

8. Protocol Compliance Testing

7.1 DNP Testing It is our opinion that one of DNP communications protocols strengths are the very detailed compliance certification test procedures produced and maintained, by the DNP V3.00 user group. These are currently available for slave implementation levels 1 and 2. From an end users perspective, this allows them to specify a DNP V3.00 Level 1 or 2 (at this time) implementation that has been fully compliance tested to the DNP V3.00 user groups certified compliance test procedures. They can be sure these implementations have been tested and certified by a third party and will interface correctly to DNP master implementations that meet the DNP master standards. It should be noted that the certification of a device only proves it is protocol compliant. Page 8 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

It does not certify operation of the device nor does it certify the point list of the device. The test procedures cover the following areas in brief: 1.Pretest Review 2. Link Layer 2.1 Reset Link and Passive Confirm support 2.2 Test Link 2.3 Request Link Status 2.4 Test Retries 3.Transport Layer 3.1 Desired Behaviour 4.Application Layer 4.1 Binary Output Status 4.2 Binary Outputs 4.3 Analog Output Status 4.4 Analog Outputs 4.5 Class Data 4.6 Indications 4.7 Time 4.8 Cold Restart 4.9 Binary Input 4.10 Binary Input Change 4.11 Binary Counters 4.12 Binary Counters, Event 4.13 Analog Input 4.14 Analog Change Event 7.2 60870-5-101 Testing At present testing is a weakness of the 60870-5-101 protocol because there are currently no official certification procedures available. It is expected this situation will change as the protocol becomes more commonly used and adopted by both master station and IED vendors. When this happens a certification testing procedure will become essential. At this time testing is mainly provided by a company called KEMA, located in the Netherlands. It is popularly considered the de-facto acceptable certification body although there are others. The best way for a user to ensure a specific slave manufacturers 60870-5-101 implementation is acceptable, is to compliance test it with their specific master station implementation. This would normally be achieved by using a master station simulator from the master station manufacturer. Page 9 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

9. Comparison Between DNP V3.00 and IEC60870-5-101

This section lists the similarities and differences between the DNP and 60870-5-101 protocols3. 8.1 General The protocols have many similarities in their functionality. Each permits: Collection of binary (digital) data Collection of analogue data Collection, freezing and clearing of counters Single pass or two-pass control of binary (digital) outputs Single pass or two-pass control of analog outputs Reporting of binary and analog events (report by exception) Time synchronisation Time-stamping events Grouping data objects File Transfer

Both protocols permit polling for all data (this is normally done at startup to collect the initial state of the slave), and subsets of data. Both normally operate by only collecting events (changes) from the field.

8.2 Differences DNP does not conform exactly to the frame format specified by the IEC: The DNP frame adds start and stop bits to each octet of the FT3 frame format (using a 16-bit CRC) to allow the use of standard asynchronous data communications equipment. The IEC chose to use the less-secure FT1.2 (which already includes start and stop bits) for 101 so that they would not need to specify a new frame format. DNP only uses balanced link services. 60870-5-101 may use balanced or unbalanced services.

Page 10 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

DNP supports only a single addressing format. 60870-5-101 allows most of the options specified in 60870-5-2. The DNP addressing format supports peer-to-peer operation, the 101 format does not.

DNP introduces a pseudo-transport layer (OSI layer 4) to build application data messages larger than a single data link frame. Each 60870-5-101 message must be contained in a single data link frame.

DNP permits more than one object type to appear in a message. 60870-5-101 only permits a single object type in a message.

DNP requires an application layer message to contain a poll request (or any other command). Polling in 60870-5-101 can be triggered by a link-layer message containing no application data.

60870-5-101 includes a concept of Cause of transmission not included in DNP. This permits a 60870-5-101 device to cause data to become available (pseudoevents) for a larger number of reasons than available to a DNP device.

DNP groups data into four classes. This may be used to prioritise event reporting. One class is for static data: current values of inputs; the other three are for event data: reporting changes. All four classes may be requested simultaneously. IEC groups data into two classes, and while not explicitly stated in the 60870-5101 standard, one class is intended for cyclic data, and the other class is for all other data. Only one class or the other may be requested in a single poll. The device indicates in the link layer which class should be polled for next.

DNP supports unsolicited reporting using a collision-avoidance mechanism for multi-drop systems. 60870-5-101 only permits unsolicited reporting on point-topoint links where collision is impossible.

DNP relies on the data link address to identify the source of the application data. 60870-5-101 uses the data link address to identify where the frame should be delivered, and includes the data addresses within the application data.

Because DNP allows more than one data type in a message, it includes more complex data type and identity information in the application data than 60870-5101. Hence parsing a DNP message is more complex than parsing a 60870-5-101 message. Page 11 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

DNP defines a number of implementation subsets that simplify determining if equipment will interoperate. Each DNP device vendor indicates which DNP objects and functions are supported in a standard-format "Device profile". The intent of this is to maximise the likelihood that devices from different vendors will work together with minimal configuration. 60870-5-101 includes an

interoperability chapter defining how a vendor indicates which objects and options are implemented. There are no defined subsets. This requires careful analysis to ensure that devices will work together or can be configured to work together. DNP is maintained by the technical committee of the DNP User Group. This body provides information about the protocol, and clarifies ambiguous areas of the protocol definition. The IEC does not provide information to clarify the interpretation of its standards. Questions are best addressed to a vendor of a product that supports 60870-5-101.

8. Conclusion
Both DNP V3.00 and IEC 60870-5-101 communications protocols go a long way to solving the interoperability problems common in previous generations of remote control systems. Selecting the correct protocol for your utility depends very much on your SCADA master systems ability to support one or both of these protocols and your network topology. In fact, there would be benefits to ensure both protocols are supported by their Master stations. This would provide the absolute maximum in flexibility of choice when interfacing to IEDs. It is obvious from this paper that the IEC60870-5-101 protocol has still not matured to the same level as DNP V3.00 but this is coming.

Page 12 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

References 1. International Standards Telecontrol equipment and systems Part 5: Transmission Protocols: Section 1 - Transmission Frame Format, Section 2 - Link Transmission Procedures, Section 3 - General Structure of Application Data, Section 4 - Definition and Coding of Application Information Elements, Section 5 - Basic Application Functions, Section 101 - Basic Telecontrol Tasks, Section 103 Informative Interface of Protection Equipment, International Electrotechnical Commission Publication 870-5-101: 1995. 2. DNP V3.00 Basic 4: Data Link Layer, Transport Functions, Application Layer and Application Object Library; Subset Definitions. 3. West. Andrew, C. Triangle Microworks Inc. Communications Standards in Power Control.

Page 13 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

4.

Appendix A DNP V3.00 Device Profile

The DNP V3.00 device profile defines the mapping of all data points used, in the standard format recommended by the DNP users group.

DNP V3.00 Device Profile

DNP V3.00 Device Profile

Vendor Name: Nu-Lec P/L,Brisbane, Australia Device Name: CAPM-4 Controller

Highest DNP Level Supported For Requests: 2 For Responses: 2

Device Function: Slave

Conforms to DNP V3.00 level 2 subset definition requirements with many additional level 3 features built in. These extra features include the parsing of read requests (FC 1) for the following objects and/or qualifiers: Binary Input (Object 1 Variations 0 Qualifiers 00, 01) Binary Input (Object 1 Variation 1 Qualifiers 00, 01, 06) Binary Output (Object 10 Variation 0 Qualifiers 00, 01) Binary Output (Object 10 Variation 2, Qualifiers 00, 01, 06) Binary Counter (Object 20 Variation 6 Qualifiers 00, 01, 06) Frozen Counter (Object 21 Variation 10 Qualifiers 00, 01, 06) Analogue Input (Object 30 Variation 0, Qualifiers 00, 01) Analogue Input (Object 30 Variations 1, 2, 3, 4 Qualifiers 00, 01, 06) Analogue Change Event (Object 32 Variations 1, 2 Qualifiers 06, 07, 08) Analogue Output Status (Object 40 Variation 1, 2 Qualifiers 00, 01) Analogue Output Block (Object 41 Variation 1, 2 Qualifiers 00, 01, 07, 08, 17, 28) Also, the following functions are included: Function codes 7, 8, 9, 10 for Binary Counters (Object 20 Variation 6) Function code 14, Warm Restart Function code 20, Enable Unsolicited Messages Function code 21, Disable Unsolicited Messages Function code 22, Assign Data Classes

Page 14 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

Maximum Data Link Frame Size (octets): Transmitted: 292 Received: 292 Maximum Data Link Retries: Configurable 0..255 Requires Data Link Layer Confirmation:

Maximum Application Fragment Size (octets): Transmitted: 2048 Received: 249 Maximum Application Layer Retries: None

Configurable, 3 settings Never, Always, Sometimes (on multi frame fragments only) Requires Application Layer Confirmation: Sometimes (only when reporting event data or when sending multifragment responses) Timeouts while waiting for: Data Link Confirm: Configurable Application Confirm: Configurable Need Time Delay: Configurable Select Operate Delay: Configurable Unsolicited Response Notification: Configurable Unsolicited Response Retry Delay: Configurable Timeouts not supported: Complete Appl. Fragment: None Complete Appl Response: None Executes Control Operations: WRITE Binary Outputs: Never SELECT/OPERATE: Always DIRECT OPERATE: Always DIRECT OPERATE - NO ACK: Always Pattern control operations are not supported

WRITE Analogue Outputs: SELECT/OPERATE: DIRECT OPERATE: DIRECT OPERATE - NO ACK:

Never Always Always Always

Count > 1: Pulse On: Pulse Off: Latch On: Latch Off: Trip/Close: Raise/Lower: Queue: Clear Queue:

Never Always Never Always Always Sometimes Never Never Never

Pulse On and Pulse Off times are ignored

Maximum Select/Operate Delay Time: Configurable 1 .. 65535 ms Reports Binary Input Change Events when no specific variation requested: Configurable with / without time Sends Unsolicited Responses: Enable/Disable Unsolicited supported Supports Collision Avoidance: Configurable Reports time tagged Binary Input Change Events when no specific variation requested: Binary Input Change with Time Static Data in Unsolicited Responses: Never Collision Avoidance Detection Method: DCD

Page 15 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

Default Counter Object: Default Object: 20 Default Variation: 06

Counter Roll Over at: 65535

Sends Multi-Fragment Responses: Yes

Page 16 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

Appendix B DNP V3.00 Implementation Table for a Nu-Lec N Series Recloser

OBJECT Obj Var Description

REQUEST (slave must parse) Func Codes (dec) 1 1 1 1 1 1 1 1 3, 4, 5, 6 1,7,8,9, 10 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 3, 4, 5, 6 3, 4, 5, 6 22 22 22 22 Qual Codes (hex) 00, 01 06 00, 01, 06 06, 07, 08 06, 07, 08 06, 07, 08 06, 07, 08 00, 01 06 00, 01, 06 17, 28 00, 01 06 00, 01, 06 00, 01 06 00, 01, 06 00, 01 06 00, 01, 06 00, 01, 06 00, 01, 06 00, 01, 06 06, 07, 08 06, 07, 08 06, 07, 08 06, 07, 08 06, 07, 08 00, 01 00, 01, 06 00, 01, 06 00, 01, 07, 08, 17, 28 00, 01, 07, 08, 06

RESPONSE (master must parse) Func Codes

N/A

Qual Codes (hex)

N/A

1 1 2 2 2 2 10 10 12 20 20 21 21 30 30 30 30 30 32 32 32 32 32 40 40 40 41 41

0 1 0 1 2 3 0 2 1 0 6 0 10 0 1 2 3 4 0 1 2 3 4 0 1 2 1 2

Binary Input - All Variations Binary Input Binary Input Change - All Variations Binary Input Change without Time Binary Input Change with Time Binary Input Change with Relative Time Binary Output - All Variations Binary Output Status Control Relay Output Block Binary counter All Variations 16 Bit Binary Counter without flag Frozen Counter All variations 16 Bit Frozen Counter without flag Analogue Input - All Variations 32 Bit Analogue Input 16 Bit Analogue Input 32 Bit Analogue Input without Flag 16 Bit Analogue Input without Flag Analogue Change Event - All Variations 32 Bit Analogue Change Event without Time 16 Bit Analogue Change Event without Time 32 Bit Analogue Change Event with Time 16 Bit Analogue Change Event with Time Analogue Output Status - All Variations 32 Bit Analogue Output Status 16 Bit Analogue Output Status 32 Bit Analogue Output Block 16 Bit Analogue Output Block

129
N/A

00, 01
N/A

129, 130 129, 130

N/A N/A

17, 28 17, 28
N/A N/A

129 129
N/A

00, 01
Echo of request N/A

129
N/A

00, 01
N/A

129
N/A

00, 01
N/A

129 129 129 129

N/A

00, 01 00, 01 00, 01 00, 01

N/A

129, 130 129, 130 129, 130 129, 130

N/A

17, 28 17, 28 17, 28 17, 28

N/A

129 129 129 129

00, 01 00, 01
Echo of request Echo of request

Page 17 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

OBJECT Obj Var Description

REQUEST (slave must parse) Func Codes (dec) Qual Codes (hex) 17, 28 07 (quantity = 1) 07 (quantity = 1)
N/A

RESPONSE (master must parse) Func Codes Qual Codes (hex)

N/A

50

Time and Date

2 1

N/A

129 129
N/A N/A

07, (quantity 1) 07, (quantity 1)

N/A N/A

52 60 60 60 60 80

2 1 2 3 4 1

Time Delay Fine Class 0 Data Class 1 Data Class 2 Data Class 3 Data Internal Indications

N/A

1 1 20,,21, 22 1 20, 21, 22 1 20, 21, 22 2 13 14 23

06 06, 07, 08 06, 07, 08 06, 07, 08 00 index = 7

N/A

N/A

N/A

N/A

N/A

N/A

N/A

No Object Note 1. 2.

N/A

N/A

All shaded areas are the additional level 3 or above function, objects, variations and/or qualifiers supported by CAPM. Bold italics response function codes represent CAPM default objects. These are the object variations that the CAPM will issue as in its response to an event (class 1, 2, 3) or integrity (class 1, 2, 3, 0) poll, or in a response to a variation 0 read request, or in an unsolicited response message. Where more than one data object variation is highlighted then default object can be configured. All Request and Response options marked N/A are not applicable.

3.

DNP Function Codes

Request Function Code 1 2 3 4 5 6 7 8 Description Read Write Select Operate Direct Operate Direct Operate, No Ack Immediate Freeze Immediate Freeze, No Ack Function Code 9 10 13 14 20 21 22 23 Description Freeze and Clear Freeze and Clear, No Ack Cold Restart Warm Restart Enable Unsolicited Msgs Disable Unsolicited Msgs Assign Class Delay Measurement Function Code 129 130 Response Description Response Unsolicited Response

Page 18 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

Appendix C IEC 60870 Interoperability Statement for a Nu-Lec N Series Recloser

Network configuration

Point-to-point Multiple point-to-point

Multipoint-party line
Multipoint-star

Physical layer
Transmission speed (control direction) Unbalanced interchange Unbalanced interchange circuit V.24/V.28 circuit V.24/V.28 Standard Recommended if >1 200 bit/s 100 bit/s 200 bit/s Balanced interchange circuit X.24/X.27 2400 bit/s 4800 bit/s 9600 bit/s 19200 bit/s 38400 bit/s Balanced circuit X.24/X.27 2400 4800 9600 19200 38400 bit/s bit/s bit/s bit/s bit/s 56000 bit/s 64000 bit/s 56000 bit/s 64000 bit/s

1200 bit/s Transmission speed (monitor direction) Unbalanced interchange Unbalanced interchange interchange circuit V.24/V.28 circuit V.24/V.28 Standard Recommended if >1 200 bit/s 100 bit/s 200 bit/s

300 bit/s 600 bit/s

2400 bit/s 4800 bit/s 9600 bit/s

300 bit/s 600 bit/s 1200 bit/s

2400 bit/s 4800 bit/s 9600 bit/s

Link layer
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively in this companion standard. Link transmission procedure Address field of link Balanced transmission Not present (balanced transmission only)

Unbalanced transmission
Frame length
255

One octet Two octets

Structured

Maximum length L (number of octets)

Unstructured

Page 19 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

Application Layer
Transmission mode for application data

Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 870-5-4, is used exclusively in this companion standard.
Common address of ASDU

One octet
One octet

Two octets
structured

Information object address

Two octets
Three octets
Cause of transmission

unstructured

One octet

Two octets (with originator address)

Selection of standard ASDUs

Process information in monitor direction

<1> <2> <3> <4> <5> <6> <7>

:= Single-point information := Single-point information with time tag := Double-point information := Double-point information with time tag := Step position information := Step position information with time tag := Bitstring of 32 bit := Bitstring of 32 bit with time tag := Measured value, normalised value := Measured value, normalised value with time tag := Measured value, scaled value := Measured value, scaled value with time tag := Measured value, short floating point value := Measured value, short floating point value with time tag := Integrated totals := Integrated totals with time tag := Event of protection equipment with time tag := Packed start events of protection equipment with time tag := Packed output circuit information of protection equipment with time tag := Packed single-point information with status change detection := Measured value, normalised value without quality descriptor

M_SP_NA_1 M_SP_TA_1 M_DP_NA_1 M_DP_TA_1 M_ST_NA_1 M_ST_TA_1 M_BO_NA_1 M_BO_TA_1 M_ME_NA_1 M_ME_TA_1 M_ME_NB_1 M_ME_TB_1 M_ME_NC_I M_ME_TC_1 M_IT_NA_1 M_IT_TA_1 M_EP_TA_1 M_EP_TB_1 M_EP_TC_1 M_PS_NA_1 M_ME_ND_1

<8> <9> <10> <11> <12> <13> <14> <15> <16> <17> <18> <19> <20> <21>

Process information in control direction

<45>

:= Single command

C_SC_NA_1

Page 20 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

<46> <47> <48> <49> <50> <51>

:= Double command := Regulating step command := Set point command, normalised value := Set point command, scaled value := Set point command, short floating point value := Bitstring of 32 bit

C_DC_NA_1 C_RC_NA_1 C_SE_NA_1 C_SE_NB_1 C_SE_NC_1 C_BO_NA_1

System information in monitor direction

<70>

:= End of initialisation

M_EI_NA_1

System information in control direction

<100> <101> <102> <103> <104> <105> <106> := Interrogation command := Counter interrogation command := Read command := Clock synchronisation command := Test command := Reset process command := Delay acquisition command
note 1

C_IC_NA_1 C_CI_NA_1 C_RD_NA_1 C_CS_NA_1 C_TS_NB_1 C_RP_NC_1 C_CD_NA_1

Parameter in control direction

<110> <111> <112> <113> := Parameter of measured value, normalised value := Parameter of measured value, scaled value := Parameter of measured value, short floating point value := Parameter activation P_ME_NA_1 P_ME_NB_1 P_ME_NC_1 P_AC_NA_1

File transfer
<120> <121> <122> <123> <124> <125> <126> := File ready := Section ready := Call directory, select file, call file, call section := Last section, last segment := Ack file, ack section := Segment := Directory F_FR_NA_1 F_SR_NA_1 F_SC_NA_1 F_LS_NA_1 F_AF_NA_1 F_SG_NA_1 F_DR_TA_1

Basic application functions

Station initialisation

Remote initialisation
General Interrogation global group 1 group 2 group 3 group 7 group 8 group 9 group 13 group l4 group 15

Page 21 of 21

Nu-lec Pty Ltd

DNP V3.00 and IEC60870-5-101

group 4 group 5 group 6

group 10 group 11 group 12

group 16

Clock synchronisation Clock synchronisation

Command transmission Direct command transmission Select and execute command Direct set point command transmission Select and execute set point command C_SE_ACTTERM used No additional definition

Short pulse duration Long pulse duration Persistent output

Transmission of Integrated totals Counter request Counter freeze without reset Counter freeze with reset Counter reset General request counter Request counter group 1 Request counter group 2 Request counter group 3 Request counter group 4 Parameter loading Threshold value Smoothing factor Low limit for transmission of measured value High limit for transmission of measured value

Parameter activation Act/deact of persistent cyclic or periodic transmission of the addressed object File transfer File transfer in monitor direction File transfer in control direction

Page 22 of 21