EtherCAT Configuration Not Updated in LabVIEW after Editing the ESI File

Updated Apr 18, 2024

Reported In


  • cDAQ-9132


  • LabVIEW


  • NI-Industrial Communications for EtherCAT

Operating System

  • Windows

Issue Details

I am using a 3rd-Party EtherCAT Slave Device (Bronkhorst) to communicate with a NI cDAQ Real Time 9132. I edited the ESI XML file (EtherCAT Slave Information) provided by the manufacturer using TwinCAT in order to add new custom variables within the ESI XML file. After I edited the original XML file and generated an edited XML file, I uploaded the new ESI File in LabVIEW but the modification provided is not taken into account in LabVIEW. The added variables are not shown in the LabVIEW project explorer as expected.

Why is my new configuration not updated in LabVIEW after I edited the ESI XML file?


If you do not see any change in the LabVIEW project, this means that your new XML file is not taken into account by your device. Actually, the device in the LabVIEW project is indexing a special directory that is supposed to host the XML file. After importing the new XML file, it is possible that the your device keeps indexing the old XML in the Directory.
Please go to the following directory C:\Program Files (x86)\National Instruments\Shared\IndComECAT\DD and delete the old XML file and try to import your new XML file again. After that, you should be able to see the update made in your file.

Additional Information

Please note that the above solution is applicable for other Third-Party devices.

For information about how to import a Third-Party ESI XML file in LabVIEW, please click here.