Skip to main content
Home
for DLMS smart meters

Main navigation

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

Breadcrumb

  1. Home
  2. Displaying of Logical Name (class Charge, Attribute Unit_charge_type, Element Commodity_reference)

Displaying of logical name (class charge, attribute unit_charge_type, element commodity_reference)

By icabrera, 5 September, 2024
Forums
DLMSDirector

Hello,

I am reading an electricity meter with the following structure:

class charge, attribute unit_charge_active, element commodity_reference with a logical_name of 1.0.15.8.0.255 (Total energy).

Reading with Gurux, in the section Commodity Reference Type, field "Target" remains empty. Expanding the field "Target", there are the only references to the Credit instances.

In the bluebook, section 4.6.4.2.5 Note 1, there is an explanation where the commodity is the Active Import Electrical Energy (not an credit instance), in the same Note 1 it is a inference that the commodity_reference is an instance of class 3 (Register, scaler_unit).

I consider (with the references to the Bluebook) that the commodity_reference is not a credit instance, it is a register instance and Gurux is not displaying correctly.

Profile picture for user Kurumi

Kurumi

8 months 1 week ago

Hi, The meter sends…

Hi,

The meter sends commodity_reference_type where meter defines the used object type (class_id), logical name, and attribute index. Gurux libraries search target using object type and a logical name. Make sure that the meter is sending the correct object type and logical name. The target object must also exist in the association view.

BR,
Mikko

icabrera

7 months 3 weeks ago

Hello, Commodity_reference…

Hello,

Commodity_reference_type specifies the following:

commodity_reference_type ::= structure
{
class_id: long-unsigned,
logical_name: octet-string,
attribute_index: integer
}

Reading the attribute 5 of a charge instance I got the following from the meter:

02 03 02 02 0f 00 0f fd 02 03 12 00 03 09 06 01
00 0f 08 00 ff 0f 02 01 01 02 02 09 01 00 10 00
00

Analyzing the frame:

02 - structure
03 - 3 elements

element #1 (charge_per_unit_scaling)

02 - structure
02 - 2 elements
0f - integer #1 [commodity_scale]
00 - value of integer #1 (= 0)
0f - integer #2 [price scale]
fd - value of integer #2 (=-3)

element #2 (commodity_reference)

02 - structure
03 - 3 elements
12 - long unsigned #1 [class_id]
00 03 - value of long unsigned #1 , class_id = 3 (Register)
09 06 - octet string #1 (len=6), [logical name]
01 00 0f 08 00 ff - value of octet-string #1 1.0.15.8.0.255
0f - integer #1 [attribute_index]
02 - value of integer #1, (=2), attribute = 2

element #3 (charge_table)

01 - array
01 - 1 element
02 - structure
02 - 2 elements
09 01 - octet string #1 (len=1), [index]
00 - value of octet_string = 1 (=0)
10 - long #1
00 00 - value of long #1 [charge_per_unit]

In the element #2, logical name is: 1.0.15.8.0.255, but the field Target of commodity reference type is EMPTY, and the options are only charge instances.

The association view contains this logical name (1.0.15.8.0.255)

Please see the referred image: https://ibb.co/C8rMBbm

Profile picture for user Kurumi

Kurumi

7 months 3 weeks ago

Hi, You have two targets in…

Hi,

You have two targets in the association view. OBIS codes 0.0.19.10.0.255 and 0.0.19.10.1.255, but Target OBIS code is 1.0.15.8.0.255. This is wrong because it's OBIS code of your charge object. The object type is also Register.

You need to check those.

BR,
Mikko

  • Log in or register to post comments
  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Fri, 05/09/2025 - 13:03
    Gurux.DLMS.Python 1.0.181
  • Wed, 05/07/2025 - 16:09
    Gurux.DLMS.Android 2.0.14
  • Tue, 05/06/2025 - 09:34
    gurux.dlms.c 9.0.2505.0601
  • Tue, 05/06/2025 - 08:51
    GXDLMSDirector 9.0.2505.0601
  • Tue, 05/06/2025 - 08:26
    gurux.dlms.java 4.0.79

New forum topics

  • I LOST MY CRYPTO, HOW DO I RECOVER IT? iFORCE HACKER RECOVERY
  • GXNet python implementation hangs on close
  • Conexión Landis ZMG310 Protocolo IEC
  • I need function of below OBIS code
  • How communicating with meter using proparatory command
More
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin