DAQmx Error -50400 or -223022 on NI PCI/PXI Devices

Updated Nov 30, 2022

Reported In


  • LabVIEW


  • NI-DAQmx

Issue Details

I receive either:

Error -50400: The transfer did not complete within the timeout period or within the specified number of retries
Error -223022: Internal Software Error occurred in DSA software. Please contact National Instruments Support

on my NI PCI/PXI device.


Error -50400:

This error indicates that the board cannot communicate with the onboard FPGA.  If the board cannot communicate with the FPGA it will not function.

Both of these error codes indicate fairly general problems that may have a number of causes in both hardware and/or software. The following troubleshooting steps should be performed in order to rule out possible software causes.  

  • Reset the device in the Measurement & Automation Explorer (NI-MAX).
  • Reboot the PC or PXI controller. 
  • Try the device in different PXI/PCI slots.
  • Reinstall the device driver in the device manager by deleting the device and letting the operating system re-detect the hardware (Action>> Scan for New Devices in the Windows Device manager). 

NOTE:  You do not need to reinstall DAQmx.

  • Self-test and Reset the device in NI-MAX - if the board is still not functioning it will throw the error here.
  • If possible, try the device in a different system.
  • Try using the system with another PC. In some cases the error might be a result of motherboard incompatibility.  
If the board still doesn’t function after trying these steps then please contact NI support for further troubleshooting.

Error -223022:

This error indicates that the ADCs never came out of their initial calibration cycle which is done immediately after driver load when the system boots.  This will occur at start up and if the calibration cycle fails then the device will be inoperable until the system is restarted and the device boots correctly. 

The error -223022 can sometimes be observed during a device self-test for a module showing a red X in Devices and Interfaces. After self-testing and failing on this error, continuing again with a self-test can result in the same error repeated. Using the same troubleshooting steps above, the problem can be addressed.