Dynamic calling of subsequence and wants to stop main sequence

[LV_user1]

HI All

I want to load a LabVIEW VI through TestS tand dynamically. 

For that I am calling a code module in one sequence and calling this sequence in the sequence call in the Main sequence.

What I want to do is , when this VI gets launched through code module( which is used in sequence) this should run in background and my main sequence should complete its execution after executing all steps.

The VI which I have launched through sequence call should run continuously.

However the issue which i am facing is my main sequence is not completing its execution until and unless I stop the VI. I have tried launching the sequence in new thread and new execution. But still it waits for the execution to get complete.

How to stop the main sequence and keep the VI running in background??

Thanks in advance

[~jiggawax~]

http://forums.ni.com/t5/NI-TestStand/Passing-parameters-to-VI-in-new-thread/td-p/1735212

Hope this helps.  Let me know if you have additional questions.

[LV_user1]

I have checked the link. However I am still not able to get the exact solution.

I want to stop my main seq after calling subsequence( which is having one VI which is running continuously).

Vi should run in background even after stoping the main seq.

But main seq does not stop until and unless VI is stopped.

[~jiggawax~]

OHHHHH I missed that part.  You mean like this example.

You need to do it in a new execution.  Otherwise the execution of your test won't complete because one of its threads is still out there.  Also, you need to set the execution settings like this:

Hope this helps.

[LV_user1]

Hi,

Thanks for the reply.

This is the same thing which I have also tried.

I ran your example also , here after generating report if you see the status of the originalAutomation.seq status then it will be still as executing only. (see the attached screenshot)

I want that the originalAutomation.seq should stop executing also.

[LV_user1]

Forgot to add attachment

[~jiggawax~]

Then you need to put the New Thread sequence in a different file.  The problem is that the New Thread sequence belongs to the sequence file and it is still executing.  TestStand owns that execution so it will still say executing.  The only way to truly not have TestStand executing at all is to create an executable out of the VI and spawn that as a new process.  Otherwise to run raw VIs from TestStand then TestStand has to own the execution.

Hope this helps,