USB-6225 Not Recognized

[Aurora_Tiffany-Davis]

Hello,

I have a PC which is having a lot of trouble recognizing a USB-6225.  Starting from a situation where the PC *does* recognize the USB-6225, here is the basic pattern:

1. PC shows USB-6225 in Device Manager under "Data Acquisition Devices".

2. MAX shows USB-6225 with valid serial number under "NI-DAQmx Devices".

3. If the PC is power-cycled via the power plug itself, the USB-6225 is no longer recognized under Device Manager ("Unknown Device") or MAX (shows as disconnected, no serial).

4. If the PC is power-cycled via Start Menu --> Turn Off, same results as above, no longer recognized.

5. If the PC is power-cycled via Start Menu --> Restart, no problems, recognized in both Device Manager and MAX.

When the USB-6225 is not recognized, unplugging and replugging the USB cable makes no difference to the situation.  In order to correct the issue, I disable and then enable via Device Manager (which also involves a restart).

This pattern is extremely repeatable. 

---

I am working with WinXP SP2, Pentium, 2.8 GHz, 504 MB RAM, and I have DAQmx 8.7.1 and MAX 4.4.1.

I know there was an issue with MAX recognizing devices from DAQmx 9.1 through 9.2.1 per this post, but that should not apply here.

I have verified that the NI Device Loader Service is set for “Automatic” start-up, along with the NI Config Manager on which it depends.

The same pattern of behavior can be seen with a Measurement Computing DAQ device that we happen to have lying around.

---

This PC was returned from a customer site - the PC and USB-6225 are used in a device we manufacture.  Apparently this issue just started happening one day.  We want not only to correct the issue, but in fact to understand the root cause and ensure it will not happen again in the future.

Any suggestions would be greatly appreciated - thanks!

[Stefo]

If it worked before and now it doesn't, if you are not facing MAX database corruption?

What is the Process For Removing MAX Database Corruption?

MAX Database Corruption Removal Tool

it might happen for example when computer wasn't turned off properly. it is just shot but worth to try.

stefo

[Aurora_Tiffany-Davis]

Thanks for the quick reply, Stefo!  I read the articles you linked to and I have some concerns... 

The first link you provided notes "One sign that your database may be corrupt is if you click on the plus sign for a folder in MAX and if instead of expanding the plus sign disappears."  This isn't happening in my case.  Also, since the USB-6225 is either found or not found in both MAX and in the OS Device Manager, I'm thinking that the problem might be something other than MAX corruption.

My main concern is to figure out root cause / not destroy any evidence.  I'm concerned that trying this might obscure information about the initial cause of the problem.  Hmmm.... I'll ponder it awhile.  🙂

[Aurora_Tiffany-Davis]

Update: Since root cause cannot be found in a timely fashion, I'm going to try to modify my application to force recognition at initialization - to ensure that the customer isn't going to feel the pain on any machines in the future.  I'll post back when I've made some progress.