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. Different OctetString

Different OctetString

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 wichot@hatmail.ir , 16 January, 2022
Forums
Gurux.DLMS

Hello,

Why two OctetString is Different but in Comment is same?

First Hex:
7E A0 1E 21 03 12 4C 08 E6 E7 00 C4 01 81 00 09 0C 07 E6 09 01 07 0A 0A 01 FF FF 2E 00 9C 39 7E

Translate:
<HDLC len="29" >
<TargetAddress Value="16" />
<SourceAddress Value="1" />
<!--I frame.-->
<FrameType Value="12" />
<PDU>
<GetResponse>
<GetResponseNormal>
<!--Priority: HIGH ServiceClass: UN_CONFIRMED invokeID: 1-->
<InvokeIdAndPriority Value="129" />
<Result>
<Data>
<!--2022-09-01 10:10:01-->
<OctetString Value="07E60901070A0A01FFFF2E00" />
</Data>
</Result>
</GetResponseNormal>
</GetResponse>
</PDU>
</HDLC>

Second Hex:
7E A0 25 21 03 12 AB 84 E6 E7 00 C4 01 81 00 09 13 32 30 32 32 2D 30 39 2D 30 31 20 31 30 3A 31 30 3A 30 31 FB F8 7E

Translate:
<HDLC len="36" >
<TargetAddress Value="16" />
<SourceAddress Value="1" />
<!--I frame.-->
<FrameType Value="12" />
<PDU>
<GetResponse>
<GetResponseNormal>
<!--Priority: HIGH ServiceClass: UN_CONFIRMED invokeID: 1-->
<InvokeIdAndPriority Value="129" />
<Result>
<Data>
<!--2022-09-01 10:10:01-->
<OctetString Value="323032322D30392D30312031303A31303A3031" />
</Data>
</Result>
</GetResponseNormal>
</GetResponse>
</PDU>
</HDLC>

if first hex, is DateTime Function created, but in second hex created with this code:

CGXByteBuffer test;
std::string val = "2022-09-01 10:10:01";
test.AddString(val);
test.Set(&test, 0, 0);
pClock->SetBegin(test);

SetBegin is CGXByteBuffer

and client cant show this time,
where is problem?

Best Regards

Profile picture for user Kurumi

Kurumi

4 years 4 months ago

Hi,

Hi,

The content is not the same. In the first example, you have date-time in octet-string and in the second one you have the string in the octet-string. DLMS standard defines the begin attribute of the clock object must be date-time in octet-string and adding date-time as a string is wrong.

DLMS standard defines data types that you must use and if you try to use different data types it doesn't work.

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

Who's new

  • Tuanhgg
  • Adel
  • charnon
  • Paddles
  • Miguel Ángel
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin