Error 0xFFFEFE26 When Deploying EtherCAT Configuration in LabVIEW™

Updated Sep 2, 2026

Reported In

Hardware

  • NI-9145
  • CompactRIO Controller

Software

  • LabVIEW
  • Measurement & Automation Explorer (MAX)

Driver

  • NI-Industrial Communications for EtherCAT

Issue Details

When working with a CompactRIO and an EtherCAT chassis or a third-party EtherCAT slave device, I receive the following error during deployment after renaming a module or adding a new module:


Error Code: 0xFFFEFE26   An internal error has occurred: The device identity data is not valid for this I/O plugin. 

 

The error occurs when deploying the EtherCAT configuration from the LabVIEW project.

Solution

This error can occur when the EtherCAT configuration being deployed conflicts with an EtherCAT configuration that is already deployed on the NI Real-Time controller.

 

To remove the existing configuration and deploy the updated one:

 

  1. Open the LabVIEW project.
  2. Right-click EtherCAT Master and select Undeploy

 

 

  1. Wait for the undeploy operation to complete.
  2. Right-click EtherCAT Master and select Deploy.

 

 

If the error persists, perform the following troubleshooting steps:

 

  1. Verify that the installed C Series modules and EtherCAT chassis are supported by the programming mode being used. Refer to C Series Module and CompactDAQ or CompactRIO Hardware Compatibility.
  2. Reset the NI Measurement & Automation Explorer (NI MAX) database:
    1. Open NI MAX.
    2. Reset the database following Reset and Fix the Measurement & Automation Explorer Database File to clear any corrupted device configurations.
    3. Restart the CompactRIO controller.
  3. Re-detect and configure the EtherCAT hardware.
  4. Redeploy the LabVIEW project.

Additional Information

Conflicting deployed EtherCAT configurations may remain on the Real-Time target after hardware changes, such as renaming modules or modifying the EtherCAT topology. Removing the deployed configuration before deploying the updated project can resolve deployment inconsistencies.