03-27-2006 09:26 PM
03-28-2006 11:57 AM
BCE,
There are many different ways in which you could implement your test system. Fortunately, TestStand provides more than enough functionality so you could implement it in different ways. One of the possibilities you mentioned in your post was to use LabVIEW to generate the TestSequence. Although this is a good idea, and one that I have seen other customers use, it does have its drawbacks. In order to create your Sequence you will have to save each Step's information in one of two ways. You could save it in a file which you would parse through using your VI, or hard code the information into the VI's algorithm. In both of these cases we will need some kind of file containing the Sequence information, be it a text file or a VI.
Wouldn't it be easier to save all the Step information from your Sequence file in a Sequence file itself? This begs the question, would it be necessary to create a Sequence at all? Why couldn't we use a Sequence that contains all the possible steps and just disable the execution of some of them based on user input? In your post you say that you find it cumbersome to skip certain steps. In my opinion it is much more cumbersome to create a Sequence every time we want to run a test.
Therefore, I believe the best way to implement your system would be to have the first Step of your Sequence pop up a dialog box where users could select which types of tests they want to run. (You might even want to add this to the Serial Number window inside the PreUUT callback). Based on the users' input we would update an array of local boolean variables which determines what tests or test categories should be run. Each Step in the Sequence would contain a precondition that would read the value from this array and determine if the Step would be executed or not.
Just my two cents. What does the rest of the community think? There is more than one way to skin a cat and TestStand provides more than enough silverware. 😉
Regards,
Santiago D
03-28-2006 06:15 PM
Santiago,
Creating a Sequence File of all of the possible test steps solves half of the problem. I am pretty new to TS, but i believe that the For Each flow control steps may solve the temperarature/voltage nested loop requirements. Use a pop-up to get temperatures and voltages and store in an array.
I'm not sure how I could change the order of the steps to allow for random test order within the temperature and voltage loops?
Thanks for your suggestions and any further ideas,
BCE
03-29-2006 03:36 PM
Hello BCE,
I am not exactly sure what you are trying to accomplish. In your first
message you mentioned that you wanted the user to be able to randomly select
which test he wants to run. If this is the case, you can create a
sequence that runs steps based upon the users selection.
If you need to randomize the order of the steps in the sequence file (and not
just execute or skip a test), you will need to programmatically create a
sequence file. You could programmatically create the sequence in LabVIEW
or TestStand using the ActiveX server. If you would like to see an
example of how to do this in TestStand please see the example called 'Sequence
Builder.seq' typically located in the following directory
C:\Program Files\National Instruments\TestStand
3.5\Examples\SequenceBuilderTool\LabVIEW
Regards,
Jesse O
Applications Engineering
National Instruments
04-03-2006 10:18 AM
Jesse,
I'm trying to create a random order of the tests, so I will need to create a test sequence each time. Thanks for the suggestion, I'll check out the example.
BCE