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 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.
Solution
Addresses larger oxFFFF are now handled correct.
Information
Issue Number: 34616
Fixed on Date: 16.6.2015
Versions: 7.11 0 BUILD 20530 | 7.20 0 BUILD 19742
Related Articles
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 ...
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 ...
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 ...
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, ...