ENI File tab

During the compilation, the KAS-IDE generates the EtherCAT Network Information (ENI) file based on the EtherCAT devices defined in the project.

EtherCAT XML Configuration File

Figure 1: ENI File tab

Import or Export an EtherCAT ENI File

Item

Description

Import ENI File

Used to browse and select an ENI file to be imported.

  • If the file is successfully imported into the project, the Use imported file option is automatically selected.
    • Once imported, the ENI file is added to the project.
  • This enables you to include EtherCAT devices in the project that are not natively supported by KAS.
  • See Add an Unsupported EtherCAT Device for more information.

Use imported ENI file

Used to specify whether or not to use the imported ENI file.

Export ENI File

Used to export the ENI file generated by the KAS-IDE.

  • Specify the name and directory for the file.
  • Only the logical devices in the project tree that are mapped to a physical device (and not simulated) are taken into account when generating the ENI file.
  • This export can be useful if you want to use the file in another context or with another program.

  • Importing an external ENI file overrides all EtherCAT project device information and configuration settings in the KAS-IDE.

    These views and configurations are not applicable when using an imported ENI file:

    • Project View: All devices located under the EtherCAT node.
    • EtherCAT Device View tabs:
      • General Properties
      • PDO Selection/Mapping
      • Distributed Clock
      • CoE Init-Commands
    • Slice I/O Properties
    • Mapping PLC Variables to Slice I/O or PDO objects.

    Information displayed in the views may not match the imported ENI file.

Use an Imported ENI File

  • The KAS-IDE works in a degraded mode when using an imported ENI file, and the Mapped to Axis settings are disabled.
    • This is because the information about the devices in the project tree and the EtherCAT widget table is no longer relevant.
  • When using an imported configuration file these parameters must be manually set for each axis:
    • the type of motion bus.
    • its address on the fieldbus ring.

    This is done by right-clicking on the Axis Pipe Block and selecting the Properties command.

  • Scan Devices must be run from the EtherCAT Devices tab before downloading the application to the controller.