11-12-2012 04:28 PM
For just a little more performance enhancement you could commit the task prior to entering the loop and avoid a few extra state transitions. (Going by memory but I seem to recall there is a "Control Task" vi
11-12-2012 04:39 PM
is this how I get mutiple channels to read? > Dev0/Ai1:Ai3
11-13-2012 08:55 AM
ok guys, with your help I've got the marked 3000 points...but it's coming out to be 3719 data points when 30 cycles are ran. Where are the 719 points that I don't need coming from?
11-13-2012 09:17 AM
I don't see anyplace where you are configuring the sample rate or number of samples so I don't understand how you can expect anything. The driver uses the same basic format as DAQmx so I would suggest you look at those examples if you don't have anything from the vendor.
11-13-2012 09:19 AM
I thought I was using the loop for my control...the delay time rather.
11-13-2012 10:39 AM
The windows clock is not going to be very accurate and is subject to a great deal of jitter. I have no idea what kind of card you are using but you should check the specs to see what sort of hardware timed sample rate it has and specifically set that. Then you should be able to set number of samples to read. Without specifying either of these, you are just going to keep getting random results.
11-13-2012 11:59 AM
Take another look at the example I posted. I showed you how to configure the sample clock.
11-13-2012 12:26 PM
when I set up a sample clock, my "cycle counter" go nuts. It counts really fast and inconsistantly...is there any way to remedy this?
11-13-2012 02:02 PM
You need to show what your modification is.
11-19-2012 10:13 AM
ok, I've been busy with other things, so sorry for the late response. Here is my VI. I'm trying to take these samples based of a given frequency, say: 1Hz, 0.5 Hz. I want to take 100 reading a sec for 1HZ... so with 30 cycles I should have 3000 data points.