Hello All,

I was trying to parse an HDLC frame(not DLMS) using GXDLMS DLMS translator.
I found that the online version of the tool parses the frame in a different manner than the offline tool, specifically the HDLC payload.
The online version always deducts the first byte of the payload while the offline tool shows the whole payload as expected.
I'm using HDLC type format 3 which shows that the payload starts right after the 2-bytes Header Check Sum (HCS).

Is there a reason why the offline parsing mechanism differ than the online one ?

i am using C# Gurux DLMS.Client.Example and trying to write own based on that example now how can read multiple meters at a same time in single connection dose i know the we need Disconnect() for every new meters before go to next meter how to do that or this method is wrong!

HI Mikko,

I have received bytes from meter as 09 04 05 00 ff ff

Now while I am converting value it is coming as below:

-- 05:00:*.255

I want value like 05:00:*

Can you please provide sample code for that in c# so I can convert it.

Hi everyone. I am reading OBIS 1.0.1.6.0.255 from a Hexing HXE310KP meter via GSM using Gurux.DLMS. I receive the following response packet:

00-01-00-01-00-10-00-09-C4-01-41-00-0D-03-17-93-80

I can see that the last three bytes correspond to the value I obtain when reading the meter using HexView software. However, when reading the same OBIS via Gurux, the value returned is only the BCD value 3.

What could be the cause of this discrepancy?

Thanks in advance for your time and assistance.

We are writing TOU profile configurations, and it is getting success if payload size is less than 512 Byte, but if size of the payload is greater than 512 bytes so getting error that "Service not allowed".

Meter negotiated hdlc TX/RX = 128 Byte and MaxPdu Size 512 Byte

Below are the Two Payload, with one which is < 512 is getting Success:

1- Write Success:

HI Mikko,

I am trying to convert string value to GXTime.

In that got

GXTime gXTime = new GXTime("07:00:00");

String '07:00:00' was not recognized as a valid DateTime.

Can you please provide update in c#. As I have to convert multiple entries.

Hello,
I want to read an energy meter using its RS232 port with GXDLMS Director.

The meter I am using is L&T EM101+ DLMS Cat C3 IS15959.

I do not have a RS232-to-USB cable with a DB9 connector right now. I have a MAX3232 RS232-to-TTL converter and an FT232RL USB-to-TTL module.

My idea is:
Meter (RS232) → MAX3232 → TTL → FT232RL → USB → GXDLMS Director

Will this work?
Can I convert RS232 to TTL using the MAX3232, then convert TTL to USB using the FT232RL, and read the meter normally with GXDLMS Director?

Hi, I am newbie with DLMS. I am testing Gurux.DLMS.Python and I am working with a meter simulation software. I am able to use the Gurux.DLMS.Client.Example.python giving the command "main.py -S /dev/ttyS0 -c 16 -s 1 -a None" and the simulator works fine. When I sniff the frames, at first step the python code send the SNRM frame:

7e 0a 07 03 21 93 0f 01 7e

the simulator answers with UA response

7e a0 20 21 03 73 73 98 81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01 ce 6a 7e

Hello Mikko,

What should I do to get method call result?
For example, object target is of GXDLMSImageTransfer type.

Let's use method 3 "image verify".
As written in BlueBook "The result of the invocation of this method may be success, temporary_failure or other_reason."

Following code works ok:
reader.readDataBlock( target.imageVerify(reader.client), reply)
How should I check that result is success, temporay failure or something else?

Is it reply.error values according to green book or something else?

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"