How do you keep the Sequential Model from continuously looping

[ATE_Dude_22]

I have an ATE project where I am using a custom "Batch Model", but I have one sequence that is just a manual control. if I choose "No Model", it works exactly how i want it to, but when run from the TestStand UI after its been deployed, the "Run UUT" button goes away unless I select a process model in the Sequence File Properties. If i select SequentialModel.seq, it continuously loops, and I'm having a difficult time finding a programmatic way of making it only run 1 time.

[~jiggawax~]

There are many ways to achieve this.  Here are a few:

1- Use the Single Pass entry point and not the Test UUTs entry point.  You may have to create another button for it or just connect the current button in the UI to the second entry point and not the first.  You can definitely call it from the menus if you are using the full-featured UI.

2- Modify the process model to not loop

3- Add the PreUUT to your client sequence file.  Put a variable in there that gets stored as a FileGlobal.  Set it to True after the dialog pops up and then check to see if it is True for a precondition on the dialog.  If it is True then just set the flag to not continue testing.

Let me know if you need more specifics on any of these.  Pick your poison.

Cheers,

[ATE_Dude_22]

Thank you, option 3 was the easiest to implement.

[ATE_Dude_22]

This is crazy, but it all of a sudden stopped working, and I can't seem to figure out why???

[~jiggawax~]

It's gotta be something in the logic somewhere.  Another thing you could try is setting that flag back to False in the ProcessSetup?

[ATE_Dude_22]

Yeah, that's what it was, but I have no idea what changed it to begin with?!?! However, it is now working again. One thing I'm not really understanding is how the Parameter called "ContinueTesting" seems to work with the process model??

I'm having a hard time tracking down where this parameters is used??

[~jiggawax~]

Inside the model there is a loop.  Not sure what version of TestStand you are using.  In later versions there is a For Loop inside of the Test UUTs entry point that uses  it.  When the PreUUT returns that gets set to a flag in that sequence.

Look at my screenshot!