high priority settings cannot precisely time loops?

[Daniel Troendle]

I have an loop that acquires data every n milliseconds and casually sets some digital output when a threshold has passed.
This digital-out is quite time-critical thus I don't like to do a on-board-acquisition but get each data just in time.
That's very fine with a 1ms loop-time as long as Windows NT has enough ressources. But if there's another time-consumptive process running, things get bad.
I started a "search for file" and parallel my application. Now Windows shared the timeslices and I have a lot of acquisition-dropouts for 10-20 ms.
So I set the VI-priority to "highest" and the WindowsNT-process priority for LabView to "realtime". At least the latter should get the VI all the time it needs.
But LabView se
ems to be fair enough to still share ressources and the dropouts continued.

Can I set my LabView-application so that it gets absolute priority in Windows NT to have a constant acquisition?

Thanks, Daniel

[Dennis_Knutson]

You can go to hardware timed acquisition or LabVIEW-RT. Windows, Linux, Mac, etc. are not deterministic operating systems. There is a lot of information on "real-time" acquisition at NI's site. Try doing a search and seeing what your options are. Good Luck.