Which products are affected?
ESP-DDS2-x (Global Drive PLC Developer Studio V2.x)
EPL-1020x (Drive PLC V7.x)
What happens?
A variable is not accessed (writing or reading) at the position of the Drive PLC memory which has been reserved for the variable. As a result, it is possible that other variables are overwritten or that a wrong value is read out.
When does the problem occur?
The response described above may occur when using one of the two functions L_MemReadDINT or L_MemReadDWORD of the LenzeMemDrv.lib or LenzeMemDrv0101.lib libraries.
Possible diagnostics?
Check by means of the DDS cross reference list (menu item: Project>Show Cross Reference) whether one of the functions L_MemReadDINT or L_MemReadDWORD is used in the project. Regarding this, please select the POU category in the Cross Reference dialog.
Short-term measures/recommendations?
Do not use the L_MemReadDINT or L_MemReadDWORD functions.
The revised LenzeMemDrv0102.lib library, with which this function restriction is eliminated, is installed when downloading Service Pack 1 of DDS V2.3. Replace the present LenzeMemDrv.lib or LenzeMemDrv0101.lib library by the new LenzeMemDrv0102.lib library in the Library manager dialog (menu item Window>Library manager).
Evaluation:
When using the L_MemReadDINT or L_MemReadDWORD functions variables may be accessed at a position in the PLC memory which is not reserved for the variable. The LenzeMemDrv library which contains the L_MemReadDINT and L_MemReadDWORD functions is used very rarely for the PLC target systems Drive PLC.
