NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Preconditions and running other steps

Problem 1:
I have a test sequence with many sub sequences. What I want to do is to be able to run a single sub sequence by using RUN SELECTED STEPS USING --> SINGLEPASS. Now I have some steps in the setup of MAIN that have to be run (machine init) all of the time so I put them in the setup. Some of the steps I want to run using single pass need the setup steps PLUS other steps. How can I get those "other Steps" to run? I CAN NOT just highlight them. The reason is an operator will be doing this for troubleshooting the UUT and may not know what to run. So it needs to be a precondition or something like that.

Example1: I have a sub sequence in MAIN that measures the resistance of a resistor. (In setup there are machine init steps). If I run just this step using "Run Selected Steps" It will work fine because the machine init steps are in set up and doesnt require anything except the measurement.

Example2:
I have a sub sequence in MAIN that measures voltage of an output. (In setup there are machine init steps). If I run this step using "Run Selected Steps" It will Fail because it relys on steps prior to it to apply power to the UUT that are not in the setup.

The question is, is there a way to run needed steps (like apply power) and not have to put them in setup. Remember,
I CAN NOT just highlight them. This is an operator running these tests.

Problem 2:
Same senario except I want to "Run Selected Step" that is a sub sequence of a sub sequence. So I need to run the setup of main plus the apply power steps. Running selected steps that is a sub sequence of a subsequence will not run the MAIN Setup.
So is there a way to run The MAIN Setup no matter where you are in the test sequence and other "apply power steps". Using some sort of precondition or something??
Thanks in advance for any help.
Erik
0 Kudos
Message 1 of 4
(3,299 Views)

Just a thought but how about using a sequence call step type. Since it has the setup, main and cleanup tabs you can set up the instrument correctly there. Your logic can be put into the preconditions of these step types and into the post action of previous steps.

Hope this helps.Smiley Happy

Now Using LabVIEW 2019SP1 and TestStand 2019
0 Kudos
Message 2 of 4
(3,292 Views)
I am using a sequence call step thats what I am calling a sub sequence I guess... The problem with this is I am using TS with a Wayne Kerr (WK) machine. Upon initialization of the WK in the steup of main, "handle" variables are created by the WK and given to TS to use as "names" for all the pins. So I think re initializing in the sub sequence will mess all of the handles up for the rest of the test. Plus even if this would work the initialization of the WK takes several seconds and would increase my test time greatly...
0 Kudos
Message 3 of 4
(3,286 Views)

I'm not familiar with your instrument or it's associated driver. I would only initilize the device once and save the handle to a variable (global? file sequence?) where you can use it in your subsequence. With this handle you might be able to reconfigure your instrument as needed in the subsequence without initializing again.

Hope this helps.

Now Using LabVIEW 2019SP1 and TestStand 2019
0 Kudos
Message 4 of 4
(3,282 Views)