Vai al contenuto

Reviewing the Year 2038 Issue (Y2K38)

Support ElsistTopicReviewing the Year 2038 Issue (Y2K38)

Home › Forum › Controllori SlimLine e Netsyst (LogicLab) › Reviewing the Year 2038 Issue (Y2K38)

Stai visualizzando 2 post - dal 1 a 2 (di 2 totali)
  • Autore
    Post
  • Maggio 19, 2026 alle 1:49 pm #85577
    Anonimo
    Inattivo

    As part of our technical risk assessment and long-term operational and lifecycle evaluation of the systems used in our projects, we are currently reviewing the so-called Year 2038 issue (Y2K38).

    As you are aware, systems that process time information based on signed 32-bit Unix timestamps may experience overflows and resulting malfunctions beginning on January 19, 2038. In particular, long-life industrial, automation, and embedded systems may be affected with regard to stability, availability, as well as security and communication functions.

    Against this background, we kindly request your technical assessment regarding the products, components, and software/firmware versions supplied by your company.

    Maggio 19, 2026 alle 1:51 pm #85579
    Sergio Bertana
    Amministratore del forum

    In our SlimLine systems two system time management functions are available:

    SysDateGetS (time in seconds):
    This function returns the system date and time in UTC expressed in seconds, using a 32-bit UDINT variable. The supported time range extends from 00:00:00 on January 1st, 1970 to 06:28:15 on February 7th, 2106.

    SysDateGetNs (time in nanoseconds):
    This function returns the system date and time in UTC expressed in nanoseconds, using a 64-bit ULINT variable. The supported time range extends from 00:00:00 on January 1st, 1970 to 23:34:33.709 on July 21st, 2554.

    Both functions are therefore immune to the Year 2038 problem (Y2K38). The first overflow limitation occurs with SysDateGetS in 2106, while using SysDateGetNs extends the limit up to 2554.

    However, the issue may arise from how the PLC program is implemented. If DATE and DATE_AND_TIME data types are used, the system may still be exposed to the Y2K38 problem. For this reason, we recommend using 64-bit data types in application development wherever possible.

    More information is available in this article.

  • Autore
    Post
Stai visualizzando 2 post - dal 1 a 2 (di 2 totali)
  • Devi essere connesso per rispondere a questo topic.