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 consecutive address range.
Solution
When the new driver configuration option "Optimized reading and writing" is enabled the driver uses a block size of up to 960 words. When disabled the driver behaves as before and uses a block size of up to 64 words.
This option is available only when using Mitsubishi Q series PLCs with the 3E binary format.
Issue Number: 214304
Fixed on Date: 14.5.2020
Versions: 8.10 0 BUILD 65969 | 8.20 0 BUILD 66111
Related Articles
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 ...
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] ...
FAQ: It seems that sometimes not all variables are correctly written to the PLC by the RGM module, although the system driver variable states that the recipe was written successfully and the option "write synchronously" is active. How can this be?
When reading a RGM recipe immediately after writing a RGM recipe, with a driver that has the option "keep update list in memory" active, and recipe variables that have been read previously, it can happen that a read cycle is currently in progress, ...
LSIS Driver doesn't fit the read/write address If variable create the bool type.
Description The LS Industrial Systems XGT driver (LS_XGT) does not use the correct read/write address for variables of type Bool. The driver writes to a different address than it uses for reading. This behavior depends on the configured type. This ...
FAQ: When I activate the option "write synchronously" for the Recipegroup manager recipe, and I write the recipe, the recipe does not seem to be written properly and also the Service Engine does not close properly. Why is that?
When the option "write synchronously" is active at a recipe, when writing a recipe (sending values to the PLC) for each recipe variable a writing confirmation is requested to the driver. On a successfull write, the driver sends a writing confirmation ...