slow initial execution in Test Stand

[dphan128]

Whenever I execute my test steps for the first time in Test Stand. It
seems to go through somekind of initialization or compiling in the
background for several seconds before the test steps are executed. And
it only does that on the very first time after I open TS.
Do I need to initialize my instruments (DMM card, DAQ card,...) under
set up folder to avoid that

[Scott Richardson (NI)]

To dphan128 -
Typically a sequence file's Load Option specifies to "Use step load
option" to load its step modules. Typically the Run Options for steps
specify to "Preload when execution begins" and to "Unload when
sequence file is closed".

So this means that when an execution starts for the first time, the
engine loads the modules it calls. This includes any sequence files
it calls and any code modules that they call, such as LabVIEW VIs,
DLLs, COM servers etc.

If you want to delay the time for preloading modules until the module
is called the first time, you can simply specify the Sequence File's
Load Option to be "Load Dynamically".

The disadvantage of not preloading is that you may not see a missing
module until you actually call the step which may be in the middle of
testing a UUT.

Scott Richardson (NI)

[dphan128]

Thank you Scott. I will try different sequence file's load options
and/or run options to see which one would work best for me.
My goal is to minimize the execution time and also make execution time
consistent everytime the sequence file is run, no matter if it is the
first time or subsequent times.