Hello,

we intend to use the Gurux DLMS .NET stack for a system that needs to communicate with a large number of smart meters in parallel.

Our application architecture is fully asynchronous and uses async/await throughout the entire call chain. However, we have not found any indication that the Gurux DLMS stack supports asynchronous communication.

From what we can see, communication appears to be implemented using synchronous/blocking socket calls.

Our concern is the following:

I am using two L&T Trivector meters connected through RS-485 looping with a USB-to-Serial converter. Earlier I asked about multiple connections in the Gurux forum(https://www.gurux.fi/node/35203). I created a sample program using the Gurux DLMS Client in C#.

The issue I am facing is:
When reading data from one meter, if I power ON the second meter, the current meter stops responding.

I suspect there may be a communication conflict or addressing problem in the RS-485 multi-drop setup.

Hi,
I am using gurux_dlms for python and I would like to know how to configure the translator properly
Here is my code

Hello Gurux Team,

We are currently facing an issue while reading meter data using the Gurux DLMS libraries.

In the field, some meters display six-digit KWH values (for example, 987654.32). However, when we fetch the value from the meter using GXDLMSDirector, we receive only five digits (for example, 87654.32).

The meter display shows the correct six-digit value, but the response appears to be skipping the first digit in the reading.

Please let us know if you require any additional logs, OBIS codes, or sample responses from our side to investigate this issue.

Hi, have you writed the date&time successfully to Prometer 100 via DLMS protocol in GXDLMS software? It seems that write is denied by prometer 100. We use client 32, password is ABCD0001, DLMS client can read date&time OBIS 0.0.1.0.0.255.
Whether Prometer 100 support date&time write permission?

data = "/?!\r\n";
writeTrace("<- " + now() + "\t"
+ GXCommon.bytesToHex(data.getBytes("ASCII")));
media.send(data, null);
if (!media.receive(p)) {
throw new Exception("Invalid meter type.");
}

---> Summary
==============
- When using **OnePassDiffieHellman** signing mode in GXDLMSDirector GUI, the application throws a "Object reference not set to an instance of an object" when trying to read objects after successful connection. Additionally, the **Server keys** section in the "Secured Connections" tab cannot be expanded or scrolled to configure server certificates.

Hello,

Using GXDLMSSecureClient with Security.AuthenticationEncryption I've managed to receive the push message sent by a Honeywell gas smart meter. The OctetString value seems to be a compact frame, more precisely CF49. There is a posibility to parse the OctetString value and get the values as a "readable format" ?

Thank you in advance