Onboard EtherCAT support is currently limited to AC500-eCo PM5072-ETH and PM5082-ETH. It is not supported by any other AC500 PLC.
Two alternatives are available for using EtherCAT:
-
Onboard EtherCAT for the AC500-eCo.
-
EtherCAT for the AC500 with the CM579 communication module.
Further information can be found here:
Onboard EtherCAT
⮫ Communication schema onboard Ethernet/EtherCAT
EtherCAT
Refer to the general description for information about the following tabs of the device editor.
Only in the case of special features is there an additional help page for the specific device editor.
If the "<device name> Parameters" tab is not shown, then select the “Show generic device configuration editors” option in the CODESYS options (“Device Editor” category).
The configuration of EtherCAT modules is based on the device description files for the used master and slave devices employed and can be adapted in the project in configuration dialogs. In order to make sure that the simplest and most error-free use possible, we recommend for standard applications that you enable the option for the “Automatic Configuration” of the master, so that the majority of the configuration settings are dopne automatically.
Optional devices
The “Optional devices” function can be used for variable hardware configurations. At the start of the stack, the system checks whether optional devices are available. If the devices are not found, then they are deactivated automatically. However, the devices can also be activated at a later date if, for example, it is a device at the end of the network line. On the other hand, if the “Automatically restart slaves” option is selected, then the activated devices are automatically switched to "operational", thereby activating the process data.
The bus cycle task is set in the general PLC settings.
Access to the EtherCAT configuration by the application takes place via instances of the EtherCAT master and EtherCAT slave. If the EtherCAT master or EtherCAT slaves are inserted as objects into a project, instances are automatically created for master and slaves which can be addressed in the application program. For example a restart, a stop or a status check of the EtherCAT device can be performed from the application.
Furthermore, the EtherCAT library offers function blocks for the reading and writing of individual parameters, even during bus operation.