FAQ
Overview
- Why is it not possible to activate the configuration in the TwinCAT project?
- Why is it not possible to log into the PLC in the stand-alone PLC project? (a)
- Why is it not possible to log into the PLC in the stand-alone PLC project? (b)
Why is it not possible to activate the configuration in the TwinCAT project?
Error Message: "Cannot copy file target – source file ‘…’ not found"
Cause: This error can have different causes:
1. | The ADS port of the stand-alone PLC project and the PLC instance in the TwinCAT project are not identical. |
| Solution: Set the same ADS port at both levels, recompile the stand-alone PLC project. If the Auto Reload TMI/TMC option is not activated in the PLC instance configurator, reload the TMC file. |
2. | The TwinCAT project and the stand-alone PLC project were not compiled for the same platform. |
| Solution: Compile both projects for the same platform. If the Auto Reload TMI/TMC option is not activated in the PLC instance configurator, reload the TMC file. |
3. | Only the TMC file was provided for the TwinCAT project, so that the path of the TMC file does not lead to the stand-alone PLC project and the PLC runtime data cannot be accessed. |
| Solution: Disable the Activate PLC configuration (copy boot files) option in the Settings tab of the TwinCAT project PLC settings. |
Why is it not possible to log into the PLC in the stand-alone PLC project? (a)
Error Message: "PLC instance parameter (0x0850801a) missmatch. Download will be aborted."
Cause: If this error occurs, the PLC module instance information has not been updated before logging in.
Solution: Acknowledge the error message dialog with Yes and ignore the subsequent error messages, or update manually using Update Instances from Target.
Why is it not possible to log into the PLC in the stand-alone PLC project? (b)
Error Message: "PLC instance parameter (0x08500005) missmatch. Download will be aborted."
Cause: If this error occurs, the PLC project does not correspond to the PLC instance of the activated TwinCAT project. This means that the TMC file and thus the PLC instance was not updated in the TwinCAT project after changes in the stand-alone PLC project.
Solution: Acknowledge the error message dialog with Yes or No and ignore the following error messages. Then update the TMC file in the TwinCAT project (context menu PLC project instance > TMI/TMC File > Reload TMI/TMC File…). If the TMC file is not provided separately but is added directly via the path of the stand-alone PLC project, the Auto Reload TMI/TMC option should be enabled in the PLC instance configurator.