How to invoke a Workspace tool from Labview using the VS API?

[LDBM]

I thought I had seem how to do this in a previous post..but no trace of it so far... Is there a .net call that can be used to launch a VS Workspace tool from LV ? 

Thx.

L.

[Devin_K]

This functionality is part of the Project API in NIVS 2010+.  I don't know of any examples, but in 2011 there is a LabVIEW wrapper for this function on the palettes under NI VeriStand >> Execution >> Project >> Workspace Automation.  Unfortunately there is no VI wrapper for it in 2010, but it still exists in the .NET API.

In addition to launching Workspace tools, you can also send messages to them with the "SendToolMessage" method. You can see an example of how to handle these messages in the example Workspace tool located at:

<LabVIEW>\examples\NI Veristand\Workspace\Workspace Tool Example.vi

[LDBM]

Ok, that sounds like a potential solution. What are the Workspace Tool Path though? For instance I want to launch the Channel Viewer tool.

L.

[Devin_K · Accepted solution]

Ah, good question.  The default tools are actually built into NI VeriStand.exe, so there's not an easy way to get the paths.  This was actually brought up in another thread you posted.  Have a look at Jarrod's response for some caveats to keep in mind.  His response also shows the current path for the TDMS Data Viewer.

The paths aren't documented, so if you need a specific tool, you're going to need to contact support so they can talk to R&D and get the path.  For your question though, the Channel Data Viewer is:

C:\<Program Files>\National Instruments\VeriStand 2011\NI VeriStand.exe\NI VeriStand\Workspace\Tools\Channel Data Viewer.vi

(where "<Program Files>" is either "Program Files" or "Program Files (x86)", depending on your operating system)

[LDBM]

Thanks Devin, it worked.  Now I remember... this sounded familiar.

Laurent

[Jarrod_S.]

If you are calling the API from LabVIEW, you don't need to pass in the full path for a built-in tool such as the Channel Data Viewer. You can simply reference it by the path "Channel Data Viewer.vi". Unfortunately this doesn't work from the Stimulus Profile Editor function call, but it does work with LabVIEW.