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. Problem With Dedicated Key On Release Request

Problem with Dedicated key on Release request

By zon7 , 24 March, 2026
Forums
Gurux DLMS for ANSI C++

After updating to the latest version of gurux.cpp (I had a very old version), i'm having problems debuging because an assert.
The problem is that after AARQ, the m_DedicatedKey stored in the GXCipher has position advanced.
Then in GXAPDU:233->GXByteBuffer:406, when trying to set the dedicated key, an assert throws because pos is already it's max size.
I'm able to reproduce this behaviour every time. Can you fix it?

Profile picture for user Kurumi

Kurumi

2 months ago

Hi, Our customers are using…

Hi,

Our customers are using the dedicated key all the time. Can you add a hex trace from AARQ and AARE so I can check what is happening?

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