11-10-2010 09:50 AM
Hello Brian,
As for the HP Desktop that you tested it on, was it an XP machine? For the Laptop machine was it 64bit or 32bit? Also have you monitored the CPU processes on both machines? This error can occur when the CPU is being used by a lot of processes.
Also when I was testing my 6009, I used a 3ft cable. Could you use a shorter length to see if this solves the issue?
Hello Frozen,
For the -200474 error, this has different fixes than this problem. Please consult this discussion forum where R&D commented about this issue.
11-10-2010 10:50 AM
Hi Jim,
The HP that works is 64-bit running Windows 7. The Dell laptop with the problem is running 32-bit Windows 7. Possibly a difference in how USB is handled in the two versions of Windows 7?
I looked at the processes when the issue first occurred and neither system was very taxed at the time, both are running multicore processors.
I will try to get a hold of a shorter cable to test with and let you know the results. Also, I just realized that the DAQ is actually the 6008 model. Sorry for that confusion, hopefully that didn't lead us astray on getting to the bottom of this problem.
Thanks again for all your help,
Brian
11-10-2010 02:50 PM
Hi Jim,
Thanks for the response. I have spend many hours searching the NI web site and have already read the post you directed me to. I have already verified that my software is specifing a 15.0 sec timeout value in the DAQmxReadAnalogF64 call. The only other suggestion in the post was to contact NI for futher troubleshooting.
Please be sure to post the solution once this issue's been resolved.
11-11-2010 08:54 AM
Hello Brian,
Could you provide the specs on both machines? Right now here is what I know;
Not working machine:
Dell Vosto Laptop with Windows 7 32-bit
Processor: ?
Version of the DAQmx driver: ?
Working Machine:
HP desktop with Windows 7 64-bit
Processor: ?
Version of DAQmx Driver:?
On the Dell Vostros laptop, have you tried other USB ports? If you have did they produce the same results? Do you have another Dell machine to try this on? I have a Dell machine here that works (T3400) but I would be interested if it is the type of computer.
Danfromsb,
If you are still looking over this post, could you post the type of computers you tried this on? Were they Dell machines?
Hello Frozen,
Since you are having a problem that is different from the forum, I would suggest creating a new forum about this and provide the information you have given here along with the link to the discussion forum. The reason why we like to have one issue dealt on each forum is to make it easy for out customers to navigate them and be able to solve their issues. Along with this, your new forum that you will create will be focused on the issue you are having which I believe it very different from this forum.
11-11-2010 09:01 AM
Yes, both of the machines that I've had problems with were relatively new Dells running 32bit Windows 7:
Dell Precision T3500
3GB Ram
Core i7
Dell Vostro 3500
3GB Ram
Core i5
Unfortunately we do not have a non Dell computer running Windows 7 to test this on. I've tried all of the different USB ports, they all seem to exhibit the same problem. With both of the computers I can run a USB 6211 without issue.
Best,
Dan
11-11-2010 11:18 AM
Not working:
Dell Vostro 3500 Windows 7 32-bit
Intel Core i5 CPU M 430
RAM: 4.0 GB
Driver: 2.6.6FO
Working Computer:
HP p6370t Windows 7 64-bit
Intel Core i3 CPU 530
RAM: 6GB
Driver: 2.3.1FO
I have tried all of the ports on the Vostro with no success. Seems that Dan and I are having the same problem on the same computer. I will check and see if I can borrow someone else's Dell to test on later today and let you know what I find. I could update the driver on the HP, but would rather not have two non-working systems if that is the problem. Also, the problem was occurring on the Dell before I updated the driver to the latest version.
Regards,
Brian
11-12-2010 10:22 AM
Hello Danfromsb and Brian,
Thanks for the extra information about this. It looks like the next person we need to talk to is Dell. It is very interesting that 2 Vostro 3500 computers have the same behavior with the USB-6009/6008. I have today tested a Dell Precision T3500 machine and a Dell Precision T3400 and I didn't have any issues with it. With the 6009, I sampled up to the maximum rate with both finite or continuous.
A Few more things to check:
1.) The 6009/6008 FIFO (Onboard buffer) can hold 256 samples (Buffer size = 512 bytes and each sample is 2 bytes). I believe that if we are having throughput issues on these machines lets try to sample at 100Hz and see if the error occurs. At this speed the throughput issues shouldn't be a problem because we are sampling at such a low level.
2.) Danfromsb, you stated that you were able to use the USB-6212 without any issue. I believe the reason why you aren't having problems is that the buffer size on it it 4095 samples which will be able to hold a lot more data in the buffer compared to the 6009/6008.
3.) Danfromsb, the Windows XP machine, is that a Dell machine as well? It would be good to compare this machine to the others to see what the differences are. This will be good information to talk to Dell about.
At this point, I can't see anything wrong with the device itself. Ultimately the performance of the devices are system dependent which is explained in this DeveloperZone. I am sorry that I could come up with any more information but I would like to hear any progress you guys make on this. Good knowledge to have in the future.
11-16-2010 01:13 PM
I'm seeing the same problem. I'm running on a Dell Vostro desktop (with 32bit Windows 7). I'm using Matlab to control the USB 6009.
I've used the same software on multiple laptops with WinXP and have never had this problem...
Just figured, I'd chime in...
Please keep us posted on what you here from Dell.
Thanks,
-Tom
11-16-2010 01:14 PM
p.s. I can work around the problem by unplugging and replugging the device in.
-Tom
11-16-2010 01:20 PM
Hello again,
The windows xp machine is not a Dell, it is a somewhat older Asus, not sure of the exact model number.
Best,
Dan