Skip to main content
Home
for DLMS smart meters
Open source solutions for DLMS smart metering

Main navigation

  • Home
  • Products
  • About us
  • Open Source
  • Community
  • Forum
  • Downloads
User account menu
  • Log in

Breadcrumb

  1. Home
  2. Forums
  3. Get Actual Raw Payload

Get actual raw payload

Forum Rules

Before commenting read Forum rules

Don't comment the topic if you have a new question.

You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.

By Bhaumik , 11 May, 2022
Forums
Gurux.DLMS

Hi Mikko,

We are testing IS16444 standard meter. In that, We are able to print the request payload in our log, but in response, we only get 00 01 00 01 00 bytes only in GXByteBuffer.

We want to print the actual payload of responses.

All communications are made in the Wrapper interface only.

can you please provide your suggestion?

Profile picture for user Kurumi

Kurumi

4 years 1 month ago

Hi,

Hi,

You need to read all the data that the meter sends. All the data is not necessarily to come in one TCP/IP frame. Try to read the data again. I believe that there are more bytes coming.

BR,
Mikko

Bhaumik

4 years 1 month ago

Hi Mikko,

Hi Mikko,

I understood that, But I want to print the payload received on TCP/IP socket.
In the log, I can print just 00 01 00 01 00 rather than the entire response packet. Is there any way to get the complete wrapper frame in GXBytebuffer or any other way.

In HDLC, Able to print the payload but in wrapper not able to print.

Profile picture for user Kurumi

Kurumi

4 years 1 month ago

Hi,

Hi,

Have you tried to use GXDLMSClient.GetFrameSize method? It will tell how many bytes there are on the WRAPPER frame.

BR,
Mikko

Bhaumik

4 years ago

Hi Mikko,

Hi Mikko,

It seems that you didn't get my point.

Whatever the frame is received from the socket, I just want to print in logs regardless of frame size.

Currently, I am logging data in the following way and it is only printing 00 01 00 01 00 for the wrapper
frame. It should be the actual payload that the meter has sent.

rd = new GXByteBuffer(p.Reply);
logger.Info(rd);

Can you please suggest how I can log that payload?

Regards
Bhaumik

Profile picture for user Kurumi

Kurumi

4 years ago

Hi Bhaumik,

Hi Bhaumik,

TCP network packets can come in fragments and I believe this is happening in your case. Your implementation shows only the first fragment from TCP/IP frame. You need to check how many bytes there are in the frame and read them all.

BR,
Mikko

  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Tue, 06/09/2026 - 11:16
    gurux.dlms.java 4.0.95
  • Tue, 06/09/2026 - 10:03
    Gurux.DLMS.Python 1.0.199
  • Mon, 06/08/2026 - 13:39
    gurux.dlms.cpp 9.0.2606.0801
  • Mon, 06/01/2026 - 10:15
    gurux.dlms.cpp 9.0.2606.0101
  • Thu, 05/28/2026 - 16:06
    gurux.dlms.java 4.0.94

New forum topics

  • Error reading L&G Meter
  • Pass a TCP Client to GXNet
  • Australian EDMI Mk10D (Essential Energy area)
  • Strange mix of data notificiation vs get response
  • DLMS Connection
More

Who's new

  • Tuanhgg
  • Adel
  • charnon
  • Paddles
  • Miguel Ángel
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin