Skip to main content
Home
for DLMS smart meters

Main navigation

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

Breadcrumb

  1. Home
  2. Addressing 1 and 2 Byte

Addressing 1 and 2 byte

By JavierDiaz, 18 April, 2025
Forums
Gurux.DLMS

Hi,

I use the settings:

Max payload size - 125

Packet SNRM with address size 1:

7E A0 1F 02 21 61 93 FF 13 81 80 12 05 01 7D 06 01 7D 07 04 00 00 00 01 08 04 00 00 00 01 89 E1 7E

Packet SNRM with address size 2:

7E A0 1F 02 21 61 93 FF 13 81 80 12 05 01 7D 06 01 7D 07 04 00 00 00 01 08 04 00 00 00 01 89 E1 7E

As far as I understand, the address with a size of 1 should be different, but here the packets are the same.

I use GXDLMSClient.GetServerAddress(logicalAddress, physicalAddress, addressSize) and see, that it return same value for size 1 and size 2.

Is this address formation correct?

Thanks.

Profile picture for user Kurumi

Kurumi

1 month ago

Hi, This is correct. When…

Hi,

This is correct. When the logical address is used, the GetServerAddress uses two bytes, or four if it doesn't fit for two. For that reason, the generated frames are the same.

BR,
Mikko

  • Log in or register to post comments
  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Tue, 05/20/2025 - 08:40
    gurux.dlms.c 9.0.2505.2001
  • Mon, 05/19/2025 - 10:19
    gurux.net.java 1.0.30
  • Mon, 05/19/2025 - 10:00
    gurux.dlms.c 9.0.2505.1901
  • Thu, 05/15/2025 - 16:26
    gurux.dlms.c 9.0.2505.1501
  • Wed, 05/14/2025 - 08:30
    gurux.dlms.c 9.0.2505.1401

New forum topics

  • HDLC Adress resolver configuration
  • Reading all "Data" object type parameter together
  • com_read getting failed for billing profile and instantaneous profile
  • Simulator connection closed
  • Regarding the dlms android project
More
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin