Zenon drivers: driver closes unexpectedly after receiving a timestamp referring to 1.1.1970 in a time zone with negative offset and daylight saving active

• Related Articles

• FAQ: What is the time zone and time format used in zenon Software Platform products and what needs to be considered?

  When you ask someone what the time is, they'll usually be able to tell you. But when you ask them what date and time sunrise was yesterday in a different country on a different continent, in a different hemisphere it gets less easy. Terms like GMT ...

• File Inspector: Time zone field does not considers the daylight saving period of a time zone

  Description In the File Inspector, the daylight saving time is not correctly displayed in the "Time zone" drop-down list. Instead of "UTC+2:00", "UTC+1:00" is displayed. However, the calculation is done correctly with an offset of "UTC/GMT + 2 ...

• DNP332 driver and DNP3_NG driver closes unexpectedly on receiving an object with a 0 timestamp on systems with a timezone greater or equal than GMT+1

  Summary When the DNP332 driver or the DNP3_NG driver receives a DNP object that contains a 0 timestamp, (01.01.1970 0:00:00.000) the driver can close unexpectedly processing this timestamp value when the system is configured to use a timezone larger ...

• zenon Changesets Excel

  Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in CSV format ...

• zenon Changesets CSV

  Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in as Excel ...