MELSECA: When optimized reading datapoints of internal Relay M with an offset range between two or more variables >= 480 words (7680 bits) then driver behaves unexpectedly

• Related Articles

• MELSECA: Driver does not use maximum block size for read and write requests

  Summary The MELSECA driver does not use an optimized block size for reading and (block)writing variables in a consecutive address range. Description The MELSECA driver does not use an optimized block size for reading and (block)writing variables in a ...

• FAQ: Can I insert more than one instance of internal driver in one project?

  In the Engineering Studio it was possible to create a second instance of the intern driver. Since zenon 8.00 it is not possible anymore to use a second instance of internal driver in the Service Engine. In future versions of zenon the possibility to ...

• MELSECA driver cannot read/write file regster variables above offset 65535

  Summary MELSECA driver cannot read/write variables of object type file regster above offset 65535 If higher offsets are used it seem to work, but does not write on the correct address. Or the variable gets an invalid status. Description MELSECA ...

• FAQ: Initialization of Internal variables (Network) in Dominant redundancy mode.

  When (re-)starting the dominant Server 1, regardless of their 'Remanence' configuration, internal variables with calculation in 'Network' are initialized first in the dominant Server 1 and only after synchronized with the running Server 2. Modules ...

• MELSECA driver: String variables show the value of the 1st (offset) string variable if displayed on the same screen

  Summary MELSECA driver: If string variables with consecutive addressing (offsets) are displayed on the same screen they all show the value of the 1st addressed (offset variable). On different screens the variables display the correct and respective ...