Electronic Design and Manufacturing International

Mk3 Energy Meter

DNP3 Profile
R e v i s i o n A 0 Release Date: 16th December 2003 1520-E-01
E.D.M.I. Pty Ltd 4/41 Deakin St Brendale, Qld, 4500 Australia E.D.M.I. (Asia) Pte Ltd Level 3 No.47 Yishun Industrial Park A Singapore 768724

 Copyright 1999-2003, Electronic Design and Manufacturing International Pty Ltd. All rights reserved. Atlas is a registered tradename of E.D.M.I. Pty. Ltd. Other product names are trademarks or registered trademarks of their respective owners.

TABLE OF CONTENTS

C h a p t e r 1

1. Introduction.................................................................................................2 2. Device Profile ..............................................................................................4

1.1 For more information........................................................................................................................2

Pa r t I

2.1 DNP Level Supported.......................................................................................................................4 2.2 Device Function................................................................................................................................4 2.3 Data Link Layer ................................................................................................................................4 2.4 Transport Layer.................................................................................................................................5 2.5 Application Layer .............................................................................................................................5 2.6 Implementation Table.......................................................................................................................6 2.7 Objects Table ....................................................................................................................................6

LIST OF TABLES

TABLE 1 DATA LINK PRIMARY FUNCTION CODES ............................................................................................4 TABLE 2 DATA LINK SECONDARY FUNCTION CODES.......................................................................................5 TABLE 3 APPLICATION FUNCTION CODES ........................................................................................................5 TABLE 4 BINARY OBJECTS ................................................................................................................................7 TABLE 5 COUNTER OBJECTS.............................................................................................................................9 TABLE 6 ANALOGUE OBJECTS ........................................................................................................................10

1. Introduction
1 r e t p a h C

This document describes the usage of DNP3 for the EDMI MK3 Energy Meter. The use of DNP3 in this meter allows the user to read instantaneous measurements (Volts, Current, Watts), time of use data (Wh, Vah, Varh) and Pulsing Input Status. The time and date of the meter can be set over DNP3.

1.1 For more information

The best source of information should generally be this document. The table of contents has been organised to make finding information as easy as possible. If you are still having problems though, EDMI support may be contacted via email at [email protected]. The EDMI web site is located at www.edmi.com.au. When contacting EDMI for support you may be asked for the meter serial number, firmware version and EziView version. The serial number is printed on the label, and is the serial number used in EziView to identify the meter. The EziView version is available under Help About in EziView. All this information will help us help you.

2. Device Profile
I t r a P

2.1 DNP Level Supported

TBA

2.2 Device Function

The Mk3 only operates as a slave device.

2.3 Data Link Layer

2.3.1 Frame Size The maximum frame size for transmitted and received packets is 292 octets including the data link header and CRCs. 2.3.2 Data Link Function codes. Function codes supported from the Primary message station. Function Code 0 2 3 4 9 Reset the link Test the Link Confirmed User Data Unconfirmed User Data Request link Status Table 1 Data link Primary function codes Description

Confirmation of packets on the data link layer is only supported in the direction from master to slave (Mk3). Therefore the master can ask for a packet to be confirmed and the Mk3 will send a confirmation when it receives a packet, but the Mk3 will never ask the master to confirm data link packets.

Function codes supported from the Secondary Station Function Code 0 1 11 Description Confirm with an acknowledgement Confirm with a negative acknowledgement Respond with status of the link Table 2 Data link Secondary function codes

2.3.3 Data Link Retries The Mk3 will never send retries because it never uses confirmation based packets. It will see retries from the master station as retries and handle them as appropriately.

2.4 Transport Layer

Fragmentation of user data from the application is supported by the transport layer. The maximum size for a fragment in the transport layer is 250 octets, including the 1 octet used for the transport header.

2.5 Application Layer

2.5.1 Packet Size The maximum size for a data packet is 2048 octets including the application layer header. Fragmentation of packets greater than 2048 octets is not supported. 2.5.2 Application Function codes. Function codes supported from the Primary message station. Function Code 0 1 2 129 Confirm a message packet Request objects from the meter Write object to the meter Response from the meter containing the requested data
5

Description

Table 3 Application Function codes

Confirmation of packets on the application layer (when the confirmation bit is set) is only supported in the direction from master to slave (Mk3). Therefore the master can ask for a packet to be confirmed and the Mk3 will send a confirmation when it receives a packet, but the Mk3 will never ask the master to confirm application packets. 2.3.3 Application layer Retries The Mk3 will never send retries because it never uses confirmation based packets. It will see retries from the master station as retries and handle them as appropriately.

2.6 Implementation Table

Object Object 1 20 30 50 60 100 Variations 1,2 1,2,5,6 1,2,3,4 1 1,2,3,4 1 Description Binary Inputs Counters Analogue Inputs Time and Date Class Objects Floating point Request Function Codes 1 1 1 2 1 1 Qualifier Codes 6, 7, 8, 9 6, 7, 8, 9 6, 7, 8, 9 7 6, 7, 8, 9 6, 7, 8, 9 Response Function Codes 129 129 129 129 129 129 Qualifier Codes 0 0 0 0 0 0

2.7 Objects Table

2.7.1 Binary inputs
Index Mk3 Register Description

0 1 2

0xF220 0xF221 0xF222

Pulsing input 1 Pulsing input 2 Pulsing input 3

3 4 5 6 7

0xF223 0xF224 0xF225 0xF226 0xF227

Pulsing input 4 Pulsing input 5 Pulsing input 6 Pulsing input 7 Pulsing input 8

Table 4 Binary objects

2.7.2 Counters
Index 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 7 Mk3 Register 0x0079 0x0179 0x0279 0x0379 0x0479 0x0579 0x0019 0x0119 0x0219 0x0319 0x0419 0x0519 0x0039 0x0139 0x0239 0x0339 0x0439 0x0539 0x0059 Description Import total Wh Export total Wh Import total varh Export total varh Import total VAh Export total VAh Import current Wh Export current Wh Import current varh Export current varh Import current VAh Export current VAh Import Previous Wh Export Previous Wh Import Previous varh Export Previous varh Import Previous VAh Export Previous VAh Import Billing Total Wh

19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46

0x0159 0x0259 0x0359 0x0459 0x0559 0x1079 0x1179 0x1279 0x1379 0x1479 0x1579 0x1019 0x1119 0x1219 0x1319 0x1419 0x1519 0x1039 0x1139 0x1239 0x1339 0x1439 0x1539 0x1059 0x1159 0x1259 0x1359 0x1459

Export Billing Total Wh Import Billing Total varh Export Billing Total varh Import Billing Total VAh Export Billing Total VAh Import Max Demand total W Export Max Demand total W Import Max Demand total var Export Max Demand total var Import Max Demand total VA Export Max Demand total VA Import Max Demand current W Export Max Demand current W Import Max Demand current var Export Max Demand current var Import Max Demand current VA Export Max Demand current VA Import Max Demand Previous W Export Max Demand Previous W Import Max Demand Previous var Export Max Demand Previous var Import Max Demand Previous VA Export Max Demand Previous VA Import Max Demand Billing Total W Export Max Demand Billing Total W Import Max Demand Billing Total var Export Max Demand Billing Total var Import Max Demand Billing Total VA

47

0x1559

Export Max Demand Billing Total VA

2.7.3 Analogue Objects

Index 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 9

Table 5 Counter Objects

Mk3 Register 0xE000 0xE001 0xE002 0xE003 0xE004 0xE005 0xE006 0xE007 0xE010 0xE011 0xE012 0xE013 0xE020 0xE021 0xE022 0xE023 0xE026 0xE030 0xE031 0xE032 0xE033 0xE040 0xE041

Description Phase A Volts Phase B Volts Phase C Volts Combined mean RMS Volts Line to Line AB Volts Line to Line BC Volts Line to Line CA Volts Line to Line Average Volts Phase A Current Phase B Current Phase C Current Combined mean RMS Current Phase A Phase Phase B Phase Phase C Phase Combined mean Phase Power Factor Phase A Watts Phase B Watts Phase C Watts Combined Watts Phase A VArs Phase B VArs

23 24 25 26 27 28 29

0xE042 0xE043 0xE050 0xE051 0xE052 0xE053 0xE060

Phase C VArs Combined VArs Phase A VA Phase B VA Phase C VA Combined VA Frequency

2.7.4 Class objects

Table 6 Analogue objects

Class 0 Data is linked to the binary objects variation 1. Class 1 Data is linked to the counter objects variation 1. Class 2 Data is linked to the analogue objects variation 1.

10

Intentionally Left Blank

11

12