"Hide" some step from display on execution view in teststand 2016

[seonk]

Hi, does anyone know is there any way to hide some step in execution view (teststand 2016)? Because I didnt want it to show to operator as they do not need to know the process and it is confussing for them. I try to read through some old post which few years back on forum, found most of them saying it is impossible to do that unless by writing custom VI or put those into subsequence and disable trace to subsequence.

[CharlieRodway]

Hi,

Are the operators executing the tests from the Sequence Editor or from an Operator Interface?

[seonk]

Hi,

Thanks for reply, is operator interface which i customize from teststand example - simple user interface.

[RaymondFarmer]

So the SequenceCall step that you what to hide.

in the Step Properties, Run Options, set the Sequence Call Trace Setting to Disable tracing in sequence

hope this helps

Ray

[seonk]

Hi,

Raymond, thanks for your reply. However i tried to use UI message and output my result to multiple column listbox instead of using execution view that suit my application better.

Thanks

[RaymondFarmer]

Are you using a custom UI message?

How do you indicate what you dont what to view in you sequence?

Ray

[seonk]

Hi Raymond,

I only indicate what i wanna show by using UI msg to update the info to my OI. However, i lost the link. I found it in this forum is some old post.

[RaymondFarmer]

This is a screen shot of the default simple UI supplied with TestStand 2014.

With the SequenceCall steps diabled tracing as outline above, all I see is the two top level steps running.

With one of the steps set back to tracing, then I see the steps in the SequenceCall.

I have dont nothing in the UI to achieve this.

regards

Ray

[CharlieRodway]

Hi,

I answered a similar question a few years ago on this topic, where I suggested that the tracing could be turned on and off selectively using ActiveX calls:

How can I choose display a step or not when sequnce running

This could be used to selectively turn on and off tracing throughout the sequence to hide sensitive or confusing sections from the operator.

I would also use pre-conditions to check if the Sequence is being executed from the editor or from an operator interface.

As the Engine API can now be accessed through expressions, I'd use a Statement step with the following expressions:

//Pre-Condition
Runstate.IsEditor == False

//Post-Expression - Turn tracing OFF
Runstate.Engine.StationOptions.TracingEnabled = False

//OR 

//Post-Expression - Turn tracing ON
Runstate.Engine.StationOptions.TracingEnabled = True

I've attached an example sequence file.

Regards,