Aborting an Execution

[JohnGleeson]

I have my own VB based interface to TestStand from which the user can select a sequence and execute it. All the steps in my sequences are themselves SubSequences created using the Sequence Adaptor. One of the steps in one particular sequence needs to do some setting up the first time it is run in the sequence so the step has a paramater called FirstTime which I set from the UI using code like

NextStepProp.SetValString "TS.SData.ActualArgs.FirstTime.Expr", 0, Chr(34) + "True" + Chr(34)

This works just fine - most of the time. The problem occurs if for some reason the user has to abort the execution of the sequence which I do in the UIMsg_Trace callback using

msg.Execution.Abort

If the user then starts another execution of the same
sequence, even though the code to set FirstTime to True is run, a MessagePopup in the SubSequence reports that the parameter is still False. This does not happen if the sequence is allowed to terminate normally and is then restarted.

What could be different in the setup after an abort compared to that after a normal termination.

Any suggestions appreciated.

[Ryan Ramcharan]

Hi John,

Why do you not put your setup code inside of the process model? This way you can have this step execute once and then enter your UUT loop? You can use a TestStand Station Global to control if the step runs or not.

Just a thought. It is generally bad architecture to set sequence dependant data inside of your OI. Your sequence should be able to be run from any OI, including the sequence editor. You should only use the OI to update the user with information generated by your test.

Bob