NOTE The documentation and/or manuals provided by the IEDs vendors must be read and understood thoroughly prior to configuration.

Similar documents
DNP3 V3.00 DEVICE PROFILE DOCUMENT

Device Profile Document

Campbell Scientific Australia DNP3 DEVICE PROFILE

DNP 3.0 device profile for AQ (5) DNP 3.0 device profile for AQ 200

DNP V3.00 Protocol Assignments

SOFTWARE DOCUMENTATION. DNP3 Configuration / Interoperability Guide for the DATRAN XL4 DNP3 RTU

SOFTWARE DOCUMENTATION. DNP3 Configuration / Interoperability Guide for the DATRAN II excel DNP3 RTU

DNP3 Device Profile. Device Profile Template. Data Dictionary. Release 2.0. January 30, 2001

DNP Points List and Implementation

Protection Terminal REF 54_ Protection Relay REX 521

DNP3 Device Profile Based on DNP XML Schema version Showing both the Device's Capabilities and its Current Configuration

DNP3 Client Configuration

GE MDS, LLC. NETio Series. Protocol Communications Supplement. March 2013 Part No A01, Rev. C

PXM 4/6/8K DNP3 PXM 4/6/8K DNP3 Ethernet Communications User Manual

DNP3 Field Device Profile. for

DAQ Electronics, Inc 262B Old New Brunswick Road, Piscataway, NJ

General Specifications

General Specifications

EVO AT SERIES BATTERY CHARGER AT SERIES BATTERY CHARGER COMMUNICATIONS MANUAL. EVO - Microprocessor Controlled Float Battery Charger JA

SCADA Controlled LOR/ER - DNP3.0 Communications Protocol - TECHNICAL MANUAL ES-SLOR-1

IEC Protocol Interoperability List

DNP 3.0 & Modbus SCADA INTERFACE INSTRUCTIONS FOR 205T BASED SYSTEMS

WebAccess DNP3 Master Ethernet Driver Guide. Advantech WebAccess. - DNP3 Master Ethernet Driver Guide Version: 1.01

A36D/TPSD DNP 3.0 & Modbus SCADA INTERFACE

TOP Server V5 to MicroLogix Using DNP3 Ethernet Driver

DNP3 Device Profile Based on DNP XML Schema version

TOP Server 5 DNP Advanced Operations. Control Relay Output Block Commands

SCADAPack DNP Driver. User and Reference Manual

350 Feeder Management System

DNP Points List and Implementation for the 6802 Vista Control

DNP3 Communication User's manual

Protocol Gateway DNP3.0 Client/Server

Technical Note DNP3 & Control Relay Output Block Command

345 Transformer Protection System

Modbus Remote Communication Protocol for REM 54_. Technical Description

Driver Manual. FS DNP3 Ethernet

Release 2.11 Standard AXE Primary Firmware is not intended for use on any 8521 Controller not licensed as a RTU.

DNP3 Communications Protocol

Release 2.11 Standard AXE Primary Firmware is not intended for use on any 8521 Controller not licensed as a RTU.

Voltage regulator TAPCON 240

DNP Master Serial Driver Help 2010 Kepware Technologies

Tejas V Master Protocol

Setting the DCM Switches

DirectNET Host. Communications Programs. In This Chapter...

REL 512 Connectivity With A Harris Westronics RTU Using DNP 3.0

A DNP3 Protocol Primer

The Multilin DGCV Voltage Regulator Controller

DNP3 Master Serial Driver PTC Inc. All Rights Reserved.

ECE 444/544 Supervisory Control & Critical Infrastructures Lectures 20 & & 28 March 2018

The DNP3 plugin PRINTED MANUAL

PM296/RPM096 POWER QUALITY ANALYZERS. Application Note: DNP Setup Using PAS V Report by Exception. BB0127 Rev. A1

CURRENT PROTECTION RELAY SMPR-1

DNP Master Ethernet Driver Help Kepware Technologies

IntelliCAP PLUS Supplement for Landis & Gyr Telegyr 8979 Protocol

DNP3 INTEGRATION KIT FOR PAC CONTROL USER S GUIDE

FLITE 395-GPRS-DNP3. DNP 3.0 communication Appendix to the User Manual. Easergy range. MV electrical network management

DNP3 SPECIFICATION DEVICE PROFILE

DNP3 SPECIFICATION DEVICE PROFILE

MVI46-MCM SLC Platform Modbus Interface Module USER MANUAL. February 5, 2004

Lufkin Modbus Serial Driver Help Kepware Technologies

Chapter 6: DNP Introduction. 6.2 Features of the DNP The OSI/ISO model. 6.3 Basic topology

DNP3 Device Profile Document For ARE-M Series Float Chargers Single-Phase Input

Communication 7. What's in this Chapter? This chapter contains the following sections:

750/760 COMMUNICATIONS GUIDE. Digital Energy Multilin. Feeder Management Relay

MODBUS Protocol for MiCOM P30 Series

Mapping Industrial Control Systems

1. System Topology Required Equipment and Components Hardware Equipment Software Equipment... 6

Kepware Technologies Differences Between 4x and 5x for DNP Drivers

MGate 5109 User s Manual

5800 Series Non-IntelliTEAM Universal Automatic Switch Control PG&E SCADA Points List

Protocol Gateway IEC Master/Slave IEC Client/Server

Advantage CT/LTC Protocol Manual

InstrumentationTools.com

FieldServer FS DNP 3.0 Ethernet

InfraSuite Device Master

ASE2000 Version 2 DNP3 Outstation Certification Tests Document Version 1.2 July 19, 2011

DNP Master Serial Driver Help Kepware Technologies

Mitsubishi FX Net Driver PTC Inc. All Rights Reserved.

TRAINING GUIDE LEVEL 3 MODBUS WRITE IMPORT COMMAND

How Can I. Integrate a Third-Party DNP3 Device? System Technical Note PowerSCADA Expert V1.0

D0 DCM Module Setup Direct

MVI46-103M. User Manual. SLC Platform. IEC Master Communication Module

Cutler-Hammer ELC Serial Driver PTC Inc. All Rights Reserved.

APPLICATION NOTES - PIGNONE P6008 RTU CUSTOM PROTOCOL

DNP3 Master Ethernet Driver PTC Inc. All Rights Reserved.

1. System Topology Required Equipment and Components PcVue SCADA Modbus Slave MGate 5109 Setting...

Metrologics, LLC. Modbus Client Application User s Manual

Modbus RTU Serial Driver Help 2010 Kepware Technologies

^2 Accessory 55E DeviceNet Option

Series PM130 PLUS Powermeters PM130P/PM130E/PM130EH

$GDSWLYH0LFUR6\VWHPV

850 Feeder Protection System

Cutler-Hammer D50/300 Driver PTC Inc. All Rights Reserved.

Telemecanique Uni-Telway Driver PTC Inc. All Rights Reserved.

Bluetooth Low Energy Protocol Stack

MX-AOPC UA Server User s Manual

M-BUS/MODBUS CONFIGURATION SOFTWARE FOR GINEERS MMCR-64

Siemens S5 3964R Driver PTC Inc. All Rights Reserved.

CONTROLLER INFORMATION SHEET

P2 Configuration Guide

Transcription:

ConfigWiz Addendum This is the DNP3.0 client addendum. This addendum describes the pop-up window tabs, fields, and ranges of valid parameters for entry in those fields. NOTE The documentation and/or manuals provided by the IEDs vendors must be read and understood thoroughly prior to configuration. Revision Description Date A Release to Production September 1999 B Formatting Update August 2001 C Multi Port Support May 2003 D Document updated with screenshots December 2005 About this Addendum Use of this addendum should be for reference purposes only; all parameters to be entered should be carefully planned prior to any configuration attempts. Any information about aspects of the DNP3.0 clients and IEDs should be referenced from the vendor documentation. NOTE Some parameters may vary from the displays in the illustrations that follow. This is because the Template.mdb file currently used by your system may be different. The user should be thoroughly familiar with the architecture of the DNP3.0 protocol as described in the DISTRIBUTED NETWORK PROTOCOL DNP3.0 DOCUMENT SET. Introduction The following is a detailed Description of QEI s implementation of the DNP3.0 protocol as a client function. This documentation is in accordance with the recommended practice of the DNP3.0 Users Group and Technical Committee. It is very important to ensure that the capabilities of the and the Field Device (IED) are compatible. Otherwise, they may not interoperate correctly. Copyright 2001 QEI, Inc. 1

ConfigWiz Addendum Implementation Notes Maximum Data Link Frame Size (octets): Transmitted: 292. Received: 292. Maximum Fragment Size (octets): Transmitted: 2048. Received: 4096. Maximum Data Link Retries: Configurable. Maximum Application Layer Retries: Configurable. Requires Data Link Layer Confirmation: Configurable. Requires Application Layer Confirmation: Never. Timeouts while waiting for Data Link Confirm: Configurable. Complete Application Fragment: None. Application Confirm: None. Complete Application Response: Configurable. Sends Control Operations WRITE Binary Outputs: Never. SELECT/OPERATE: Configurable per point to send pulse or latch commands. Only transmits requests with a single object header per message, ie. range will be 1 for qualifier 17 hex or hex. DIRECT OPERATE: Configurable to send pulse or latch commands. Only transmits requests with a single object header per message, ie. range will be 1 for qualifier 17 hex or hex. DIRECT OPERATE - NO ACK: Never. Count > 1: Supported when commanded by 6CPP6 server software. Pulse On: Always. Pulse Off: Never. 2 Copyright 2001 QEI, Inc.

ConfigWiz Addendum Latch On: Close commands from 6CPP6's master are translated to latch on. Latch Off: Trip commands from 6CPP6's master are translated to latch off. Queue: Never. Clear Queue: Never. Expects Binary Input Change Events Either time-tagged or non-time-tagged for a single event: Yes. Both time-tagged and non-time-tagged for a single event: No. Additional Notes Message Size Information: All messages issued from the 6CPP6 to outstations, with the exception of writing file objects, are transmitted in a single link layer frame. Frozen Accumulators: Freeze command not transmitted to slaves and frozen accumulators are not read. Communications Channel Turnaround: 4ms Multi Port Communications: Each port assigned to DNP Client will poll in parallel with any and all other ports assigned to DNP Client. Copyright 2001 QEI, Inc. 3

ConfigWiz Addendum Implementation Table Shading key: Grp is shaded every other group as a visual aid. Shaded Func and Qual codes indicate those that are supported by the 6CPP6-processor board. OBJECT Grp Var Description 1 0 Binary input - all variations Func Codes (dec) Response (parsed by 6CPP6/6ACP5) Qual Codes (hex) 1 1 Binary input 129 00,01,17, 1 2 Binary input with status 129 00,01,17, 2 0 Binary input change - all variations 2 1 Binary input change without time 129 17,18,27, 2 2 Binary input change with time 129 17,18,27, 2 3 Binary input change with relative time 129 17,18,27, 10 0 Binary output - all variations 10 1 Binary output 10 2 Binary output status 129 response ignored 12 0 Control block - all variations 00,01,17, 12 1 Control relay output block 129 echo of request 12 2 Pattern control block 12 3 Pattern mask 20 0 Binary counter - all variations 20 1 32-bit binary counter 129 00,01,17, 20 2 16-bit binary counter 129 00,01,17, 20 3 32-bit delta counter 129 00,01,17, 20 4 16-bit delta counter 129 00,01,17, 20 5 32-bit binary counter without flag 129 00,01,17, 20 6 16-bit binary counter without flag 129 00,01,17, 20 7 32-bit delta counter without flag 129 00,01,17, 4 Copyright 2001 QEI, Inc.

ConfigWiz Addendum Response OBJECT (parsed by 6CPP6/6ACP5) Func Codes Qual Codes Grp Var Description (dec) (hex) 20 8 16-bit delta counter without flag 129 00,01,17, 21 0 Frozen counters - all variations 21 1 32-bit frozen counter 129 response ignored 21 2 16-bit frozen counter 129 response ignored 21 3 32-bit frozen delta counter 00,01,17, 00,01,17, 21 4 16-bit frozen delta counter 21 5 32-bit frozen counter with time of freeze 21 6 16-bit frozen counter with time of freeze 21 7 32-bit frozen delta counter with time of freeze 21 8 16-bit frozen delta counter with time of freeze 21 9 32-bit frozen counter without flag 129 response ignored 21 10 16-bit frozen counter without flag 129 response 21 11 32-bit frozen delta counter without flag 21 12 16-bit frozen delta counter without flag 22 0 counter change event - all variations ignored 00,01,17, 00,01,17, 22 1 32-bit counter change event without 129 17,18,27, time 22 2 16-bit counter change event without 129 17,18,27, time 22 3 32-bit delta counter change event 129 17,18,27, without time 22 4 16-bit delta counter change event 129 17,18,27, without time 22 5 32-bit counter change event with time 129 17,18,27, 22 6 16-bit counter change event with time 129 17,18,27, 22 7 32-bit delta counter change event 129 17,18,27, with time 22 8 16-bit delta counter change event with time 129 17,18,27, Copyright 2001 QEI, Inc. 5

ConfigWiz Addendum OBJECT Grp Var Description 23 0 Frozen counter events - all variations Func Codes (dec) Response (parsed by 6CPP6/6ACP5) Qual Codes (hex) 23 1 32-bit frozen counter event without time 23 2 16-bit frozen counter event without time 23 3 32-bit frozen delta counter event without time 23 4 16-bit frozen delta counter event without time 23 5 32-bit frozen counter event with time 23 6 16-bit frozen counter event with time 23 7 32-bit frozen delta counter event with time 23 8 16-bit frozen delta counter event with time 30 0 Analog input - all variations 30 1 32-bit analog input 129 00,01,17, 30 2 16-bit analog input 129 00,01,17, 30 3 32-bit analog input without flag 129 00,01,17, 30 4 16-bit analog input without flag 129 00,01,17, 31 0 Frozen analog input - all variations 31 1 32-bit frozen analog input 31 2 16-bit frozen analog input 31 3 32-bit frozen analog input with time of freeze 31 4 16-bit frozen analog input with time of freeze 31 5 32-bit frozen analog input without flag 31 6 16-bit frozen analog input without flag 32 0 Analog change event - all variations 32 1 32-bit analog change event without 129 17,18,27, time 32 2 16-bit analog change event without 129 17,18,27, time 32 3 32-bit analog change event with time 129 17,18,27, 32 4 16-bit analog change event with time 129 17,18,27, 6 Copyright 2001 QEI, Inc.

ConfigWiz Addendum OBJECT Grp Var Description 33 0 Frozen analog event - all variations Func Codes (dec) Response (parsed by 6CPP6/6ACP5) Qual Codes (hex) 33 1 32-bit frozen analog event without time 33 2 16-bit frozen analog event without time 33 3 32-bit frozen analog event with time 33 4 16-bit frozen analog event with time 40 0 Analog output status - all variations 40 1 32-bit analog output status 40 2 16-bit analog output status 129 response ignored 41 1 32-bit analog output block 00,01,17, 41 2 16-bit analog output block 129 echo of response 50 0 Time and date - all variations 50 1 Time and date 50 2 Time and date with interval 51 0 Time and date CTO - all variations 51 1 Time and date CTO 129 07 qty=1 51 2 Unsynchronized Time and date CTO 129 07 qty=1 52 0 Time delay - all variations 52 1 Time delay coarse 129 07 qty=1 response ignored 52 2 Time delay fine 129 07 qty=1 60 0 Not defined 60 1 Class 0 data 60 2 Class 1 data 60 3 Class 2 data 60 4 Class 3 data 70 1 File identifier 80 1 Internal indications Copyright 2001 QEI, Inc. 7

ConfigWiz Addendum OBJECT Grp Var Description 81 1 Storage object Func Codes (dec) Response (parsed by 6CPP6/6ACP5) Qual Codes (hex) 82 1 Device profile 83 1 Private registration object 83 2 Private registration object descriptor 90 1 Application identifier 100 1 Short floating point 100 2 Long floating point 100 3 Extended floating point 101 1 Small packed binary coded decimal 101 2 Medium packed binary coded decimal 101 3 Large packed binary coded decimal 8 Copyright 2001 QEI, Inc.

ConfigWiz Addendum Client Configuration The following is a Description of the configuration using ConfigWiz. DNP3.0 is a multi-function, multi-layer protocol that involves complex client/server and inter-layer interactions. The user must possess a thorough understanding of the protocol features and their application prior to proceeding with the client configuration. Port Configuration In general, the selected communications port should be configured in accordance with the requirements of the communications channel as described in ConfigWiz Users Manual (UM- 2012). However, the following two parameters are protocol-specific and should be configured using the procedures below: 1. Select Ports from the Components menu. The Ports selection window displays. NOTE The port is arbitrary. The port used by the DNP3.0 client on your system may differ. 2. Then select the port(s) used by the DNP3.0 client and click Select. The Port Options window displays. 3. Click the SPECIAL tab. Copyright 2001 QEI, Inc. 9

ConfigWiz Addendum 4. Enter the following configuration information. Field Name Parity RtsCts Delay PushTo Talk Enable CTS Timeout Parameters 8/No (This is the default parameter and it may already be set correctly.) 40 (This is the default parameter and it may already be set correctly.) Yes/No. Default is No. Yes/No. Default is No. Port speed Timeout Value 1200 bps 6000 ms 2400 bps 3000 ms 4800 bps 2000 ms 9600 bps 1000 ms (For higher speeds use 1000ms.) 5. Click Apply to enter the changes. 6. Click OK. 7. Click Exit on the Ports selection window. 10 Copyright 2001 QEI, Inc.

ConfigWiz Addendum Field Device (IED) Configuration Use the following procedure for configuring the field devices for the DNP3.0 client: 1. Click on the field device icon in the ConfigWiz main window. 2. The IED Options configuration window displays. Copyright 2001 QEI, Inc. 11

ConfigWiz Addendum Analog Tab Select the ANALOG tab. The point scaling parameter fields display. QEI s DNP3.0 client provides for the normalizing of each received integer value to a fully scaled, signed 16-bit binary integer. In many IEDs, the engineering values represented by binary integers are not scaled to the maximum value. To normalize the values, the full-scale engineering value should be entered for each point in ConfigWiz. Select the parameter entry field and change the value as needed. The value can range from 1 to 32-bit binary value. If there is a problem selecting the parameter field for point #1, first select point #2, then reselect point #1. 12 Copyright 2001 QEI, Inc.

ConfigWiz Addendum Control Duration Tab Select the CONTROL DURATION tab. Enter the desired contact closure time for each output point. If the value is not known or if it is not critical, leave the default setting of 2000 ms. Copyright 2001 QEI, Inc. 13

ConfigWiz Addendum Control Type Tab Select the CONTROL TYPE tab. The data acquired by the DNP3.0 client is usually routed (mapped) to a Master Station Server that operates in the Select Before Operate (SBO) mode. However, the Field Device connected to the DNP3.0 client may not be capable of operating in SBO mode. The control type required by the client can be configured in the client, regardless of the master station s operating mode. Select the desired mode on a per point basis via the pull-down menu as shown on the screen below. Setpoints Tab The same procedure applies to Setpoints, which are analog controls. Select the SETPOINT tab to prompt the window for control type selection, and then select the desired mode using the pull-down menu. 14 Copyright 2001 QEI, Inc.

ConfigWiz Addendum Standard Tab Select the STANDARD tab. The configuration parameter for each field is described below. Field Name Address Port Number Misc Flags Response Timeout Inhibit Point No Description The address of the Field Device (IED). This should match the address configured in the device. Enter the port number the Field Device (IED) is physically connected to. This must be one of the ports assigned to the DNP3.0 client. These flags are a set of communications control parameters. Their functions are listed below. The &h denotes that the number following is a hexadecimal number. It is recommended that the settings &h01 be used in most applications for L1, L2 devices. See Misc. Flags Bit Definitions. This is the time required to receive an application information packet (fragment) from the time of transmitting the polling packet. This time is a function of the communications channel speed and has to be configured accordingly. See Response Timeout by Channel Speed table. The address of the status point used by the Field Device to inhibit controls. Leave the default setting if this feature is not used. Copyright 2001 QEI, Inc. 15

ConfigWiz Addendum Field Name Static Poll Period Counter Poll Period E-Port Number Description The time interval in seconds between polls for static data (Class 0 or all data). If the client is polling for event data then a long period (several minutes) between Static Data Polls is appropriate. If the client is not polling for event data then the static poll interval should be shorter (10 to 15 seconds). The period of accumulator polls (several minutes may be appropriate). If the selected PortNumber is e-port, then this field should contain the specific number of the e-port to be used for this device. 1 to 127 e-ports can be selected. Misc Flags Bit Definitions Bit Bit 0 Bit 1 Definition The least significant bit, is used to enable class poll for events. If this bit is set to a one (1) the client will poll for events (Classes 1,2,3). If it is set to a zero (0) the client will only poll for static data (all data, Class 0). Some IEDs do not support polling for events. Used for configuring link layer acknowledgement. If this bit is set to a one (1) the client will ask the Field Device to confirm the receipt of the message. In general, link layer acknowledgements should not be used in transmissions from the Client to the IEDs. Bit 2 Used in conjunction with control inhibit. A specific status point from the IED can be used to inhibit controls from the Client to the IED. Bit 2 specifies which state of the status point will inhibit the outgoing control. The default setting is 0 and should be left as the configuration parameter if the inhibit function is not used. Bit 3 Used to inhibit polling of the IED. This can be used for troubleshooting purposes. Normally, the IED is polled for events, static data and counters depending on the configuration. It may be useful to disable the polling of an IED while maintaining all the other configuration. If the value of Bit 3 is one (1) the polling of the associated IED is disabled. The default is zero (0). Bit 4 Bit 5 Used to disable counter (accumulator) polling. When accumulators are defined in the Sizing DNP3C#n dialog box the Client will poll for counters in accordance with the programmed time interval (see Counter Poll Period). There are implementation levels which do not support this function but send the counter values in response to a static data poll (Class 0). In that case it is necessary to disable the counter poll in the Client by entering a value of 1 for Bit 4. The default is 0 which enables counter poll. Used to disable event poll during static data poll. The Client normally polls for static data (all data) by polling for all four variations of object 60 (Class 1,2,3,0) which means that event data is also acquired as part of the poll. Some implementations do not respond to class poll other than Class 0. In these cases the the poll for Class 1,2,3 as part of the static data poll should be disabled by setting Bit 5 to 1. The default value of Bit 5 is 0. 16 Copyright 2001 QEI, Inc.

ConfigWiz Addendum Response Timeout by Channel Speed This is the time required to receive an application information packet (fragment) from the time of transmitting the polling packet. This time is a function of the communications channel speed and has to be configured accordingly. Channel Speed Timeout 1200 bps 30000 ms. 2400 bps 15000 ms. 4800 bps 8000 ms. 9600 bps 6000 ms. Driver Configuration Use the following procedure for configuring the drivers for the DNP3.0 client: 3. Select the Driver button at the bottom left on the IED Options configuration window. The driver configuration window displays. Copyright 2001 QEI, Inc. 17

ConfigWiz Addendum AppLayer Tab Field Name AppLayer MaxRetries Service RequestTime Control ApertureTime Description If the inbound message from the IED fails the client will poll again for the information. This parameter defines how many times the client should retry to obtain the information from the IED. In general, the initial poll and two retries should be sufficient. The AppLayer retries should be coordinated with LinkLayer retries to obtain the best communications efficiency. If LinkLayer retries are used then AppLayer retries should be limited to one. If two or more ApplLayer reties are used then LinkLayer reties should be none. This time must be longer than the Port Timeout and should be coordinated with the communications speed as listed under the Service Request Time Parameters. After receipt of a selection command in a SBO control sequence, the execute command must be received within the ControlApertureTime in order to be accepted. Typical value is 30 sec. 18 Copyright 2001 QEI, Inc.

ConfigWiz Addendum Service Request Time Parameters Speed Service Request Time 1200 bps 20000 ms 2400 bps 10000 ms 4800 bps 5000 ms 9600 bps 3000 ms LinkLayer Tab Field Name Rtu Address LinkLayer MaxRetries Description The DNP3.0 protocol requires both Source and Destination Addresses. This entry is the Source Address of the Client. QEI default is 1024 or &h400. This is the maximum number of polling attempts at the link layer level. Usually, if Application Layer retries are used, there is no need for link layer retries and this parameter should be set to zero (0). Copyright 2001 QEI, Inc. 19

ConfigWiz Addendum Standard Tab Select the Standard tab in the driver configuration window. The STANDARD tab contains only a Description field for entering device designations in the form of ASCII strings. 20 Copyright 2001 QEI, Inc.