Deployment and Scan Mode Errors Using EtherCAT

Updated Nov 6, 2023

Reported In


  • Industrial Controller
  • CompactRIO Chassis


  • LabVIEW


  • NI-Industrial Communications for EtherCAT

Issue Details

I am running into errors when deploying my code to a Real-Time controller that is configured as an EtherCAT master. What do these errors mean and how can I resolve them?

Related Errors

After Successful Deployment 

An error occurred while attempting to switch the I/O scan mode. 

The slave device deployed to the real-time target does not match the device in the EtherCAT network. The mismatch happens if a slave device has been inserted, removed, or substituted after deployment. Redeploy the device to ensure that each device in the network matches the device in the LabVIEW project tree.

Deployment Error

LabVIEW: (Hex 0x80DF0002) A File I/O error occurred

After Refreshing Modules in NI Distributed System Manager

Error -66226 occurred at an unidentified location

Possible reason(s):

LabVIEW: (Hex 0xFFFEFD4E) Incorrect use of internal API for I/O variable


error -66226.png



Please be aware that these errors can occur in different contexts. Below you will find some general troubleshooting steps you can try to implement to solve the issue. 
  • The primary Ethernet port on a Real-Time (RT) controller cannot be used for EtherCAT communication. One cause of the errors mentioned above is attempting to use the primary Ethernet port for EtherCAT communication. You can check which Ethernet adapter is primary in NI MAX by navigating to the Network Settings tab of your target (see screenshot below). 
  • Undeploy the old configuration, rebuild the application, and redeploy everything to the target (may resolve software corruption).
  • Try switching your RT target to active mode (enables connection to the network), by right-clicking over the target and selecting Utilities»Scan Engine Mode»Switch to Active Mode.
  • Reinstall the NI Scan Engine software on your RT controller. 
  • Reformat the controller (may resolve hardware issues).

Additional Information

If the LabVIEW: (Hex 0x80DF0002) Error persists, and you are using cRIO 21.0 upgrade to cRIO 22.0.0 or the latest to fix the issue.