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. 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 year 3 months 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

  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Mon, 07/27/2026 - 12:37
    gurux.dlms.cpp 9.0.2607.2701
  • Thu, 07/23/2026 - 16:19
    gurux.dlms.java 4.0.96
  • Thu, 07/09/2026 - 14:34
    Gurux.DLMS.Python 1.0.201
  • Fri, 06/26/2026 - 16:32
    Gurux.Service 3.0.2606.2601
  • Wed, 06/24/2026 - 08:36
    Gurux.DLMS.Python 1.0.200

New forum topics

  • Service not known error on gprs communication
  • Help Needed: Interfacing Saral 100 Energy Meter with Microcontroller via RS232
  • Connecting Meter to Agent via serial
  • Reading block profile with Compact array
  • DLMS server - serving multiple similar datasets gathered from multiple meters across distinct logical addresses
More
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin