Cross-linking the wrong LabVIEW VI code modules

[Eugene12]

There is often problems with cross-linking the wrong LabVIEW VI code modules. Why not automatically import VIs into TestStand from LabVIEW projects using the name of the LV project as a name extension for each VI in TestStand?

For example, if the name of the LV project is "Project 1.lvproj" and contains VIs named A.vi and B.VI, then these could easily be loaded into testStand as "A-Project 1.vi" and "B-Project 1.vi"?

Eugene

[Eugene12]

Here is a link that explains this better:

http://forums.ni.com/ni/board/message?board.id=170&message.id=487004&query.id=10619907#M487004

[RayFarmer]

Eugene

Check out the following link, there is still time left

http://forums.ni.com/ni/board/message?board.id=330&thread.id=29209

[Eugene12]

Okay Ray,

I have now applied.

Thanks,

Eugene

[Scott_Richardson]

Eugene - I am changing the status of this idea to 'beta'. The TestStand 2010 beta includes support for calling VIs in a project. You can sign up for the beta here: http://www.ni.com/beta. It would be most helpful to us to have LabVIEW users start experimenting with these changes and report back any issues or additional suggestions. Scott Richardson