Skip to main content

13 DLMS/COSEM

Introduction

IEC 62056 is a set of standards for electricity metering data exchange by International Electrotechnical Commission.

The IEC 62056 standards are the international standard versions of the DLMS/COSEM specification.

DLMS or Device Language Message Specification (originally Distribution Line Message Specification),[1] is the suite of standards developed and maintained by the DLMS User Association (DLMS UA) and has been adopted by the IEC TC13 WG14 into the IEC 62056 series of standards. The DLMS User Association maintains a D Type liaison with IEC TC13 WG14 responsible for international standards for meter data exchange and establishing the IEC 62056 series. In this role, the DLMS UA provides maintenance, registration and compliance certification services for IEC 62056 DLMS/COSEM.

COSEM or Companion Specification for Energy Metering, includes a set of specifications that defines the transport and application layers of the DLMS protocol. The DLMS User Association defines the protocols into a set of four specification documents namely Green Book, Yellow Book, Blue Book and White Book. The Blue Book describes the COSEM meter object model and the OBIS object identification system, the Green Book describes the architecture and protocols, the Yellow Book treats all the questions concerning conformance testing, the White Book contains the glossary of terms. If a product passes the conformance test specified in the Yellow Book, then a certification of DLMS/COSEM compliance is issued by the DLMS UA.

The IEC TC13 WG14 groups the DLMS specifications under the common heading: "Electricity metering data exchange - The DLMS/COSEM suite". DLMS/COSEM protocol is not specific to electricity metering, it is also used for gas, water and heat metering.

Source: https://en.wikipedia.org/wiki/IEC_62056

DLMS Master

Overview

DLMS (Device Language Message Specification) is a suite of standards developed and maintained by the DLMS User Association. COSEM (Companion Specification for Energy Metering) includes a set of specifications that define the transport and application layers of the DLMS protocol.

In DLMS/COSEM all the data in electronic utility meters and devices are represented by means of mapping them to appropriate classes and related attribute values.

Objects are identified with the help of OBIS (Object Identification System) codes (as per IEC 62056-61).

The DLMS driver allows only for readout and displaying only numeric values of DLMS object data fields. Connection via TCP (HDLC or WRAPPER) or serial (RS232/RS485) port are supported.

The setup of the DLMS driver consists of communication and tag configuration. Protocol specific parameters (except for DLMS/IEC handshake mode) apply for both serial and IP connections.

Configuration

Devices section

serialnumber, server_address and id define the meter addressing parameters. Either serialnumber (meter serial number) or a combination of server_address (physical server address) and id (logical server address) is used. If a serial number is provided, physical and logical server addresses are ignored.

Before configuring the Device section it is best to first check the connection parameters with a 3rd party DLMS utility.

master_address defines the client address. This usually depends on the authentication used. Most meters support 16 for no authentication.

type defines the object referencing. SN should be used for short name referencing and LN for logical name referencing.

mode defines the communications mode. If IEC is used along with comms settings for serial readout, the connection is initiated as per IEC 62056-21, at the default initial baud rate (300 7E1). DLMS-HDLC shall be used for HDLC connections via IP. DLMS-WRAPPER is also supported for IP connections. The default setting is DLMS-HDLC.

timeout_ms defines the reply timeout for telegrams both via serial and TCP.

auth and password define the authentication mode and password. This can be set to None, or other authentication variant (see table below), depending on the mode configured and supported by the particular meter.
ip and port define the IP address and TCP port for DLMS communication via IP. To use TCP/IP
communication set protocol to DLMS TCP and for serial use DLMS serial

Connection parameters are device specific and can differ between makes, models and utility companies. For initial connection settings please refer to the configuration of the particular meter.

When ip and port are configured, any serial port settings are ignored and connection is initiated only via IP.

Device configuration parameters for DLMS meters acquisition:

Parameter Type Description Required

Default value

(when not specified)

Range

name

string

User-­friendly name for a device

Yes


description string

Description of a device

No


device_alias string

Alphanumeric string to identify a device

Yes


enable boolean

Enabling/disabling of a device

No 1 0 1
protocol string

Protocol to be used

Yes
DLMS serial, DLMS TCP
serialnumber integer

Meter serial number

No 0

slave_address integer

Meter physical server address

No 1600

id integer

Meter logical server address

No 0

address_size integer

Meter address size in bytes

No 1 1 4

master_address

integer

Client address

Yes


type string

Meter object referencing: SN - short referencing, LN - logical referencing

No SN SN, LN
mode string

Initial handshake mode.

Yes DLMS-­HDLC DLMS, IEC, DLMS-­DLC or DLMS-­RAPPER
timeout_ms integer

Timeout in milliseconds

No 2500

auth string

Authentication.

No None None, Low, High, HighMd5, HighSha1, HighSha256, HighGmac HighEcdsa
password string

Password for authentication

No when auth is None


ip string

IP address

Yes (For TCP)


port integer

TCP port

Yes (For TCP)


device

Communication port

Yes (For Serial)
PORT1 PORT2
baudrate integer

Communication speed, bauds/s

No (For Serial) 9600 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200
databits integer

Data bit count for communication

No (For Serial) 8 6 9
stopbits integer

Stop bit count for communication

No (For Serial) 1 1 2
parity string

Communication parity option

No (For Serial) none none, even,  odd
flowcontrol string

Communication device flow control option.

No (For Serial) none none
retry_counter integer

Number of requests, before link is considered lost (device status signals are changed) and reconnect attempt will be issued

No 3

scan_rate_ms integer

If provided and positive ­ all reads and writes will be executed within the timeframe in milliseconds

No 10000

poll_delay_ms integer

Minimum time delay in milliseconds to wait before sending any data on port.

No 200

Signals section

The tag_job defines the tag job. A list of comma-separated OBIS codes (or a single OBIS) should be used. Attribute indexes for objects of types register and extended register are selected automatically. Any other object types should include the attribute index in the form of OBIS:index.
tag_job_todo defines the job sub-job. This field should contain an OBIS code from within the list of the tag_job.

DLMS configuration parameters creating signals:

Parameter Type Description Required

Default value

(when not specified)

Range


signal_name

string

User-­friendly signal name

Yes



device_alias

string

Device alias from a Devices tab

Yes



signal_alias

string

Unique alphanumeric name of the signal to be used

Yes



enable

boolean

Enabling/disabling of an individual signal

No 1

0

1

log

boolean

Enable logging in event log

No 0



SN

integer

Address of value to read (Short name).

No



job_todo

string

Tag job as single or multiple comma separated OBIS codes

Yes



tag_job_todo string Tag sub job Yes


number_type string Type of a number (FLOAT, DOUBLE, DIGITAL, etc.) Yes


pulse_short_time_ms string Time interval for short output pulse to stay active No


pulse_long_time_ms integer Time interval for long output pulse to stay active No


Debugging the DLMS service

If configuration for DLMS devices is set up, handler for protocol will start automatically. If configuration is missing or contains errors, protocol will not start. It is done intentionally decrease unnecessary memory usage.

DLMS protocol runs a service called pooler. If DLMS does not work properly (e.g. no communication between devices, data is corrupted, etc.), a user can launch a debug session from command line interface and find out why link is not functioning properly. To launch a debugging session, a user should stop pooler process and run pooler command with respective flags as in the table shown below.

Procedure for DLMS Master protocol service debugging:

  • Step 1: Service must be stopped by entering the following command into the wcclite:
    /etc/init.d/pooler stop
  • Step 2: After service is stopped it must be started with the preferred configuration file (JSON files found in /etc/ folder) and a debug level 7: pooler ­-c /etc/pooler.json ­-d7 -dlms                                                                                      Additional output forming options are described in the table below.
  • Step 3: Once the problem is diagnosed normal operations can be resumed with the following command: /etc/init.d/pooler start

DLMScommand line debugging options

Option  Description
­-h [ –help ]  Display help information
­-V [ –version ]  Show version
-p [ –port ] ­Show output for one port only
­-d <debug level> Set debugging level
-­c [ –config ]  Config path
-­a [ –app ] Show application layer data
–l [ –link ]  Show link layer data
–t [ –transport ]  Show transport layer data
-­r [ –redis ]  Show Redis messages
-­R [ –readyfile ]  Ready notification file