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. TX & RX Trace Logging In Secured Connection

TX & RX trace logging in secured connection

By lrd2 , 11 December, 2023
Forums
Gurux DLMS for Java

Hi,

Is there any setting which enables frame logging in encrypted connections? I use standard logging from GDLMSReader example and when connection is encrypted, bytes are not visible in logs.

Best wishes,
Piotr

Image
Profile picture for user Kurumi

Kurumi

2 years 6 months ago

Hi, If you add -t Verbose…

Hi,

If you add -t Verbose argument, you can see sent and received bytes.
Logging doesn't depend on the authentication level.

BR,
Mikko

lrd2

2 years 6 months ago

My bad, I meant encrypted…

My bad, I meant encrypted connection, not HLS. Does logging depend on encryption?

Profile picture for user Kurumi

Kurumi

2 years 6 months ago

Hi, Used encryption doesn't…

Hi,

Used encryption doesn't affect logging. Send and receive bytes are shown on the console when verbose mode is used.

I believe that you have made changes for the reader and logging is ignored.

BR,
Mikko

lrd2

2 years 5 months ago

Hi Mikko, I found the reason…

Hi Mikko, I found the reason for this empty logs. There is a bug in Gurux Example, GXDLMSReader.java.

The reason for empty logs is that there are empty frames being sent during updateFrameCounter method execution. When using WRAPPER interface, GXDLMSClient::snrmRequest returns empty byte array, which is then transmitted to the meter. Meter does not respond to such transmission, which causes the timeout excetpion in client app.

Empty transmission is performed because there is incorrect 'if' condition in the code. It checks whether the 'data' byte array is null, but it actually never is. Instead, when using WRAPPER interface, 'date' byte array is empty.

So the condition should be
if (data.length > 0)
instead of
if (data != null)

After this change, transmission is processed correctly within updateFrameCounter() method.

Image
Profile picture for user Kurumi

Kurumi

2 years 5 months ago

Hi Piotr, Thank you for…

Hi Piotr,

Thank you for pointing this out. This is now fixed and updated to the GitHub.

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
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin