Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

DAQmx 9.1.1 and 9.2.0 are not compatible with Win7 bit, but 9.0.0 is?

Once you uninstalled everything, that would have removed the MAX database, whereas an upgrade would have persisted the existing upgrade, which should explain why the database corruption was corrected when moving to DAQmx 9.0.

Seth B.
Principal Test Engineer | National Instruments
Certified LabVIEW Architect
Certified TestStand Architect
0 Kudos
Message 11 of 19
(1,976 Views)

If that's the case, the the problem with 9.1.1 and 9.2.0 is very obvious. I installed 9.2.0 after completely remove the parts as I did before installing 9.0.0, so the corrupted database is supposed to be removed too, but it still couldn't detect the two cards. I never tried upgrading existing driver.

0 Kudos
Message 12 of 19
(1,964 Views)

This will probably sound like a pretty strange question, but what brand are your keyboard and mouse?

Seth B.
Principal Test Engineer | National Instruments
Certified LabVIEW Architect
Certified TestStand Architect
0 Kudos
Message 13 of 19
(1,928 Views)

The PC was purchased from HP and the keyboard and mouse came together, so I suppose they are HP brand?

0 Kudos
Message 14 of 19
(1,918 Views)

We have recently discovered an software bug that was introduced in DAQmx 9.1 that can cause the MAX Database to become unusable by DAQmx, resulting in devices not showing up in MAX.  This issue occurs when certain Human Interface Devices (HIDs) are connected when the machine boots.  Among the HIDs that can cause this issue are certain models of HP keyboards or mice.

 

May I have your permission to contact you directly via email to have you test out a fix we are working on for this issue?

Seth B.
Principal Test Engineer | National Instruments
Certified LabVIEW Architect
Certified TestStand Architect
0 Kudos
Message 15 of 19
(1,899 Views)
yes, please email me related info, but i can only test the fix in two weeks. will this bug be fixed in next release?
0 Kudos
Message 16 of 19
(1,881 Views)

To follow up on this forum, we have identified this as a known issue with versions of NI-DAQmx from 9.1 through 9.2.1.  We have released patches for these versions that we are making available today at the KnowledgeBase article linked below and through NI Update Service.  The issue will be corrected in NI-DAQmx 9.2.2 and later. We will also be releasing an NI-DAQmx 9.1.7 that includes the fix for those who would like to minimize upgrade risk from version 9.1.x.

 

For more information on this issue, please consult KnowledgeBase 5DF9GJZL: Why Do Certain USB Interface Devices Prevent NI Devices from Appearing in MA...

Seth B.
Principal Test Engineer | National Instruments
Certified LabVIEW Architect
Certified TestStand Architect
0 Kudos
Message 17 of 19
(1,800 Views)

I have had a similar trouble with a mouse just today. I was lucky to have found this post since I don't think I would have tried pulling out the mouse on my first ten guesses.

This one is an old dell/logitech USB mouse that I had hanging around.  I was using it on a dell-mini that uses windows 7 starter. The mouse works fine with everthing else on that laptop.   Pulling out the mouse and using the touch pad appears to have fixed the problem with my .exe creeated by labview on another computer.

 

If you want to know more detail you can contact me,  Do you think trying out some other mouses might also solve the problem? Fortunalty the guy going to be using the equipment for a demo loves touch pads.  Hate 'em myself.

0 Kudos
Message 18 of 19
(1,755 Views)

Hello millonas,

 

If you apply one of the patches from this KB, you should be able to use any mouse you desire.

 

Regards

Seth B.
Principal Test Engineer | National Instruments
Certified LabVIEW Architect
Certified TestStand Architect
0 Kudos
Message 19 of 19
(1,740 Views)