NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TS ActiveX API, Get Currently Executing Step Name

I would like to, from LabVIEW, connect to TestStand, and retrieve the name of the currently Executing Step, without supplying a sequence file path such as if I were to use the GetSequenceFileEx method.

 

If there is no sequence file actively executing, it is ok if this returns an error.



I saw my father do some work on a car once as a kid and I asked him "How did you know how to do that?" He responded "I didn't, I had to figure it out."
0 Kudos
Message 1 of 4
(2,887 Views)

I guess, that it is not possible.

To access executing step name, you need to have sequence context reference. So one way is to launch from LabVIEW TS Engine -> sequence -> get context. The second way (but I'm not sure in it), that your sequence in pre or post step callbacks will broadcast (by named queue, or something) name of executed step, and you LabVIEW application will catch it. Broadcast sequence context does not make sense, b/c while you will process it, it'll be changed (b/c it has dynamic value).

But, maybe, someone knows nice solution for it - in this case I'd also be very happy to hear it...

 

Sincerely, kosist90

 

logos_middle.jpg

 

JKI VI Tester – useful tool for LabVIEW developer

0 Kudos
Message 2 of 4
(2,867 Views)

Hey,

 

There TestStand Palette gives you a Sequence Context ctl for your front panel. This should be your input, and you need to send the reference of ThisContext from the Sequence you wish to track.

 

From that, a property node gives you the Step reference and calls the currently executing step in that Context.

 

I've attached a vi that just outputs the name of the current Step, but you should be modifying this.

 

I hope this helps.

 

Nic 

--------
Nico
Systems Engineer

Certified TestStand Architect Certified LabVIEW Architect

0 Kudos
Message 3 of 4
(2,824 Views)

This approach is clear; but it means, that you need to add input SequenceContext to every code module executing within TestStand - what is quite annoying and not optimal; and then somehow also send this data away - b/c, as author of topic told, he'd like to connect to TestStand, and retreive step names.

 

Sincerely, kosist90

 

logos_middle.jpg

 

Caraya test framework for LabVIEW – convert your VIs to test code!

0 Kudos
Message 4 of 4
(2,815 Views)