NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Working with small timing (ms)

Is it possible with TestStand to create sequence to check a change state of a signal within 1 ms ?

 

What is the minimum timebase to work with TestStand without having disturbation by Windows or something like that ?

 

Thanks. 

0 Kudos
Message 1 of 3
(2,827 Views)
Although you can typically execute steps in substantially less than a millisecond, Windows is not a real-time OS. Any program you write can be suspended for unpredictable durations at unpredictable times. Thus you might usually be able to monitor at a certain rate, but occasionally, you'll get a performance hiccup. You can use the Step Insert Menu>>Synchronization>>Advanced>>Thread Priority step type to raise the priority of your critical thread. You can also kill unneeded programs and services. Both will improve your chances of maintaining a constant throughput and it is possible that you might empirically determine that you can get "reliable enough" timing for your application. However, if you want a guarantee, you'll need to either perform your operation in hardware, or use a real-time OS.
0 Kudos
Message 2 of 3
(2,818 Views)
I should also mention that one way to work around this is to measure the time between your readings. If a performance hiccup violates your timing constraints, you can restart the test from the beginning in hopes of having better luck next time. Of course, this doesn't help in cases where an unsuccessful attempt is not acceptable.
0 Kudos
Message 3 of 3
(2,815 Views)