Error -2147138467 When Trying to Read or Write the SDO of a EtherCAT Device

Updated Sep 28, 2026

Reported In

Software

  • LabVIEW

Driver

  • NI-Industrial Communications for EtherCAT

Issue Details

I'm working with a third-party EtherCAT device in LabVIEW™. When I try to read or write a Service Data Object (SDO), I receive the following error:

Error -2147138467 occurred at Invoke Node in SDO-readParam.vi->testTemp.vi


Possible reason(s):
NI-Industrial Communications for EtherCAT: (Hex 0x8005445D) An SDO request sent by the master has been aborted by the slave device due to incorrect initial commands or incorrect PDO selection. Check the configuration of the slave device on the device's property page and ensure that the configuration is correct.

Solution

This error can occur for several reasons related to EtherCAT slave configuration and compatibility. Review the following troubleshooting steps:

 

  • Verify that the correct EtherCAT Slave Information (ESI) file is being used. If the device uses a SoftMotion Drive Interface (SDI) Plug-in, do not import the manufacturer's default ESI file into LabVIEW. The SDI Plug-in may require a modified ESI file, and using the manufacturer's file can result in incompatible object mappings.
  • Verify that the firmware installed on the third-party drive matches the firmware version for which the SDI ESI file was created. The supported firmware version can typically be found in the title of the ESI file located in: C:\Program Files (x86)\National Instruments\Shared\IndComECAT\DD
  • Install a compatible version of NI-Industrial Communications for EtherCAT. Download the latest supported version from the NI website.
  • Collect a Wireshark [EXTERNAL LINK] network capture to analyze the EtherCAT communication between the Real-Time target and the EtherCAT device. Reviewing the packet exchange may help identify rejected SDO requests or configuration mismatches.

Additional Information

The error code 0x8005445D indicates that the EtherCAT slave device rejected the SDO request. This commonly occurs when:

 

  • The requested object index or subindex is not supported.
  • The slave device firmware version does not match the imported device description.
  • The configured PDO mapping differs from the mapping expected by the application.
  • The EtherCAT slave was deployed with an incompatible ESI file.