Thanks for the explanation Dennis. I just tried both ways suggested by
you guys and they both work fine. Many thanks. Have a good weekend.
Will have more questions next week :)
LabVIEW is a dataflow language. The order of execution is detemined by
data flowing from one function to another. A function will not execute
until all of its data is present. Those functions that are not
connected by wires, will not have data dependency and LabVIEW will
attempt to execute them in
Thanks Julien and Dennis. What do you mean by data dependency? Why do
I need it? Please explain to me just anything, I'm new to LabView.
Cheers,
LabVIEW 7 has the Delay function with error in/out connections so you
could use those for data dependency instead of a sequence structure.
Older (and current) versions have a Wait(ms) function with error
in/out as well but it's kind of hidden. If you go to the Data
Acquisition>Counter>Intermediate
Thanks a lot Julien. I just changed to "Wait" and it works perfectly
even with very small time delay. I had never actually understood the
difference between the two VIs until I read that explanation. Many
thanks.
Btw, I have another question regarding the time delay. Is there any
simple way to hav
Hi,
Why don't you use the "wait (ms)" stock VI. This enables you to wait
for the specified time.
Here's a little explanation between the VI you've used and the "Wait
(ms)" VI :
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/12b2ea9ad5b265ad86256257004dd8e2?OpenDocument
Hope thi
Hi, I=92m using LV to move a linear stage stepwise. I use =93Wait until
next ms multiple=94 in a =93for=94 loop to specify the time delay between
the steps. When the time is set to 2000 ms, things are fine. But when
it is set to < 1500 ms, the time delay is significantly shorter
between the first t
