Using lvproj or lvlib from TestStand?

[Believer]

I have an Agilent 34401 LabVIEW driver that is in the .lvproj and .lvlib format - but not available as

an LLB. I want to call the various VIs as steps from a TestStand sequence.

But I also have many other drivers like this.

So, while I can reference the individual VIs directly from TestStand in the subdirectories

(like Initialize.vi in the Public directory), I am concerned that this 'Initialize.vi' might get

'mixed up' with another driver's version of 'Initialize.vi' if I use the 'Relative Path' option.

Should I use 'Absolute Path' in the TestStand step (not recommended in most cases)

or is there some way for the step to reference the VI through the actual .lvproj or .lvlib file?

Bottom line - how do you use a driver like this from TestStand?

Thanks in advance,

Ronnie

[dowNow]

I second this question.

cc

[Manooch_H]

Hi Ronnie,

In TestStand 4.2, when you specify the module (browse to a VI), TestStand grabs the full name of that module, including its namespace, and stores it. Then, when the module is actually loaded into memory (the time this occurs may be different based on the Step Load Option you've specified), TestStand again grabs the full name of the module that is about to be loaded into memory, and compares it with the full name that was stored when the module was initially specified. If the full names match, TestStand will then continue to load the module into memory.

As long as you use unique relative paths for the VIs that you call, TestStand will call the correct VI. For example, calling two separate Initialize VIs via the relative path Public\Initialize.vi or simply Initialize.vi will cause problems. However, calling two separate Initialize VIs via the relative paths Driver1\Public\Initialize.vi and Driver2\Public\Initialize.vi will be okay.

Hope this helps Ronnie.

[Believer]

Thanks for the reply Manooch H. But it seems to me that the project files (lvproj - perhaps even the lvlib?)

know the actual paths of the VIs in them. If this is true, then could there not be a step type that could

allow you to select the lvproj file and then drill down to choose the specific VI within it (like an LLB) ?

[Manooch_H]

We have had customers request this feature in the past and we greatly appreciate the feedback. We are currently looking into the possibility of providing support for calling LabVIEW VIs in the context of LabVIEW Projects and Libraries in a future version of TestStand.

Thank you for your feedback Ronnie!

Message Edited by Manooch_H on 07-27-2009 12:40 PM