Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Recognizing USB-6259 DAQ

Hi I have this issue using a NI USB-6259 DAQ where I will connect it, it is recognized, and everything is working fine, then if I do one of the following it is no longer recognized or usable by LabVIEW:

  1. turn it off then back on (using the switch on the back)
  2. unplug the USB cable and plug it back in
  3. close the laptop (go into sleep mode) and reopen it

After doing one of these, if I try to use the DAQ for DAQmx Read or Write in a LabVIEW program, I will get an error like "The client process has been disconnected from the configuration server."   If I go into Windows Device Manager, I can see the device and it says it's working fine. If I go into NI MAX, it lists the device but says the status is "Not present."   Restarting LabVIEW doesn't help.  

 

The only way I can make the device usable again is if I restart the computer completely, then it's fine.  It's just sort of a pain to have to restart every time.  What can I do to make LabVIEW recognize the device again?  I have tried using the "Reset Configuration Data" command in NI MAX, but that only seems to help because it forces me to restart the computer, then the same problem exists.  

 

Pretty sure all software/drivers are up to date. Running LabVIEW 2013 on Windows 7.

0 Kudos
Message 1 of 2
(3,668 Views)

Hello tk4b

 

This really seems like an odd problem, I have never heard of something like this before. Are you running on a 64 bit or 32 bit computer and LabVIEW?

Even if the drivers are up to date, sometimes they got damaged and present unexpected behaviour. I would suggest trying to do a reapair of the drivers, or uninstalling and reinstalling them. If that does not work, I would try with another version of the DAQmx drivers, like 9.7 for example.  If that does not solves the problem, I would uninstall the drivers, then uninstall LabVIEW, then clean the registry and restart the computer. Then I would install LabVIEW again and then the drivers. I know this might be a little bit tedious, but if something got corrupt or damaged by some reason, this will most likely solve it.

 

Cheers. 

Fabián M.
Internal Sales Engineer
National Instruments
0 Kudos
Message 2 of 2
(3,638 Views)