TestStand deployment user interface

[stevesteve]

I have deployed my TestStand sequence and am using the 'Full-Featured', Labview TestExec user interface that comes with TestStand to run the sequence. On the surface it looks ok, but I am having intermittent failures in my sequence when running the 'Full-Featured Labview interface, whilst when running the actual TestStand Development interface the errors do not occur. It looks like a timing or scheduling difference between the TestStand development interface and the 'Full-Featured' Labview deployment interface (TestExec.exe). Possibly the 'Full featured' deployment interface is running quicker or out of sync.

What is the difference in the execution of sequences between the TestStand development interface and the deployment Full-Featured interface?

The sequence is deployed on the same PC.

System: Windows 7 32bit, TestStand 12 sp1.

[RaviShrigiri]

The link gives a basic understanding of the UI versus TS sequence editor :

http://www.ni.com/white-paper/7560/en/

Few questions :

Are you using the default user interface given by NI or you have customised it?

Does it happen with other user interface also (NI provides UI developed in c++,C# and CVI).

What error are you facing?Can you share the image.

Ravi

[stevesteve]

I am using the default full featured interface that came with TestStand 2012, I have not customised it (don't know how to). The problem appears to be that the 'Full featured' user interface appears to go faster than the TestStand interface causing sequence pass/fail tests to sometimes fail due to hardware reading/writing timing. I believe the speed of sequences depends on the graphics that are displayed, so maybe a difference there between the two interfaces. I have only tried the Labview one as I could in theory edit it as I have labView (if i new what I was doing).

Is there a way of slowing down the Full featured labview interface?

Steve

[RaviShrigiri]

Hello Steve,

You can slow down by enabling tracing and varying tracing speed.(Configure -->Station Options --> check for the tracing options and the speed bar).

This option is valid for both sequence editor and UI.

But i am curious to know why its failing (not erroring out) sometimes using a UI and not sequence editor.

Is it a specific test which fails or its totally random.

Regards,

Ravi

[Norbert_B]

What kind of modules are you calling in your sequence?

If they are LV VIs: What is the LV adapter configuration? Is it the same for both use cases (SeqEdit vs. Full Featured UI)?

Norbert