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?

I am trying to use a USB optical probe where, in the media settings, the port shows as Prolific Technology, Inc with the following configuration: Baud rate 9600, Data bits 8, Parity None, Stop bits 1, and Chipset Prolific. However, when I click Read and Open in the Android application, I get the error Failed to open serial port. On Windows, the same setup works fine and data is fetched successfully, but it fails on Android.

Hi Gurux Team,

I am trying to connect a smart meter using an optical probe with an Android phone

through the Gurux DLMS Android App.

Case 1 (Error: Invalid Logical Name)

When I configure the connection with these parameters:

Manufacturer: India Standard

Referencing: Logical Name

Interface: HDLC

Password: [Provided]

Wait Time: 30:00

Address Type: Default

Physical Address: 1

Logical Address: 0

Authentication: US

Client Address: 48 / 16 / 30

Security Policy: Authentication + Encryption

Hi Gurux Team,

I am trying to connect a smart meter using an optical probe with an Android phone

through the Gurux DLMS Android App.

Case 1 (Error: Invalid Logical Name)

When I configure the connection with these parameters:

Manufacturer: India Standard

Referencing: Logical Name

Interface: HDLC

Password: [Provided]

Wait Time: 30:00

Address Type: Default

Physical Address: 1

Logical Address: 0

Authentication: US

Client Address: 48 / 16 / 30

Security Policy: Authentication + Encryption

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: