09-19-2008 11:54 AM
Dear community,
Something happened and I am experiencing an error -50405 when trying to output
single analog value and subsequently read an analogue value. My hardware is USB 6008.
I have Nidaq mx 8.8.0f2, windows xp sp3, labview 8.5.1 and labview 7.1.1. It does not work in both of them.
The system where it all worked was a windows xp system (sp2) with NIDAQ MX 8.<something>.
I recently updated the system where it was working with service pack 3 for windows xp and some security
updates from windows update. When I rolled back the updates the situation still remained the same.
I updated to the most recent NIdaq - no luck.
I reconnected the board to the other system with a fresh install of windows xp sp3, labview 8.5.1. and nidaq -
same results, but in my mind it takes more time for the system to reach this sate.
When the system is stuck in this state, attempted reset of the device from the automation explorer returns the same
error on both machines.
The read is done either from a timed loop (lv 8.5.1, lv 7.1.1) or just from a vi running in other 1 executon system with high
priority.
Is there a possibilty of broken HW?
From my point of view it is either this or some synchronisation error in the new drivers.
Please advice me what can be done here.
09-22-2008 10:33 AM
09-22-2008 05:34 PM
Hello mzu,
Is your USB-6008 connected to your computer using a USB hub? Also, does the error happen with all of the USB ports? If you haven't tried, I recommend trying the USB-6008 using other USB ports. Also, if you are using a hub, I recommend connecting the USB-6008 to your computer directly. Lastly, if the problem persists, perform the following actions:
1. Reset the USB-6008 from the driver, using the DAQmxResetDevice VI in LabVIEW.
2. Open Measurement & Automation Explorer (MAX), expand your Devices and Interfaces, expand your DAQmx Devices, select the USB-6008, and perform a Reset Device.
3. Disconnect, and reconnect your USB-6008 from the computer, and then reboot the computer.
Regards,
Wallace F.
09-24-2008 05:25 PM
Thank you, Wallace_F
the problem actually was with the computer power supply, which blew up last morning. Installed a new one - so far so good ...