LOGIC: Shared Memory driver generates a wrong timestamp after conversion from v12 to v14

• Related Articles

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

• Cannot create a CTI variable using driver object type V Memory

  Summary In zenon 7.10 Editor (32 & 64 bit), if you have a pre-existing CTI variable, you cannot change its driver object type from K-memory to V-memory. Note: Even with creating a new variable based on CTI driver, V Memory object Type, REAL Datatype, ...

• T5BusExZenOnRT : Zenon to Logic shared memory. Some value change are lost in VMRead

  Summary If values from zenon Runtime to Logic runtime must be buffered due to a sharing violation of shared Memory these values are never re-sent if every 100ms cycle there are set values to be transefered from Logic Runtime to zenon Runtime. ...

• OPCUA client driver after the build 55804 generates with the variable import wrong variable names

  Summary OPCUA Client driver generates wrong variable names at import (after build 55804) Description OPCUA Client driver generates wrong variable names at import (after build 55804) Information For the version 7.60 and 8.00 exists the posibility to ...

• Value of a variable is set to zero (0) after writing in zenon logic when the variable is from the straton to zenon runtime shared memory driver, and the zenon driver is set to simulation programmed

  Summary With a modbus energy driver set to simulation programmed, and a variable of the modbus energy driver set to "externally visible", writing the variable in a zenon logic runtime sets the variable value to zero. The variable can be correctly ...