My application can successfully connect to the meter and read the associated scaler profile (1.0.94.91.6.255). It also correctly reads that there are 2 rows of data available in the billing profile buffer.

However, when I call mClient.readRowsByEntry(profile, 1, rowCount), the communication fails. The Logcat shows the following error:

I am trying to Disconnect and Reconnect DLMS smart meter(HPL) using Optical probe. Below log which one I am getting.
Invocation Counter: 81 80 12 05 01 80 06 01 80 07 04 00 00 00 01 08 04 00 00 00 01
AARE Hex: 61 69 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 0E A4 0A 04 08 48 50 4C 00 00 2E 9D 08 88 02 07 80 89 07 60 85 74 05 08 02 02 AA 12 80 10 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 BE 23 04 21 28 1F 30 00 00 00 00 A6 86 76 6C 80 E7 39 F8 47 C5 AC 8A CD DF 56 89 35 E2 9F 96 4E 39 0B 57 9C C8

Hi Mikko Sir,

I need to create methods in my app's code for writing data to the COSEM Object of the meter. Can you please guide on how can I do that?

For example, I've to set 0.0.94.96.20.255 Payment Mode from prepaid to postpaid (or vice versa). For doing that in windows GXDLMSDirector, we change its value from 0 to 1 or 1 to 0 and write it to the meter after making a secured US connection.

Please guide.

Thanks,
Kshitiz

Hello Gurux Team and Community,

I'm writing to share an issue I encountered with the official Gurux.DLMS.Android example project from GitHub when running it on newer versions of Android.

The Problem
The application works perfectly on a device running Android 12 (API 31). However, when I try to run the same project on a device with Android 15 (API 35), the app is not working at all.

I'm building a DLMS/COSEM client on Android using custom USB serial communication (no GXSerial/GXMedia). I send an SNRM request and receive a UA response that starts and ends with 0x7E, but the Gurux Java parser treats it as malformed.

Works:
Genus and Landis+Gyr meters: UA parsed correctly.

Fails:
HPL and L&T meters: UA response appears malformed.

The same configuration (client address, baud rate, etc.) works fine in the Gurux DLMS demo app.

Hi,

I’m using GXSerial (USB) without GXMedia to read DLMS meter data. During Association Response, I receive all OBIS codes in one large response frame, like this:

i am using gurux android project where not able to connect with the usb prob
prob details given below

man info:Silicon Labs:CP2102
USB to UART bridge controller
chipset:CP21XX
serial:0001
Boud rate:9600
data bits:8
parity :none
stop bits :1

Hi Mikko Sir,

I was looking through the forums and read some, but I'm still not sure if it is possbile to connect to DLMS Smart Meters and read data through bluetooth using the android app: https://github.com/Gurux/Gurux.DLMS.Android

Please provide some reference guides and a path on how can I implement such thing in my app, it is already reading data through HDLC interface using UART cable.

Thanks,
Kshitiz

Hi,

I am integrating Bluetooth communication using the Gurux Java library. The communication setup, including SNRM and AARQ requests, is working fine. However, the Association Request does not work with meters other than LGZ Single Phase over Bluetooth, even though it works correctly over serial communication. I verified that the Association Request sent over both serial and Bluetooth is identical, but only the Bluetooth fails to get a response. Please suggest what could be the possible issue."

7E A0 19 03 41 32 3A BD E6 E6 00 C0 01 C1 00 0F 00 00 28 00 00 FF 02 00 91 53 7E