RE: Accessing RunState Sequence Variables

[Nick92]

Hi all,

I'm looking to access the run-state variables of a sequence prior to calling it and wanted to know if this can be done. The overall objective is to disable tracing into specified sub-sequences while retaining the execution arrow within 'MainSequence'.

I am aware of 'RunState.Engine.StationOptions.TracingEnabled' and 'RunState.Execution.TracingDisabled', while these can be used to disable tracing into sub-sequences they cause the execution arrow to remain on it's current step until the execution is complete.

Each sub-sequence has the 'RunState.Tracing' variable which can be used to disable the tracing of that sequence alone. Given that 'RunState' this is a recursive property, is it possible to access this variable from the calling sequence? 

Thanks 🙂

Nick

[Jonah_TSE]

Hi Nick, 

Is there a reason you want to use the TestStand API to do this?

I think what you're trying to achieve is possible to do in the sequence call settings for the sub-sequences that you want to disable tracing for.

Under "run options" for any sequence call, you can set "Sequence Call Trace Setting", as shown below.

This will maintain the current position of the execution arrow in the main sequence as well.

This post covers a similar topic: https://forums.ni.com/t5/NI-TestStand/Set-Sequence-Call-Trace-Setting-for-a-SequenceCall-Step/td-p/1...

Hope this helps,

Jonah

[Nick92]

Hi Jonah,

Thanks for the response, while it is possible to go through and manually disable tracing on each sequence call. My aim is to achieve this programmatically, prior to entering the sub-sequence. The reasoning for this is that I have many sub-sequence calls throughout the applications I develop and rather than setting the tracing options per sequence call I am looking for a simple way to handle them all at runtime.

Using the variables I mentioned in my first post, I can disable tracing on-the-fly however this causes the execution arrow on the top level to freeze and the application appears as though it's not running, while this isn't the case I've found the end user prefers to see some sort of progress as tests are happening.

Many thanks.

Nick.