ceweprometer serial port meter reading 3.1.4

8/10/2019 CewePrometer Serial Port Meter Reading 3.1.4

1/33

CewePrometerSerial Port Meter Reading

Rev 3.1.4


2/33

CewePrometer Serial Port Meter Reading.doc Cewe Instrument AB

2

ContentsRevision History 3

Contact 3

Overview 4

Baud rate changeover ............ ............. ............ .............. ............. ............ .............. ............. .............. ............ .... 4

Protocol arbitration ........................................................................................................................................ 4

IEC62056-21 4

Communication mode ..................................................................................................................................... 4

Connecting ...................................................................................................................................................... 4

Error handling ............ ............ ............. .............. ............. ............. ............. .............. ............. ............ .............. . 6

Calculation of the block check character (BCC) ............ ............. ............. .............. ............. ............ .............. . 6

Communication messages ............................................................................................................................... 7

Event IDs and data ..................... ............ .............. ............. .............. ............ .............. ............. ............ ......... 26

IEC62056-21 with OBIS codes 2828

DLMS/COSEM 2929

General ..................................................................................................................................................... 2929 Supported objects ...................................................................................................................................... 2929


3/33


3

Revision HistoryRevision Date Description Signature0.1 Feb 12, 2004 Created GLN1.0 Sep 20, 2004 Messages in meter firmware 1.1.0 added. Some clarifications made. GLN1.2 Mar 2, 2005 Event ids added. New tags for logged values added. GLN1.3 Sept 26, 2005 Description of calculation of the block check character (BCC) is added.

Description of id's 109500, 100D00 and 101300 added. Minor fixesdone.

GLN

1.4 July 18, 2006 Messages in meter firmware 1.3.0 added. NEN1.4 2 nd Ed. Mar 1, 2007 New messages for firmware 1.4.0 added. Changes of access level of

time set command. Changes in General info text length. New event andlogger flag for battery backup time has ended.

PLM

1.4 3 rd Ed. July 17, 2007 Message id history, add information about in what firmware version acertain message id was implemented.

THR

2.0 Oct, 2008 Added OBIS over 62056-21. Added DLMS. RPO3.0 Mar, 2010 Adapted to FW 2.1 and 3.0 RPO3.1.0 Sep, 2010 Added changes for FW 2.2 and 3.1 PLM3.1.1 May, 2011 Minor corrections RPO3.1.2 Nov, 2011 Added messages 100E and 1014 for 62056-21. RPO

3.1.3 Jul, 2013 Fixed typo in message 100D. RPO3.1.4 Sep, 2013 Clarified that MD values uses Extended Register class. RPO

ContactFor further information or technical assistance please contact Cewe Instrument.

World Wide Web www.ceweinstrument.se E-Mail [email protected]

Tel +46 155 77500

Address Cewe Instrument ABBox 1006SE-611 29 Nykping


4/33


4

OverviewThis document describes how to read data from the CewePrometer using IEC1107/ IEC62056-21 orDLMS/COSEM.

This document is a complement to the IEC1107/ IEC62056-21 and describes only Cewe Instrument specific aspectsof the standard. IEC62056-21 is a replacement to the IEC1107 and hereafter we are only referring to the IEC62056-21 standard.

For DLMS/COSEM, this document describes the specifics for CewePrometer. For general information about theprotocol, refer to the standard documents (white, green and blue books from the DLMS User Association). Theimplementation in CewePrometer is based on Blue Book 8 th edition and Green Book 6 th edition.

DLMS/COSEM is not supported on the optical interface, only on RS232, RS485 and Ethernet.

This document only describes meter reading; it is not intended for meter configuration. When configuring the meterthrough IEC62056-21 other aspects have to be taken into consideration, not mentioned in this document.

Baud rate changeover

The RS-232/422/485 ports on the meter do not have the baud rate changeover. Instead the communication starts atthe baud rate set up in the meter. Using the optical interface complies with the standard which means thecommunication always starts at 300 bps.

Protocol arbitrationThe communication ports supporting DLMS/COSEM automatically detects the type of communication to beIEC62056-21 or DLMS/COSEM. Once a type of protocol has been detected, the port stays in that mode until theconnection is closed or times out.

IEC62056-21

Communication modeCewePrometer supports IEC62056-21 protocol mode C - programming mode. The optional partial block read andformatted codes are not supported.

ConnectingWhen connecting to the meter using mode C programming mode the meter serial number is used as the deviceaddress. The device address may be omitted if only one meter is expected to answer. The meter answers with aidentification message where the manufacturers identification is CWI. After the acknowledgement/option selectmessage the meter answers with a P0-command which is an operand for secure algorithm. The operand is not usedtoday but may be used in the future. The PC/HHU answers with a P2 command where the data consists of a plaintext password for one of the access levels, in the future the password may be encrypted with a secure algorithm

yet to be selected . Please note that the P2 must be sent from the PC/HHU even if there are no passwords in themeter. The meter will in this case accept an arbitrary string as the password. It may be an empty string.

The meter has five access levels:Level 1 Read only access.Level 2 Adjust meter clock and setting meter clock forward to an absolute time, finish historical period

(which causes a maximum demand reset).Level 3 Change configuration. Setting the meter clock to an absolute time.Level 4 Update firmware.Level 5 Calibrate meter.


5/33


5

Example:The meter serial number is: 135701The meter password for access level 2 is: ABCDEF

PC/HHU -> /?! or. /?135701!Meter < ACK>061

P0(xxxx)-> < SOH>P2(ABCDEF)

If the P2 command contains an illegal password the meter will return a break message instead of .

PC/HHU -> < SOH>P2(AAAAAA)Meter B0


6/33


6

Error handlingIf the meter does not accept a command, an error message is returned. An error message has the same format as anormal data message but the data set starts with ER: followed by a three digit error code in decimal format e.g.ER:001.

The following error codes may be returned:

001 Non existing main id: There is no message with the requested main id. Main id is the first four leadingdigits in the message id. i.e. 0152 in 015200.

002 Non existing sub id: There is no message with the requested sub id. Sub id is the last two digits in themessage id i.e. 00 in 015200.

003 Locations requested exceeds limit: A maximum of 16 locations may be read in a single read command e.g.R1101200(33) is not accepted and the meter returns error message 003.

004 Data format error: The format of the data set in a data message has not a valid format, e.g. a character stringis sent when the meter expects an integer.

005 Data content error: The data set in a data message has not a valid content, e.g. a value is given outside validlimits.

006 Message read only: Returned when a write command is sent to a read only message.

007 Message write only: Returned when a read command is sent to a write only message.

008 Reserved

009 General error message.

010 Access denied: Returned when current access level is not enough for the requested message.

Example:Meter accepts the read command and returns a data message:

PC/HHU -> R1108700(1)Meter R1108800(1)Meter


7/33


7

Communication messages

General infoFloatsWhen the meter returns floating point values they are given in scientific notation with 1 to 9 significant digits.Decimal point and/or exponent will be omitted when possible, e.g.:01e91.234567891.23456789e10 etc.

Floats are either single (32 bits) or double (64 bits) precision.

Hex bytesHex bytes are always sent/received as two characters i.e. B is sent/received as 0B.

IntegersMay be 8, 16 or 32 bits. Where the bit resolution exceeds 8, it is stated. Integers are always sent/received withleading zeroes omitted.

Message id:sThe message id:s are in hexadecimal format. Leading zeroes may be omitted i.e. 015200 may be sent as 15200. Themeter will recognise both upper case and lower case characters in the id i.e. 108a00 and 1008A00 are bothacceptable. The meter will always send upper case characters in the id.


8/33


8

Date and timeID No. R/W Access

levels (R,W)Description Example

100C00 R/W 1, 2(3) 1 Date and time(yyyymmdd,hhmmss)

1

In meter firmware versions prior to 1.1.0 thewrite access level was 3.

(20040209,145926)

108A00 W N/A, 2 Slide time(S,P)S: 28800...28800P: 1...40

The meter time is adjusted every minute by Ppercent of a minute until the time has beenadjusted S seconds. This is the preferred wayof adjusting the meter time.

If there is a slide time in process, writinganother slide time message cancels the current

process and starts a new. By writing 0,0 theongoing time adjustment is cancelled.

(7,20)

109500...109509

R/W 1, 3 Daylight Saving time settings, year no 0..9(SM,SD,SH,EM,ED,EH,A)

SM: Start month (1-12)SD: Start day (1-31)SH: Start hour (0-23)EM: End month (1-12)ED: End day (1-31)EH: End hour (0-23)A: DST adjustment in minutes

Start time is given in standard time and end istime given in daylight saving time. To use thisfunction a start year has to be set (message id1096).

Note: In meter firmware versions previous to1.3.0 only year no 0 is available.

(3,28,2,10,31,3,60)

1096 R/W 1, 3 Daylight saving time start year

Start year for the daylight saving time settings.If start year is set to 0, year no 0 configurationwill always be active.

Note: This message is only available in meterfirmware versions 1.3.0 and later.


9/33


9

ID No. history

ID No. Firmware

1.0.0 1.1.0 1.2.0 1.3.0 1.4.0

100C00 x c x x x108A00 x x x x x109500 x x x x x10950109 x x109600 x x


10/33


10

Energy registersID No. R/W Access


100800 R 1, N/A Energy registersReturned as 18 comma separated floats withdouble precision.

1: active energy imp. (Wh)2: active energy exp.3: reactive energy QI (varh)4: reactive energy QII5: reactive energy QIII6: reactive energy QIV7: apparent energy imp. (VAh)8: apparent energy exp.9: reactive energy imp. (varh)10: reactive energy exp.11: reactive energy ind.12: reactive energy cap.13: active energy imp. L1 (Wh)

14: active energy imp. L215: active energy imp. L316: active energy exp. L117: active energy exp. L218: active energy exp. L3

(8.78649208e3,3.03188899e3,1.56434299e4,5.19229712e3,0,...

10D000 R 1, N/A Current TOU infoReturned as 6 integers. (energy rate,MDrate,energy day type,MD day type,season,tariffstructure)


(6,7,1,2,3,0)

10D100...10D107

R 1, N/A TOU-registers 0...7Returned as 8 comma separated floats with

double precision. First float is rate 0 and lastfloat is rate 7.

Message 10D100 is TOU-register 0 and10D107 is TOU-register 7. What each TOU-register represents is defined in message10D200.


(8.78649208e3,3.03188899e3,1.56434299e4,5.19229712e3,

0,...


11/33


11

10D200 R/W 1, 3 TOU-registers select(r0r1r2r3r4r5r6r7)Returned as 8 hex bytes. Defines what eachTOU-register represents. First hex byte selectswhat TOU-register 0 represents. Last hex byteselects what TOU-register 7 represents.

00: active energy imp. (Wh)01: active energy exp.02: reactive energy imp. (varh)03: reactive energy exp.04: reactive energy ind.05: reactive energy cap.06: reactive energy QI (varh)07: reactive energy QII08: reactive energy QIII09: reactive energy QIV0A: apparent energy imp. (VAh)0B: apparent energy exp.17...1E: external reg. 0..7


(030405060708090A)

ID No. history

ID No. Firmware

1.0.0 1.1.0 1.2.0 1.3.0 1.4.0

100800 x x x x x10D000 x x x x10D10007 x x x x10D200 x x x x


12/33


12

External registers (pulse input registers)ID No. R/W Access


10A100 R 1, N/A External registersReturned as 8 comma separated floats withdouble precision. First float represent external

register 0. Last float represent external register7.

(7.6644565e5,9.928e5,1.4892e5,1.8935716e5,0,0,0,0)

10A200...10A207

R/W 1, 3 External register description 0...70 to 17 character string.

(Check meter)

10A300...10A307

R/W 1, 3 External register unit 0...70 to 4 character string.

(Wh)

10A400...10A407

R/W 1, 3 External register format 0...7(prefix, no. of decimals)

prefix use0: no prefix1: kilo2: Mega3: Giga

4: Tera

no. of decimals: 0...4

(2,3)

ID No. history

ID No. Firmware

1.0.0 1.1.0 1.2.0 1.3.0 1.4.0

10A10007 x x x x x10A20007 x x x x x10A30007 x x x x x10A40007 x x x x x


13/33


13

Instant valuesID No. R/W Access

levels(R,W)

Description Example

015200 R 1, N/A Instant valuesReturned as 46 comma separated floats with

single precision:

1: phase voltage L1 (volts) 1 2: phase voltage L23: phase voltage L34: main voltage L1-L2 (volts)5: main voltage L2-L36: main voltage L3-L17: current L1 (ampere)8: current L29: current L310: phase symmetry voltage L1 (rad -Pi...Pi) 2

11: phase symmetry voltage L212: phase symmetry voltage L3

13: phase symmetry current L1 (rad -Pi...Pi)14: phase symmetry current L215: phase symmetry current L316: phase angle L1 (rad -Pi...Pi)17: phase angle L218: phase angle L319: power factor L1 (0.0...1.0)20: power factor L221: power factor L322: active power L1 (W) 4

23: active power L224: active power L325: reactive power L1 (var) 4

26: reactive power L2

27: reactive power L328: apparent power L1 (VA)29: apparent power L230: apparent power L331: THD voltage L1 (0.0...1.0) 5

32: THD voltage L233: THD voltage L334: THD current L1 (0.0...1.0) 5

35: THD current L236: THD current L337: total active power (W) 4

38: total reactive power (var) 4

39: total apparent power (VA)40: total power factor (0.0...1.0)41: total phase angle (rad -Pi...Pi)42: frequency (Hz)43: voltage transformer ratio44: current transformer ratio45: secondary nominal voltage (volt) 3

46: secondary nominal current (ampere)

1 For 2-element meters phase voltage is 0.

2 For 2-element meters the phase symmetries arefor the line to line voltages.

(5.18032e3,5.18094e3,5.19453e3,8.97436e3,

8.98244e3,8.98662e3,1.00546e2,1.00417e2,1.0079e2,0,...


14/33


14

3 Given in phase voltage for 3-element metersand line to line voltage for 2-element meters.

4 Positive values means import energy direction,negative values export energy direction.

5

1.0 equals 100%

01500x R 1, N/A Harmonic amplitudesReturned as 31 comma separated singleprecision floats. Values given in volts/amperespeak value. First value is the fundamental value,second value is the first harmonic.

In the message Id no. replace x with:

x use0: voltage L11: voltage L22: voltage L33: current L14: current L25: current L3

(7.63053e2,1.19017e2,1.5805e2,7.87409e1,3.95637e-2...

01510x R 1, N/A Harmonic phase anglesReturned as 31 comma separated singleprecision floats. Values given in radians relativevoltage L1 (-Pi...Pi). First value is the phaseangle of the fundamental, second value is thephase angle of the first harmonic.

In the message Id no. replace x with:

x use0: voltage L11: voltage L22: voltage L33: current L14: current L25: current L3

(1.13196e1,1.7033,2.26157,1.12749,1.56938e-3...

015400 R 1, N/A Voltage UnbalanceDefinition according to IEC 61000-4-30 (2008)Class A except measuring period, which is 20cycles instead of 10(50 Hz)/12(60 Hz)Returns single precision value. The example 0.1represents 10% voltage unbalance.

(0.1)

ID No. history

ID No. Firmware

1.0.0-1.4.0 2.x 3.0.x 3.1.0

01500005 x x x x01510005 x x x x015200 x x x x015400 x


15/33


15

Logged values (stored profile)ID No. R/W Access


100D00 R/W 1, 3 Logger 0 channel countOne integer (0-50) which is the number ofchannels stored in logger 0.

(5)

100E00 R/W 1,3 Logger 0 periodOne integer giving the period in seconds.Must be one of the predefined values 60,120, 180, 240, 300, 600, 900, 1200, 1800 or3600.

(3600)

101100 W N/A, 1 Set logger 0 read offset(yyyymmdd,hhmmss)

By writing 19700101,000000 the completecontent of the logging memory can beretrieved.

(20040203,020000)

101200 R 1, N/A Get next record from logger 0(yymmddhhmm,tag,value0...value9)(yymmddhhmm,tag,value0...value49) 4

tag: bit use 0: Time set1: Disturbed2: User alarm3: Parameter data change 1

4: Reverse running 1 5: Meter clock in daylight saving

time 1 6: Voltage lost/missing 1 7: Corrupted8: Battery 2

9: Power Loss 3 10-15: reserved

value0..value49 returned as 1 to 10 commaseparated double precision floats depending onhow many channels the meter has beenconfigured with.

When the end of the logging memory has beenreached EOF is returned

When instantaneous values are logged theaverage over the logging period is stored.When energies and external registers arelogged the current reading of the registers arelogged.

Up to 16 records can be read in the samecommand e.g. R1101200(16)

1Only in meter firmware 1.2.0 and later.2Only in meter firmware 1.4.0 and later.3 Only in meter firmware 2.1.0 and later.4 Only in meter firmware 3.1.0 and later.

(0402112015,2,4.96634762e4,1.03131386e4,1.03762926e4)

When the end of the loggingmemory is reached:

(EOF)


16/33


16

10D500 R 1, N/A Get next record with rate info from logger 0(yymmddhhmm,tag,value0...value49,MD rate,egy. rate)

This is basically the same message as 101200only that this message contains informationabout the MD rate and energy rate present

when the record was stored. Note: This message is only available in meterfirmware versions 1.1.0 and later.

(0402112015,2,4.96634762e4,1.03131386e4,1.03762926e4,4,3)

100F00 R/W 1, 3 THIS MESSAGE IS OBSOLETEFROM FW 2.1.0See 1140 114A instead.

What is logged in each channel of logger 0(c0c1c2c3c4c5c6c7c8c9)

Returned as 10 hex bytes representingbitmaps:bit 0...5: Defines quantity to log e.g. current,

voltage, active energy etc.

bit 6...7: Phase to log: 0=all phases (total oraverage), 1=L1, 2=L2, 3=L3. It isnot possible to log all quantities perphase.

bit 0...5 use00: active energy imp. 1

01: active energy exp. 1

02: reactive energy imp.03: reactive energy exp.04: reactive energy ind.05: reactive energy cap.06: reactive energy QI07: reactive energy QII08: reactive energy QIII09: reactive energy QIV0A: apparent energy imp.0B: apparent energy exp.0C: phase voltage 1

0D: line to line voltage 1

0E: current 1

0F: active power 1

10: reactive power 1

11: apparent power 1

12: frequency13: phase angle 1

14: power factor 1

15: THD voltage 116: THD current 1

17...1E: external reg. 0..7

Ex. 0C three phase average voltage8C phase voltage L2D3 phase angle L3

1 Possible to log per phase.

(00010203000000000E0A)


17/33


17

11400x..11720x 1

R/W 1,3 What is logged in channel(quantity, phase, instant_value_type)

Where quantity is one of:0: active energy imp.

1: active energy exp.

2: reactive energy imp.

3: reactive energy exp.4: reactive energy ind.5: reactive energy cap.6: reactive energy QI7: reactive energy QII8: reactive energy QIII9: reactive energy QIV10: apparent energy imp.11: apparent energy exp.12: phase voltage

13: line to line voltage

14: current

15: active power

16: reactive power

17: apparent power

18: frequency19: phase angle

20: power factor

21: THD voltage

22: THD current

23...30: external reg. 0..731..61: voltage harmonics 1..3162..92: current harmonics 1..3193: voltage unbalance

and phase is one of0: system (all phases)1: L12: L23: L3

and instant_value_type is one of:

0: NA1: Average2: Max3: Min4: Instant

x should be 0 for Logger 1 and 1 for Logger 2.Examples114000 is for channel 1, logger 1.114101 is for channel 2, logger 2.114900 is for channel 10, logger 1.117100 1 is for channel 50, logger 1.

Note: These messages are only available inmeter firmware version 2.1.0 and later.

1 FW 2.1: 10 channels 11400x-114A0XFW 3.1: 50 channels 11400x-11720X

(12, 1,3)


18/33


18

101300 R/W 1, 3 Logger 1 channel countsame as logger 0

101400 R/W 1, 3 Logger 1 periodsame as logger 0

101700 W N/A, 1 Set logger 1 read offsetsame as logger 0

101800 R 1, N/A Get next record from logger 1

same as logger 010D600 R 1, N/A Get next record with rate info from logger 1same as logger 0


101500 R/W 1, 3 THIS MESSAGE IS OBSOLETEFROM FW 2.1.0See 1140 114A instead.

What is logged in each channel of logger 1same as logger 0

ID No. history

ID No. Firmware

1.0.0 1.1.0-1.4.1 2.0.0 2.1.0 2.2.0 3.0.0 3.1.0 100D00 X X X X X X X 100F00 X X 101100 X X X X X X X 101200 X X X X X X X 101300 X X X X X X X 101500 X X X101700 X X X X X X X 101800 X X X X X X X 10D500 X X X X X X 10D600 X X X X X X 114000..114A01 X X X X 114B00..117201 X X


19/33


19

Maximum demandID No. R/W Access


106500...106507

R 1, N/A MD-value 0...7(quantity,yymmddhhmm,highest,yymmddhhmm,second highest,

yymmddhhmm,third highest)

quantity use0: active power imp.1: active power exp.2: reactive power imp.3: reactive power exp.4: reactive power ind.5: reactive power cap.6: reactive power QI7: reactive power QII8: reactive power QIII9: reactive power QIV10: apparent power imp.

11: apparent power exp.

highest, second highest, third highest as singleprecision floats.

If yymmddhhmm equals 7001010000 noMD-value has been registered by the meter.

(0,0402040500,1.76952e6,0402031200,1.50058e6,0402112000,1.30823e6)

106600...106607

R 1, N/A MD-value 0...7 with rate info(quantity,yymmddhhmm,rate,highest,yymmddhhmm,rate,second highest,yymmddhhmm,rate,third highest)

This is basically the same message as 106500...106507 only that this message has rate

information included.

Rate as integer. The actual rate when the MDoccurred.


(0,0402040500,4,1.76952e6,0402031200,4,1.50058e6,0402112000,5,1.30823e6)

103500 W N/A, 2 Finish period/MD-resetThis message copies the MD-registers to ahistorical register and thereafter clears thecurrent readings of the MD-registers.

Note: This message will also copy the currentreadings of energy registers and external

registers etc. to the historical register.

()


20/33


20

ID No. history

ID No. Firmware

1.0.0 1.1.0 1.2.0 1.3.0 1.4.0

10650007 x x x x x

10660007 x x x x103500 x x x x x


21/33


21

Historical registerID No. R/W Access


103700...10370D

R 1, N/A Historical period time stamp(yyymmdd,hhmmss)

Returns the time when the historical period wasfinished. Message 103700 is the newest periodand 10370D the oldest. When the meter returns(19700101,000000) no older periods exists.

(20040210,172011)

103800...10380D

R 1, N/A Historical energy registersReturned as 12 comma separated floats withdouble precision. Message 103800 returns thenewest period.

1: active energy imp. (Wh)2: active energy exp.3: reactive energy QI (varh)4: reactive energy QII

5: reactive energy QIII6: reactive energy QIV7: apparent energy imp. (VAh)8: apparent energy exp.9: reactive energy imp. (varh)10: reactive energy exp.11: reactive energy ind.12: reactive energy cap.

103900...10390D

R 1, N/A Historical external register (pulse inputs)Returned as 8 comma separated floats withdouble precision. Message 103900 returns thenewest period.

float 1..8 represents external register 0...7.

104000...10400D R 1, N/A Historical MD-register 0(quantity,yymmddhhmm,highest,yymmddhhmm,second highest,yymmddhhmm,third highest)

quantity use0: active power imp.1: active power exp.2: reactive power imp.3: reactive power exp.4: reactive power ind.5: reactive power cap.6: reactive power QI7: reactive power QII

8: reactive power QIII9: reactive power QIV10: apparent power imp.11: apparent power exp.

Highest, second highest, third highest as singleprecision floats.

If yymmddhhmm equals 7001010000 noMD-value has been registered by the meter.


22/33


22

104100...10410D

R 1, N/A Historical MD-register 1see above

104200...10420D


104300...10430D


104400...

10440D

R 1, N/A Historical MD-register 4

see above104500...10450D


104600...10460D


104700...10470D


104800...10480D

R 1, N/A Historical MD-register 0 with rate info

(quantity,yymmddhhmm,rate,highest,yymmddhhmm,rate,second highest,yymmddhhmm,rate,third highest)

This is basically the same message as Historical MD-register 0 (104000... 10400D)

only that this message has rate informationincluded.

Rate as integer. The actual rate when the MDoccurred.

Note: Historical MD-register messages areonly available in meter firmware versions 1.1.0and later.

104900...10490D

R 1, N/A Historical MD-register 1 with rate infosee above

104A00...104A0D


104B00...

104B0D

R 1, N/A Historical MD-register 3 with rate info

see above104C00...104C0D


104D00...104D0D


104E00...104E0D


104F00...104F0D


105000...10500D

R 1, N/A Historical TOU-registers 0

Returned as 8 comma separated floats withdouble precision. Message 105000 returns thenewest period and 10500D the oldest.

First float is TOU-register for rate 0. Last floatis TOU-register for rate 7.

Note: Historical TOU-register messages areonly available in meter firmware versions 1.1.0and later.

105100...10510D

R 1, N/A Historical TOU-register 1see above

105200...10520D



23/33


23

105300...10530D


105400...10540D


105500...10550D


105600...

10560D

R 1, N/A Historical TOU-register 6

see above105700...10570D


103500 W N/A, 2 Finish period/MD-reset

Copies MD-values, current readings of energyregisters, TOU-registers and external registersto the historical register. Clears the currentreadings of the MD-registers.

()

ID No. history

ID No. Firmware

1.0.0 1.1.0 1.2.0 1.3.0 1.4.0

103500 x x x x x1037000D x x x x x1038000D x x x x x1039000D x x x x x1040000D x x x x x1041000D x x x x x1042000D x x x x x1043000D x x x x x1044000D x x x x x1045000D x x x x x

1046000D x x x x x1047000D x x x x x1048000D x x x x1049000D x x x x104A000D x x x x104B000D x x x x104C000D x x x x104D000D x x x x104E000D x x x x104F000D x x x x1050000D x x x x1051000D x x x x

1052000D x x x x1053000D x x x x1054000D x x x x1055000D x x x X1056000D x x x x1057000D x x x x


24/33


24

Event logID No. R/W Access


102100 W N/A, 1 Set event log read offset(yyyymmdd,hhmmss)

By writing 19700101,000000 the complete

content of the event log can be retrieved.

(20000101,000000)

102200 R 1, N/A Get next event

(yymmddhhmmss,event id,data)

event id 1: 16 bit integerdata: 6 hex bytes of data. The

interpretation of these bytes dependson the event id.

When the end of the event log has beenreached EOF is returned

Up to 16 events can be read in the samecommand e.g. R1102200(16). The

event log may contain up to 40 events.1The event ids are listed in the section EventIDs and data

(040209145950,2,4EA027400000)

102300 R 1, N/A Total count of events(16 bit integer)

A maximum of 40 events can be stored in theevent log before the oldest event is overwritten.The total count is the no. of events occurredsince last reset, and may exceed 40.

(98)

ID No. history

ID No. Firmware

1.0.0 1.1.0 1.2.0 1.3.0 1.4.0

102100 x x x x x102200 x x x x x102300 x x x x x


25/33


25

MiscellaneousID No. R/W Access


107100...107103

R/W 1, 3 General info text 0...3(label,text)

label: 0 to 17 character string with adescription of the text.

text: 0 to 17 character string with a generalpurpose text.

(Owner,Cewe Instrument)

100700 R 1, N/A Meter internal temperatureas single precision float.

(2.525e1)

108700 R 1, N/A Meter serial number0 to 16 character string.

(135701)

10DA00 R 1, N/A Meter firmware version(major,minor,rev)as three comma separated integers.

(1,1,0)

106B00 R 1, N/A Sags and swells(sags count,swells count,reserved)

as three comma separated 32bit integers.

(4,6,0)

011200 R 1, N/A Measuring propertiesas 16 bit integer.

bit use0: measuring mode 0 = 3-element, 1 = 2-

element1: nominal frequency 0 = 50Hz, 1 = 60Hz

(3)

10D800 R/W 1, 3 Battery backup time leftas 32 bit integer.Represents number of seconds until the meterreports that the battery needs to be exchanged.-1 represents inactive function.

(-1)

ID No. history

ID No. Firmware

1.0.0 1.1.0 1.2.0 1.3.0 1.4.0

011200 x x x c c100700 x x x x x102500 x x x x106B00 x x x x x10710003 x x x x c108700 x x x x x

10D800 x


26/33


26

Event IDs and data

The message Get next event (102200) returns event IDs as well as additional event data. The event id is returned asa decimal integer and the additional data as 6 hexadecimal bytes.

ID Data Description Example1 Phase (L1=00...L3=02) Single phase reverse energy

direction1,010000000000

phase 00 00 00 00 002 Meter time after adjustment in seconds since 1 Jan 1970

00:00 (32 bit)Time set (2004-11-04

16:58:07)2,9F5F8A410000LSB MSB 00 00

3 N/A Registers cleared 3,000000000000

4 Logger no. (00=logger0, 01=logger1) Logger has been reset 4,010000000000logg.no. 00 00 00 00 00

5 N/A Supply lost 5,000000000000

6 N/A Historical registers cleared(all billing periods cleared)

6,000000000000

7 N/A Historical period finishedand MD-registers reset(Billing period reset)

7,000000000000

8 N/A All MD-registers cleareddue to configurationchanged

8,000000000000

9 Logger no. (00=logger0, 01=logger1) Logger cleared due toconfiguration changed

9,010000000000logg.no. 00 00 00 00 00

14 Duration in seconds (32 bit) Voltage interruption inseconds

(0 seconds)14,000000000000LSB 00 00 MSB 00 00

15 Duration in seconds (32 bit) Voltage sag (674 seconds)15,A20200000000LSB 00 00 MSB 00 00

16 Duration in seconds (32 bit) Voltage swell (341 seconds)16,550100000000LSB 00 00 MSB 00 00

17 N/A Voltage below limit 17,000000000000

18 N/A Voltage exceeding limit 18,000000000000

19 N/A Power factor below limit 19,000000000000

20 N/A Voltage unbalance 20,000000000000

21 N/A Current unbalance 21,000000000000

22 N/A Active power below limit 22,000000000000

23 N/A Active power exceedinglimit

23,000000000000

24 N/A Voltage THD exceedinglimit

24,000000000000

25 N/A Current THD exceedinglimit

25,000000000000

26 Phase (L1=00...L3=02), Harmonic no (01-30) Single harmonic on voltageexceeding limit

(5:th harm on L1)26,000400000000phase harm.no. 00 00 00 00

27 Phase (L1=00...L3=02), Harmonic no (01-30) Single harmonic on currentexceeding limit

(3:rd harm on L2)27,010200000000phase harm.no. 00 00 00 00

28 Input no. (00-07), pulse length in ms. (16 bit) Digital input pulse lengthtoo long

(inp. 4, 300ms)28,042C01000000inp.no. pl.LSB pl.MSB 00 00 00


27/33


27

29 Input no. (00-07), pulse length in ms. (16 bit) Digital input pulse lengthtoo short

(inp. 3, 20ms)29,031400000000inp.no. pl.LSB pl.MSB 00 00 00

30 Bitmask of one or a combination of phases (bit0=L1,bit1=L2, bit2=L3)

Voltage phase failure. 2-element meters will alwayshave phases = 00.

(Phase failure onL1 and L2)30,030000000000phases 00 00 00 00 00

42 N/A Meter configuration altered 42,000000...

43 N/A Meter calibration altered 43,000000...

44 N/A Meter initialised 44,000000...

45 Bitmask of one or a combination of phases/elements(bit0=L1, bit1=L2, bit2=L3)

Reverse running. 2-elementmeters will always havebit1(L2) = 0

(Reverse runningon L1 and L3)45,050000000000phases 00 00 00 00 00

46 N/A Meter firmware upgrade 46,000000...

47 N/A Time to change battery 47,000000...

1000 N/A Energy registers corrupt 1000,000000...

1001 N/A Communication moduleconfig. corrupt

1001,000000...

1002 N/A I/O module config. corrupt 1002,000000...

1003 N/A Measuring module config.corrupt

1003,000000...

1004 N/A Measuring moduleinitialisation corrupt

1004,000000...

1005 N/A Measuring modulecalibration corrupt

1005,000000...

1006 N/A Main module config.corrupt

1006,000000...

1007 N/A Historical period corrupt 1007,000000...

1008 N/A MD-register corrupt 1008,000000...

1009 N/A Measuring module faulty 1009,000000...


28/33


28

IEC62056-21 with OBIS codesAs an alternative to the message id:s described in the section IEC62056-21 above, OBIS codes can be used asdescribed in this section.

OBIS codes can only be used for reading, limited to the objects listed in the table below. It is mode C and requiresthe same connection process as ordinary message id:s.

Use the R5 command and OBIS code format A-B:C.D.E as given in this example: R5 1-1:1.8.0()

Response is on the form 1-1:1.8.0 (000000.25*MWh)

The example above has no F part. If a billing period is to be retrieved, use the following structure: R5 1-1:1.8.0*12()

Billing periods are denoted by a VZ modulo 15. The current VZ has OBIS code 0.1.0.

OBIS code Quantity Comment1-1:1.2.0 Active Import1-1:1.4.0 Rising demand1-1:1.6.0.f f denotes billing period. Note that this is relative VZ.1-1:1.8.e.f e = 0 gives total active import.

e from 1 to 8 gives corresponding rate.f denotes billing period.

1-1:1.29.0 Energy accumulated from the beginning of the loggingintervall of logger #1 (Time integral 5 in OBISterminology)

C = 2, with same variants as C = 1 Active ExportC = 3, only with D = 8 and 29. Reactive ImportC = 4, only with D = 8 and 29. Reactive Export1-x:0.8.0 External register (x 1) signifies which pulse input to read. X = 2 gives

pulse input #1 etc.0.0.0 Meter serialnumber

0.1.0 VZ Billing period (historical register) counter.0.1.2*f Timestamp Timestamp of billing period identified by f.0.9.1 Local time0.9.2 Local dateP.1 Logger #1 Implementation follows the VDN Lastenheft

specification except for:status word will always read 00only logging of registers listed above will be supportedi.e. averages of instantaneous values will be excluded.


29/33


29

DLMS/COSEM

GeneralCewePrometer supports referencing of COSEM objects using logical (long) names over HDLC. Physical layer uses1 start bit, 8 data bits, no parity and one stop bit.

Supported baud rates depend on the specific port; see CewePrometer User Manual for detai ls.

All three modes of HDLC addressing is supported (1, 2 or 4 byte), but a meter can only be configured with one bytelower HDLC address. The normal restrictions apply for restricted addresses according to the standard.

The upper HDLC address (logical device address) is always 1.

To configure the lower HDLC device address for a meter, connect using CeweConfig and select the Communicationand Security form. The device address is available for configuration as bus address for each communication port(except optical).

SecurityThere are three associations available in CewePrometer. Their characteristics are as follow:

Client ID Security method Access0x10 none Association (0.0.40.0.1.255) and logical device

name (0.0.42.0.0.255)0x11 LLS (password corresponding to meter

access level 1).All meter objects except end billing period script(0.0.10.0.1.255). Clock (0.0.1.0.0.255) secondattribute is read only.

0x12 LLS (password corresponding to meteraccess level 2).

All meter objects including end billing periodscript. Clock can be set.

Supported objectsThis section describes what COSEM objects are provided by CewePrometer over DLMS COSEM.

Unless otherwise stated, all object values are returned as double precision floating point numbers (IEEE 754) in thebase (SI) unit. For example, the energy register for active import (1.1.1.8.0.255) is given in Wh.

Abstract objectsThe following general abstract objects are available:

Obis code Object Interface class0.0.1.0.0.255 Clock Clock

0.0.10.0.1.255 End billing period script Script table0.0.40.0.1.255 Association Association LN0.0.42.0.0.255 Logical device name Register

The script 0.0.10.1.255 is hidden, i.e. the attribute 2 cannot be read.


30/33


30

Electricity objects

Miscellaneous

Obis code Object Interface class Supported from FW1.0.99.1.0.255 Load Profile (Logger) 1 Profile Generic1.0.99.2.0.255 Load Profile (Logger) 2 Profile Generic 2.1.x1.0.99.98.0.255 User Event Log Profile Generic1.0.99.98.1.255 System Event Log Profile Generic1.1.0.1.0.255 Billing period counter Register1.1.0.1.1.255 Number of billing periods Register1.1.0.1.2.x Timestamp for VZ = x,

1 x 15Register

1.1.0.1.2.255 Timestamp for last billingperiod

Register

1.1.0.2.0.255 Firmware version Register 2.1.x

Load profiles (loggers)

The load profiles can be read as a whole or by using selective access on attribute 2. The selective access must be byrange (access selector 1) and use the clock (obis 0.0.1.0.0.255, attr 2) as restricting object.

A load profile (logger) entry always contains the timestamp (clock attribute 2) followed by a 16 bit status object. SeeCewePrometer documentation for the meaning of the status bits. Then follows the data configured to be capturedaccording to the meters configuration.

What to store in the respective load profile is configured under the Logger node in CeweConfig.

Attribute 3 on a profile generic object supplies a list of the objects captured by the profile. There are a number ofobjects not otherwise supported over COSEM DLMS that can be stored in a profile, as described in the followingtable:

Obis Object1.1.128.8.0.255 QI + QIII1.1.129.8.0.255 QII + QIV1.1.130.7.0.255 Average of phase voltages (only 3-element meter)1.1.131.7.0.255 Average of all three currents.1.1.132.7.0.255 3-element meter: L1- L2 main voltage.

2-element meter: Not used (L1-L2 has the code 1.1.32.7.0.255)1.1.132.7.1.255 3-element meter: L2-L3 main voltage.

2-element meter: Not used (L2-L3 has the code 1.1.72.7.0.255)1.1.132.7.2.255 3-element meter: L1-L3 main voltage.

2-element meter: L1-L3 main voltage.1.1.132.7.3.255 Average of all three main voltages.0.1.96.10.1.255 The status word in a load profile.1.1.c.128.e.255 Max instant value in integration period.1.1.c.129.e.255 Min instant value in integration period.1.1.c.130.e.255 Momentaneous instant value at end of integration period.1.1.t.d.124.255 THD, t is one of 12, 32, 52, 72, 11, 31, 51 or 71, and d is one of 7, 128, 129 or 130.1.1.t.d.h.255 Harmonics, where t is one of 12, 32, 52, 72, 11, 31, 51 or 71, and d is one of 7, 128, 129 or 130,

and h is from 1 to 32.c is any of the supported c values for instant values. e is one of 0, 4, 15, 26, 124 or 128 (e0 indicate aphase angle).


31/33


31

Event logsThe rules for access of attribute 2 are the same for event logs as for load profiles (see section 0).

A user event log entry contains a timestamp (clock attribute 2) followed by a 16 bit word describing the event.A system event log entry contains a timestamp (clock attribute 2) followed by a 16 bit status word and then 6

additional bytes with extra data for the event.

EnergyEnergy objects are available as total (E = 0) and depending on meter configuration as four different tariffs (E from 1to 4). CewePrometer supports 8 tariffs, but only the first four are available over the DLMS COSEM protocol in thisversion. The configuration for what energy objects are available as tariffs is set in the Time of Use node, the TOUtab, in CeweConfig.

Energy objects can also be retrieved for the current bill ing period (F = 255) or for one of 15 historical periods (Ffrom 1 to 15). F = VZ identifies the youngest value, F = VZ-1 the second youngest etc, and wrapping around for F< 1. VZ is available in the object with code 1.1.0.1.0.255.

Example, assuming VZ = 4:First (youngest) period F = 4Second F = 3Third F = 2Fourth F = 1Fifth F = 15Sixth F = 14

Depending on meter configuration for Maximum Demand, the following variants of energy register may or may notbe available: highest (D = 6), second highest (D = 16) and third highest (D = 26). These maximum demand variantsare only available with E = 0, but may be available as historical registers (depending on configuration). Theconfiguration for maximum demand is set in the Maximum Demand node of CeweConfig.

Basic energy objects are implemented using the DLMS interface class Register , and Maximum Demand values areimplemented using the DLMS interface class Extended Register .

Energy objects always as A = 1 and B = 1, E and F as described above. Normal energy registers have D = 8, whilemaximum demand has D as described above. C should have a value according to the following table:

C Quantity Also available in 2-element?1 Active + (QI + QIV) Yes2 Active (QII + QIII) Yes3 Reactive + (QI + QII) Yes4 Reactive (QIII + QIV) Yes5 Reactive QI Yes6 Reactive QII Yes7 Reactive QIII Yes8 Reactive QIV Yes9 Apparent + Yes10 Apparent Yes21 Active + L1 No22 Active L1 No41 Active + L2 No42 Active L2 No61 Active + L3 No62 Active L3 No


32/33


32

Instant values

Instant values have A = 1, B = 1, F = 255, and unless otherwise specified, D = 7.

Instant values are implemented using the DLMS interface class Register .

The following instant values are available:

C Quantity Also available in 2-element?1 Total Active Power Yes3 Total Reactive Power Yes9 Total Apparent Power Yes13 Power factor Yes14 Frequency Yes21 Active Power L1 No23 Reactive Power L1 No29 Apparent Power L1 No31 Current L1 Yes32 Voltage L1 Yes, L1-L233 Power Factor L1 No41 Active Power L2 No43 Reactive Power L2 No49 Apparent Power L2 No51 Current L2 No52 Voltage L2 No53 Power Factor L2 No61 Active Power L3 No63 Reactive Power L3 No69 Apparent Power L3 No71 Current L3 Yes72 Voltage L3 Yes, L2 L3

73 Power Factor L3 No

Harmonics and THDHarmonics and THD are available for voltages and currents supported on the meter type (2- or 3-element). E = 0gives the total. E = 1 is the fundamental, E = 2 is 2 nd harmonics, etc up to E = 31.E = 124 gives the THD.

Phase AnglesObis code 1.1.81.7.E.255 gives phase angles as follow:

E Angle4 U1 to I115 U2 to I226 U3 to I3128 Aggregated (manufacturer specific)

None of these are supported on 2-element meters.


33/33


External registers

CewePrometer supports 8 external registers. They are available with obis codes on the format 1.B.1.8.E.F, where 2 B 9 identifies the register, and E and F tariff and billing period respectively (as described in section 0).

NOTE that C must be set to 1 regardless of what quantity is stored in an external register.

ceweprometer serial port meter reading 3.1.4

Documents