12-03-2014 08:08 PM
Hi all,
I'm using DAQ 9234 to measure sound (microphone) and vibration (velocity) wave for developing an automation tester in a production line I am working on.
But I'm having a problem which the DAQ 9234 (with DAQ 9171 as a USB chassis) keep disconnected from PC, and I need to re-plug the USB to get it re-connect.
I heard that this DAQ have been stopped.
Is there anyone in the group seen such connection problems?
Thanks.
12-03-2014 08:20 PM
You may get a better response on a DAQ specific group. Try posting your question here:
12-04-2014 07:09 AM
Just a quick thought, and may not be related at all.
I have had problems in the past with Win7 shutting down USB devices.
Good luck,
James
PS. I agree with David, this isn't the best forum for this question.
12-04-2014 03:38 PM
kipizoki,
I agree you may have better luck with the technical content of your post in another forum, but since you posed the question...
Signal.X specializes in noise and vibration applications for production testing, and generally speaking we stick to PCI and PXI platforms for these systems because of the reliability and uptime expectation that they generally have. If you have any questions about how we do this and why, feel free to contact me.and we can chat further.
Thanks,
Rob
12-05-2014 05:50 AM
Hi Rob,
Thanks for the reply, actually, the problem I faced is the DAQmx task runs successfully for some time, but then returns Error -50808.
I already go thorugh all of the forum links below and follow their suggestion but I'm still can't get it fixed.
2. http://forums.ni.com/t5/LabVIEW/LabVIEW-cDAQ-Error-50808/td-p/2839770
12-05-2014 12:27 PM
Is it on a USB hub? If so, plug it directly to the PC.
12-05-2014 07:37 PM
yes, it is on powered usb hub.
is there any difference?
12-05-2014 08:55 PM
What is the behavior when plugged directly to the of with no hub? Does it still have the problem?
12-05-2014 09:02 PM
yes.it does..i can only do 1 time read,and it got disconnected for the 2nd
time read..
12-07-2014 04:04 PM
Tell us more about your system/set up. OS, hardware etc.
I've had similar issues in the past where it turned out to be a dodgy USB3 driver. Fixed by either uninstalling the USB3 driver or updating the BIOS.