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

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

• 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

  Summary Driver closes unexpectedly after receiving a timestamp referring to 1.1.1970 in a time zone with negative offset and daylight saving active Description Driver closes unexpectedly after receiving a timestamp referring to 1.1.1970 in a time ...

• FAQ: From a certain amount of connected Smart Clients the Smart Server closes unexpectedly, what can I do?

  It is possible that the Smart Server closes as it runs out of possible memory address space for a 32-bit application. In this case use the Smart Server 64-bit version.

• T5BusProfNetIO: stratonrt closes unexpectedly when receiving an invalid ProfiNet DCP frame

  Summary The zenon logic application using a ProfiNet IO Contoller fieldbus driver closes unexpectedly on receiving an invalid ProfiNet message. Description The zenon logic application using a ProfiNet IO Contoller fieldbus driver closes unexpectedly ...

• The DNP3_TG driver closes unexpectedly without an error message after receiving a specific response to a file transfer request.

  Summary The DNP3_TG driver closes without an error message when a specific outstation reports a file size 0xFFFFFFFF in a response to a file open request. In this particular case, the outstation reports 0xFFFFFFFF to indicate not a file size of 4GB ...