07-20-2012 09:53 AM
Hello,
We( my colleagues and me) encountered two different problems with a NI DAQ USB 6341 Card.
Here is our general system Information :
WIN 7 , 32 Bit
NI DAQmx 9.5.5
NI USB DAQmx 6341
MAX 5.3.1
First Problem:
This Problem was encountered on a Windows 7 development Notebook with NI DAQ 9.5.5 Driver and Labview 2010
AND on a windows 7 deployment notebook with NI DAQ 9.5.5 Runtime(STD).
The Card stops working suddenly and both blue LEDs go dark. After that we try to unplug /replug the cards power supply. We also disconnected the USB cable and did any combination of the two /( power -> usb -> MAX / power -> MAX -> usb etc).
After unplugging/replugging two cases can happen:
A)Sometimes Windows says: "The device can not be identifyed and it can not be installed." In this cas eteh device stays inactive in MAX, too.
B)Sometimes Windows says: " The Device has been installed succesfully" In this case the Device shows up in MAX, too.
In Case A nothing can be done but unplugging again.
In Case B the device either can be reset or it can not.
if it can be reset the self test will also work.
If it can not be reset the selftest does not work either.
If selftest/ reset does not work, both report error "-88705: Device is either not installed correctly or not connected to the system." Never the less the device is marked as present in the devicelist.
We hought this problem to be fixed after we installed DAQ 9.5.5 RTE to a notebook that never has any National Instruments software on it.When we connected it to the card, this made the card work for two days in a row. And then the problem came back.
Second problem:
This Problem was encountered on a Windows 7 development Notebook with NI DAQ 9.5.5 Driver and Labview 2010.
We use the card for data acquisition.While the card is NOT busy with data acquisition we query one data point per second to draw a plot of the current amplitude of some channels. The code used for this is attached to this post as a picture.
The behavior generated by a calling the attached VI once per second, is this:
Call -> Immediate Answer
Call -> 3 to 5 seconds -> Answer
Call -> Immediate Answer.
Call -> 3 to 5 seconds -> Answer
Call.......
But we want an immediate answer every time. Formerly we used NI USB 6210 and 6212 cards with the same labview sourcecode and the code works fine with them.
It does not make any difference if the card is connected to the Notebook directly or via a USB Hub. We also plugged in a USB 6210 Card in the same Notebook (with AND without hub) without changing the software, driver or anything else and it worked fine every time.
If we place a "Commit Changes to hardware" DAQ VI or a "Set Timing" DAQ VI prior to the "Get Samples" DAQ VI the waiting is done at the "Commit changes to Hardware" VI.
Neither of the both problems has been encountered on DELL Desktop Computers with Win XP SP2.
Is it possible that this is a problem similar to the Win7/ USB 6008,6009 problem?
I hope somebody can help us.
Thanks in Advance
Sebastian
07-31-2012 04:27 AM
Hi Sebastian,
thanks for your detailed description. - I opened a service request parallel.
So, please check the email correspondence.
The issue, that the device in random cases is not detected by windows device manager and MAX might have several reasons:
- for communicating with NI-DAQmx devices the deviceloader service has to be started
- USB chipset of the computer
- NI-DAQmx driver doesn't work properly
Kind regards,
Rupert Donauer,
NIG, AE
06-26-2013 02:10 PM
Any updates on this service request? We are also seeing problem #1.
06-27-2013 01:25 AM
Hi,
I might send an email with further instructions to solve this behaviour.
Anyway I recommend to install the latest version of NI-DAQmx driver:
http://joule.ni.com/nidu/cds/view/p/id/3811/lang/en
The following link describes also issues if the NI device loader (a service, which discover the hardware) isn't starting properly
http://digital.ni.com/public.nsf/allkb/0819391CA91B3EB38625731D00024649
Best regards,
RupiDo
06-27-2013 02:31 AM
Hi RupiDo,
Thanks for your answer.
I'll check it out as soons as I find the time for it.
I think that will be around Monday.
Regards
Sebastian