LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

USB6008 - mixed up analog input channels

Jaime,

 

I agree these are two issues, the first (exception -2002279) happens once in a while unexpectedly in vmware, or when i put a breakpoint in my async callback and wait a few seconds before letting the program continue to run.  This causes the  the returned data[,] array to get jumbled in the incorrect order as compared to the order the channels were created.

 

I have not been able to reproduce this outside of vmware, so I am hoping that is the problem.  I will keep you posted.

 

Thanks,

James 

0 Kudos
Message 11 of 13
(1,238 Views)

I also run into the same problem, but with the other type of usb device (NI USB-6009). In my case the input data seemed to be mixed up randomly independtenly from the order/number of channels or grouping type. But!

 

The problem only occured in my software, and not in the Measurement & Automation (actually almost not), where I created the same aivoltage task. Consequently they must do something in a different way than I do.  I figured out if I stop my program while having a wrong order in the result data array the Measurement & Automation task will also have a wrong order at first time run, but it will work fine after.

 

So, I gave a try to call StopTask and ClearTask when closing my program (I always used them when creating new tasks, but its not enough) to clear up the memory, and what a surprise..? It seems to be working fine!

0 Kudos
Message 12 of 13
(1,060 Views)

Hi all together,

 

unfortunately the problem you're giving a description of looks pretty familiar to me. I'm using the USB device NI USB-6009 (We have installed the newest drivers recently) as well and I have the same issue with a randomly mixing order of my channels (three AI).

 

It also does work in Measurement & Automation.I also had implemented TarPista's recommendation with the Stop and Clear-Task and it didn't help 😞

 

Does anybody else had to face this problem again or does anyone else know another possibility to solve this problem?

 

@ Jaime F/ NI: Could the R&D find out the reason for this behaviour and fix this bug?

 

Thank you very much for all kind of support!

 

 

0 Kudos
Message 13 of 13
(911 Views)