Error -201003 When I Run My Task in MAX or LabVIEW

Issue Details

• I have a LabVIEW application or NI MAX Task that is programmed to acquire data.  Most of the time the program runs fine but sometimes I get Error -201003 saying the devices aren't connected.
• I am trying to use an NI Data Acquisition (DAQ) device, such as a PCIe-6363, on a new or different computer. When I perform a self-calibration and a self-test, I get no errors. However, when I try to create a task in MAX, I get the error:

Solution

In addition to the possible reason(s) listed in the DAQmx Explain Error window, Error -201003 can be caused by the following:

• NI-DAQ™mx driver is not installed properly or has not been updated.
• The slot location of the DAQ device has been changed.

This problem can be caused by software incompatibility between your device driver, operating system, and development environment. Please ensure you are using the newest software versions that supports your hardware and your computer's operating system. If you do not have the newest device drivers that is supported by your hardware, OS, and software, please install the newest driver and restart your computer.

You can check to make sure your LabVIEW, operating system (OS), and driver versions are all compatible using the compatibility charts linked below.

• LabVIEW and Microsoft Windows Compatibility
• NI-DAQmx and LabVIEW Compatibility

If the hardware drivers are up to date and the issue still persists, try these additional steps: 

1. Check that the device is powered on and is detected by your operating system. To do so, go to Control Panel>>Device Manager and expand the Data Acquisition Devices category. If your module is visible in this section, it indicates that it is properly installed and has been detected by your operating system. If not, then turn your computer off and on again.
   1. If your device is not visible here, ensure that the device is properly powered. Many devices have a power LED. Ensure this LED is on. If it is not, your device or the power supply may be damaged. Try a different power supply.
   2. For PCI(e) devices make sure the device is properly seated in the PCI(e) slot of the host PC.
   3. For USB devices, make sure that the USB port is working on the PC, or try a different USB port on the host PC. 
2. After the NI DAQ device shows up in Device Manager, go to Measurement & Automation Explorer (MAX) and check if the device is visible under Devices and Interfaces. Older versions of MAX may contain a sub-directory for DAQmx Devices where the device should be found. If it shows up and gives the same error or does not appear, uninstall NI-DAQmx and reinstall it. Make sure you get the right version or if necessary, an updated version.
3. If you are using a cDAQ with an integrated controller, you may get this error if your executable runs before all of the modules initialize. Either wait before running your application or programmatically add a wait function.
4. If you are using a network cDAQ, check that the firmware is up to date and compatible with the installed version of DAQmx.
5. Lastly, if the NI DAQ Device shows up in MAX but still gives Error -201003 from the test panel, it indicates that the device is interacting with the driver but is giving the error because DAQ Assistant still has the previous configuration information from MAX. To update the module configuration for DAQ Assistant, do the following for every instance of DAQ Assistant in your VI that uses the same module:
   1. Double-click on DAQ Assistant and go to Configuration>>Details.
   2. Right-click the item under Physical Channel and choose Change Physical Channel.
   3. From the menu window that opens up, select the current device configuration and confirm that it is the right one by checking in MAX to see that the device number matches.
6. Alternatively to the previous step, you can change the name of the DAQ Device under MAX by right-clicking the device and selecting Rename from the menu.

If the NI DAQ device is not visible in Device Manager or never appears in MAX, it could indicate that the device is damaged. If possible, try the NI DAQ device on another host PC with a compatible software stack.
 

If using a cRIO compatible with the DAQmx driver.

When setting the Real-Time Executable as a startup application it may take some time to initialize all hardware during boot. This is due to DAQmx setting up synchronisation domains and other configurations for C-Series modules.

Try adding an initial delay of a few seconds before calling the DAQmx task. Some targets may take up to 90s to fully initialize.

 

Additional Information

This error can occur in any Application Development Environment (ADE) when using the NI-DAQmx driver.