Corrected from: PLC Designer V3.12
Response of the new version:
When updating an EtherCAT slave in a PLC Designer project, the previously selected mapping to the slave's process data is maintained.
What happens?
- After building a project, the following error message appears:
"Identifier 'xxx' not defined"
- A variable mapped to a process date of an EtherCAT slave has no write/read access to the process date.
When does this behaviour occur?
If an EtherCAT slave is updated in a PLC Designer project (menu item "Update device..." in the context menu of the slave or "Set all to newest" in the project environment), the PDO selection is reset to the default setting in the "Process data" tab of the slave. I.e. the mapping to all process data which is not in the default setting is deleted.
The error message described under 1. occurs during the build process if a variable has been declared on the "EtherCAT I/O mapping" tab and this process date was dropped when updating the EtherCAT slave due to the reset to the default setting.
The problem described under 2. occurs if a variable globally or locally declared in a POU was mapped to a process date in the EtherCAT I/O mapping which was dropped due to the update.
Which products are affected?
PLC Designer V3.9 and higher
Short-term measures:
After updating an EtherCAT slave, check the EtherCAT I/O mapping of the EtherCAT slave and correct the mapping, if necessary.
Evaluation/recommendations:
After updating an EtherCAT slave in a PLC project, part of the mapping may be reset or deleted. The mapping can be restored manually. An EtherCAT slave update is required if a later device description is to be used in a PLC project.
