Limitations

The following limitations are considered when working with the Automation_Builder ECAD interface:

• The scope of a PBF file is limited to one single PLC including all connected devices.
• There is no representation of XC variants of devices in Automation_Builder. Therefore, always use the standard variant for export. This might lead to part data mismatch when importing into the ECAD tool.
• In reimport or round trip import cases, if any changes are made in ECAD by adding a new communication module with connecting to one of the PLC slot or replacing existing communication module, then those device changes to the communication modules are not displayed as connected to PLC slots during the import in Automation_Builder diff and import, instead those CM modules are added under the device pool. After merging and importing is completed, to work with device pool devices Export and Import Interfaces Export and Import Interfaces.
• IO mapping data cannot be imported for IO devices plugged to an EtherCAT slave when they are imported individually to the device pool because of missing hierarchy information. After arranging the devices properly in the device tree, the import can be done again to import also the IO mapping data.