David,
There are different options which you might try.
1. At runtime, you can dynamically determine which sequence to call. For
example, page 11-5 of the Getting Started Manual discusses an example of
dynamically selecting different sequences to call.
2. Also, there is an example on the web at
www.ni.com/support/edp/Follow the link to TestStand and download Dynamically Determine Which Code
Module to Run.
3. Other options that you should consider is the Limit Loader step type.
You can programmatically load any step property with the limit loader.
There are shipping examples that use the Limit Loader and there are examples
on the web.
Best regards,
Paul Mueller
NI
David Joyce
wrote in message
news:38C6D979.8ACF2D6E@zworld.com...
> We are currentl
y evaluating TestStand as our future manufacturing test
> engine.
>
> I'm not sure that this is the correct question, but can TestStand
> sequences be loaded at run-time?
>
> We want to distribute the TestStand engine onto our manufacturing floor
> as a functional test master program for all of our single board computer
> UUTs. We need to be able to reconfigure TestStand for each type of UUT.
>
> These UUTs share the highest level of test sequences (e.g. RAM test, CPU
> test, RTC test), however the UUTs may have major design differences that
> make steps, or sequences, within the tests very different. For example:
> UUTs may have different processors and require completely different CPU
> tests, or the type and number of I/O may be completely different between
> UUTs with identical processors.
>
> We want to build a set of directories with each one unique to a UUT.
> TestStand would be instructed at run-time as to the UUT and configure,
> or reconfigure, itself accordingly.
>
> Any sug
gestions or examples would be appreciated.
>
> Thank you
>
