Autopopulate Project Path for a LabVIEW Action Step

[martin.perry]

I am working on a project that uses TestStand to verify the behavior of a LabVIEW project. The labview project is still under development and the project name iterates with the revision (ex. "project name vXX.lvproj"). If the Project name is changed this now makes all the currently written TestStand sequences break as they cannot locate the project.

My goal is to make the steps project name independent in a way that they would look for a project file from within a relative path. Has anyone figured a way around these limitations in specifying a Project Path?

I currently have the sequence editor setup within a workspace that defines the root of my relative paths and the steps are setup to use relative paths, this allows it to find the named project regardless of disk location (we have several dozen developers).

Any help is appreciated, if you have any other question about how things are setup feel free to ask.

Martin

[JL@NI]

Hello Martin,

I was thinking of a way for an operator of your TestStand sequence to select the current revision of the LabVIEW Project to run the test on. There is an API call that displays a file dialog box enabling a user to choose the current revision of your LabVIEW Project. Once you have that path, you can store it in a parameter and use it to update the LabVIEW Action Step's project path. Because of the structure of LabVIEW projects, the VI Path name in the Action Step must contain "My Computer\". I added a statement that will append the VI name to the required string "My Computer\". Attached is an example sequence file (TestStand 2010 SP1).

A couple of things to note:

1) To make some of these properties accessible you need to configure your station options. Go to Configure >> Station Options >> Preferances and select Show Hidden Properties

2) Make sure that the code module in the action step loads dynamically.

The API method used in my example is DisplayFileDialog Method. 

There are a few other ways to achieve what you want. If anyone else can think of other ways, please chime in!

Regards,

Jeff L.