DNP_3 ProcessGateway - variables timestamp is calculated wrong

• Related Articles

• SNMP ProcessGateway - trap timestamp is calculated wrong

  Description The SNMP Process Gateway produced incorrect trap timestamps that were offset because the Gateway calculated timestamps incorrectly. The issue has been addressed and the behavior is now as expected. To benefit from this fix: Update your ...

• LOGIC: StratonNG driver generates a wrong external timestamp after conversion from v12 to v14

  Description If a zenon Logic project has been converted from zenon version 12 to zenon version 14, the external timestamp of a variables set by VSI* functions went wrong (e.g. vsiCopy). The issue has been addressed and the VSI* function handling of ...

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

• Alarm areas: wrong value of status variables of linked Alarm Classes when number of alarms exceeds the size of ring buffer

  Summary If the number of alarms exceeds the size of the ring buffer, the status variables of linked Classes in Alarm areas are calculated wrong. Description If the number of alarms exceeds the size of the ring buffer, the status variables of linked ...

• FAQ: HTML5 WebEngine local variables are mirrored to all clients?

  Variables used in the WebEngine are mirrored into all HTML5 Clients. If a HTML5 Client has write access, it can alter variables for the native Service Engine and all connected HTML5 clients even when the calculation of the variable is set to "local". ...