NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Passing of Parameters to Test Sequences

Solved!
Go to solution

Hello,

 

I am looking for a flexible method in which to pass parameters in from a common test executive sequence to dynamically called test sequences.  Here is what I currently have in place.

 

  1.  A common test executive sequence that retrieves parameters from a database based upon the station, the UUT part number, and the tests being run.  There are three categories of test parameters:
    1. Station Specific
    2. Part Number Specific
    3. Test Specific.
  2. The test executive sequence empties and then populates a container variable for each category with the variables retrieved from the database.  For example:
    1. Station.LocationID, Station.Region
    2. PartNumber.FirmwareVersion, PartNumber.VoltageSupply, PartNumber.MaxCurrent
    3. TestSequence.MaxLimit, TestSequence.MinLimit, TestSequence.Setpoint
  3. These containers are passed to the test sequence, which have the containers as parameters.  Note that the test executive does not have knowledge of which station parameters and part number parameters are actually being used by the test sequence(s).

As long as the variable names and types match, all is good.  This always true for the Test Sequence parameters.  However, some test sequences do not use all of the Station or Part Number parameters so if the test executive populates the container with all of them, calling the test sequence generates an error.  We could populate the test sequences with all Station and Part Number parameters but this will become unwieldly over time.  Plus if a new Station or Part Number parameter is added in future, all test sequences have to be touched.

 

We found a work around which is emptying each container in the test sequences.  This works because the test executive populates the parameters for the test sequence.  However, I think this is not an ideal solution because it requires local variables for each parameter assigned a value with #NoValidation.  I am looking for other suggestions.

CLA
0 Kudos
Message 1 of 3
(1,444 Views)
Solution
Accepted by topic author terickson

Do I understand correctly, that you get an error, when "unexpected" / "unwanted" data is passed in your container down to the subsequence?

 

Are the containers type-def'ed? Have you tried disabling type check on the parameter?

Oli_Wachno_0-1686754871210.png

 

 

 

 

Message 2 of 3
(1,396 Views)

Learn something new every day.  Did not know that existed until now.  Thanks!  It works.

CLA
0 Kudos
Message 3 of 3
(1,381 Views)