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. Node
  3. Get By Block Transfer and Retry

Get by Block Transfer and Retry

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 anilbhide , 15 August, 2022
Forums
DLMSDirector

Hi,

We have observed one failure under below scenario,

Electricity Meter Load Profile data is being read block by block through Cellular Communication Module. During one of the blocks, the response from Meter got lost in Network and did not reach to Gurux Director within timeout, hence Gurux retired for the same block, but this retry request is rejected by Meter as the Invocation Counter within the meter was higher than the used by Gurux.(The counter within the meter got incremented for response packet which never reached to Gurux, hence creating the mismatch).
Hence, during retry it is required that Gurux should increment the counter even if the response for previous request has not received.
Can you please check this and confirm?

Thanks for the support.

Anil Bhide

Profile picture for user Kurumi

Kurumi

4 years 1 month ago

Hi Anil,

Hi Anil,

You are right. GXDLMSDirector re-sends the generated message and doesn't generate a new message. The reason is that there are meters that can't handle if the invocation counter value is increased on re-send.

I'll need to think about how to handle this. I believe that there will be another parameter for GXDLMSDirector so older meters can also be handled.

BR,
Mikko

  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Wed, 08/26/2026 - 09:04
    Gurux.DLMS.Python 1.0.203
  • Mon, 08/17/2026 - 11:28
    Gurux.DLMS.Python 1.0.202
  • Mon, 08/17/2026 - 09:47
    gurux.dlms.cpp 9.0.2608.1701
  • Mon, 08/17/2026 - 09:25
    gurux.dlms.c 9.0.2608.1701
  • Mon, 07/27/2026 - 12:37
    gurux.dlms.cpp 9.0.2607.2701

New forum topics

  • Security vulnerability report — request for a private contact (GuruxDLMS.c / ANSI C)
  • Topic: Insufficient Memory Error When Reading Class 7 Profile Generic Objects
  • SN ReadResponse returns all-null values when response spans multiple HDLC frames
  • Gurux.Serial.Android 3.0.6 – CH340 (HL-340) USB-Serial Adapter Not Working,
  • Trying to talk to a L&G E360 meter (Using Python Gurux)
More

Who's new

  • cyby
  • Metin Onan
  • ssv007
  • 3nzol3dur
  • dw772
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin