TestStand Handles parameters' order in seqs

Question

Hi, Guys, I'm new to TestStand and I'm using LabVIEW for years.
I want to know if TestStand can do the job below.
Some background:
1, Various Test parameters are to be adjusted or measured, and some of them should run first.
2, User might define some test sequence including some or all test parameters, and their order might be very different.
3, Parameters belong to some Classes.
e.g, Set Temp@-10, Set Temp@25 are Class Set_Temp
4, Test conditions and seqs are stored in database. Some conditions exist in Parameters, like Class Set_Temp.
5, To reduce instrument idle time, we separate test parameters to different tester, so my boss has to hire more operators and handing time with DUT would increase.
We install/uninstall DUT to EVB manually.
For example,
1) A runs first
2) C runs before E,F.
3) H runs after A, and it doesn't mater if it runs after H. Let's assume Parameter C is for acquiring wfms/data, etc. The following E, F are for analysis.
4) CD, CB,CG can't run in parallel.
Seq1:
Parameter A
Parameter D
Parameter C
Parameter E
Parameter F
Parameter H
Seq2:
Parameter A
Parameter B
Parameter G
Parameter C
Parameter E
Parameter F
Parameter H
My question is
Can TestStand arrange them automatically based on the present seq? So we can merge 2+ testers to one?
I don't want to alter database tables too much. I'd like to use the present UI. 
Thanks.
Solved!
Go to Solution.

Answer 1

labc,
Your use of the word Parameter makes absolutely no sense regarding TestStand.  I'm assuming you mean Step????
In TestStand there are two uses of the word parameter:
Use A: a parameter is a variable that is passed to a code module (i.e. LabVIEW).  Since you've been doing LabVIEW for years then think of a parameter as a connector on the connector pane.  For a subVI you can have multiple connectors.  They are all passed at the same time.  When TestStand calls a code module, whether it's a dll, VI, COM or other, they all go at the same time.  Order is irrelevant.
Use B:  a Parameter (and I capitalize it on purpose) is a section for variables in a sequence.  It is used to pass information back and forth between calling sequences and sub sequence (just like subVIs).  Think of it as the "connector pane" of sequences.
Ok stepping down from my soapbox now......
In order to find you the right solution I would need to understand your application and use better.   Let me know if my understanding is correct:
You have 2 sequence files with various steps that run in order.  They both have some of the same steps in them?  You are worried that if both Sequence Files are executed at the same time then they could conflict with each other?  The simplest solution is to just not run them at the same time.  Otherwise you will have to use locks and synchronization so they don't tromp on each other.
Also, where are your Classes stored?  Are they .NET assemblies?  Where are you storing your "parameters"?  Are they in the Sequences or in some code module?
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~