access step name in labview

[SZTE]

Is there any way to access the name of the current Step, as a string, in LabVIEW using the Sequence Context?

[GovBob]

I've had to change the name of a step at runtime. What I did was to use the ActiveX adapter to get the step name and write it to a local variable. Runstep.Sequence.Main(name of step you want, I used the unique ID). Configure the step for the TestStand API and the Object class should be Property OBject. Check call method. The action should be Get Property and the property should be Name. Create your local variable under the value column and this you can then use for your LabView code. Hope this helps.

[SZTE]

Thank for you for input. I'm pretty new with both Teststand and LabVIEW. I didn't do exactly as you mentioned but I got what I wanted. I took a lot of research direction from your description and looked into the ActiveX properties. I was able to extract the Step name using Propery Nodes of the Sequence Context. The Teststand help document for "Accessing TestStand Objects Inside Other TestStand Objects" had a code example that I changed to fit my needs. Thank you again for your help in directing my where to look.

[RayFarmer]

Hi,

Here's a labview VI that may help.

It obtains the Sequence Name from where the step was called, The Step name, and the full path from top level sequence to the step. eg if a step, "Action" was called from the process model and the step is in the MainSequence. the Resultant string would be MainSequence Callback->MainSequence->Action.


Regards
Ray Farmer

[SZTE]

Sorry, I'm using LabVIEW 7.0.

[RayFarmer]

Hi,

Try this. Hope its save to version 7.0 ok

Regards
Ray Farmer

[SZTE]

Thank you, it opened just fine. I ended up using pretty much the exact code from that example, a small part anyway. How important is it to close the references to the Sequence Context?

[RayFarmer]

Hi,

Its good practices to tidy up, after you have finished, but dont close the SequenceContext reference you pass into the VI, only those you derive from the main reference.

I surpose you could end up with a small memory leak for each un-closed reference. Which could be come a large leak depending on how many times your VI's get called before your application is closed.


Regards
Ray Farmer