Integrating DLMS/COSEM Energy Meters into Siemens WinCC

Overview: DLMS/COSEM Energy Meter Integration into Siemens WinCC

DLMS/COSEM (Device Language Message Specification / Companion Specification for Energy Metering) is the dominant international protocol for advanced metering infrastructure. Defined by the IEC 62056 series of standards and maintained by the DLMS User Association, the protocol is used in electricity, gas, water, and heat meters deployed by utilities, industrial facilities, and commercial buildings.

When a SCADA platform such as Siemens WinCC must consume data from DLMS/COSEM meters, engineers typically encounter a protocol gap: WinCC's native channel drivers cover S7, Modbus TCP/RTU, OPC UA, DNP3, and IEC 61850, but DLMS/COSEM is not exposed as a built-in channel. This reference documents the technical path from a DLMS meter on a serial RS-485 or TCP/IP link to a WinCC tag database, with emphasis on three architectural options: a DLMS-to-Modbus protocol gateway, an OPC UA server with a DLMS plug-in, and direct IEC 61850 station bridging. Field-proven Modbus register mapping, OBIS code translation, multi-drop RS-485 addressing, and WinCC tag configuration steps are documented in detail.

IEC 62056 Architecture and Protocol Stack

The IEC 62056 suite is structured as a four-layer communication model that maps cleanly onto the OSI stack. Each layer is implemented in a distinct standard, allowing meters and head-end systems to mix-and-match transports without changing the data model.

Three reference communication profiles are commonly deployed:

• Profile A (IEC 62056-21): Local optical port, IEC 62056-21 Mode E, ASCII or binary HDLC, 300-19 200 bit/s.
• Profile B (IEC 62056-46 over TCP/IP): Direct Ethernet or GPRS, HDLC over TCP port 4059, multi-drop via logical client/server addressing.
• Profile C (IEC 62056-46 over RS-485): Wired RS-485, HDLC, logical addressing 1-127.

For SCADA integration, the most common path uses Profile C (RS-485) or Profile B (TCP/IP). Both terminate at a converter that exposes the meter data to WinCC through a protocol WinCC already understands.

COSEM Object Model and OBIS Code Reference

COSEM defines a class-based object model where every measured value, parameter, or event is represented as an instance of an Interface Class (IC). Each interface class exposes standardized attributes (logical_name, value, scaler_unit, capture_time) that any DLMS client can request without prior knowledge of the meter vendor's proprietary register layout.

Objects are located using OBIS codes - six numeric value groups (A.B.C.D.E.F) that uniquely identify a measurement. The DLMS User Association maintains the OBIS master list; a subset used in 90% of utility deployments is shown below.

Siemens WinCC Native DLMS Driver Status

WinCC Professional V17 through V19 and WinCC Unified V16 through V19 do not ship a native DLMS/COSEM channel. The licensed channel set covers:

• SIMATIC S7 (RFC1006 over TCP)
• Modbus TCP / Modbus RTU (Ethernet / serial)
• OPC UA Client / OPC DA Client
• DNP3 (with SIMATIC RFxxx or third-party add-on)
• IEC 61850 Client (WinCC V17+ with Energy Suite option)
• PROFINET, EtherNet/IP, Allen-Bradley DF1

DLMS/COSEM is absent because IEC 62056-46 is dominated by utility deployments, where utilities typically run DLMS UA-conformant head-end systems (e.g., EnergyIP, meterdata.management systems). Industrial SCADA platforms such as WinCC, FactoryTalk View, and Ignition treat DLMS as a foreign protocol and require a bridging layer.

Attempts to load a third-party DLMS driver DLL into WinCC's channel architecture are not officially supported by Siemens and create version-upgrade risk. A hardware or software gateway that translates DLMS into Modbus TCP or OPC UA is the industry-accepted integration method.

Integration Path Comparison: Gateway vs. OPC UA vs. Direct

For industrial customers running WinCC, the Modbus TCP gateway is the most cost-effective and lowest-risk choice. OPC UA is preferred when the wider plant already standardizes on OPC UA for data acquisition (e.g., back to a historian via UA Pub/Sub).

Protocol Gateway Architecture (DLMS-to-Modbus TCP)

A DLMS-to-Modbus gateway sits on the meter side of the network and exposes a Modbus TCP server interface to WinCC. Internally, the gateway polls the DLMS meters using a configurable schedule and caches the most recent value of each OBIS code in a holding register block. WinCC then reads these holding registers as if they were native Modbus devices.

The gateway typically implements the following internal data flow:

1. Boot: read meter profile (logical device name, supported OBIS list, security suite).
2. Open HDLC association with each configured meter at its logical address (1-127).
3. Negotiate authentication (Suite 0 = no auth, Suite 1 = LLS, Suite 2 = HLS with SHA-256).
4. Periodic poll: GET.request (class 3, attr 2) for each mapped OBIS code, on a 1-15 s cycle.
5. Decode xDLMS APDU, apply scaler_unit (e.g., value 12345, scaler -3, unit 30 = 12.345 kWh).
6. Write scaled value to internal Modbus register at configured offset.
7. Respond to WinCC's Modbus TCP reads from its holding register block on TCP/502.

RS-485 Multi-Drop Wiring and Logical Addressing

When meters are daisy-chained on a single RS-485 trunk, each meter must have a unique DLMS logical address and the bus must be terminated once at each end. Recommended practice for IEC 62056-46 over RS-485:

OBIS-to-Modbus Register Mapping Strategy

The gateway holds a configuration table that maps Modbus registers to OBIS codes. A clean scheme groups registers in 100-register blocks per meter to simplify WinCC tag structure. The example below maps three-phase active and reactive energy plus instantaneous values for one meter at Modbus slave ID 1.

WinCC Channel and Tag Configuration Procedure

The following steps configure WinCC Professional / WinCC Unified to read the gateway via Modbus TCP. The procedure assumes TIA Portal V18 or higher and a gateway IP of 192.168.10.50.

1. Add Modbus TCP driver. In TIA Portal, open the WinCC project, navigate to Devices & Networks, add a new device, and select SIMATIC WinCC Professional > HMI > Modbus TCP.
2. Configure connection. Open Connections, create a new Modbus TCP connection. Set Partner IP = 192.168.10.50, Port = 502, Station Address = 1 (Modbus slave ID of gateway).
3. Add tags. In the HMI tag table, create external tags. For each OBIS code in the table above, define a tag with Connection = ModbusTCP_1, Address = 40001 + offset, Data Type = DWord (for 32-bit energy/power), Length = 2 words, Acquisition Mode = Cyclic, Cycle = 1 000 ms.
4. Apply scaling. In the tag's linear scaling, set Value range = 0 to 999999999 and Scaling = x 0.001 for energy values. For voltage, set Scaling = x 0.1 (giving 0.1 V resolution).
5. Test with tag simulator. Right-click the tag, select Update value, and verify against a known reference (e.g., walk-up read of the meter with a DLMS client tool such as open-source DLMS-COSEM Python client).
6. Map tags to screen objects. Bind I/O fields, bar graphs, and trend controls in the WinCC screen to the HMI tags. Configure trend logging to archive energy totals at 15-min intervals.
7. Set up alarm conditions. Create analog alarm limits for voltage (e.g., < 207 V or > 253 V on a 230 V nominal) and for current imbalance across L1/L2/L3.

Verification, Diagnostics, and Troubleshooting Matrix

For deeper protocol-level diagnostics, deploy Wireshark on a tap point and apply the DLMS dissector. Watch for HDLC S-frames (RR, RNR) indicating flow control. An RNR storm from one meter indicates it cannot keep up - typically caused by event logs filling the buffers; clear the meter's event log (OBIS 0.0.96.15.0.255) as preventive maintenance.

Security Suites and Authentication Levels

IEC 62056-62 defines four security suites that meter and head-end must agree on:

The DLMS User Association publishes the conformance test tool and a master conformance test report for each certified meter; request this from the meter vendor before deployment. The official IEC 62056 standard set is available from the IEC webstore - verify any claims of "IEC 62056 compliant" against the specific part number (e.g., IEC 62056-46:2018 is the 2nd edition HDLC over TCP/IP).