NI cDAQ not view in MAX

[Pqueeck]

Hello,

I have the problem that my NI cDAQ-9172 is not more viewed/recognized in MAX. But this hardware is well recognized by Windows (2000 SP4) in the Device Manager under Data Acquisition Devices and also under the USB Root Hub (it is connected with a USB cable). "This device is working properly"

This device was working well before. I just connected last week a light source device (not from NI) with a USB connection + installed its driver. This lignt source is not more in the lab and so not more connected to the computer. Today it is the first time that I try to work again with my NI hardware.

I restore the MAX database but nothing changed.

What can I do to "force" MAX to find the cDAQ?

I have a FW camera connected and this one is still recognized and working with MAX. The problem seem to be connected to the USB connection.

Thank you in advance for your help.

Patrick Queeckers

[AdnanZ]

Have you tried re-installing the DAQmx driver? I believe that's the best solution that I can think of at this point.

[Pqueeck · Accepted solution]

Solution found.

With the help of an engineer of NI from Belgium, we found the solution: the NI Device Loader was not running !!!

To started it:

Go to Control Panel»Administrative Tools»Services»NI Device Loader. Check to make sure that the status of this service is Started. If it is not, the status for this service will be blank. Highlight NI Device Loader and select the Start Service option in the Services window toolbar. For the changes to take effect, close out of the Services window and restart MAX.

After started this service, MAX found the NI cDAQ hardware and it works properly. 

But after a reboot of the computer, this service was again not started (it is in automatic mode) and the hardware was listed in the MAX but not working.

I changed the properties of the service "NI Device Loader" in the recovery tab, I put the "First failure" parameter to "Restart the service". After that is it working after a reboot.

[Brad_K]

Hi Patrick,

That sounds like a reasonable workaround, but NI Device Loader should not stop running like that. Could you open Event Viewer and check the System log for events regarding NI Device Loader or NI-PAL? Look for events that have "nipalk" or "nidevldu" in the Source column, or where "Service Control Manager" is in the Source column and the event description mentions "NI Device Loader".

Brad