For simple operations would be nice to have possibility to drag and drop functions from LV functions palette directly (default step type can be Action)
This would be very nice. Many times I just want to call a simple VI that is already built into LabVIEW, but instead have to create a wrapper VI just to bring it outside of LabVIEW to call within TestStand. Seems very redundant, and creates additional file management that would otherwise not be needed.
Raydur, if you already have a VI built whether it's in the Labview vi.llb folder or one of your own then all you need to do is browse for it with the 'Browse for VI' button.
There is no need to create a wrapper.
But I do like the idea of having access to the LabVIEW palettes from TestStand it would make it a lot easier.
RayFarmer - for VI's I've built this is relatively simple. For VI's built into LabVIEW I find it difficult to actually locate where these are. Is there an easy way to do this? Using the example of the OP, if I wanted to call the VI from the LabVIEW String pallete "Match Pattern" - where would I browse to find this VI, or more generally how would I know where to find this? If I browse to vi.lib/string there isn't anything pertinent there. Is there a way to tell where the library is that contains a built-in VI? Is there some logic behind the pallete groupings and where the actual VI is located on disk?
It sounds like we are trying to create a crutch to add needed functionality to the TS language -- If there's features native to LV that we are needing to call, shouldn't these be added to the TS language itself rather than adding the overhead of calling to the LV engine, LV executing the code, and then returning data back?
warren_scott - you are right that it's overhead, but LV is far in front of TS, so a lot of functions in TS language are missing; the intension is to use what we have in LV already
