Product notes · 28 July 2026
Why We Retired Our IEC 62056-21 Meter Driver
Nothing was wrong with it. It became one mode inside a full DLMS/COSEM driver, because the readout a meter prints is its summary, not the meter.
We stopped shipping our IEC 62056-21 driver for electrical meters. Not because anything was wrong with it: it became one mode inside a full DLMS/COSEM driver.
The protocol has a long history. Landis & Gyr, later bought by Siemens, created it as FLAG. It was standardized as IEC 1107, renamed IEC 61107, then renamed again to IEC 62056-21. You may never have heard of it, but the electricity meter in your home or office very likely speaks it. Retiring a driver that works fine is a strange feeling – correct, but strange.
Where the old driver stopped
Here is what it used to do: open with a sign-on and ask the meter for its data readout – mode C, in practice. Plenty of meters answer that happily. Others answer the sign-on and then say they only do mode E, the standard’s way of saying “acknowledge me and I switch to HDLC”. The old driver could see that reply. It had nowhere to go from there.
And the readout you do get is a fixed telegram the vendor chose to print: the meter’s summary, not the meter. Underneath sits a whole COSEM object model – every register, with its class, attribute, scaler and unit.
So we followed the handoff. Same optical head, same RS-485 run, the whole object model.
What that changed in practice
- Two networks: TCP/IP for a meter with a network port or behind a TCP-to-serial gateway, and serial for RS-485, RS-232 and optical.
- Device discovery, which an ASCII meter can never support. It walks the endpoint in layers – reachable, interface (HDLC, IEC 62056-47 wrapper, or a 62056-21 sign-on), referencing, identity, authentication – and lists one row per confirmed meter.
- Mode auto follows whatever the meter answers with, so a mode A-D meter still reads as an ASCII readout on the same device type. Nothing already commissioned gets stranded.
- Named points: points arrive named from their OBIS description, with unit and precision resolved from the meter’s own scaler.
Why your Kamstrup would not answer
This also explains a support question we heard for years. Kamstrup meters ignore the 62056-21 sign-on the old driver always led with, so they never replied. With the DLMS/COSEM driver, a Kamstrup Omnipower answers with these settings:
| Setting | Value |
|---|---|
| Client address | 18 |
| Server address | 16 |
| Password | 12345 |
| Mode | HDLC |
Read-only by design
There is no write path in the driver. Nothing in Tridium Niagara can change a setting on a meter someone gets billed against.
If you want to point it at a meter on your own bench, send us your Niagara Host ID and we will set up a trial of the DLMS/COSEM driver.