This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

Device Produces Error -88705 or 800403833 in NI-MAX but Shows Up in Windows Device Manager

Updated Jun 19, 2019

Reported In

Hardware

  • GPIB-USB-HS
  • GPIB-USB-B
  • cDAQ-9188
  • cDAQ-9184
  • NI ELVIS
  • NI-9862

Software

  • NI-XNET 18.5

Driver

  • NI-DAQmx
  • NI-488.2

Operating System

  • Windows

Issue Details

  • I have a GPIB/DAQmx device that I'm trying to open in the Measurement and Automation Explorer (NI-MAX). When I self-test it in MAX, I get the following Error -88705:The specified device is not present or is not active in the system. The device may not be installed on this system, may have been unplugged, or may not be installed correctly.
  • When I look for my GPIB/DAQmx device in Windows Device Manager, my device shows up correctly. If this has happened before, I remember needing to restart something, potentially "NI Monitor". 
  • I receive a Device is not reachable message in NI MAX when trying to connect with my Ethernet CompactDAQ (cDAQ). I can ping the device and see the device and modules with the Web Interface. I can even change the IP address of the cDAQ and the IP address will hold correctly.  But, I cannot see my c series modules in the cDAQ chassis in NI-MAX.  When I perform a self-test on the device, it returns Error -88705.
  • When resetting my DAQmx device in NI-MAX, I receive Error code: 80040383 without any error detail.

Solution

Your NI Device Loader and NI Configuration Manager Services may have stopped without restarting. Follow these steps to restart the service as well as set them to automatically restart if they encounter an error or timeout.

For Windows 10/8/7: 
  1. Log in as an administrator or as a user with administrative privileges. 
  2. Select Start » Control Panel » System and Security » Administrative Tools »Services
  3. Locate the NI Device Loader (nidevldu) and select Properties from the drop-down menu.
  4. Make sure that the service is Started. If it is not, use the Start button to start the service.
  5. Click on the Recovery tab and select Restart the Service from the First failure, Second failure, and Subsequent failures listboxes, as shown in the image below.

For Windows 2000/XP:
  1. Log in as an administrator or as a user with adnimistrative privileges.
  2. Navigate to Start » Settings » Control Panel » Administrative Tools »Services.
  3. Right click on the NI Device Loader service and select Properties from the drop-down menu.
  4. Make sure the service is Started. If it is not, use the Start button to start the service.
The NI Device Loader will automatically start the NI Configuration Manager service. Changing this configuration should ensure that the correct service start every time you reboot your computer.

If the NI Device Loader still does not respond, check if National Instruments mDNS Responder Service is started in Services. NI Device loader is dependent on the mDNS Responder Service in NI-DAQmx versions earlier than 9.6. If National Instruments mDNS Responder Service will not start, please contact NI Support.
 

For every Operating System: 

If the previous procedure does not solve the issue, try following the next steps:

  1. Go to NI MAX
  2. Navigate to Tools » Reset Configuration Data.
  3. Click Yes on the next dialog boxes that appears.
  4. Restart the computer after that.

Or you can follow the next article:

How to Fix or Reset the NI MAX Database File

 

Additional Information

This can happen when a computers operating system takes a long time to boot. The additional time used by the OS to address the heavy demand of resources from other service may cause the NI Device Loader and NI Configuration Manager Services to timeout and not start properly. 

WAS THIS ARTICLE HELPFUL?

Not Helpful