Which products are affected?
L-force Loader V4.0
GD Loader V3.0
What happens?
A parameter set file (*.GDC) which does not match with the binary file (*.BIN) included in the PLC target system can be downloaded to a PLC target system. If the L-force Loader writes user codes which are not included in the PLC target system these codes are indicated in a message box. A message window informs the user that the parameter set transfer was faulty.
When does the problem occur?
The response described above occurs when the L-force Loader is first used to load a binary file and the matching parameter set file to a PLC target system. Then another binary file with the parameter set file selected before is loaded to the same target directory. In this case the L-force Loader does not realize that the parameter set file does not match with the binary file.
Possible diagnostics?
None.
Short-term measures/recommendations?
This function restriction is eliminated with L-force Loader V4.2.
The L-force Loader V4.2 checks before downloading the parameter set file which binary file is included in the PLC target system. The message window displays the following information:
Starting a rescan to update the Lenze Drive Server information. This will take some time.
Evaluation:
A parameter set file which does not match with the binary file can be loaded to the PLC target system by means of L-force Loader V4.0. It is quite unusual to load different binary files with the same parameter set file directly one after the other to the same PLC target system. This function restriction is eliminated with L-force Loader V4.2.
