for DLMS smart meters | Open source solutions for DLMS smart metering

By pratim1988 , 27 November, 2025

Regarding android app

Forums

Hello Sir,
I am using below dependency in my Android project. But when I ran my project with minSDK version 29 its gives error so, to using those I need to maintain my minSDK version 31. Is it possible to run in 29?
implementation(libs.gurux.dlms)
releaseImplementation(libs.guruxDlmsAndroid)
implementation(libs.gurux.serial.android)
implementation "org.gurux:gurux.common.android:3.0.4"
implementation "com.github.mik3y:usb-serial-for-android:3.9.0"

By thiesens , 26 November, 2025

Release download

Forums

DLMSDirector

Did you remove all releases of GXDLMSDirector?
I cant find any download

By JoshuaStar , 25 November, 2025

Getting data from dlms cat-c3 bi-directional meter

Forums

Gurux.DLMS

Hi everyone,

I’m trying to interface a Schneider Electric / L&T DLMS Category C3 bi-directional energy meter using its RS232 port, which is exposed using an RJ11 4-pin connector. I’m stuck at a few points and would really appreciate guidance.

1. RJ11 RS232 Pinout (4-pin) for L&T / Schneider meter

The meter manual is not clear on the RS232 pinout.
Does anyone know the exact mapping for:

Pin 1 – ?

Pin 2 – ?

Pin 3 – ? (ground?)

Pin 4 – ?

A confirmed TX, RX, GND assignment would help a lot.

2. No voltage on pins?

By andre538 , 25 November, 2025

GetRequestWithList Translator error

Forums

DLMSDirector

Hello Mikko,

there is a bug in Gurux DLMS Translator while processing GetRequestWithList

sample data exchange:

TX: 08:26:48 7E A0 39 02 23 61 76 ED 4D E6 E6 00 C0 03 C1 04 00 03 01 00 00 06 00 FF 02 00 00 03 01 00 00 06 01 FF 02 00 00 03 01 00 00 06 02 FF 02 00 00 03 01 00 00 06 03 FF 02 00 A7 4F 7E
RX: 08:26:48 7E A0 21 61 02 23 96 9B D4 E6 E7 00 C4 03 C1 04 00 12 08 FC 00 12 00 05 00 12 00 32 00 12 00 3C FD 80 7E

By sebashb , 20 November, 2025

Honeywell / Elster AS3500 reading data with DLMSDirector

Forums

DLMSDirector

Honeywell / Elster AS3500 and AS3000 are very common in Portugal for renewable energy metering.

I have a AS3500 W12B-743-OSE-0037S-DD000 meter which I'm trying to read with DLMSDirector but so far without any success.

The only thing I managed to do was use the HDLC Address Resolver and find out that the meter manufacturer is ELS. Then I cloned the settings for Elster and changed just the flag from ELE to ELS.

By muraligowda980… , 18 November, 2025

Firmware Upgrade is pending at Verification Stage

Forums

DLMSDirector

Hi,

I am trying to upgrade firmware to a TCP wrapper meter using GXDLMSDirector.

During the process, Gurux application is retrying image verification stage indefinitely until the disconnection request or power off.

GXDLMSDirector Application Version:- 9.0.2409.2004

I have attached log for your reference.

By dlmsDeveloper , 15 November, 2025

gurux.c testing with gxdlmsdirector ctt test

Forums

Gurux DLMS for ANSI C

Hi,

I use Gurux.c library and when i tested it with gxdlmsdirector ctt test
The Communication is ok between this two (Device and Software)
But when software was sent only this :

7e a0 2f 00 02 0e d3 03 10 5e 66 e6 e6 00 c8 1e
30 00 00 00 0c 63 a9 c6 fe 56 8e 96 a8 9f fe ed
1b c9 a9 a3 15 20 64 85 be 96 2f 07 00 c8 b8 6e
7e

By technoshell , 15 November, 2025

Initiate Conformance

Forums

DLMSDirector

3 Phase meter Frames are as under
08:16:20 Send SNRM request.
TX: 7E A0 07 03 41 93 5A 64 7E
08:16:20
RX: 7E A0 20 41 03 73 3E 9D 81 80 14 05 02 03 40 06 02 03 40 07 04 00 00 00 01 08 04 00 00 00 01 B7 29 7E
08:16:20 Send AARQ request.
TX: 7E A0 57 03 41 10 DF 07 E6 E6 00 60 49 A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 41 42 43 44 45 46 47 48 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 0A 80 08 4E 43 43 4D 53 45 4C 4C BE 17 04 15 21 13 20 00 00 00 00 F7 52 BF B3 AB 60 AE E5 78 1E 55 59 EF F5 4D B6 7E
08:16:21

By enemy235 , 13 November, 2025

Logical name, can be nullified/corrupted

Project

gurux.dlms.java

Status

Closed (works as designed)

I’ve encountered an issue where the meter can send an incorrect response to the request for first attribute and after that local LN is changed.

Current Behavior:
When parsing the response for the first attribute, the Logical Name of a local object is being updated based on the meter’s response. This can cause problems if the response is incorrect. I’ve observed cases where the LN becomes null or changes to a different one entirely. (I've seen a meter to respond with two PDUs in one TCP message, or meter closed the TCP connection before responding.)
Once this happens, further communication with that object is impossible. The only way to recover is to refresh the association or manually correct the Logical Name.

Example:
In one instance, the meter responded to the current security setup 0.0.43.0.0.255 with the real instance of currently connected security setup: 0.0.43.0.5.255. That changed the local object from 0.0.43.0.0.255 to 0.0.43.0.5.255.

Suggested Solution:
The Logical Name should never be modified based on responses from the meter.
A possible solution would be to maintain an internal copy of the LN that remains immutable and is used for all requests, while a secondary copy could reflect any changes reported by the meter.

Currently it should be handled by this method. But the check can be skipped, if the value is not a byte[]. If it is a null, it will return a null. This check needs some work and also the setLogicalName in each object can be adjusted, to not to change the LN. But the LN needs to be changed when loading the object from xml or i think when reading the associacion list, it uses this method also.

public static String toLogicalName(final Object value) {
if (value instanceof byte[]) {
byte[] buff = (byte[]) value;
if (buff.length == 0) {
buff = new byte[6];
}
if (buff.length == 6) {
return (buff[0] & 0xFF) + "." + (buff[1] & 0xFF) + "." + (buff[2] & 0xFF) + "." + (buff[3] & 0xFF) + "."
+ (buff[4] & 0xFF) + "." + (buff[5] & 0xFF);
}
throw new IllegalArgumentException("Invalid Logical name.");
}
return (String) value;
}

Priority

Normal