05-30-2007 11:37 AM
05-30-2007 11:43 AM
05-30-2007 01:54 PM
05-30-2007 02:22 PM
05-31-2007 06:06 PM
Dhawal,
Your other post said that you had things working – did something change? Also, a bit more explanation around what is not working and what you are getting / expect to get may help us narrow down what is wrong (along with posting the latest version of your VI). Are you getting errors or just wrong return values?Regarding the VI in the previous post, The DAQ card holds the last value it was given until a new value is output or the task is cleared (outputs default 0v). From the VI posted, it seems that after the arithmetic inside the while loop is true 512 times, than you output a value. Are you looking to output 0v the very next iteration? If so, I would put a DAQmx write in the false case (which adds +1 to the shift register) and output the value 0. I would also put the same DAQmx write, outputting a value of 0v, after the while loop, before you clear the output task. This will make sure that the last value output is always 0v.
06-02-2007 02:35 AM
Hi David,
Sorry for the late reply. I would want the voltage to be zero , not after the first iteration, but after the triggering is over (i.e. the labview would start recording the data once the trigger is initiated, and would again stop recording when the triiger point stops). I was trying to get the zero voltage whenever the trigger is not reached.
I hope I m making myself clear, still i m writing in points what exactly I would want.
1. labview is started
2. machine is started.
3. Labview will not record the data till the trigger is reached.
4. It will start collecting the data points once the trigger has reached and the C++ program would output a value, which would change one or more process parameters of the machine.
5. After a particular period of time (not constant), the trigger stops again, as the triggering condition is not met----- This is where I would want labview to send zero voltage signal to the machine.
Thanks in advance.
Dhawal
06-02-2007 02:23 PM
06-04-2007 01:06 AM
In order to smooth everything out and have it work correctly, I would suggest only using the 'Y Values' of the waveform when manipulating and saving data so that all datatypes are similar (not waveform vs. double array). You can obtain these by using a 'Get Waveform Components.vi', found in the waveform pallet, and choosing 'Y' from the drop down menu for the output. This will take your input waveform, and give you a 1D array of values representing your Y-Axis data.
06-04-2007 10:32 AM
06-04-2007 10:50 AM