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 GXDateTime Value After Upgrading

Different GXDateTime value after upgrading

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 henkyprayoga , 24 September, 2020
Forums
Gurux DLMS for Java

Hi,

Before I'm using Gurux.java version 3.0.6. Here's how it parse using that version:

<WRAPPER len="36" >
<TargetAddress Value="1" />
<SourceAddress Value="1" />
<PDU>
<!--Decrypt data:
<GetResponse>
<GetResponseNormal>
<!--Priority: HIGH ServiceClass: CONFIRMED invokeID: 1-->
<InvokeIdAndPriority Value="C1" />
<Result>
<Data>
<!--9/25/20, 2:19 AM-->
<OctetString Value="07E409190502132D00000000" />
</Data>
</Result>
</GetResponseNormal>
</GetResponse>
-->
<GeneralGloCiphering>
<SystemTitle Value="148D000000020003" />
<CipheredService Value="3000000001F7D9016C81911EF2B2A514E0BCB6EC457B708726BA7E3AF2BF33508EA27A" />
</GeneralGloCiphering>
</PDU>
</WRAPPER>

However, after I upgrade it to 4.0.23, the DateTime shifted +7 hours. I believe this is due to our time zone is GMT+7

<WRAPPER len="36" >
<TargetAddress Value="1" />
<SourceAddress Value="1" />
<PDU>
<!-- Decrypt data: C4 01 C1 00 09 0C 07 E4 09 19 05 02 13 2D 00 00 00 00
<GetResponse>
<GetResponseNormal>
# Priority: HIGH ServiceClass: CONFIRMED invokeID: 1
<InvokeIdAndPriority Value="C1" />
<Result>
<Data>
# 9/25/20, 9:19 AM
<OctetString Value="07E409190502132D00000000" />
</Data>
</Result>
</GetResponseNormal>
</GetResponse>
-->
<GeneralGloCiphering>
<SystemTitle Value="148D000000020003" />
<CipheredService Value="3000000001F7D9016C81911EF2B2A514E0BCB6EC457B708726BA7E3AF2BF33508EA27A" />
</GeneralGloCiphering>
</PDU>
</WRAPPER>

How to use the latest version but with the same timezone behavior with 3.0.6?

Thank you very much.

Profile picture for user Kurumi

Kurumi

5 years 11 months ago

Hi,

Hi,

I believe that your meter is using UTC time zone and not the DLMS standard time zone.
http://www.gurux.fi/Gurux.DLMS.Objects.GXDLMSClock

Set
cl.setUseUtc2NormalTime(true);

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