Wait ms Timer Multiple returning inaccurate timer value
Quote:
> Agree completely but why can't LV provide access to the windows multimedia
> timer like LabWindows does? Provide me a timer, I can start/stop by changing
> its properties and run that in a separate thread. Obviously if I have
> another thread starving this timer thread, it won't help much but using
> multi-media timer, I have seen very good results on a windows2000 machine.
> Now win95/98 and derivatives are all other story.
This is equivalent to making a separate loop, preferably in a VI with an
elevated priority. Make the loop have a wait ms or occurrence with a
timeout value.
This is different from having a function callback on a windows timer,
but it is similar. LV has a timer thread that is tied into the same
multimedia timer. That thread provokes timeouts on occurrences and
reschedules code that has waited the appropriate amount of time based
upon wait ms. Problem is, being scheduled and running are two different
things. If another loop is running at that point, it will get it in the
way if they happen to share the same execution system. If the waking
task is higher priority, the OS should respond pretty quickly to switch
out the threads.
Greg McKaskle