IEC62056-21 driver, variable with datatype 'Date and Time' lead to driver stop if timestamp is invalid.

• 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 ...

• S7TCP32 driver stops if you read DATE AND TIME variable with wrong time values

  Summary The S7TCP32 driver stops if it reads a DATE AND TIME variable with a wrong time value. That means one of the following Byte values is out of range: Byte 3 - hour - crash with value 30 or higher Byte 4 - minute - crash with a value 90 or ...

• The RemoteRT driver does not consider the following changes in the editor when afterwards a reload of the runtime is performed: modifying a former incorrect net address to a correct net address and then perform a reload of the zenon runtime does not lead to a correct communication behaviour (variables stay INVALID) modifying a former correct symbolic address of a variable to an incorrect symbolic variable and then perform a reload of the zenon runtime does not lead to a communication error (va

  Summary The RemoteRT driver behaves unexpected under following circumstances: change over from a former incorrect net address to a correct net address and then perform a reload of the zenon runtime does not lead to a correct communication ...

• Sorting by timestamp in the variable diagnosis screen in the runtime ignores the date

  Summary When sorting on the timestamp column in the variable diagnosis screen, only the time is considered from the timestamp, not the date. DescriptionWhen sorting on the timestamp column in the variable diagnosis screen, only the time is considered ...

• S7TCP driver is adding the timezone difference to a value of a DATE_AND_TIME Variable

  Description The S7 TCP-IP driver did not handle timezone differences regarding UTC and local system time correctly for DATE_AND_TIME variable values. The issue has been fixed and the behavior is now as expected. To benefit from this fix: Update your ...