A1800 ALPHA Meter: DLMS Protocol Implementation PG42-1019D

A1800 ALPHA® meter
DLMS protocol implementation

PG42-1019D
www.elster.com
Technical manual i Contents
Contents
1 DLMS support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
A1800 ALPHA meter communication overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
DLMS protocol configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Opening modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
COSEM level specifics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
HDLC level specifics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Objects supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
2 Current billing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Class 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Class 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
Scale factor unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
Communication example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
3 Profiling capture objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
1 Logical name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
2 Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3 Capture objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
4 Capture period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
5 Sort method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
6 Sort object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
7 Entries in use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
8 Profile entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
Parameterized reading of LP and IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Load profile in pulses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Load profile in engineering units (cumulative and noncumulative) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
4 Event log objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
1 Logical Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
2 Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
3 Capture objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4 Capture Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
5 Sort Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
6 Sort Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
7 Entries in Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
8 Profile Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Technical manual ii Contents
Parameterized reading of event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2
Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2
5 Instrumentation and demand objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Instrumentation objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5
Class 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5
Communication example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
6 Self reads and previous billing objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
1 Logical Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
2 Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
3 Capture Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
4 Capture Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
5 Sort Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
6 Sort Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
7 Entries in Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
8 Profile Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
Parameterized reading of self reads & previous billing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Self Read or Previous Billing - Total . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3
Self Read or Previous Billing - Tier1/Tier2/Tier3/Tier4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4
Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5
7 Clock objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
8 Script objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2
9 Other objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Other objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Demand objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Connection diagram object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
CT, VT ratio objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Metering point IDs objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Error and warnings objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2
Technical manual iii Contents
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2
Class 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2
Class 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3
Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3
10 ANSI table objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

ANSI table objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Class 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Communication example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Technical manual iv Contents
DLMS implementation 1-1 DLMS support
1 DLMS support
Overview
This document describes the specific implementation of the DLMS protocol, version 6, for
the A1800 ALPHA meter series 110 and later. This document, along with the documents
describing DLMS objects and the DLMS color books, provides information on
communicating with A1800 ALPHA meter series 110 using DLMS protocol.
Note: For the remainder of this document, use of the term “A1800 ALPHA meter” refers
specifically to the series 110 or later unless otherwise indicated.
This implementation of the DLMS protocol is fully compliant with the DLMS standards and
has been tested with the Certification Test Tool (CTT) version 2 provided by the DLMS User
Association (UA), of which Elster is a member.
Related documents
The documents describing DLMS objects and their associated color book name are as
follows:
Table 1-1. DLMS objects documents
Number Date Edition Title
DLMS UA 1000-1 2007 8 COSEM Identification System and Interface Classes (Blue book)
DLMS UA 1000-2 2007 6 DLMS/COSEM architecture and protocols (Green book)
DLMS UA 1001-1 2007 3 DLMS/COSEM Conformance Testing Process (Yellow book)
The standards used in this implementation of DLMS protocol are as follows:

Table 1-2. Standards used in implementation of DLMS standards
Number Date Edition Title
IEC 62056-21 2002 1.0 Electricity metering - Data exchange for meter reading, tariff and
load control - Part 21: Direct local data exchange
load control - Part 46: Data link layer using HDLC protocol
load control - Part 53: COSEM Application layer
load control - Part 61: Object identification system (OBIS)
load control - Part 62: Interface classes
ANSI C12.19 1997 Utility industry end device data tables
IEEE 1377
Revision history
The A1800 ALPHA Meter DLMS Protocol Implementation manual can be referred to by its
document number: PG42-1019. Each release of this manual is designated with a letter,
with the first release being “A,” the second being “B,” and so forth.
The following table lists the releases of this document, the date of release, and any notes
about the changes made.
Release Date Brief description

A 24 April 2009 Initial release of the document.
B 25 September 2009 Corrected “Parameterized reading of LP/IP” to “Parameterized reading of self reads &
previous billing data” on page 6-2.
19 April 2010 Corrected typograhical error on front cover.
C 25 June 2010 Reviewed chapters 3, 4, 5, 6, and 9.
D 14 December 2011 Revised “Load profile in engineering units (cumulative and noncumulative)” on
page 3-3.
A1800 ALPHA meter communication overview

The A1800 has 3 communication ports:
Table 1-3. A1800 ALPHA meter communication ports
Port Data rate Notes
Port 0 (optical) Fixed starting rate of 9600 bps ANSI C12.18 and DLMS protocols are
auto-detected at 9600 bps
Remote port 1 and All-session fixed data rate; data rate ANSI C12.21 and DLMS protocols are
Remote port 2 is configurable auto-detected at the configured data
rate
The ports are configured using the Metercat and MeterHat configuration software. The
frame format is, by default, as follows:
• 8 data bits
• no parity
• 1 stop bit
When using DLMS protocol with IEC 62056-21 Mode E opening, the following frame format
is accepted:
• 7 data bits
• even parity
• 1 stop bit
DLMS protocol configuration

The DLMS protocol can be configured using an Elster software tool. The following
parameters can be configured:
• Remote port data rate can be 2400, 4800, 9600, 14400, 19200 or 28800 bps
• The optical port has a fixed opening data rate of 9600 bps
• Physical address of the DLMS device (for 2/4 bytes addressing)
In case of 1 byte addressing (direct communication), the physical address is
irrelevant.
• DLMS passwords
The A1800 ALPHA meter currently supports only low-level security. Passwords are 20
bytes long.
Opening modes
The A1800 ALPHA meter supports two opening modes:
• IEC 62056-21 Mode E

This mode uses a 7E1 (7 data bits/even parity /1 stop bit) frame format using the
starting data rate for the selected port (that is, the data rate cannot be negotiated).
This continues with Direct HDLC, changing the frame to 8N1 (8 data bits/no parity/
1 stop bit).
• Direct HDLC
This mode uses an 8N1 frame format at the configured data rate, skipping the
Mode E preamble.
COSEM level specifics

Logical names (LN) addressing is implemented; short names addressing is not supported.
The objects list can be downloaded from the Association LN Object List (0.0.40.0.1.255).
Only full selective access is allowed for this object.
There are two clients available through two associations as follows:

Table 1-4. Available clients through associations
Association Client number Security Observations
0 16 None The public client. Only the DLMS mandatory objects, metering
point IDs, detected connection diagram, CT/VT ratio,
accuracy class, and phase rotation objects are available.
1 17 Low level All the supported objects are available.
The maximum COSEM buffer size is 512 bytes. For more information on the COSEM layer,
see the DLMS Blue Book.
HDLC level specifics

The maximum HDLC buffer size is 128 bytes. All 3 types of addressing are available:
• 1 byte
Direct access only; 1 byte for the Logical Device ID (Upper HDLC address)
• 2 bytes
The first byte is the Logical Device ID (Upper HDLC address); the second byte is the
physical ID (Lower HDLC address)
• 4 bytes
The first 2 bytes of the address are the Physical ID (Upper HDLC address); the last 2
bytes are the Logical Device ID (Lower HDLC address)
Figure 1-1. Available HDLC addressing

LSB
Upper HDLC address 1
LSB LSB
Upper HDLC address 0 Lower HDLC address 1
First byte Second byte
LSB LSB LSB LSB
Upper HDLC addr high 0 Upper HDLC addr low 0 Lower HDLC addr high 0 Lower HDLC addr low 1
First byte Second byte Third byte Fourth byte
Only one Logical Device is present in the meter, and the address of the Logical Device is 1.
The Client ID can be one of the following:
• 16
Public client; uses no security; used only for very few objects (see Table 1-4)
• 17
Uses low level security (20 bytes of password configurable through a configuration
software); all the objects supported are present
The following conformance block parameters are supported by the meter:
• Block transfer with get

• Block transfer with set
• Get
• Set
• Selective access (only entry descriptor is supported)
• Action
For more information on the HDLC layer, see the DLMS Green Book.
Note: Not all the objects supported by the meter will appear in the list of objects
downloaded from the Association LN Object List. Depending on the meter
configuration, only a subset of these will be present. For example, if Load Profile is
not enabled, no Load Profile Object will appear in the Object List.
Objects supported
Table 1-5. A1800 ALPHA meter DLMS objects supported

OBIS code
Description
A B C D E F
0 0 1 0 0 255 clock
0 0 40 0 1 255 COSEM objects of IC "Association SN/LN" (DLMS mandatory)
0 0 41 0 0 255 COSEM objects of IC "SAP assignment" (DLMS mandatory)
0 0 42 0 0 255 COSEM logical device name (DLMS mandatory)
0 0 65 0 0 255 ANSI ST0
0 0 65 0 1 255 ANSI ST1
0 0 65 0 2 255 ANSI ST2
0 0 65 0 3 255 ANSI ST3
Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

OBIS code
Description
A B C D E F
0 0 65 0 4 255 ANSI ST4
0 0 65 0 5 255 ANSI ST5
0 0 65 0 6 255 ANSI ST6
0 0 65 0 10 255 ANSI ST10
0 0 65 0 11 255 ANSI ST11
0 0 65 0 13 255 ANSI ST13
0 0 65 0 15 255 ANSI ST15
0 0 65 0 20 255 ANSI ST20
0 0 65 0 21 255 ANSI ST21
0 0 65 0 22 255 ANSI ST22
0 0 65 0 23 255 ANSI ST23
0 0 65 0 24 255 ANSI ST24
0 0 65 0 25 255 ANSI ST25
0 0 65 0 26 255 ANSI ST26
0 0 65 0 27 255 ANSI ST27
0 0 65 0 28 255 ANSI ST28
0 0 65 0 30 255 ANSI ST30
0 0 65 0 31 255 ANSI ST31
0 0 65 0 32 255 ANSI ST32
0 0 65 0 33 255 ANSI ST33
0 0 65 0 50 255 ANSI ST50
0 0 65 0 51 255 ANSI ST51
0 0 65 0 52 255 ANSI ST52
0 0 65 0 53 255 ANSI ST53
0 0 65 0 54 255 ANSI ST54
0 0 65 0 55 255 ANSI ST55
0 0 65 0 60 255 ANSI ST60
0 0 65 0 61 255 ANSI ST61
0 0 65 0 62 255 ANSI ST62
0 0 65 0 63 255 ANSI ST63
0 0 65 0 64 255 ANSI ST64
0 0 65 0 70 255 ANSI ST70
0 0 65 0 71 255 ANSI ST71
0 0 65 0 72 255 ANSI ST72
0 0 65 0 73 255 ANSI ST73
0 0 65 0 74 255 ANSI ST74
0 0 65 0 75 255 ANSI ST75

OBIS code
Description
A B C D E F
0 0 65 0 76 255 ANSI ST76
0 0 65 0 80 255 ANSI ST80
0 0 65 0 81 255 ANSI ST81
0 0 65 0 82 255 ANSI ST82
0 0 65 0 83 255 ANSI ST83
0 0 65 0 84 255 ANSI ST84
0 0 65 0 85 255 ANSI ST85
0 0 65 0 86 255 ANSI ST86
0 0 65 0 87 255 ANSI ST87
0 0 65 0 88 255 ANSI ST88
0 0 65 0 89 255 ANSI ST89
0 0 65 0 90 255 ANSI ST90
0 0 65 0 91 255 ANSI ST91
0 0 65 0 92 255 ANSI ST92
0 0 65 0 93 255 ANSI ST93
0 0 65 0 94 255 ANSI ST94
0 0 65 0 95 255 ANSI ST95
0 0 65 0 96 255 ANSI ST96
0 0 65 0 97 255 ANSI ST97
0 0 65 16 1 255 ANSI MT1
0 0 65 16 2 255 ANSI MT2
0 0 65 16 3 255 ANSI MT3
0 0 65 16 4 255 ANSI MT4
0 0 65 16 5 255 ANSI MT5
0 0 65 16 8 255 ANSI MT8
0 0 65 16 9 255 ANSI MT9
0 0 65 16 10 255 ANSI MT10
0 0 65 16 11 255 ANSI MT11
0 0 65 16 13 255 ANSI MT13
0 0 65 16 14 255 ANSI MT14
0 0 65 16 15 255 ANSI MT15
0 0 65 16 16 255 ANSI MT16
0 0 65 16 17 255 ANSI MT17
0 0 65 16 18 255 ANSI MT18
0 0 65 16 19 255 ANSI MT19
0 0 65 16 21 255 ANSI MT21
0 0 65 16 23 255 ANSI MT23

OBIS code
Description
A B C D E F
0 0 65 16 29 255 ANSI MT29
0 0 65 16 31 255 ANSI MT31
0 0 65 16 32 255 ANSI MT32
0 0 65 16 34 255 ANSI MT34
0 0 65 16 40 255 ANSI MT40
0 0 65 16 42 255 ANSI MT42
0 0 65 16 47 255 ANSI MT47
0 0 65 16 48 255 ANSI MT48
0 0 65 16 49 255 ANSI MT49
0 0 65 16 50 255 ANSI MT50
0 0 65 16 51 255 ANSI MT51
0 0 65 16 52 255 ANSI MT52
0 0 65 16 53 255 ANSI MT53
0 0 65 16 54 255 ANSI MT54
0 0 65 16 55 255 ANSI MT55
0 0 65 16 56 255 ANSI MT56
0 0 65 16 57 255 ANSI MT57
0 0 65 16 58 255 ANSI MT58
0 0 65 16 59 255 ANSI MT59
0 0 65 16 60 255 ANSI MT60
0 0 65 16 61 255 ANSI MT61
0 0 65 16 62 255 ANSI MT62
0 0 65 16 63 255 ANSI MT63
0 0 65 16 64 255 ANSI MT64
0 0 65 16 65 255 ANSI MT65
0 0 65 16 66 255 ANSI MT66
0 0 65 16 67 255 ANSI MT67
0 0 65 16 68 255 ANSI MT68
0 0 65 16 76 255 ANSI MT76
0 0 65 16 77 255 ANSI MT77
0 0 65 16 80 255 ANSI MT80
0 0 65 16 81 255 ANSI MT81
0 0 65 16 82 255 ANSI MT82
0 0 65 16 83 255 ANSI MT83
0 0 65 16 87 255 ANSI MT87
0 0 65 16 88 255 ANSI MT88
0 0 65 16 89 255 ANSI MT89

OBIS code
Description
A B C D E F
0 0 65 16 90 255 ANSI MT90
0 0 65 16 91 255 ANSI MT91
0 0 65 16 92 255 ANSI MT92
0 0 65 16 93 255 ANSI MT93
0 0 65 16 94 255 ANSI MT94
0 0 65 16 95 255 ANSI MT95
0 0 65 16 96 255 ANSI MT96
0 0 65 16 97 255 ANSI MT97
0 0 65 16 98 255 ANSI MT98
0 0 65 17 200 255 ANSI MT200
0 0 65 17 201 255 ANSI MT201
0 0 65 17 202 255 ANSI MT202
0 0 65 17 203 255 ANSI MT203
0 0 65 17 204 255 ANSI MT204
0 0 65 32 13 255 ANSI PST13
0 0 65 32 32 255 ANSI PST32
0 0 65 32 33 255 ANSI PST33
0 0 65 32 54 255 ANSI PST54
0 0 65 48 13 255 ANSI PMT13
0 0 65 48 32 255 ANSI PMT32
0 0 97 97 0 255 Displayed error byte1 (Er1)
0 0 97 97 3 255 Displayed warning byte1 (F1)
0 0 98 1 0 255 Profile generic: Self Read Data Total
0 0 98 1 1 255 Profile generic: Self Read Data Tier1
0 0 98 2 0 255 Profile generic: Previous Billing Data Total
0 0 98 2 1 255 Profile generic: Previous Billing Data Tier1
0 1 10 0 1 255 Script - demand reset

OBIS code
Description
A B C D E F
0 1 10 1 0 255 Script - self read
0 1 10 1 1 255 Script - season change
1 0 96 1 0 255 Metering point ID 1 - Factory serial number
1 0 96 1 1 255 Metering point ID 2 - Meter ID
1 0 96 1 2 255 Metering point ID 3 - Utility serial number
1 0 96 1 3 255 Metering point ID 4 - Account (customer ID)
1 0 96 1 4 255 Metering point ID 5 - Program ID (Active program id)
1 0 96 1 5 255 Metering point ID 6 - Firmware version
1 0 96 1 6 255 Metering point ID 7 - Firmware revision
1 0 99 1 0 255 Profile generic: Load Profile in pulses
1 0 99 1 1 255 Profile generic: Load Profile in eng. units - cumulative
1 0 99 1 2 255 Profile generic: Load Profile in eng. units - noncumulative
1 1 0 2 4 255 Detected connection diagram
1 1 0 4 2 255 CT ratio
1 1 0 4 3 255 VT ratio
1 1 0 8 0 255 Block demand interval
1 1 0 8 1 255 Sliding demand interval
1 1 1 2 0 255 kW Del cumulative, current billing period
1 1 1 2 1 255 kW Del cumulative, rate 1, current billing period
1 1 1 6 0 255 kW Del max, current billing period
1 1 1 6 1 255 kW Del max, rate 1, current billing period
1 1 1 7 0 255 kW - System - active power +
1 1 1 8 0 255 kWh Del, total, current billing period
1 1 1 8 1 255 kWh Del, rate 1, current billing period
1 1 2 2 0 255 kW Rec cumulative, current billing period
1 1 2 2 1 255 kW Rec cumulative, rate 1, current billing period

OBIS code
Description
A B C D E F
1 1 2 6 0 255 kW Rec max, current billing period
1 1 2 6 1 255 kW Rec max, rate 1, current billing period
1 1 2 7 0 255 kW - System - active power -
1 1 2 8 0 255 kWh Rec, total, current billing period
1 1 2 8 1 255 kWh Rec, rate 1, current billing period
1 1 3 2 0 255 kVAR Del cumulative, current billing period
1 1 3 2 1 255 kVAR Del cumulative, rate 1, current billing period
1 1 3 6 0 255 kVAR Del max, current billing period
1 1 3 6 1 255 kVAR Del max, rate 1, current billing period
1 1 3 7 0 255 KVAR - System - reactive power +
1 1 3 8 0 255 kVARh Del, total, current billing period
1 1 3 8 1 255 kVARh Del, rate 1, current billing period
1 1 4 2 0 255 kVAR Rec cumulative, current billing period
1 1 4 2 1 255 kVAR Rec cumulative, rate 1, current billing period
1 1 4 6 0 255 kVAR Rec max, current billing period
1 1 4 6 1 255 kVAR Rec max, rate 1, current billing period

OBIS code
Description
A B C D E F
1 1 4 7 0 255 KVAR - System - reactive power -
1 1 4 8 0 255 kVARh Rec, total, current billing period
1 1 4 8 1 255 kVARh Rec, rate 1, current billing period
1 1 5 2 0 255 kVAR Q1 cumulative, current billing period
1 1 5 2 1 255 kVAR Q1 cumulative, rate 1, current billing period
1 1 5 6 0 255 kVAR Q1 max, current billing period
1 1 5 6 1 255 kVAR Q1 max, rate 1, current billing period
1 1 5 8 0 255 kVARh Q1, total, current billing period
1 1 5 8 1 255 kVARh Q1, rate 1, current billing period

OBIS code
Description
A B C D E F
1 1 9 7 0 255 KVA - System - apparent power (vectorial) +
1 1 10 7 0 255 KVA - System - apparent power (vectorial) -
1 1 13 7 0 255 Power factor - System
1 1 14 7 0 255 Line frequency
1 1 21 7 0 255 kW - Line 1 - active power +
1 1 22 7 0 255 kW - Line 1 - active power -
1 1 23 7 0 255 KVAR - Line 1 - reactive power +

OBIS code
Description
A B C D E F
1 1 24 7 0 255 KVAR - Line 1 - reactive power -
1 1 29 7 0 255 KVA - Line 1 - apparent power +
1 1 30 7 0 255 KVA - Line 1 - apparent power -
1 1 31 7 0 255 Current - Line 1
1 1 31 7 1 255 1st harmonic current - Line 1
1 1 31 7 2 255 2nd harmonic current - Line 1
1 1 31 7 3 255 3rd harmonic current - Line 1
1 1 31 7 4 255 4th harmonic current - Line 1
1 1 31 7 124 255 Current THD - Line 1
1 1 31 7 125 255 Total demand distortion - Line 1
1 1 32 7 0 255 Voltage - Line 1
1 1 32 7 1 255 1st harmonic voltage - Line 1
1 1 32 7 2 255 2nd harmonic voltage - Line 1
1 1 32 7 3 255 3rd harmonic voltage - Line 1
1 1 32 7 4 255 4th harmonic voltage - Line 1

OBIS code
Description
A B C D E F
1 1 32 7 124 255 Voltage THD - Line 1
1 1 33 7 0 255 Power factor - Line 1
1 1 51 7 0 255 Current - Line 2
1 1 51 7 124 255 Current THD - Line 2
1 1 52 7 0 255 Voltage - Line 2

OBIS code
Description
A B C D E F
1 1 52 7 124 255 Voltage THD - Line 2
1 1 71 7 0 255 Current - Line 3
1 1 71 7 124 255 Current THD - Line 3
1 1 72 7 0 255 Voltage - Line 3

OBIS code
Description
A B C D E F
1 1 72 7 124 255 Voltage THD - Line 3
1 1 81 7 0 255 Voltage phase angle - Line 1 - Va to Va
1 1 81 7 4 255 Power factor angle - Line 1
1 1 81 7 10 255 Voltage phase angle - Line 2 - Vb to Va
1 1 81 7 20 255 Voltage phase angle - Line 3 - Vc to Va
1 1 81 7 40 255 Current phase angle - Line 1 - Ia to Va
1 1 81 7 50 255 Current phase angle - Line 2 - Ib to Va
1 1 81 7 60 255 Current phase angle - Line 3 - Ic to Va
1 1 99 98 0 255 Profile generic: Event Log
Error codes
If an error occurs while accessing an object, an error code is returned as follows:
Table 1-6. Error codes
Error code Name Description
0 SUCCESS The reading completed successfully
2 TEMPORARY_FAILURE The operation requested is not possible at the moment. This can happen
while reading a large buffer attribute of a Load Profile (LP) / Instrumentation
Profile (IP) object when a new ANSI LP/IP block is created during
communication
3 READ_WRITE_DENIED The read/write operation is denied
4 OBJECT_UNDEFINED An object or an attribute requested is not defined
9 OBJECT_CLASS_INCONSISTENT Object Interface Class does not match the requested object
11 OBJECT_UNAVAILABLE The LP/IP requested might not be configured or an error occurred
14 DATA_BLOCK_UNAVAILABLE The parameters given in the selective access are invalid
15 LONG_GET_ABORTED The requested block number does not match the block sequence number
16 NO_LONG_GET_IN_PROGRESS A continue block transfer was requested when no block transfer was in
progress
255 OTHER_REASON Other error reasons not listed above
DLMS implementation 2-1 Current billing
2 Current billing
Objects
Table 2-1. Current billing objects

OBIS code
Description IC
A B C D E F
1 1 1 2 0 255 kW Del cumulative, current billing period 3
1 1 1 2 1 255 kW Del cumulative, rate 1, current billing period 3
1 1 2 2 0 255 kW Rec cumulative, current billing period 3
1 1 2 2 0 255 kW Rec cumulative, rate 1, current billing period 3
1 1 3 2 0 255 kvar Del cumulative, current billing period 3
1 1 3 2 0 255 kvar Del cumulative, rate 1, current billing period 3
1 1 4 2 0 255 kvar Rec cumulative, current billing period 3
1 1 4 2 0 255 kvar Rec cumulative, rate 1, current billing period 3
1 1 5 2 0 255 kvar Q1 cumulative, current billing period 3
1 1 5 2 0 255 kvar Q1 cumulative, rate 1, current billing period 3
Table 2-1. Current billing objects (Continued)

OBIS code
Description IC
A B C D E F
1 1 1 6 0 255 kW Del max, current billing period 4
1 1 1 6 1 255 kW Del max, rate 1, current billing period 4
1 1 2 6 0 255 kW Rec max, current billing period 4
1 1 2 6 0 255 kW Rec max, rate 1, current billing period 4
1 1 3 6 0 255 kvar Del max, current billing period 4
1 1 3 6 0 255 kvar Del max, rate 1, current billing period 4
1 1 4 6 0 255 kvar Rec max, current billing period 4
1 1 4 6 0 255 kvar Rec max, rate 1, current billing period 4
1 1 5 6 0 255 kvar Q1 max, current billing period 4
1 1 5 6 0 255 kvar Q1 max, rate 1, current billing period 4

OBIS code
Description IC
A B C D E F
1 1 1 8 0 255 kW Del total, current billing period 3
1 1 1 8 1 255 kW Del, rate 1, current billing period 3
1 1 2 8 0 255 kW Rec total, current billing period 3
1 1 2 8 0 255 kW Rec, rate 1, current billing period 3
1 1 3 8 0 255 kvar Del total, current billing period 3
1 1 3 8 0 255 kvar Del, rate 1, current billing period 3
1 1 4 8 0 255 kvar Rec total, current billing period 3
1 1 4 8 0 255 kvar Rec, rate 1, current billing period 3
1 1 5 8 0 255 kvar Q1 total, current billing period 3
1 1 5 8 0 255 kvar Q1, rate 1, current billing period 3

OBIS code
Description IC
A B C D E F
Attributes
Class 3
Table 2-2. Class 3 attributes

Rights Rights
Attribute Data Type Description
Client 16 Client 17
1. Logical Name Octet-string (6) The OBIS code. - R
2. Value Long64 The value of the object. - R
3. Scale factor unit Scale factor unit type The scalar that has to be applied to the value, - R
represented as an integer, and the unit of
measurement, as an enumeration.
Actual Value = Value × 10scale factor
Class 4

Rights Rights
Client 16 Client 17
3. Scale factor unit Scale factor unit type The scalar that has to be applied to the value, - R
represented as an integer, and the unit of
4. Status Null Not used. - R
5. Capture Time Octet-string (12) The time that corresponded to the maximum value. - R
Scale factor unit
Table 2-4. Scale factor units

Scale factor code Unit Quantity
30 Wh Active energy
27 W Active power (P)
32 varh Reactive energy
29 var Reactive power (Q)
Communication example
Setup
• Port: COM4
• Frame: 8N1
• Data rate: 9600 bps
• HDLC Tx size: 128 bits
• HDLC Rx size: 128 bits
• Windows (Rx/Tx): 1
• HDLC addressing: 2 bytes
• Physical ID: 66
• Client ID: 17
• Logical Device ID: 1
• Authentication level: LOW
• Password: 11111111112222222222
• Conformance block: block transfer with get, block transfer with set, get, set, selective
access, action
• Client max PDU size: 65535
• DLMS version: 6
Traffic
Table 2-5. Symbols used in the communication examples

Symbol Meaning
--> DLMS packet sent by the client (computer)
<-- DLMS packet sent by the server (meter)
==> or <== APDU packets (Not transmitted like this on the physical channel but are part of the DLMS
packets above; composed of data sent over multiple packets)
<++ ASN encoded data (Not sent like this on the physical channel but are composed of data sent
over multiple packets)
Sending HDLC SNRM frame, Source ID:11, Destination Logical ID:1, Destination Physical:42,
Control:93
COM4 --> 7e a0 08 02 85 23 93 03 8e 7e
Received HDLC UA frame, Source Physical ID:42, Source Logical ID:1, Destination:11, Control:73
COM4 <-- 7e a0 1f 23 02 85 73 bf 05 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
Sending AARQ, Application context:1, Authentication mechanism:1, Conformance block:181d, Client

max pdu size:ffff
COM4 ==> 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07 80 8b 07 60 85 74 05 08 02 01 ac 16
80 14 31 31 31 31 31 31 31 31 31 31 32 32 32 32 32 32 32 32 32 32 be 10 04 0e 01 00 00 00 06 5f
1f 04 00 00 18 1d ff ff
Sending HDLC Information frame, Source ID:11, Destination Logical ID:1, Destination Physical:42,
Control:10
COM4 --> 7e a0 51 02 85 23 10 96 1c e6 e6 00 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07
80 8b 07 60 85 74 05 08 02 01 ac 16 80 14 31 31 31 31 31 31 31 31 31 31 32 32 32 32 32 32 32 32
32 32 be 10 04 0e 01 00 00 00 06 5f 1f 04 00 00 18 1d ff ff 97 e7 7e
Received HDLC Information frame, Source Physical ID:42, Source Logical ID:1, Destination:11,
Control:30
COM4 <-- 7e a0 38 23 02 85 30 6d 25 e6 e7 00 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02
01 00 a3 05 a1 03 02 01 00 be 10 04 0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07 d8 d4 7e
Received APDU
COM4 <== 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02 01 00 a3 05 a1 03 02 01 00 be 10 04
0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07
AARE success
Get request, OBIS:1.1.1.6.0.ff, IC:4, Attribute:3
Get request APDU

COM4 ==> c0 01 81 00 04 01 01 01 06 00 ff 03 00
Control:32
COM4 --> 7e a0 1a 02 85 23 32 48 98 e6 e6 00 c0 01 81 00 04 01 01 01 06 00 ff 03 00 60 ab 7e
Control:52
COM4 <-- 7e a0 17 23 02 85 52 14 6f e6 e7 00 c4 01 81 00 02 02 0f fc 16 1b aa cf 7e
Received APDU
COM4 <== c4 01 81 00 02 02 0f fc 16 1b
Get response success
ASN.1 encoded data follows
COM4 <++ 02 02 0f fc 16 1b
Get request APDU

COM4 ==> c0 01 81 00 04 01 01 01 06 00 ff 01 00
Control:54
COM4 --> 7e a0 1a 02 85 23 54 78 9e e6 e6 00 c0 01 81 00 04 01 01 01 06 00 ff 01 00 d0 98 7e
Control:74
COM4 <-- 7e a0 19 23 02 85 74 98 4a e6 e7 00 c4 01 81 00 09 06 01 01 01 06 00 ff 4b 90 7e
Received APDU
COM4 <== c4 01 81 00 09 06 01 01 01 06 00 ff
COM4 <++ 09 06 01 01 01 06 00 ff
Get request APDU

COM4 ==> c0 01 81 00 04 01 01 01 06 00 ff 02 00
Control:76
COM4 --> 7e a0 1a 02 85 23 76 68 9c e6 e6 00 c0 01 81 00 04 01 01 01 06 00 ff 02 00 b8 b2 7e
Control:96
COM4 <-- 7e a0 1a 23 02 85 96 48 93 e6 e7 00 c4 01 81 00 15 00 00 00 00 00 07 0c b0 fb 1a 7e
Received APDU
COM4 <== c4 01 81 00 15 00 00 00 00 00 07 0c b0
COM4 <++ 15 00 00 00 00 00 07 0c b0
Get request APDU

COM4 ==> c0 01 81 00 04 01 01 01 06 00 ff 04 00
Control:98
COM4 --> 7e a0 1a 02 85 23 98 18 92 e6 e6 00 c0 01 81 00 04 01 01 01 06 00 ff 04 00 68 e6 7e
Control:b8
COM4 <-- 7e a0 12 23 02 85 b8 14 01 e6 e7 00 c4 01 81 00 00 46 af 7e
Received APDU
COM4 <== c4 01 81 00 00
COM4 <++ 00
Get request APDU

COM4 ==> c0 01 81 00 04 01 01 01 06 00 ff 05 00
Control:ba
COM4 --> 7e a0 1a 02 85 23 ba 08 90 e6 e6 00 c0 01 81 00 04 01 01 01 06 00 ff 05 00 b0 ff 7e
Control:da
COM4 <-- 7e a0 1f 23 02 85 da 74 3d e6 e7 00 c4 01 81 00 09 0c 07 d8 0b 0b 00 00 36 00 00 00
00 00 cb 6d 7e
Received APDU
COM4 <== c4 01 81 00 09 0c 07 d8 0b 0b 00 00 36 00 00 00 00 00
COM4 <++ 09 0c 07 d8 0b 0b 00 00 36 00 00 00 00 00
Sending HDLC DISC frame, Source ID:11, Destination Logical ID:1, Destination Physical:42,
Control:53
COM4 --> 7e a0 08 02 85 23 53 0f 48 7e
COM4 <-- 7e a0 1f 23 02 85 73 bf 05 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
DLMS implementation 3-1 Profiling capture objects
3 Profiling capture objects
For load profiling and instrumentation profiling
Attributes
All attributes have the following rights based on which client is being used:
• no rights when used with client 16 (the public client)

• read rights when client 17 is used
1 Logical name
Table 3-1. Logical name OBIS codes
OBIS code
Description
A B C D E F
1 0 99 1 0 255 Load Profile in pulses
1 0 99 1 1 255 Load profile in engineering units, cumulative
1 0 99 1 2 255 Load profile in engineering units, non-cumulative
1 0 99 128 0 255 Instrumentation Profile, set 1
1 0 99 129 0 255 Instrumentation Profile, set 2
2 Buffer
The data represents the intervals specified in the request. The invalid (skipped) intervals are
also present in the profile buffer and are filled with 0s. Each entry has multiple fields., and
those fields are as following:
1. capture time
• OBIS code: 0, 0, 1, 0, 0, 255
• the timestamp of the interval
2. Channel data for each channel which is configured and supported
• OBIS code: depending on LP/IP configuration
3 Capture objects
The following capture objects are present:
Table 3-2. Capture objects present
OBIS code Class ID Attribute
Description
A B C D E F
0 0 1 0 0 255 8 2 Time stamp of the interval
a b c d e 255 3 2 Channel data (maximum 8 channels for LP) (see Sources below)
4 Capture period
The profile interval size in seconds.
5 Sort method
The entries are presented in a LIFO (last-in first-out) fashion, with the newest entry first.
6 Sort object
No object to sort by.
7 Entries in use
The number of intervals (including some invalid ones) that the profile object has recorded
so far and are available through the buffer attribute.
8 Profile entries
The maximum number of entries the profile object can record. It depends on meter
configuration.
Parameterized reading of LP and IP

The profile buffer entries can be retrieved by either demanding the whole data (using 0x00
as access selector) or by doing a selective access request. In the latter case, the only
supported selective access type is the entry descriptor (using 0x02 as access selector).
Specifying the desired data is done using selectors as follows:
Table 3-3. Parameterized reading of profile selectors
Selector Description
From Entry 0: from the most recent entry
X: from entry number x, the 1st entry being the most recent entry
To Entry 0: to the oldest entry
X: to entry number x, the 1st entry being the most recent entry
From Value 0: from the start of the capture objects (time stamp)
X: from capture object number x, the 1st one being the time stamp
To Value 0: to the last capture object
X: to capture object number x, the 1st one being the time stamp
Error codes
When an error occurs during the reading of the requested profile, an error code is returned
as follows:
Table 3-4. Profile reading error codes
Error code Name Description
0 SUCCESS The reading completed successfully
2 TEMPORARY_FAILURE A new ANSI block was created making reading attribute buffer of the
capture object impossible in this attempt
3 READ_WRITE_DENIED The read/write operation is denied
11 OBJECT_UNAVAILABLE The LP/IP requested might not be configured or an error occurred
14 DATA_BLOCK_UNAVAILABLE The parameters given in the selective access are invalid
Sources
Load profile in pulses
Source
Quantity
Capture object
The final value is obtained by multiplying the quantity in pulses with the multiplier and
scaling it with the scale factor:
Actual value = LP value × Multiplier × 10 scale factor
where:
• Actual value is in engineering units

• LP value is in pulses
Load profile in engineering units (cumulative and noncumulative)

Source
Capture Object Quantity
A B C D E F
The final value is obtained by scaling the value with the scale factor:
Actual value = LP value × 10 scale factor
where:
• Actual value is in engineering units

• LP value is in engineering units
DLMS implementation 4-1 Event log objects
4 Event log objects
Attributes
All attributes have no rights when used with client 16 (the public client) and read rights
when client 17 is used.
1 Logical Name
OBIS codes
Description
A B C D E F
1 1 99 98 0 255 Events Log
2 Buffer
The number of buffer entries for the Event Log Object is determined by the maximum
number programmed in the meter and by the number of events recorded so far. Each
entry has multiple fields. One of the fields is the following:
1. Capture Time
• OBIS code: 0, 0, 1, 0, 0, 255
• The timestamp of the entry
3 Capture objects
OBIS codes
Class ID Attribute Description
A B C D E F
0 0 1 0 0 255 8 2 Time Stamp of the entry
4 Capture Period
No capture period is available because events are triggered by a calendar entry or by a
button press.
5 Sort Method
6 Sort Object
7 Entries in Use
This represents the number of Event Log entries available.
8 Profile Entries
This represents the maximum number of Event Log entries that can be stored.
Parameterized reading of event log

as access selector) or by doing a selective access request. In the latter case the only
From Entry 0 - from the most recent entry
X - from entry number 'x', the 1st entry being the most recent entry
To Entry 0 - to the oldest entry
X - to entry number 'x', the 1st entry being the most recent entry
From Value 0 - from the start of the capture objects (time stamp)
X - from capture object number 'x', the 1st one being the time stamp
To Value 0 - to the last capture object
X - to capture object number 'x', the 1st one being the time stamp
Setup
• Port: COM4
• Frame: 8N1
• Physical ID: 88
• Client ID: 17
• Password: 01234567890123456789
access, action
• DLMS version: 6
• No selective access used
Traffic

Symbol Meaning
--> DLMS packet sent by the client

Symbol Meaning
Control:93
COM4 --> 7e a0 08 02 b1 23 93 cc 6b 7e
COM4 <-- 7e a0 1f 23 02 b1 73 7d d4 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e

max pdu size:ffff
COM4 ==> 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07 80 8b 07 60 85 74 05 08 02 01 ac 16
80 14 30 31 32 33 34 35 36 37 38 39 30 31 32 33 34 35 36 37 38 39 be 10 04 0e 01 00 00 00 06 5f
1f 04 00 00 18 1d ff ff
Control:10
COM4 --> 7e a0 51 02 b1 23 10 59 f9 e6 e6 00 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07
80 8b 07 60 85 74 05 08 02 01 ac 16 80 14 30 31 32 33 34 35 36 37 38 39 30 31 32 33 34 35 36 37
38 39 be 10 04 0e 01 00 00 00 06 5f 1f 04 00 00 18 1d ff ff 84 94 7e
Control:30
COM4 <-- 7e a0 38 23 02 b1 30 af f4 e6 e7 00 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02
01 00 a3 05 a1 03 02 01 00 be 10 04 0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07 d8 d4 7e
Received APDU
COM4 <== 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02 01 00 a3 05 a1 03 02 01 00 be 10 04
0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07
AARE success
Get request APDU

COM4 ==> c0 01 81 00 07 01 01 63 62 00 ff 02 00
Control:32
COM4 --> 7e a0 1a 02 b1 23 32 87 7d e6 e6 00 c0 01 81 00 07 01 01 63 62 00 ff 02 00 fb 67 7e
Control:52
COM4 <-- 7e a0 2c 23 02 b1 52 eb 2d e6 e7 00 c4 01 81 00 01 01 02 04 09 0c 07 d9 02 18 00 0b
04 18 00 00 00 00 12 00 01 12 00 02 12 00 12 e4 7b 7e
Received APDU
COM4 <== c4 01 81 00 01 01 02 04 09 0c 07 d9 02 18 00 0b 04 18 00 00 00 00 12 00 01 12 00 02
12 00 12

COM4 <++ 01 01 02 04 09 0c 07 d9 02 18 00 0b 04 18 00 00 00 00 12 00 01 12 00 02 12 00 12

Get request APDU

COM4 ==> c0 01 81 00 07 01 01 63 62 00 ff 03 00
Control:54
COM4 --> 7e a0 1a 02 b1 23 54 b7 7b e6 e6 00 c0 01 81 00 07 01 01 63 62 00 ff 03 00 23 7e 7e
Control:74
COM4 <-- 7e a0 5b 23 02 b1 74 f0 4c e6 e7 00 c4 01 81 00 01 04 02 04 12 00 08 09 06 00 00 01
00 00 ff 0f 02 12 00 00 02 04 12 00 01 09 06 00 00 60 81 00 ff 0f 02 12 00 00 02 04 12 00 01 09
06 00 00 60 81 01 ff 0f 02 12 00 00 02 04 12 00 01 09 06 00 00 60 81 02 ff 0f 02 12 00 00 ca bb 7e
Received APDU
COM4 <== c4 01 81 00 01 04 02 04 12 00 08 09 06 00 00 01 00 00 ff 0f 02 12 00 00 02 04 12 00
01 09 06 00 00 60 81 00 ff 0f 02 12 00 00 02 04 12 00 01 09 06 00 00 60 81 01 ff 0f 02 12 00 00
02 04 12 00 01 09 06 00 00 60 81 02 ff 0f 02 12 00 00

COM4 <++ 01 04 02 04 12 00 08 09 06 00 00 01 00 00 ff 0f 02 12 00 00 02 04 12 00 01 09 06 00
00 60 81 00 ff 0f 02 12 00 00 02 04 12 00 01 09 06 00 00 60 81 01 ff 0f 02 12 00 00 02 04 12 00
01 09 06 00 00 60 81 02 ff 0f 02 12 00 00
Get request APDU

COM4 ==> c0 01 81 00 07 01 01 63 62 00 ff 04 00
Control:76
COM4 --> 7e a0 1a 02 b1 23 76 a7 79 e6 e6 00 c0 01 81 00 07 01 01 63 62 00 ff 04 00 2b 33 7e
Control:96
COM4 <-- 7e a0 16 23 02 b1 96 ba 35 e6 e7 00 c4 01 81 00 06 00 00 00 00 7b df 7e
Received APDU
COM4 <== c4 01 81 00 06 00 00 00 00

COM4 <++ 06 00 00 00 00
Get request APDU

COM4 ==> c0 01 81 00 07 01 01 63 62 00 ff 07 00
Control:98
COM4 --> 7e a0 1a 02 b1 23 98 d7 77 e6 e6 00 c0 01 81 00 07 01 01 63 62 00 ff 07 00 43 19 7e
Control:b8
COM4 <-- 7e a0 16 23 02 b1 b8 c6 fd e6 e7 00 c4 01 81 00 06 00 00 00 01 f2 ce 7e
Received APDU
COM4 <== c4 01 81 00 06 00 00 00 01

COM4 <++ 06 00 00 00 01
Get request APDU

COM4 ==> c0 01 81 00 07 01 01 63 62 00 ff 08 00
Control:ba
COM4 --> 7e a0 1a 02 b1 23 ba c7 75 e6 e6 00 c0 01 81 00 07 01 01 63 62 00 ff 08 00 8b 9a 7e
Control:da
COM4 <-- 7e a0 16 23 02 b1 da d2 bd e6 e7 00 c4 01 81 00 06 00 00 00 10 fa cf 7e
Received APDU
COM4 <== c4 01 81 00 06 00 00 00 10

COM4 <++ 06 00 00 00 10
Control:53
COM4 --> 7e a0 08 02 b1 23 53 c0 ad 7e
COM4 <-- 7e a0 1f 23 02 b1 73 7d d4 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
DLMS implementation 5-1 Instrumentation and demand objects
5 Instrumentation and demand objects
Instrumentation objects
Table 5-1. Instrumentation objects

Object OBIS
Description IC
A B C D E F
1 1 1 7 0 255 kW - System - active power + 3
1 1 2 7 0 255 kW - System - active power - 3
1 1 3 7 0 255 KVAR - System - reactive power + 3
1 1 4 7 0 255 KVAR - System - reactive power - 3
1 1 9 7 0 255 KVA - System - apparent power (vectorial) + 3
1 1 10 7 0 255 KVA - System - apparent power (vectorial) - 3
1 1 13 7 0 255 Power factor - System 3
1 1 14 7 0 255 Line frequency 3
1 1 21 7 0 255 kW - Line 1 - active power + 3
1 1 22 7 0 255 kW - Line 1 - active power - 3
1 1 23 7 0 255 KVAR - Line 1 - reactive power + 3
1 1 24 7 0 255 KVAR - Line 1 - reactive power - 3
1 1 29 7 0 255 KVA - Line 1 - apparent power + 3
1 1 30 7 0 255 KVA - Line 1 - apparent power - 3
1 1 31 7 0 255 Current - Line 1 3
1 1 31 7 1 255 1st harmonic current - Line 1 3
1 1 31 7 2 255 2nd harmonic current - Line 1 3
1 1 31 7 3 255 3rd harmonic current - Line 1 3
1 1 31 7 4 255 4th harmonic current - Line 1 3

Object OBIS
Description IC
A B C D E F
1 1 31 7 124 255 Current THD - Line 1 3
1 1 31 7 125 255 Total demand distortion - Line 1 3
1 1 32 7 0 255 Voltage - Line 1 3
1 1 32 7 1 255 1st harmonic voltage - Line 1 3
1 1 32 7 2 255 2nd harmonic voltage - Line 1 3
1 1 32 7 3 255 3rd harmonic voltage - Line 1 3
1 1 32 7 4 255 4th harmonic voltage - Line 1 3
1 1 32 7 124 255 Voltage THD - Line 1 3
1 1 33 7 0 255 Power factor - Line 1 3
1 1 51 7 0 255 Current - Line 2 3

Object OBIS
Description IC
A B C D E F
1 1 51 7 124 255 Current THD - Line 2 3
1 1 52 7 0 255 Voltage - Line 2 3
1 1 52 7 124 255 Voltage THD - Line 2 3
1 1 71 7 0 255 Current - Line 3 3

Object OBIS
Description IC
A B C D E F
1 1 71 7 124 255 Current THD - Line 3 3
1 1 72 7 0 255 Voltage - Line 3 3
1 1 72 7 124 255 Voltage THD - Line 3 3
1 1 81 7 0 255 Voltage phase angle - Line 1 - Va to Va 3
1 1 81 7 4 255 Power factor angle - Line 1 3
1 1 81 7 10 255 Voltage phase angle - Line 2 - Vb to Va 3
1 1 81 7 20 255 Voltage phase angle - Line 3 - Vc to Va 3

Object OBIS
Description IC
A B C D E F
1 1 81 7 40 255 Current phase angle - Line 1 - Ia to Va 3
1 1 81 7 50 255 Current phase angle - Line 2 - Ib to Va 3
1 1 81 7 60 255 Current phase angle - Line 3 - Ic to Va 3
1 1 140 7 0 255 KVA - System - apparent power (arithmetic) + 3
1 1 143 7 0 255 Power factor - system arithmetic 3
1 1 144 7 0 255 KVAR - vectorial system - reactive power + 3
1 1 146 7 0 255 KVAR - signed vectorial system - reactive power 3
1 1 147 7 0 255 Vectorial power factor angle - System 3
Attributes
Class 3

Rights Rights
Client 16 Client 17
1. Logical Octet-string (6) The OBIS code. - R
Name
3. Scale factor Scale factor- The scale factor that has to be applied to the - R
unit type value, represented as an integer, and the unit of
Actual value = Value × Multiplier × 10 Scale factor
where:
• Acutal value is in engineering units

• the scale factor is the 3rd attribute of the instrumentation object
Scale factor Unit

30 Wh Active energy
27 W Active power (P)
32 VARh Reactive energy
29 VAR Reactive power (Q)

28 VA Apparent power (S)
33 A Current (I)
35 V Voltage (U)
56 % Percentage
8 ° (phase) angle
44 Hz Frequency (f, ω)
255 Count No unit, integer count
Setup
• Port: COM4
• Frame: 8N1
• Physical ID: 55
• Client ID: 17
• Authentication level: Low
• Password: 00000000000000000000
access, action
• DLMS version: 6
Traffic

Symbol Meaning
Sending HDLC SNRM frame, Source ID:11, Destination Logical ID:1

Destination Physical:37, Control:93
COM4 --> 7e a0 08 02 6f 23 93 d8 f4 7e
Received HDLC UA frame, Source Physical ID:37, Source Logical ID:1

Destination:11, Control:73
COM4 <-- 7e a0 1f 23 02 6f 73 56 11 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
Sending AARQ, Application context:1, Authentication mechanism:1

Conformance block:181d, Client max pdu size:ffff
COM4 ==> 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07 80 8b 07 60 85 74 05 08 02 01 ac 16
80 14 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 be 10 04 0e 01 00 00 00 06 5f
1f 04 00 00 18 1d ff ff
Sending HDLC Information frame, Source ID:11, Destination Logical ID:1

COM4 --> 7e a0 51 02 6f 23 10 4d 66 e6 e6 00 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07
80 8b 07 60 85 74 05 08 02 01 ac 16 80 14 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
30 30 be 10 04 0e 01 00 00 00 06 5f 1f 04 00 00 18 1d ff ff e0 87 7e
Received HDLC Information frame, Source Physical ID:37, Source Logical ID:1
COM4 <-- 7e a0 38 23 02 6f 30 84 31 e6 e7 00 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02
01 00 a3 05 a1 03 02 01 00 be 10 04 0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07 d8 d4 7e
Received APDU
COM4 <== 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02 01 00 a3 05 a1 03 02 01 00 be 10 04
0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07
AARE success
Get request, OBIS:1.1.e.7.0.ff, IC:3, Attribute:3
Get request APDU

COM4 ==> c0 01 81 00 03 01 01 0e 07 00 ff 03 00

COM4 --> 7e a0 1a 02 6f 23 32 93 e2 e6 e6 00 c0 01 81 00 03 01 01 0e 07 00 ff 03 00 4f 74 7e
COM4 <-- 7e a0 17 23 02 6f 52 fd 7b e6 e7 00 c4 01 81 00 02 02 0f fc 16 2c 96 8a 7e
Received APDU
COM4 <== c4 01 81 00 02 02 0f fc 16 2c
COM4 <++ 02 02 0f fc 16 2c
Get request APDU

COM4 ==> c0 01 81 00 03 01 01 0e 07 00 ff 01 00

COM4 --> 7e a0 1a 02 6f 23 54 a3 e4 e6 e6 00 c0 01 81 00 03 01 01 0e 07 00 ff 01 00 ff 47 7e
COM4 <-- 7e a0 19 23 02 6f 74 71 5e e6 e7 00 c4 01 81 00 09 06 01 01 0e 07 00 ff 6e 78 7e
Received APDU
COM4 <== c4 01 81 00 09 06 01 01 0e 07 00 ff
COM4 <++ 09 06 01 01 0e 07 00 ff

Get request APDU

COM4 ==> c0 01 81 00 03 01 01 0e 07 00 ff 02 00

COM4 --> 7e a0 1a 02 6f 23 76 b3 e6 e6 e6 00 c0 01 81 00 03 01 01 0e 07 00 ff 02 00 97 6d 7e
COM4 <-- 7e a0 1a 23 02 6f 96 a1 87 e6 e7 00 c4 01 81 00 14 00 00 00 00 00 07 a0 d1 d6 23 7e
Received APDU
COM4 <== c4 01 81 00 14 00 00 00 00 00 07 a0 d1
COM4 <++ 14 00 00 00 00 00 07 a0 d1
Sending HDLC DISC frame, Source ID:11, Destination Logical ID:1

COM4 --> 7e a0 08 02 6f 23 53 d4 32 7e

COM4 <-- 7e a0 1f 23 02 6f 73 56 11 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
DLMS implementation 6-1 Self reads and previous billing objects
6 Self reads and previous billing objects
Attributes
All attributes have no rights when used with client 16 (the public client) and read rights
when client 17 is used.
1 Logical Name
OBIS codes
Description
A B C D E F
0 0 98 1 0 255 Self Read Data - Total (for all tiers)
0 0 98 1 1 255 Self Read Data - Tier 1
0 0 98 2 0 255 Previous Billing Data - Total (for all tiers)
0 0 98 2 1 255 Previous Billing Data - Tier 1
2 Buffer
The number of buffer entries for the Self Read Object is determined by the maximum
number programmed in the meter and by the number of self reads performed. The
Previous Billing Object has maximum of one entry. Each entry has a time stamp and data
as described below:
1. Capture Time
• OBIS code: 0, 0, 1, 0, 0, 255
• the time stamp of the entry
2. Data for each configured quantity (summation, demand, maximum demand). If
maximum demand is configured, then 2 objects with the same OBIS code (the OBIS
code of that maximum demand object) and different attributes will be provided, one
containing the actual data and another containing the time stamp when that
maximum demand occurred.
3 Capture Objects
OBIS codes Class ID Attribute

Description
A B C D E F
0 0 1 0 0 255 8 2 Time Stamp of the entry
1 1 c d 0 255 3 2 Data for summation or demand (see Sources below)
1 1 c d 0 255 4 2 Data for maximum demand (see Sources below)
1 1 c d 0 255 4 5 The time stamp when maximum demand occurred (see
Sources below)
4 Capture Period
No capture period is available.
5 Sort Method
6 Sort Object
7 Entries in Use
For Self Reads, this represents the number of self reads available. For Previous Billing this
will always be 1.
8 Profile Entries
For Self Reads, this represents the maximum number of self reads that can be recorded.
For Previous Billing this will always be 1.
Parameterized reading of self reads & previous billing data

as access selector) or by doing a selective access request. In the latter case the only
Table 6-1.
From Entry 0 - from the most recent entry
X - from entry number 'x', the 1st entry being the most recent entry
To Entry 0 - to the oldest entry
X - to entry number 'x', the 1st entry being the most recent entry
From Value 0 - from the start of the capture objects (time stamp)
X - from capture object number 'x', the 1st one being the time stamp
To Value 0 - to the last capture object
X - to capture object number 'x', the 1st one being the time stamp
Sources
Self Read or Previous Billing - Total
Source
Capture object Quantity
A B C D E F
1 1 1 2 0 255 kW Del cumulative, current billing period
1 1 1 6 0 255 kW Del max, current billing period
1 1 2 2 0 255 kW Rec cumulative, current billing period
1 1 2 6 0 255 kW Rec max, current billing period
1 1 3 2 0 255 kVAR Del cumulative, current billing period
1 1 3 6 0 255 kVAR Del max, current billing period
1 1 4 2 0 255 kVAR Rec cumulative, current billing period
1 1 4 6 0 255 kVAR Rec max, current billing period
Self Read or Previous Billing - Tier1/Tier2/Tier3/Tier4
Source Capture object

Description
A B C D E F A B C D E F
1 1 1 2 e 255 1 1 1 2 0 255 kW Del cumulative, current billing period, rate e
1 1 1 6 e 255 1 1 1 6 0 255 kW Del max, current billing period, rate e
1 1 1 8 e 255 1 1 1 8 0 255 kWh Del current billing period, rate e
Source Capture object

Description
A B C D E F A B C D E F
1 1 2 2 e 255 1 1 2 2 0 255 kW Rec cumulative, current billing period, rate e
1 1 2 6 e 255 1 1 2 6 0 255 kW Rec max, current billing period, rate e
1 1 2 8 e 255 1 1 2 8 0 255 kWh Rec current billing period, rate e
1 1 3 2 e 255 1 1 3 2 0 255 kVAR Del cumulative, current billing period, rate e
1 1 3 6 e 255 1 1 3 6 0 255 kVAR Del max, current billing period, rate e
1 1 3 8 e 255 1 1 3 8 0 255 kVARh Del current billing period, rate e
1 1 4 2 e 255 1 1 4 2 0 255 kVAR Rec cumulative, current billing period, rate e
1 1 4 6 e 255 1 1 4 6 0 255 kVAR Rec max, current billing period, rate e
1 1 4 8 e 255 1 1 4 8 0 255 kVARh Rec current billing period, rate e
1 1 5 2 e 255 1 1 5 2 0 255 kVAR Q1 cumulative, current billing period, rate e
1 1 5 6 e 255 1 1 5 6 0 255 kVAR Q1 max, current billing period, rate e
1 1 5 8 e 255 1 1 5 8 0 255 kVARh Q1 current billing period, rate e
Note: “e" represents the tier number (1≤e≤4).
Setup
• Port: COM4
• Frame: 8N1
• Physical ID: 55
• Client ID: 17
• Password: 00000000000000000000
access, action
• DLMS version: 6
• Using selective access: from entry 1; to entry 1; from value 1; to value 3
Traffic

Symbol Meaning
Control:93
COM4 --> 7e a0 08 02 6f 23 93 d8 f4 7e
COM4 <-- 7e a0 1f 23 02 6f 73 56 11 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
max pdu size:ffff
COM4 ==> 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07 80 8b 07 60 85 74 05 08 02 01 ac 16
80 14 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 be 10 04 0e 01 00 00 00 06 5f
1f 04 00 00 18 1d ff ff
Control:10
COM4 --> 7e a0 51 02 6f 23 10 4d 66 e6 e6 00 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07
80 8b 07 60 85 74 05 08 02 01 ac 16 80 14 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
30 30 be 10 04 0e 01 00 00 00 06 5f 1f 04 00 00 18 1d ff ff e0 87 7e
Control:30
COM4 <-- 7e a0 38 23 02 6f 30 84 31 e6 e7 00 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02
01 00 a3 05 a1 03 02 01 00 be 10 04 0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07 d8 d4 7e
Received APDU
COM4 <== 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02 01 00 a3 05 a1 03 02 01 00 be 10 04
0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07
AARE success
Get request APDU
COM4 ==> c0 01 81 00 07 00 00 62 01 01 ff 02 01 02 02 04 06 00 00 00 01 06 00 00 00 01 12 00
01 12 00 03
Control:32
COM4 --> 7e a0 2d 02 6f 23 32 9e 06 e6 e6 00 c0 01 81 00 07 00 00 62 01 01 ff 02 01 02 02 04
06 00 00 00 01 06 00 00 00 01 12 00 01 12 00 03 64 47 7e
Control:52
COM4 <-- 7e a0 35 23 02 6f 52 e4 0d e6 e7 00 c4 01 81 00 01 01 02 03 09 0c 07 d9 02 12 00 0a
1a 00 00 00 00 00 14 00 00 00 00 00 00 00 00 14 00 00 00 00 00 00 00 00 25 40 7e
Received APDU
COM4 <== c4 01 81 00 01 01 02 03 09 0c 07 d9 02 12 00 0a 1a 00 00 00 00 00 14 00 00 00 00 00
00 00 00 14 00 00 00 00 00 00 00 00

COM4 <++ 01 01 02 03 09 0c 07 d9 02 12 00 0a 1a 00 00 00 00 00 14 00 00 00 00 00 00 00 00 14
00 00 00 00 00 00 00 00
Get request APDU
COM4 ==> c0 01 81 00 07 00 00 62 01 01 ff 06 00
Control:54
COM4 --> 7e a0 1a 02 6f 23 54 a3 e4 e6 e6 00 c0 01 81 00 07 00 00 62 01 01 ff 06 00 1e ba 7e
Control:74
COM4 <-- 7e a0 23 23 02 6f 74 08 c6 e6 e7 00 c4 01 81 00 02 04 12 00 00 09 06 00 00 00 00 00
00 0f 00 12 00 00 aa 7f 7e
Received APDU
COM4 <== c4 01 81 00 02 04 12 00 00 09 06 00 00 00 00 00 00 0f 00 12 00 00
COM4 <++ 02 04 12 00 00 09 06 00 00 00 00 00 00 0f 00 12 00 00
Get request APDU
COM4 ==> c0 01 81 00 07 00 00 62 01 01 ff 03 00
Control:76
COM4 --> 7e a0 1a 02 6f 23 76 b3 e6 e6 e6 00 c0 01 81 00 07 00 00 62 01 01 ff 03 00 a6 c4 7e
Control:96
COM4 <-- 7e a0 6d 23 02 6f 96 8e a2 e6 e7 00 c4 01 81 00 01 05 02 04 12 00 08 09 06 00 00 01
00 00 ff 0f 02 12 00 00 02 04 12 00 03 09 06 01 01 01 08 01 ff 0f 02 12 00 00 02 04 12 00 03 09
06 01 01 01 02 01 ff 0f 02 12 00 00 02 04 12 00 04 09 06 01 01 01 06 01 ff 0f 02 12 00 00 02 04
12 00 04 09 06 01 01 01 06 01 ff 0f 05 12 00 00 ed 65 7e
Received APDU
COM4 <== c4 01 81 00 01 05 02 04 12 00 08 09 06 00 00 01 00 00 ff 0f 02 12 00 00 02 04 12 00
03 09 06 01 01 01 08 01 ff 0f 02 12 00 00 02 04 12 00 03 09 06 01 01 01 02 01 ff 0f 02 12 00 00
02 04 12 00 04 09 06 01 01 01 06 01 ff 0f 02 12 00 00 02 04 12 00 04 09 06 01 01 01 06 01 ff 0f
05 12 00 00
COM4 <++ 01 05 02 04 12 00 08 09 06 00 00 01 00 00 ff 0f 02 12 00 00 02 04 12 00 03 09 06 01
01 01 08 01 ff 0f 02 12 00 00 02 04 12 00 03 09 06 01 01 01 02 01 ff 0f 02 12 00 00 02 04 12 00
04 09 06 01 01 01 06 01 ff 0f 02 12 00 00 02 04 12 00 04 09 06 01 01 01 06 01 ff 0f 05 12 00 00
Get request APDU
COM4 ==> c0 01 81 00 07 00 00 62 01 01 ff 01 00
Control:98
COM4 --> 7e a0 1a 02 6f 23 98 c3 e8 e6 e6 00 c0 01 81 00 07 00 00 62 01 01 ff 01 00 16 f7 7e
Control:b8
COM4 <-- 7e a0 19 23 02 6f b8 11 52 e6 e7 00 c4 01 81 00 09 06 00 00 62 01 01 ff d0 b6 7e
Received APDU
COM4 <== c4 01 81 00 09 06 00 00 62 01 01 ff
COM4 <++ 09 06 00 00 62 01 01 ff
Get request APDU
COM4 ==> c0 01 81 00 07 00 00 62 01 01 ff 04 00
Control:ba
COM4 --> 7e a0 1a 02 6f 23 ba d3 ea e6 e6 00 c0 01 81 00 07 00 00 62 01 01 ff 04 00 ae 89 7e
Control:da
COM4 <-- 7e a0 16 23 02 6f da f9 78 e6 e7 00 c4 01 81 00 06 00 00 00 00 7b df 7e
Received APDU
COM4 <== c4 01 81 00 06 00 00 00 00
COM4 <++ 06 00 00 00 00
Get request APDU
COM4 ==> c0 01 81 00 07 00 00 62 01 01 ff 05 00
Control:dc
COM4 --> 7e a0 1a 02 6f 23 dc e3 ec e6 e6 00 c0 01 81 00 07 00 00 62 01 01 ff 05 00 76 90 7e
Control:fc
COM4 <-- 7e a0 13 23 02 6f fc 99 1a e6 e7 00 c4 01 81 00 16 02 b6 35 7e
Received APDU
COM4 <== c4 01 81 00 16 02
COM4 <++ 16 02
Get request APDU
COM4 ==> c0 01 81 00 07 00 00 62 01 01 ff 07 00
Control:fe
COM4 --> 7e a0 1a 02 6f 23 fe f3 ee e6 e6 00 c0 01 81 00 07 00 00 62 01 01 ff 07 00 c6 a3 7e
Control:1e
COM4 <-- 7e a0 16 23 02 6f 1e d1 f8 e6 e7 00 c4 01 81 00 06 00 00 00 01 f2 ce 7e
Received APDU
COM4 <== c4 01 81 00 06 00 00 00 01
COM4 <++ 06 00 00 00 01
Get request APDU
COM4 ==> c0 01 81 00 07 00 00 62 01 01 ff 08 00
Control:10
COM4 --> 7e a0 1a 02 6f 23 10 83 e0 e6 e6 00 c0 01 81 00 07 00 00 62 01 01 ff 08 00 0e 20 7e
Control:30
COM4 <-- 7e a0 16 23 02 6f 30 ad 30 e6 e7 00 c4 01 81 00 06 00 00 00 08 33 53 7e
Received APDU
COM4 <== c4 01 81 00 06 00 00 00 08
COM4 <++ 06 00 00 00 08
Control:53
COM4 --> 7e a0 08 02 6f 23 53 d4 32 7e
COM4 <-- 7e a0 1f 23 02 6f 73 56 11 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
DLMS implementation 7-1 Clock objects
7 Clock objects
An instance of the clock interface class handles the information about time and date
stamps. When referenced directly, the clock object specifies the time attribute of the meter.
When it is part of complex structures, such as extended register or profile generic
interfaces, the clock object specifies a time stamp.
Objects
Object OBIS
Description IC
A B C D E F
0 0 1 0 0 255 Clock object 8
Attributes
Attribute Data Type Description Rights Client 16 Rights Client 17

2. Time Octet-string (12) The local time as 12 characters - R/W
(4.1.6.1. Blue Book 8th Edition)
3. Time Zone Long The deviation of local time to GMT, in - R/W
minutes
4. Status Unsigned Same status as in time attribute - R
5. DST start Octet-string - - -
6. DST end Octet-string - - -
7. DST deviation Integer Number of minutes to be corrected - R/W
by a DST time set (max ±120 min)
8. DST enabled Boolean TRUE - DST function enabled - R
9. Clock base Enum Defines where the basic timing - R/W
information comes from
Time Attribute consists of the following bytes:
• year high byte

• year low byte
• month
• day of month
• day of week
• hour
• minute
• second
• hundredths of second
• deviation high byte
• deviation low byte
• clock status
The clock status (as part of the Time attribute or as a separate attribute) is an 8 bit string as
follows:
0. (LSB): invalid value

1. doubtful value
2. different clock base
3. invalid clock status
4. reserved
5. reserved
6. reserved
7. (MSB): daylight saving active
Clock base possible sources:
0. not defined
1. internal crystal
2. mains frequency 50 Hz
3. mains frequency 60 Hz
4. GPS (global positioning system)
5. radio-controlled
Methods
Attribute Description Rights Client 16 Rights Client 17

1. Adjust to quarter - - -
2. Adjust to measuring period - - -
3. Adjust to minute - - -
4. Adjust to present time - - -
5. Preset adjusting time - - -
6.Shift time - - -
Note: The time can be set by writing the Time attribute of the clock, not with its methods.
Setup
• Port: COM4
• Frame: 8N1

• Physical ID: 55
• Client ID: 17
• Password: 00000000000000000000
access, action
• DLMS version: 6
Traffic

Symbol Meaning

COM4 --> 7e a0 08 02 6f 23 93 d8 f4 7e

COM4 <-- 7e a0 1f 23 02 6f 73 56 11 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e

COM4 ==> 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07 80 8b 07 60 85 74 05 08 02 01 ac 16
80 14 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 be 10 04 0e 01 00 00 00 06 5f
1f 04 00 00 18 1d ff ff

COM4 --> 7e a0 51 02 6f 23 10 4d 66 e6 e6 00 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07
80 8b 07 60 85 74 05 08 02 01 ac 16 80 14 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
30 30 be 10 04 0e 01 00 00 00 06 5f 1f 04 00 00 18 1d ff ff e0 87 7e
COM4 <-- 7e a0 38 23 02 6f 30 84 31 e6 e7 00 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02
01 00 a3 05 a1 03 02 01 00 be 10 04 0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07 d8 d4 7e
Received APDU
COM4 <== 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02 01 00 a3 05 a1 03 02 01 00 be 10 04
0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07
AARE success
Get request APDU

COM4 ==> c0 01 81 00 08 00 00 01 00 00 ff 02 00
Control:32
COM4 --> 7e a0 1a 02 6f 23 32 93 e2 e6 e6 00 c0 01 81 00 08 00 00 01 00 00 ff 02 00 65 d7 7e
Control:52
COM4 <-- 7e a0 1f 23 02 6f 52 dd 21 e6 e7 00 c4 01 81 00 09 0c 07 d0 01 01 06 01 17 13 ff fe
d4 01 ba de 7e
Received APDU
COM4 <== c4 01 81 00 09 0c 07 d0 01 01 06 01 17 13 ff fe d4 01
COM4 <++ 09 0c 07 d0 01 01 06 01 17 13 ff fe d4 01

COM4 --> 7e a0 08 02 6f 23 53 d4 32 7e

COM4 <-- 7e a0 1f 23 02 6f 73 56 11 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
DLMS implementation 8-1 Script objects
8 Script objects
Objects
Object OBIS
Description IC
A B C D E F
0 1 10 0 1 255 Performs a demand reset 1
0 1 10 1 0 255 Performs self read 1
0 1 10 1 1 255 Performs a season change 1
Attributes

2. Script Array - R
Methods

1. Execute Unsigned integer - W
Setup
• Port: COM4
• Frame: 8N1
• Physical ID: 55
• Client ID: 17

• Password: 00000000000000000000
access, action
• DLMS version: 6
Traffic

Symbol Meaning

COM4 --> 7e a0 08 02 6f 23 93 d8 f4 7e

COM4 <-- 7e a0 1f 23 02 6f 73 56 11 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e

COM4 ==> 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07 80 8b 07 60 85 74 05 08 02 01 ac 16
80 14 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 be 10 04 0e 01 00 00 00 06 5f
1f 04 00 00 18 1d ff ff

COM4 --> 7e a0 51 02 6f 23 10 4d 66 e6 e6 00 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07
80 8b 07 60 85 74 05 08 02 01 ac 16 80 14 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
30 30 be 10 04 0e 01 00 00 00 06 5f 1f 04 00 00 18 1d ff ff e0 87 7e
COM4 <-- 7e a0 38 23 02 6f 30 84 31 e6 e7 00 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02
01 00 a3 05 a1 03 02 01 00 be 10 04 0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07 d8 d4 7e
Received APDU
COM4 <== 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02 01 00 a3 05 a1 03 02 01 00 be 10 04
0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07
AARE success

COM4 --> 7e a0 1c 02 6f 23 32 0b d9 e6 e6 00 c3 01 81 00 09 00 01 0a 01 00 ff 01 12 00 01 5a
4a 7e
COM4 <-- 7e a0 11 23 02 6f 52 65 40 e6 e7 00 c7 01 81 00 40 f6 7e
Received APDU
COM4 <== c7 01 81 00

COM4 --> 7e a0 08 02 6f 23 53 d4 32 7e

COM4 <-- 7e a0 1f 23 02 6f 73 56 11 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
DLMS implementation 9-1 Other objects
9 Other objects
Other objects
Demand objects
Object OBIS
Description IC
A B C D E F
1 1 0 8 0 255 Block demand interval 3
1 1 0 8 1 255 Sliding demand interval (calculated as 3
demand subinterval * number of subintervals)
Connection diagram object
Object OBIS
Description IC
A B C D E F
1 1 0 2 4 255 Detected connection diagram 1
CT, VT ratio objects
Object OBIS
Description IC
A B C D E F
1 1 0 4 2 255 CT ratio 1
1 1 0 4 3 255 VT ratio 1
Metering point IDs objects
Object OBIS
Description IC
A B C D E F
1 0 96 1 0 255 Factory serial number 1
1 0 96 1 1 255 Meter ID 1
1 0 96 1 2 255 Utility serial number 1
1 0 96 1 3 255 Account 1
1 0 96 1 4 255 Program ID 1
1 0 96 1 5 255 Firmware version 1
Error and warnings objects
Object OBIS
Description IC
A B C D E F
0 0 97 97 0 255 Displayed Error Byte 1 (Error 1) 1
0 0 97 97 3 255 Displayed Warning Byte 1 (Warning 1) 1
Attributes
Class 1

1. Logical Name Octet-string (6) The OBIS code.
2. Value Unsigned-Long 64 The multiplier that has to be applied externally, along with the
scaler, to obtain the value in engineering units
CT/VT Ratio value
Integer The Scalar that must be applied externally, along with the
multiplier, to obtain the value in engineering units
Octet-string (16) Factory serial number
Octet-string (16) Meter ID, Utility serial number, Account
Long-unsigned Program ID
Unsigned Firmware version, Firmware revision
Bit-string One byte represented the code of the Error displayed on the
meter's screen
Connection diagram strings:
Number of elements Service type

2 E 3WD .
1 1PH
3 3WY
4WD
4WY
NOLOCK
Class 3

1. Logical Name Octet-string (6) The OBIS code.
2. Value Long64 The value of the object.
3. Scale factor Scale factor type The scalar that has to be applied to the value, represented as
an integer, and the unit of measurement, as an enumeration.
Setup
• Port: COM4
• Frame: 8N1
• Physical ID: 66
• Client ID: 17
• Password: 11111111112222222222
access, action
• DLMS version: 6
Traffic

Symbol Meaning
Control:93
COM4 --> 7e a0 08 02 85 23 93 03 8e 7e
COM4 <-- 7e a0 1f 23 02 85 73 bf 05 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
max pdu size:ffff
COM4 ==> 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07 80 8b 07 60 85 74 05 08 02 01 ac 16
80 14 31 31 31 31 31 31 31 31 31 31 32 32 32 32 32 32 32 32 32 32 be 10 04 0e 01 00 00 00 06 5f
1f 04 00 00 18 1d ff ff
Control:10
COM4 --> 7e a0 51 02 85 23 10 96 1c e6 e6 00 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07
80 8b 07 60 85 74 05 08 02 01 ac 16 80 14 31 31 31 31 31 31 31 31 31 31 32 32 32 32 32 32 32 32
32 32 be 10 04 0e 01 00 00 00 06 5f 1f 04 00 00 18 1d ff ff 97 e7 7e
Control:30
COM4 <-- 7e a0 38 23 02 85 30 6d 25 e6 e7 00 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02
01 00 a3 05 a1 03 02 01 00 be 10 04 0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07 d8 d4 7e
Received APDU
COM4 <== 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02 01 00 a3 05 a1 03 02 01 00 be 10 04
0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07
AARE success

Get request APDU
COM4 ==> c0 01 81 00 01 00 00 61 61 01 ff 01 00
Control:32
COM4 --> 7e a0 1a 02 85 23 32 48 98 e6 e6 00 c0 01 81 00 01 00 00 61 61 01 ff 01 00 c7 fe 7e
Control:52
COM4 <-- 7e a0 19 23 02 85 52 ac 0e e6 e7 00 c4 01 81 00 09 06 00 00 61 61 01 ff 50 96 7e
Received APDU
COM4 <== c4 01 81 00 09 06 00 00 61 61 01 ff

COM4 <++ 09 06 00 00 61 61 01 ff
Get request APDU

COM4 ==> c0 01 81 00 01 00 00 61 61 01 ff 02 00
Control:54
COM4 --> 7e a0 1a 02 85 23 54 78 9e e6 e6 00 c0 01 81 00 01 00 00 61 61 01 ff 02 00 af d4 7e
Control:74
COM4 <-- 7e a0 14 23 02 85 74 ec 36 e6 e7 00 c4 01 81 00 04 01 01 3c 2b 7e
Received APDU
COM4 <== c4 01 81 00 04 01 01

COM4 <++ 04 01 01
Control:53
COM4 --> 7e a0 08 02 85 23 53 0f 48 7e
COM4 <-- 7e a0 1f 23 02 85 73 bf 05 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
DLMS implementation 10-1 ANSI table objects
10 ANSI table objects
ANSI table objects
Object OBIS
Description IC
A B C D E F
0 0 65 0 0 255 ST 0 - General Configuration Table 26
0 0 65 0 1 255 ST 1 - General Manufacturers Identification Table 26
0 0 65 0 2 255 ST 2 - Device Nameplate Table 26
0 0 65 0 3 255 ST 3 - Mode and Status Table 26
0 0 65 0 4 255 ST 4 - Pending table status 26
0 0 65 0 5 255 ST 5 - Device Identification Table 26
0 0 65 0 6 255 ST 6 - Utility Information Table 26
0 0 65 0 10 255 ST 10 - Maximum dimensions for data sources 26
0 0 65 0 11 255 ST 11 - Actual Sources Limiting Table 26
0 0 65 0 13 255 ST 13 - Demand Control Table 26
0 0 65 0 15 255 ST 15 - Multipliers 26
0 0 65 0 20 255 ST 20 - Dimension Register Table 26
0 0 65 0 21 255 ST 21 - Actual Register Table 26
0 0 65 0 22 255 ST 22 - Data Selection Table 26
0 0 65 0 23 255 ST 23 - Current Register Data Table 26
0 0 65 0 24 255 ST 24 - Previous Season Data Table 26
0 0 65 0 25 255 ST 25 - Previous Demand Reset Data Table 26
0 0 65 0 26 255 ST 26 - Self Read Data Table 26
0 0 65 0 27 255 ST 27 - Present Register Selection Table 26
0 0 65 0 28 255 ST 28 - Present Register Data Table 26
0 0 65 0 30 255 ST 30 - Dimension Display Table 26
0 0 65 0 31 255 ST 31 - Actual Display Table 26
0 0 65 0 32 255 ST 32 - Display Source Table 26
0 0 65 0 33 255 ST 33 - Primary Display List Table 26
0 0 65 0 50 255 ST 50 - Dimension Time and TOU Table 26
0 0 65 0 51 255 ST 51 - Actual Time and TOU Table 26
0 0 65 0 52 255 ST 52 - Clock Table 26
0 0 65 0 53 255 ST 53 - Time Offset Table 26
0 0 65 0 54 255 ST 54 - Calendar Table 26
Object OBIS
Description IC
A B C D E F
0 0 65 0 55 255 ST 55 - Clock State Table 26
0 0 65 0 60 255 ST 60 - Dimension Profile Table 26
0 0 65 0 61 255 ST 61 - Actual Load Profile Table 26
0 0 65 0 62 255 ST 62 - Load Profile Control Table 26
0 0 65 0 63 255 ST 63 - Load Profile Status Table 26
0 0 65 0 64 255 ST 64 - Load Profile Data Set 1 Table 26
0 0 65 0 70 255 ST 70 - Dimension Log Table 26
0 0 65 0 71 255 ST 71 - Actual Dimension Log Table 26
0 0 65 0 72 255 ST 72 - Events Identification Table 26
0 0 65 0 73 255 ST 73 - History Log Control Table 26
0 0 65 0 74 255 ST 74 - History Log Data Table 26
0 0 65 0 75 255 ST 75 - Event Log Control Table 26
0 0 65 0 76 255 ST 76 - Event Log Data Table 26
0 0 65 0 80 255 ST 80 - Dimension User Defined Tables Function Limiting Table 26
0 0 65 0 81 255 ST 81 - Actual User Defined Tables Function Limiting Table 26
0 0 65 0 82 255 ST 82 - User Defined Tables List Table 26
0 0 65 0 83 255 ST 83 - User Defined Tables Selection Table 26
0 0 65 0 84 255 ST 84 - User Defined Tables 26
0 0 65 0 90 255 ST 90 - Dimension Telephone Table 26
0 0 65 0 91 255 ST 91 - Actual Telephone Table 26
0 0 65 0 92 255 ST 92 - Global Parameters Tables for Remote Port 1 26
0 0 65 0 93 255 ST 93 - Originate Parameters Table for Remote Port 1 26
0 0 65 0 94 255 ST 94 - Originate Scheduling Tables for Remote Ports 1 and 2 26
0 0 65 0 95 255 ST 95 - Answer Parameters Table for Remote Ports 1 and 2 26
0 0 65 0 96 255 ST 96 - Call Purpose Table for Remote Ports 1 and 2 26
0 0 65 0 97 255 ST 97 - Call Status Table for Remote Ports 1 and 2 26
0 0 65 16 1 255 MT 1 26
0 0 65 16 2 255 MT 2 26
0 0 65 16 3 255 MT 3 26
0 0 65 16 4 255 MT 4 26
0 0 65 16 5 255 MT 5 26
0 0 65 16 8 255 MT 8 26
0 0 65 16 9 255 MT 9 26
Object OBIS
Description IC
A B C D E F
0 0 65 16 10 255 MT 10 26
0 0 65 16 11 255 MT 11 26
0 0 65 16 13 255 MT 13 26
0 0 65 16 14 255 MT 14 26
0 0 65 16 15 255 MT 15 26
0 0 65 16 16 255 MT 16 26
0 0 65 16 17 255 MT 17 26
0 0 65 16 18 255 MT 18 26
0 0 65 16 19 255 MT 19 26
0 0 65 16 21 255 MT 21 26
0 0 65 16 23 255 MT 23 26
0 0 65 16 29 255 MT 29 26
0 0 65 16 31 255 MT 31 26
0 0 65 16 32 255 MT 32 26
0 0 65 16 34 255 MT 34 26
0 0 65 16 40 255 MT 40 26
0 0 65 16 42 255 MT 42 26
0 0 65 16 47 255 MT 47 26
0 0 65 16 48 255 MT 48 26
0 0 65 16 49 255 MT 49 26
0 0 65 16 50 255 MT 50 26
0 0 65 16 51 255 MT 51 26
0 0 65 16 52 255 MT 52 26
0 0 65 16 53 255 MT 53 26
0 0 65 16 54 255 MT 54 26
0 0 65 16 55 255 MT 55 26
0 0 65 16 56 255 MT 56 26
0 0 65 16 57 255 MT 57 26
0 0 65 16 58 255 MT 58 26
0 0 65 16 59 255 MT 59 26
0 0 65 16 60 255 MT 60 26
0 0 65 16 61 255 MT 61 26
0 0 65 16 62 255 MT 62 26
0 0 65 16 63 255 MT 63 26
0 0 65 16 64 255 MT 64 26
0 0 65 16 65 255 MT 65 26
0 0 65 16 66 255 MT 66 26
0 0 65 16 67 255 MT 67 26
Object OBIS
Description IC
A B C D E F
0 0 65 16 68 255 MT 68 26
0 0 65 16 76 255 MT 76 26
0 0 65 16 77 255 MT 77 26
0 0 65 16 80 255 MT 80 26
0 0 65 16 81 255 MT 81 26
0 0 65 16 82 255 MT 82 26
0 0 65 16 83 255 MT 83 26
0 0 65 16 87 255 MT 87 26
0 0 65 16 88 255 MT 88 26
0 0 65 16 89 255 MT 89 26
0 0 65 16 90 255 MT 90 26
0 0 65 16 91 255 MT 91 26
0 0 65 16 92 255 MT 92 26
0 0 65 16 93 255 MT 93 26
0 0 65 16 94 255 MT 94 26
0 0 65 16 95 255 MT 95 26
0 0 65 16 96 255 MT 96 26
0 0 65 16 97 255 MT 97 26
0 0 65 16 98 255 MT 98 26
0 0 65 17 200 255 MT 200 26
0 0 65 17 201 255 MT 201 26
0 0 65 17 202 255 MT 202 26
0 0 65 17 203 255 MT 203 26
0 0 65 17 204 255 MT 204 26
0 0 65 32 13 255 PST 13 - Pending table ST-13 26
0 0 65 48 13 255 PMT 13 26
0 0 65 48 32 255 PMT 32 26
Attributes
Class 26
Rights Rights
Client 16 Client 17
2. Table ID Long-unsigned The ANSI table ID. Can be a standard or a - R
manufacturer table.
3. Length Double-long- Number of octets in the table buffer. - -
unsigned
4. Buffer Octet-string (variable) An offset based selective access is used, the - R
offset in the table being double-long-unsigned
and the count a long-unsigned
Note: Only selective access is supported (offset, length). Attempting to read the full buffer
without selective access enabled will result in an error code.
Setup
• Port: COM4
• Frame: 8N1
• HDLC Transmit size: 128 bits
• HDLC Receive size: 128 bits
• Physical ID: 66
• Client ID: 17
• Password: 11111111112222222222
access, action
• DLMS version: 6
Traffic

Symbol Meaning
Control:93
COM4 --> 7e a0 08 02 85 23 93 03 8e 7e
COM4 <-- 7e a0 1f 23 02 85 73 bf 05 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
max pdu size:ffff
COM4 ==> 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07 80 8b 07 60 85 74 05 08 02 01 ac 16
80 14 31 31 31 31 31 31 31 31 31 31 32 32 32 32 32 32 32 32 32 32 be 10 04 0e 01 00 00 00 06 5f
1f 04 00 00 18 1d ff ff
Control:10
COM4 --> 7e a0 51 02 85 23 10 96 1c e6 e6 00 60 42 a1 09 06 07 60 85 74 05 08 01 01 8a 02 07
80 8b 07 60 85 74 05 08 02 01 ac 16 80 14 31 31 31 31 31 31 31 31 31 31 32 32 32 32 32 32 32 32
32 32 be 10 04 0e 01 00 00 00 06 5f 1f 04 00 00 18 1d ff ff 97 e7 7e
Control:30
COM4 <-- 7e a0 38 23 02 85 30 6d 25 e6 e7 00 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02
01 00 a3 05 a1 03 02 01 00 be 10 04 0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07 d8 d4 7e
Received APDU
COM4 <== 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02 01 00 a3 05 a1 03 02 01 00 be 10 04
0e 08 00 06 5f 1f 04 00 00 10 1d 02 00 00 07
AARE success
Get request, OBIS:0.0.41.0.1.ff, IC:1a, Attribute:4

Get request APDU
COM4 ==> c0 01 81 00 1a 00 00 41 00 01 ff 04 01 01 02 02 06 00 00 00 00 12 00 20
Control:32
COM4 --> 7e a0 25 02 85 23 32 65 26 e6 e6 00 c0 01 81 00 1a 00 00 41 00 01 ff 04 01 01 02 02
06 00 00 00 00 12 00 20 1b 8c 7e
Control:52
COM4 <-- 7e a0 33 23 02 85 52 95 22 e6 e7 00 c4 01 81 00 09 20 45 45 20 20 41 31 38 30 30 52
20 20 02 00 02 01 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 3e 94 7e
Received APDU
COM4 <== c4 01 81 00 09 20 45 45 20 20 41 31 38 30 30 52 20 20 02 00 02 01 20 20 20 20 20 20
20 20 20 20 20 20 20 20 20 20

COM4 <++ 09 20 45 45 20 20 41 31 38 30 30 52 20 20 02 00 02 01 20 20 20 20 20 20 20 20 20 20
20 20 20 20 20 20
Control:53
COM4 --> 7e a0 08 02 85 23 53 0f 48 7e
COM4 <-- 7e a0 1f 23 02 85 73 bf 05 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00
00 01 53 3b 7e
About Elster
Elster is one of the world’s largest electricity, gas and
water measurement and control providers. Our
offerings include distribution monitoring and control,
advanced smart metering, demand response,
networking and software solutions, and numerous
related communications and services – key
components for enabling consumer choice,
operational efficiency and conservation. Our products
and solutions are widely used by utilities in the
traditional and emerging Smart Grid markets.
With a heritage of more than 170 years of providing
utility solutions, Elster enjoys a reputation as a leading
innovator and has played, and continues to play, an
important role in shaping industry standards with
respect to performance, reliability, accuracy and
functionality.
ALPHA, ALPHA Plus, REX, and EnergyAxis are registered

trademarks. Metercat, AlphaPlus, REX2, REX2-EA, and gREX are
trademarks of Elster. Other products and company names
mentioned herein may be the trademarks and/or registered
trademarks of their respective owners.
Elster
208 S Rogers Lane
Raleigh, NC 27610-2144
United States
T +1 800 338 5251 (US toll free)
T +1 905 634 4895 (Canada)
F +1 919 212 4801
www.elster.com
© 2011 by Elster. All rights reserved.

No part of this software or documentation may be reproduced,
transmitted, processed or recorded by any means or form,
electronic, mechanical, photographic or otherwise, translated
to another language, or be released to any third party without
the express written consent of the Elster.
Printed in the United States of America.

A1800 ALPHA Meter: DLMS Protocol Implementation PG42-1019D

Uploaded by

Copyright:

Available Formats

You might also like

A1800 ALPHA Meter: DLMS Protocol Implementation PG42-1019D

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

A1800 ALPHA Meter: DLMS Protocol Implementation PG42-1019D

Uploaded by

Copyright:

Available Formats

A1800 ALPHA® meter

DLMS protocol implementation

1 DLMS support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

2 Current billing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

3 Profiling capture objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

4 Event log objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Parameterized reading of event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

5 Instrumentation and demand objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

6 Self reads and previous billing objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

7 Clock objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

8 Script objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

9 Other objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

10 ANSI table objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

The standards used in this implementation of DLMS protocol are as follows:

Release Date Brief description

A1800 ALPHA meter communication overview

DLMS protocol configuration

• IEC 62056-21 Mode E

COSEM level specifics

There are two clients available through two associations as follows:

HDLC level specifics

Figure 1-1. Available HDLC addressing

The Client ID can be one of the following:

The following conformance block parameters are supported by the meter:

• Block transfer with get

Table 1-5. A1800 ALPHA meter DLMS objects supported

Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

Table 1-5. A1800 ALPHA meter DLMS objects supported (Continued)

Table 2-1. Current billing objects

Table 2-1. Current billing objects (Continued)

Table 2-1. Current billing objects (Continued)

Table 2-1. Current billing objects (Continued)

Table 2-2. Class 3 attributes

Table 2-3. Class 4 attributes

Scale factor unit

Table 2-4. Scale factor units

Table 2-5. Symbols used in the communication examples

Sending AARQ, Application context:1, Authentication mechanism:1, Conformance block:181d, Client

Get request, OBIS:1.1.1.6.0.ff, IC:4, Attribute:3

Get request APDU

Get response success

ASN.1 encoded data follows

Get request, OBIS:1.1.1.6.0.ff, IC:4, Attribute:1

Get request APDU

Get response success

ASN.1 encoded data follows

Get request, OBIS:1.1.1.6.0.ff, IC:4, Attribute:2

Get request APDU