How to connect to a running sequence

[Ovide]

I have an Operator Interface that has been created in LabWindows CVI 8.0 and I am using TestStand 3.5.

The Operator Interface launches TestStand. The problem is that I am unable to debug my TestStand sequences this way.

Once the Operator Interface has started running my sequences I cannot attach to these sequences.

I can only start running my TestStand sequences stand-alone until the point where input is required from the Operator Interface.

Therefore, in debugmode, I would like to lauch the Operator Interface and wait for TestStand being launched.

I will launch TestStand manually (and place some breakpoint). This way I will be able to step through the sequence files with an active connection between Operator Interface and TestStand.

Can anyone tell me how to connect to a running sequence?

Suggestions for a different approach?

Thanks in advance,

Greetz,

David

[RayFarmer]

Hi,

If you have deployed with a debug licence and you have logged into TestStand (Operator Interface) with a user that isn't an operator, then you should beable to set breakpoint in your Operator Interface.

Regards

Ray Farmer

[Ovide]

Ray,

The problem is not placing breakpoints in the Operator Interface (custom made in CVI). I am able to do so. The problem is the fact that I cannot place breakpoints in my sequence files and step into the sequence files by launching the user interface. The Operator Interface starts execution with TS_EngineNewExecution (TS CVI API). When opening the sequence editor after the Operator Interface was launched I can only start running a new instance and not attach to the already running instance.

Greetz, David

[Sean]

I'm trying to clarify what you're hoping to do.

My interpretation is that you want to start execution in one executable, e.g. operator interface.  Then, at some point during execution, you want to continue that execution using a different interface, e.g. sequence editor.  Is this what you're trying to do?

If this is what you're after then I strongly doubt it would be possible.  You normally debug within the sequence editor, then use your operator interface after you're happy with it.

[RayFarmer]

Hi,

First thing, you either use the Operator Interface or the Sequence Editor to run your sequence files not both.

Second, what are you trying to debug, Operator Interface or your Sequence File?

If its the Sequence File, then it would be best to use the Sequence Editor, but if you cant use that, then run your Operator Interface as an Exe and not launched from CVI. (You can Debug into your DLL's by setting the External Process in CVI as either the sequence editor or your test exec program (Operator Interface) Then you run debug from CVI which will launch the external process.)

Within your Operator Interface with the Sequence File loaded, you can set breakpoints on steps, run Selected steps, (with or without process model entry points), run sequences, or run  Single Pass or Test UUTs. The only thing you will not beable to do is look at the values of your variables used in your sequences. (Thats why its best to use the Sequence Editor).

Hope this helps

Ray Farmer

[potpi]

Hi,

I am currently programming a CVI operator interface which uses TestStand sequences files. The sequences are executed properly but at the end no teststand report are generated and I really do not see why.

I launch my execution by using :

TS_EngineNewExecution (g_engine, NULL, g_sequenceFileToRun, "MainSequence", 0, VFALSE, TS_ExecTypeMask_TracingInitiallyOff,
CA_DEFAULT_VAL, CA_DEFAULT_VAL, CA_DEFAULT_VAL, &g_executionRan);

But I do not know if the problem comes from this expression.

Moreover, what I really need is what do i have to write in my code to launch a SINGLE PASS or a test UUT's from CVI ?

thanks for your help

Configuration :

TestStand Engine Version:4.2.1(4.2.1.83)

Sequence editor 4.2.1.83

Licence: development system

LabWindows CVI 9.0

OS: Windows XP

[RayFarmer]

Hi,

The reason you are not getting reports is because you are not running your sequence with the process model.

You need to pass the ProcessModel sequence file object and the run either the sequence Single Pass or Test UUTs and not MainSequence.

[potpi]

Ok. I modify my code as you ask me to do :

TS_EngineNewExecution (g_engine, NULL, g_sequenceFileToRun, "Single Pass",

"C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\SequentialModel.seq" ,

VFALSE, TS_ExecTypeMask_TracingInitiallyOff,
CA_DEFAULT_VAL, CA_DEFAULT_VAL, CA_DEFAULT_VAL, &g_executionRan);

And it works now.

Thanks Ray