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. Gxtime Y38K Bug

gxtime Y38K bug

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 wildstray , 10 January, 2022
Forums
Gurux.DLMS

I'm working on clock registers and noticed that gxtime structure using everywhere to represent timestamps in other structures or alone, has the value only 32 bit long in epoch format...

typedef struct
{
#ifdef DLMS_USE_EPOCH_TIME
uint32_t value;
#else
struct tm value;
#endif
int16_t deviation;
DATETIME_SKIPS skip : 16;
DLMS_DATE_TIME_EXTRA_INFO extraInfo : 8;
DLMS_CLOCK_STATUS status : 8;
} gxtime;

So the library itself is affected by Y38K bug. Are also raw COSEM timestamps in 32 bits format... so this is a structural and uncorrectable bug... or it could be avoided changing uint32_t with uint64_t value in struct gxtime?

TIA!
BR,
Andrea

  • 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