In HPL meters, sometimes we receive values with the scalar already applied, while other times the response comes without the scalar, requiring us to divide the value by 1000. Why does this inconsistency occur, even in meters of the same make?

Hi,

Is this C library DLMS certified?
I understand that the user implementation based on this library can have issues due to verity of reasons, but this query is specifically for the library part.

This is my first time trying to get data on DLMS in python.

GXDLMSDirector connects everything, everything is visible.
I tried the example from Gurux.DLMS.Client.Example.python/main.py and it also reads everything, but it reads all the parameters.

Is there an example of code where I could read the list of OBIS codes that I need, because everything I tried didn't work for me?

Hi,

Iam trying to read Apator OTUS meter via Wrapper.
I have security packages and manufacturer tool, but I can not read the meter so far.
I can read some objects trough public association, but I need to read management association.
I can read the configuration of meter via maanufacturer tool and I can see the management access is HLSGMAC and client address etc. But I can not manege the gurux settings.
Could you please help.
I can share the communication log of manufacturer tool by e mail.

Many thanks

I have a Landis+Gyr E660 with an Ethernet module E66C.
I can connect to it using the Interface Wrapper (client address 10, logical server 1, physical server 1, authentication set to none).

However, with this setup I only receive serial numbers and similar information.
I need to read the actual metering data.

Any advice on how to properly connect to it would be greatly appreciated.

Hi Kurumi,

Hi, i'm using Gurux DLMS C.
I'm receiving APDU from the meter in binary format like below. I believe its simple APDU.
Please help me understand how to parse it with gurux C library.
Thank you.

# this is sent every middle of a minute
########################################
0F # data notification
00 00 00 03 # invoke id
00 # and priority

02 02 # structure [2]
16 # enum
01 # value
01 # array
16 # 22 elements ?

Hello Gurux Community,

I have a meter that uses HDLC over DLMS/COSEM via optical or RS232 interface, working well with Gurux tools.

My backend HES sends and receives bare DLMS packets without HDLC framing or addressing. For example, a raw DLMS packet from HES looks like this: