NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

How do I make a process model sequence (not entry point) available to the test sequence?

I have sequences that update process model data in the process model sequence that I would like to make public so that I can call this sequence from the test sequence.

I am using TS2.

I know that I could insert a sequence call and when specifying the module simply select the process model sequence file. Is there a more direct way of specifying the process model sequence file? Can I hide sequences in the process model so that they can't be called by the test sequence?

Message Edited by Francey on 05-19-2005 06:38 AM

0 Kudos
Message 1 of 5
(3,397 Views)
You can always call a sequence by reference. To get the Process Model of the current execution, you can use the reference "RunState.Root.Runstate.SequenceFile".

There is no concept of public/private sequences in TestStand, so you won't be able to hide any sequences.

Allen P
NI
0 Kudos
Message 2 of 5
(3,374 Views)
Thanks.

My next question would be how to create a step type that calls the sequence. And that when inserting a call to this step type I could enter the sequence paramters using the same dialog (or similar) to that of the standard sequence adapter dialog.
0 Kudos
Message 3 of 5
(3,367 Views)
When creating a custom step type, you can check "Designate an adapter", and use the Sequence Call adapter. If you would like to make the user unable to change this property, you can disable the "Can Specify Module" property on the "Disable Properties" page.

Warning: If you ever want to change the parameters or the sequence call you are making for all steps, you must load ALL of the sequences that use this step, check the "apply changes in this dialog to all loaded steps of this type" box when you make the changes. This means that you should be very careful to make sure you have your step type designed properly before you begin using instances of it. The reason this is the case, is that the module is a property for each instance of the step, rather than the step type. We are simply giving a default value. By disabling the specify module dialog, we are preventing the user from being able to change from the default.

Allen P
NI
0 Kudos
Message 4 of 5
(3,362 Views)
Thanks,

I will give that a try and let you know how I get on.
0 Kudos
Message 5 of 5
(3,358 Views)