ESI Files Tab

This tab lists the available ESI (EtherCATClosedEtherCAT is an open, high-performance Ethernet-based fieldbus system. The development goal of EtherCAT was to apply Ethernet to automation applications which require short data update times (also called cycle times) with low communication jitter (for synchronization purposes) and low hardware costs Slave Information) files and provides the ability to add and remove files.

Figure 5-109: The ESI Files tab

ESI files are sorted by vendor and then the files provided by the vendor. Each file lists the device it supports including

  • Device name
  • Device description
  • Device revision number

ESI files are easily added to the list by clicking the Add button and navigating to where the file is saved. The Delete button will remove a file from the list but not your hard drive.

For more information on working with ESI files, see the ESI File Management topic.


  • WARNING: Replacing an ESI file changes the configuration of any associated device to the new file. You will be prompted to confirm or cancel replacing an ESI file and the associated devices' configurations.

ESI files will be replaced when: 

  • Opening a project file that contains an ESI file that is different from the file in the KAS Internal Library of ESI Files stored on the PC.
    • You are prompted to select "term_A" (use the version in the project) or "term_B" (use the ESI Internal Library version). Selecting "term_A" will overwrite the ESI Internal Library version.
  • Pressing the Add button in the ESI Files tab view and:
    • importing an ESI file name that already exists in the KAS Internal Library of ESI Files stored on the PC.
    • importing an ESI file that contains duplicate device information that already exists in the KAS Internal Library of ESI Files stored on the PC.

  • It is strongly recommended that you do not add or remove ESI files while multiple instances of the KAS IDE are open. Doing so modifies a global cache of ESI files. Changes to the global ESI file cache from one instance of the KAS IDE could create unexpected consequences in another instance.