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
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] ...
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: 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, ...
MELSECA.exe driver Frame 3E, Optimized reading and writing sends more than 960 words if more than 15360 device points have been defined
Description The PLC responded with an error rejecting read/write requests during optimized communication. This was caused by the MELSECA driver producing Frame 3E requests that exceeded the 960-word/block limit when more than 15,360 device points ...
MELSECA: enhancements to meet market needs
The already existing driver object types Link Relay, Latch Relay and Internal Relay M now support the 16-bit data types INT, UINT and WORD. In addition, these new data types use batch-read and batch-write for the BOOL-based address range to read or ...