Running sequence starts second testing-sequence

[OnlyOne]

Hello,

in Teststand 4.2 i have in the the SequenceFileLoad of the model a SequenceCall to a sequence starting with "Use New Execution".

This sequence is running/looping all the time and checking some hardware-inputs.

If there is then a special input then i am starting the testing-sequence which makes measurements to the DUT by executing a SequenceCall.

Currently i start this test-sequence also as "Use New Execution" but it seems as this needs much memory when starting to often.

So my question is:

1. Is there an option to close the previous new executions

OR (better ?)

2. Is it also ok if i set in the SequenceCall of this testing-sequence the Execution Options to "None" instead of "Use New Execution"?

Thanks for help

[snowpunter]

Rather than spawning a new execution in the SequenceFileLoad callback why not loop in your PreUUT (or similar) callback looking for the external input? This would greatly simplify your execution and would follow the intended design pattern of TestStand.

[OnlyOne]

Yes i know what you mean. But i have more than one sequence that is executed. If i would use the preuut then i have to copy this in all of my sequences.

Currently:

Model.SeqFileLoad --> NewExecution[looping-sequence] --> NewExecution[testing-sequence]

The looping-sequence receives digital and serial signals and executes then different a testing-sequence.

My question is only if i can execute the "testing-sequence" also with Execution Options = "None" instead of "Use New Execution"?

Thx

[Topper_Harley]

I understand that you keep your initial sequence running all the time. When a condition is met, this sequence launches another sequence ("test-sequence") as a new execution.

Do you want several instances of "test-sequence" to run in parallel with each other or is it just one instance at a time?

Have you considered using the Wait step to wait for an execution before launching a new one?

[OnlyOne]

The "always-running"-sequence is waiting with a notification that the test-sequence is finished.

And i always have only one test-sequence running at a time. Never parallel.

Does this mean that i can start the test-sequence without the option "new execution"?

[Topper_Harley]

Yes, I suppose so as you do not run any squences in parallel.

[OnlyOne]

The problem is when i switch from "New Execution" to "None" that it does not execute my model-TestUUT in this mode.

I need to execute the model-steps for example for the report-generation.

So perhaps an other ways: How can i close the already opened executions? (When running the default OPUI in C:\Program Files\National Instruments\TestStand 4.2.1\UserInterfaces\Full-Featured\LabVIEW\TestExec.exe then each execution gets his own state-icon on the left side. When pressing the icon i can see the last results.

So it would be good to close the old executions to free up memory.

How can this be done?

Thx

[OnlyOne]

Here is a screenshot of what i mean:

[OnlyOne]

Hm, sorry i cant edit my last posts, that why i have to reply again.

I find in the menu of the OPUI it is possible to close the executions which means there must be a command for this.

How can i execute the marked parts directly in TS?

For example before a new start i can call this command and close the last execution.

Thanks

[Topper_Harley]

You do not have to close each execution manually, as is closes when the respective sequence is over.

The execution status LED changes color based on whether the sequence is running, suspended, or finished. A gray execution status LED with green checkmark means that the UUT passed the execution. The execution is not running any more.