07-12-2013 10:01 AM - edited 07-12-2013 10:05 AM
I have a 6008 and am using DAQmx (and could easily switch to DAQmx Base if that helps), and I am trying to use it to set an output voltage according to a non-PID feedback algorithm. I'd thought that continuous samples would help, but 6008 does not appear to support continuous samples (only On Demand?).
What happens to the output voltage when the On Demand, Single Sample write is done? Does it revert to 0? Hang out at the last applied value (if so, problem solved)? What about an On Demand Waveform write?
I really need this signal to stand still while I'm trying to figure out what to do next.
Can I assign a waveform with a long time betwen samples, then override that with a different write command and a new waveform, and smoothly change the voltage that way?
07-12-2013 11:55 AM
07-12-2013 01:42 PM - edited 07-12-2013 01:55 PM
In the case of single sample measurements, the notion that it's a single sample. Sounds very localized in time.
In the case of a waveform, it's all those zeroes at the end of the waveform control.
07-12-2013 01:54 PM
07-12-2013 02:00 PM - edited 07-12-2013 02:07 PM
You asked why I thought it might go to 0. I answered that question.
The problem I thought I had is gone, but I'm still trying to do this on-demand single-sample write, and it seems like anything I try to do with the Timer produces an error. If I try Waveform, it gives an error 200088, and if I do single sample, it says that it only supports On Demand, which is hardwired in. and the other polymophic VIs aren't appropriate sense. Is the trick that I need to not use the Timer VI at all on my output stream? Is that what On Demand means?
Oh, right - I forgot the other reason I thought it might go back to 0 - it would explain what I'm seeing. When I take the timer off my output, I don't get errors, but it doesn't seem to actually ever change the voltage. If it only make a tiny spike for whatever reason, that would explain that.
Is there an actual manual for DAQmx itself in Labview? Not these 'getting started' that show one way to do things, not tutorials that show a different way to do things, not one that assumes I'm using the Assistant or MAX, but an actual honest to goodness manual for DAQmx itself? I feel like I'm swimming through documentation, three quarters of which is too simple and three quarters of which applies to something that looks exactly like what I'm doing but is completely incompatible with it.
07-12-2013 02:06 PM