Get ALL Steps name using TestStand API

[LVEnt]

Hi All,

I am trying to read all the steps in a TS Sequence using the TS API. I have successfully been able to get the steps in the MainSequence, but I am looking for a solution to get ALL the steps, even the ones in a sequence call.

Can you give me some pointers.

TIA.

[Ahmed99]

can you explain more please ?  what output you need ? 

[LVEnt]

I need the step names & the Unique Step ID of all the steps in the Sequence, including the subsequences.

[Ahmed99]

write this in any pop msg or expression you get step name

RunState.Sequence.Main["Step5"].name

[LVEnt]

I need to get all the sequence names using the TestStand API and loop through them all to get their step names (Is my guess), I also need to do this in LV. The VI I attached is where I have managed to get the step names in the mainsequence, but I am stuck as to how to do this for all subsequences.

[Ahmed99]

ok make like that : for loop with 9 loops and local.stepnum as incrementer 

and so on 

[LVEnt]

I might not be explaining this correctly, but I need the solution in LabVIEW. The TestStand Seq is just to test the code out.

[Ahmed99]

ok you just need to make the ID and name arrays as output in connector pane then they appear in module load you can put them in local variables and use them

[LVEnt]

If you notice, inside that last sequence call there is another step, I need that step name as well, the current VI I posted, gets upto this point. I need the step name inside the sequence call.

[Oli_Wachno]

From what I understand, you need a possiblity to analyze the steps in the subsequencess being called as well.

So, from in your toplevel sequence, you need to analyze all the test steps, if any is a SequenceCall (Step.StepType.Name == "SequenceCall").

If so, you will find the information about the sequence being called in the Step.SData container

you need to cover three cases:

- UseCurrentFile (Step.TS.SData.UseCurFile == True)

- "regular calls" to arbitrary sequences in sequence files (Step.TS.SData.SFPath, Step.TS.SData.SeqName)

and

- Calls Specified by Expression (Step.TS.SData.SpecifyByExpr == True)

though tis last one is not neccessarily analysable during develkopment.

If you are wondering, where this Step.SData is coming from:

But you have to make the following setting first