calling labview executable from teststand

[mrbean]

Once I removed the Error In and Error Out, it worked.  The other parameters now show up correctly.  Thanks.

[asbo]

Teds, were you able to use any clusters with the DLL interface or is it probably a good general rule that they're off-limits?

[Teds]

Cluster and Boolean inputs do not appear to show up properly.  When you build the DLL in LabVIEW with a boolean and clusters, the Function Prototype ( with C Calling Conventions ) is:

LVBoolean *EnablePopUp + TD1 *errorInNoError

TestStand does not recognize either.

My solution was to use separate inputs for cluster elements and a numeric for the boolean.   Not the ideal solution but it works.

Asbo, I suppose you could try to add the parameters manually when mapping the cluster in TestStand.  Then you could try to select perhaps a 'C struct' for the Category and see if that works.  

Thanks,

PH

[asbo]

I don't have any projects that require this interface right now, it was more a point of a curiosity.

Based on the linked documents below, it does sound like using a C struct could be a solution. I'll have to remember to play with this when I have some free time.

http://zone.ni.com/devzone/cda/tut/p/id/3936

http://www.docstoc.com/docs/31464530/Passing-Labview-Cluster-to-C-Structure-in-DLL

[mrbean]

Is the DLL's ini file similar to that of the exe - can I add "

allowmultipleinstances=true

" to it to allow multiple instances?

[mrbean]

In 2009, I see Calling System Exec.vi.  Is that the one you're referring to? 

[mrbean]

Attached is what I currently do, but as a VIT, I don't have control of various things like (in the EXE's .ini file)

allowmultipleinstances=true. 

However, I need to use subpanels so that each instance of the EXE is on a separate tab.  I'm not sure how to do (with an EXE or DLL) what I now do with a VIT.