ESI and ENI Files

The EtherCAT master uses the information from the ENI file to initialize and configure the EtherCAT network.

• The ESI files are provided by the vendor for each device.
  • They contain information about the device functionality and its settings.
• The ESI files are used by the KAS-IDE to generate the ENI file.
• The KAS controller’s EtherCAT master uses the ENI file for network initialization and configuration.

Figure 1: EtherCAT Network Architecture 1 Image courtesy of EtherCAT.org, http://www.ethercat.org/pdf/english/etg2200_v2i0i1_slaveimplementationguide.pdf

ENI File

A network configuration file in XML format. The ENI file describes the network topology, the initialization commands for each device, and commands which have to be sent cyclically. The ENI file is provided to the master, which sends commands according to this file. The KAS-IDE creates the ENI file after a network discovery, which can be exported or imported. A scan and compile should be redone, if the network changes, in order to regenerate the ENI file.

ESI File

A device description in XML format. This is a fixed file provided by the supplier of a given EtherCAT device. The ESI file contains information about the device's functionality and settings. EtherCAT device vendors must provide an ESI file, which is used by the KAS-IDE to compile the network information (e.g., process data structures, initialization commands) and create the ENI file.

• 
  

• KAS uses ENI schema version 1.3 (May 20, 2009).
  See the ETG.2100 specification at www.ethercat.org for more information.