I need to develop a delay that is 2 minutes long (a test is supposed to run for

[Sateesh]

two minutes). I need this delay to be consistently 2 minutes long whenever I run the test. I have used the "Wait until next ms" vi, but this does not give a consistent performance between runs. Has anyone crossed this path before? If so, what should I use?

[ag]

two minutes). I need this delay to be consistently 2 minutes long whenever I run the test. I have used the "Wait until next ms" vi, but this does not give a consistent performance between runs. Has anyone crossed this path before? If so, what should I use?"Sateesh" wrote in message
news:506500000008000000741E0000-986697009000@quiq.com...
> I need to develop a delay that is 2 minutes long (a test is supposed
> to run for two minutes). I need this delay to be consistently 2
> minutes long whenever I run the test. I have used the "Wait until next
> ms" vi, but this does not give a consistent performance between runs.
> Has anyone crossed this path before? If so, what should I use?
>
>

What about the plain old Wait?

[Jo]

two minutes). I need this delay to be consistently 2 minutes long whenever I run the test. I have used the "Wait until next ms" vi, but this does not give a consistent performance between runs. Has anyone crossed this path before? If so, what should I use?I had the same problem with "Wait until next ms" and it indeed was fixed by using the "Wait" vi. (+/-0.5 second)

[Gorka Larrea]

two minutes). I need this delay to be consistently 2 minutes long whenever I run the test. I have used the "Wait until next ms" vi, but this does not give a consistent performance between runs. Has anyone crossed this path before? If so, what should I use?You can use get dite time in seconds at the beginning and compare it continuously with it's current value to see when time exceeds two minutes (or any time). I think this should be sufficiently consistent.
Hope this helps

[Dr. Spite]

two minutes). I need this delay to be consistently 2 minutes long whenever I run the test. I have used the "Wait until next ms" vi, but this does not give a consistent performance between runs. Has anyone crossed this path before? If so, what should I use?This might actually be inadvisable. We have had problems using "Get Date and Time" continuously as use as a timer. It actually started slowing the computer clock down, causing it to lose time while running. This may have just been poor Win95 handling, but its something to watch out for. Try using the milisecond timer (with appropriate wrap around considerations) to do timing instead.

[Gorka Larrea]

two minutes). I need this delay to be consistently 2 minutes long whenever I run the test. I have used the "Wait until next ms" vi, but this does not give a consistent performance between runs. Has anyone crossed this path before? If so, what should I use?I use get date & time in seconds continuously for over 8 hours and nothing strange happened, perhaps because i'm using WinNT...

[Albert.Geven]

two minutes). I need this delay to be consistently 2 minutes long whenever I run the test. I have used the "Wait until next ms" vi, but this does not give a consistent performance between runs. Has anyone crossed this path before? If so, what should I use?wait until next ms, does not wait so many seconds the first time but waits until the next multiple of 2 minutes on the system clock comes by.
So if it is called more than once (e.g. in a for loop)it is waiting exactly 2 minutes.
If you need to wait the first time also 2 minutes use "wait ms", the function with the wristwatch.