Keps

Thanks for the advice and the vi. It was the wait ms function that I needed. I know it won't be deterministic in windows but it was just terrible. I still don't quite understand when the timer was starting on the wait ms multiple since the timer in the second loop started after the first ended. Anyway it is well behaved now, within the constraints of windows. I like the wait.vi and would use it, but this code is not mine and time is of the essence here.

Here is the code. It steps through a few array values in each for loop, the first one totaling 200ms and the second 300. The result is timing that sometimes resembles the programmed values, but it is usually much shorter than the 500ms total.

I have an executable application that is running on an XP netbook. It is controlling a USB DAQ device from NI (don't have the model number off hand). It is attempting to do things in 10s of milliseconds and the timing, as you might expect is terrible. I understand that but, the timing is too short! This I don't understand at all. It is effectively setting some digital channels to one state for 200ms, changing the state after another 300ms and repeating this over and over again. The timing is all over the place but averages about 60% of what it is programmed from. Any idea how bad timing winds up shortening these intervals? I am using the wait ms multiple function. Any help, advice etc. would be greatly appreciated.