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

• Related Articles

• AllenDF1 driver: FLOAT and STRING variables show wrong values when the offset considers data type flag is active on driver configuration

  Summary In specific project configuration/offset constellation invalid Bit is set when a FLOAT variable is seen in a screen even if all offset configuration is correct. The problem occurs when in the driver configuration it is enabled the "Offset ...

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

• 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

  Description The MELSECA driver behaves unexpectedly when reading data points of the internal Relay M in an optimized way. Sporadically wrong values are displayed. This occurs in an offset range between two or more variables >= 480 words (7680 bits). ...

• Checklist: Driver(s) cannot establish a reliable communication

  Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• The HYDROMETER driver does not map the variables to the correct registers according the configured variable offset.

  Summary When a variable with according offset is advised for every register in the zenon runtime, the HYDROMETER driver maps the register values correctly to the appropriate variable offsets. When only having a few variables advised in the zenon ...