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. Ignore Packets With Different Source and Target

ignore packets with different source and target

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 ali_bahal , 22 June, 2021
Forums
Gurux.DLMS

I have a meter that I use it's gprs modem to read data. but when I read parameters , it send some Irrelevant packets with different source and target address. is there a way to ignore this packets ?
in below example, last packet is of this kind.

Send AARQ request.
TX: 00010001000100386036A1090607608574050801018A0207808B0760857405080201AC0A80083030303030303030BE10040E01000000065F1F0400001E5DFFFF
RX: 00010001000100446142A109060760857405080101A203020100A305A10302010088020780890760857405080201AA0A80083030303030303030BE10040E0800065F1F040000101801000007
Read object type Register index: 3
TX: 000100010001000DC001C100030100200700FF0300
RX: 000100010001000AC401010002020F001623
Read object type Register index: 2
TX: 000100010001000DC001C100030100200700FF0200
RX: 0001000100010007C4010100120000
Read object type Register index: 3
TX: 000100010001000DC001C100030100340700FF0300
RX: 000100010001000AC401010002020F001623
Read object type Register index: 2
TX: 000100010001000DC001C100030100340700FF0200
RX: 0001000100010007C4010100120000
Read object type Register index: 3
TX: 000100010001000DC001C100030100480700FF0300
RX: 000100010001000AC401010002020F001623
Read object type Register index: 2
TX: 000100010001000DC001C100030100480700FF0200
RX: 0001000100010007C40101001200D2
Read object type Register index: 3
TX: 000100010001000DC001C1000301001F0700FF0300
RX: 000100010001000AC401010002020FFE1621
Read object type Register index: 2
TX: 000100010001000DC001C1000301001F0700FF0200
RX: 0001000100010007C4010100120000
Read object type Register index: 3
TX: 000100010001000DC001C100030100330700FF0300
RX: 000100010001000AC401010002020FFE1621
Read object type Register index: 2
TX: 000100010001000DC001C100030100330700FF0200
RX: 0001000100100015DD100000000030333939333330303036313612001F

Profile picture for user Kurumi

Kurumi

4 years 11 months ago

Hi,

Hi,

That is done automatically. If the source and target address are different than what the client is using data is skipped. This is happening all the time when there are several meters in the RS-485 bus.

BR,
Mikko

ali_bahal

4 years 11 months ago

But why I receive the last

But why I receive the last packet?

Profile picture for user Kurumi

Kurumi

4 years 11 months ago

Hi,

Hi,

It's shown on the trace, but GXDLMSClient.GetData should skip it. What programming language you are using? I can verify it.

BR,
Mikko

ali_bahal

4 years 11 months ago

We are using c#. It does not

We are using c#. It does not ignore and after that packet I get this error :
Insufficient memory to continue the execution of the program

Profile picture for user Kurumi

Kurumi

4 years 11 months ago

Hi,

Hi,

I'll test this right away.

BR,
Mikko

ali_bahal

4 years 11 months ago

Thank you. Please consider

Thank you. Please consider the error I get after.

Profile picture for user Kurumi

Kurumi

4 years 11 months ago

Hi,

Hi,

I checked this and it works like expected. Received data is handled. The problem is that the meter sends invalid data. The message is broken and it's causing the problem.
You should inform the meter manufacturer of this.

I'll talk should messages like this just ignored so they don't break the communication.

BR,
Mikko

ali_bahal

4 years 11 months ago

Thank you very much. I'll

Thank you very much. I'll inform the manufacturer.

ali_bahal

4 years 11 months ago

I talked with meter

I talked with meter manufacturer and they say, It's a keep a live packet and can be recognized with "DD". Despite the matter that keep alive should not be send middle of reading, do you think it's dlms standard?

Profile picture for user Kurumi

Kurumi

4 years 11 months ago

Hi,

Hi,

I'm sorry to say, but 0xDD is not keep-alive. It's GeneralCiphering where data is encrypted. This is defined in the DLMS standard.

BR,
Mikko

ali_bahal

4 years 11 months ago

Thanks

Thanks

  • 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