Skip to main content
Home
for DLMS smart meters
Open source solutions for DLMS smart metering

Main navigation

  • Home
  • Products
  • About us
  • Open Source
  • Community
  • Forum
  • Downloads
User account menu
  • Log in

Breadcrumb

  1. Home
  2. Reading OBIS Code 1.8.0 Register Name Difference

Reading OBIS Code 1.8.0 Register Name Difference

By Burger , 26 February, 2024
Forums
General discussion

I try to read register with address 1.8.0 because according my research on internet 1.1.1.8.0.255 refers to total active import energy.

But according to returned message from Gurux and 62056-61, 1.8.0 is said to be Sum Li Active power+ (QI+QIV) Time integral 1 Rate 0.

Do these two description mean the same or if not what causes the difference?

Image

Burger

2 years 4 months ago

1.8.0 Total active import…

1.8.0 Total active import energy

Image
Profile picture for user Kurumi

Kurumi

2 years 4 months ago

Hi, In DLMS standard 1.1.1.8…

Hi,

In DLMS standard 1.1.1.8.0.255 means Sum Li Active power+ (QI+QIV) Time integral 1 Rate 0. You need to ask the meter vendor what is counted for total active import energy in this meter.

I believe that the meter manufacturer is using a shorter description and they mean the same, but you need to verify this from the meter vendor.

BR,
Mikko

  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Thu, 07/09/2026 - 14:34
    Gurux.DLMS.Python 1.0.201
  • Fri, 06/26/2026 - 16:32
    Gurux.Service 3.0.2606.2601
  • Wed, 06/24/2026 - 08:36
    Gurux.DLMS.Python 1.0.200
  • Mon, 06/15/2026 - 08:52
    gurux.dlms.c 9.0.2606.1501
  • Tue, 06/09/2026 - 11:16
    gurux.dlms.java 4.0.95

New forum topics

  • Reading block profile with Compact array
  • DLMS server - serving multiple similar datasets gathered from multiple meters across distinct logical addresses
  • CGXDLMSProfileGeneric::SetValue for attribute 3. Possible memory leak
  • Clou
  • DLMS Server how to set server logical address, and attach object to different association
More
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin