Hi, we have built a product around the NI USB-6008 OEM. The device is controlled by our application (written in C) through the DAQmx driver (version 9.2.2). Recently, we are seeing problems when the application executes on particular Windows7/x64 machines or when the NI USB-6008 is connected through an USB hub. Based on our application I have written a test program which shows different results depending on the PC platform and whether a USB hub is used or not. The test program and the complete result files are attached to this post. We see following behavior: 1) Desktop PC Windows7/x64, no USB hub The program works correct. Also, if the test program is started multiple times in a row no errors occur. 2) Desktop PC Windows7/x64, Dell Monitor 2408 WFP as USB hub The test program fails. Although the actual data acquisition works, a following call to DAQmxStopTask() fails with the error -50405: ... Call GetRealSamplesAvail() after reading samps GetRealSampleAvail result: 0 Calling DAQmxStopTask() DAQmx Error: NI Platform Services: No transfer is in progress because the transfer was aborted by the client. The operation could not be completed as specified. Task Name: _unnamedTask<0> Status Code: -50405, Read voltages (DAQmxStopTask), -50405 If the test program is started again it hangs in DAQmxResetDevice(). The function DAQmxResetDevice() returns with the error -50405 when USB is unplugged. 3) Desktop PC Windows7/x64, USB hub (EXSYS EX-1177, www.exsys.ch) Same behavior as in 4) 4) Dell notebook Latitude E6410, Windows7/x64 Usually, after an USB enumeration the test program works correct. In most cases however, the second or third call of the test program (after an USB enumeration) fails. We get a timeout since DAQmxGetReadAvailSampPerChan() reports zero as the number of available samples. It seems that the data acquisition process has not been started correctly. … Task is in complete state, ok Calling DAQmxStartTask() AcquireAInWhenAvailable() Calling GetRealSamplesAvail() GetRealSampleAvail result: 0 Calling GetRealSamplesAvail() GetRealSampleAvail result: 0 .. and so on till timeout (see i<tmax_ms/200) If the test program fails all following runs will fail as well. The only way to recover is to unplug USB. We have not seen any problems on Windows XP. For failure 2) (monitor hub) there is the workaround to directly connect to the PC. Therefore, we could live with this behavior. However, operating the device on a notebook (see 4) is a real issue, since most of our customers are going to upgrade to such a platform. Has anyone an idea how we can operate reliably the USB 6008? Thanks for your help Ray

Multifunction DAQ

Analog data acquisition with NI USB 6008 stalls on some Windows7/x64 machines

I am not sure if this is the right thread for this, but I think I am having a similar issue. I have a NI USB-6008 that will work when connected to one Windows XP laptop(#1) but not to another Windows XP laptop (#2). It was connected to the onboard USB ports on both laptops. When the USB-6008 is connected, it looks like it is working fine. I am monitoring a 5v signal which triggers a software command it a labview exe. I measure 5v at the USB-6008 inputs and the 5v signal shows up in the test panel in the Measurement and Automation software. When I turn the 5v on and off, it doesn't do anything in the software. When connected to laptop #1, the software functions as intended. I decided to try using a NI cDAQ-9172 with laptop #2 to see if it would work and when it is connected, the software functions correctly, which validates that the software is correct. I can only think that there is some hardware configuration difference between the laptops. If anyone has any ideas I would appreciate it.