wait and wait until next multiple functionality

[AB@17]

If you observe the this vi,it is behaving quite different ;why is it so? It has to work as per functionality

[altenbach]

---

@Bhramaji wrote:
If you observe the this vi,it is behaving quite different ;why is it so? It has to work as per functionality

---

Which VI?

[AB@17]

attchement was not proper,now i have attached

[RavensFan]

What is your real question?

Wait and Wait until Next msec functions are different.  Their functionality is well documented, and they are behaving exactly like they are supposed to.

[AB@17]

As per functionality,the Wait until next muliple has to be running at 80ms as multiple of 10,but it is running at 75ms why?

[RavensFan · Accepted solution]

Those two waits are happening in parallel.  So that frame of the sequence is going to take the longer of the two waits, either 75 msec has passed, or it has waited until a 10 msec multiple of the timer has been reached.  Of course while it is waiting 75 msecs, it will have passed 10 msec intervals many times.

You didn't specify an 80 msec multiple of the timer clock, you specified a 10 msec multiple of the timer clock..

[Neos]

You are expecting something which is not intutive.

i will explain by an example.

In attached snippet

if you get some value in first frame of sequence structure , now in second frame both the function are in parallel they are free to execute anytime so suppose first wait until next multiple executes it will give value after first frame timers value plus miliseconds which are next multiple of 8 and its work is over. now wait function will be executing unless 75 miliseconds crossed ,after that this frame will complete. So after completion of this frame the value of milisecond timer you will get is what is expected in 75 multiples.

Just saw Ravens explained about this in simple words, Okay they are Knights