Eidt Part of sequence to only execute once in Test UUT

[ShaneDonn]

Hi,

I am using 1 sequece file to execute testing on a number of different product types.

At the moment I am using a message box for the user to select the product under test and based on the return from the message box I select the correct limits to laod with the property loader.

My problem is I don't want to see this message box everytime a device is test using Test UUTS. (only on the forst run)

Can anyone please adivse the best approach to handling this case.

PS: I would like to stay away from modifying my OI, as I do not want to get into the case of having custom OIs for different test sequences.

Regards,

Don1.

[Gary_H]

Hi,

One possible solution would be to create a PreUUTLoop callback sub-sequence within your client sequence file, assuming you are using the SequentialProcessModel.seq.

Then place the step that calls the message box within the PreUUTLoop callback sub sequence.

This should have the effect of displaying your message box only once, when the sequence is first run, before

the first test loop.

regards,

Gary. 

[ShaneDonn]

Hi Gary,

Thanks for the input.

I am fairly new to TestStand, can u give me a quick list of the basic instructions I need to try this out?

Will the edited PreUUT be used for all programs going forward or can I use the default TestStand one in future programs?

Regards,

Don1

[Gary_H · Accepted solution]

Hi,

To try out my suggestion do:

1. Open your sequence file in the Teststand Editor.

2. Select the Edit drop menu, select the Sequence File Callbacks. . . option.  

    This should display a new dialogue box displaying the available callbacks associated with the Process Model in use.

3. In the new dialogue box select/highlite the PreUUTLoop callback, then select Add.

    This should add a new sub-sequence to your sequence file called PreUUTLoop.

    Close the new dialogue box.

4. Open/select the new PreUUTLoop sub-sequence in your sequence file.

    Insert a new Message Popup type step into the main step group, add some simple text just to try out the idea.

5. Run your sequence file. The simple text you entered should appear as a Message Popup dialogue

    box, just once, before entering the test loop.

6. If this works for you, replace the Message Popup step with your steps which obtain the user information.

regards,

Gary.

[ShaneDonn]

Hi Gary,

This works perfect.

Thanks for all the help,

Regards,

Don1.

[Gary_H]

Hi,

I forgot to answer your other question about using the PreUUTLoop in future sequences.

My suggestion would be to modify the Process Model.

Assuming you are using the standard SequentialProcessModel, try the following:

1. Open the SequentialProcessModel.seq in the Teststand editor.

2. Replace the empty PreUUTLoop callback sub-sequence in the Process Model sequence with your own.

3. Remove the PreUUTLoop callback sequence from your own test sequence, if it exists.

The above steps ensure that all your own future test sequences will run your own PreUUTLoop

callback without having to remember to include the callback actually in the future test sequence.

regards,

Gary.  

[DRock]

Thanks for your detailed and impeccable answer(s), Gary! 

I simply want to add, Don1, that you'll want to make sure you have a backup of your ProcessModel before making modifications.  Typically, users will keep the <TestStand>\Components\Models\TestStandModels directory intact as installed by default, but make a duplicate of that folder and place it in the <TestStand Public>\Components\Models\TestStandModels directory.  This allows them to modify and utilize a copy, while always ensuring that a backup exists, if necessary.

[ShaneDonn]

I appreciate the input DRock.

Regards,
Don1.