new hardware found on old usb hardware

[bjlv]

I am using a NI-USB-6210 DAQ card just fine, with one major annoyance.  On every reboot of the Dell desktop computer the "New Hardware Found" sequence is triggered, even though it is always the same 6210 plugged into the same USB port.  Is there a setting in MAX somewhere to get rid of this annoying message on every reboot?  The computer is running Widows XP, and the DAQmx is version 8.3 with MAX version 4.1, and this happens on several different Dell computers that are nearly identical.  They all have the same DAQmx, MAX, and WinXP, but are slightly different CPUs.  Three of four are exactly the same, one is similar, but bought several months earlier.  All behave the same.  The old one has the LabVIEW 8.0.1 development system on it, the other three run the RunTimeEngine only.

[Sandra_T]

Hello bjlv,

Do you have administrative rights on your system? I know that this was an issue that was reported with some of our USB-GPIB devices. Windows can exhibit some odd behaviour, particularly with laptops and non-Administrator users. You can reference this Discussion Forum posting on this issue.

Are you logged on as Administrator on your system when you installed the device for the first time? By installing the device when you are the Administrator, it allows Device Manager in Windows to use the device information stored in the registry when the device is connected. The system will no longer need to run the "Found New Hardware" wizard.


Regards,
  Sandra T.

Applications Engineer | National Instruments

[bjlv]

Hi Sandra:
Thanks for replying.  I was administrator when the USB-6210s were installed, so that was not the problem.  Today, I had a problem with the database getting corrupted for MAX, so in fixing that, this problem went away.  I don't know what precipitated the database problem, but telephone support for that problem led to deleting the data subfolder under MAX.  The rebuilt folder with its rebuilt config3.mxs file seems to have fixed the problem about the new hardware found on that computer.  I have yet to try this on the other three, which are geographically dispersed now.  I will let you know if I have success with them.  One tidbit that this database problem recalled to mind was the order things were installed.  The computer with the database problem is the only one that has LabVIEW development on it, which was installled first.  That installation included traditional DAQ also, because I like some of the support files that go with it (like Wait(+).vi buried in the counter support).  The USB-6210 came with a newer verson of MAX and DAQmx, which was installed second.  Maybe there was a problem with the second installation leading to corrupt files.  The other three never had LabVIEW development on them, only RunTime, so I am unsure if there were two version of DAQmx on them ever.
Bart

[Sandra_T]

Hello Ben,

Thanks for the reply. It appears like the issue is resolved. Here is a KnowledgeBase document on the connection error for you're reference.

Why Do I Get a Measurement & Automation Explorer (MAX) Database Connection Error?

In your case it appears like you had a corrupted file. This is often very rare. I am glad you got your issue resolved.

Have a nice day!

Regards,
  Sandra T.

Applications Engineer | National Instruments