Open VI Reference to a LabVIEW executable.

[Michel_Gauvin]

Hello,

I haven't done this for a while and it's not working like expected.  I'm trying to "Open VI Reference" from executable A.exe to B.exe.  I'm trying to get a control value from B.exe in A.exe.  Can someone send me an example?

Right now I'm at this stage: I have A.exe running as a LabVIEW executable.  I'm trying to "Open VI Reference" to A.exe from LabVIEW development without success.  Not sure what I'm doing wrong.

Don't hesitate to ask more info if you need some.

LabVIEW 2012, Windows 8.1.

Thanks,

Michel

[crossrulz]

You need to refeernce the VI that is INSIDE of the exe.  If your exe was built with the 8.x format, then the the VI's location will be A.exe\blah.vi.  If in the newer format, then you need to know the directory structure of the project to get the the VI you want since the newer formats make the executables like a zip file.

[mikeporter]

First you have to get an application reference to the instance of LabVIEW that is running the VI you want to access.

Code?

Mike...

[mikeporter]

You only need to worry about the directory structure if the VI isn't already in memory. If it is in memory all you need is the name. Static references are your friend.

Mike...

[Bob_Schor]

I don't think you can do this with executables.  "Open VI by Reference" is analogous to calling the VI by putting its icon on your block diagram.  What you are trying to do is to execute another executable (which has nothing to do with LabVIEW -- it could be any executable, such as Microsoft Word).  You could uses a System Command (that may be the wrong term), something like going to a Windows Command Prompt and typing the name of the program (the Executable) that you want to run, but it is a little clumsy.

BS

[mikeporter]

The OP says that the executable was created in LabVIEW.

Mike...

[Bob_Schor]

Once you have an Executable, does it matter that the underlying Development system is LabVIEW, rather than (say) Visual Studio, or Matlab?  I suppose you could write an application that "knows" to, for example, listen to a TCP/IP port and interpret/execute commands, but that doesn't sound like the question being asked.

BS

[VItan]

---

@Bob_Schor wrote:

Once you have an Executable, does it matter that the underlying Development system is LabVIEW, rather than (say) Visual Studio, or Matlab?  I suppose you could write an application that "knows" to, for example, listen to a TCP/IP port and interpret/execute commands, but that doesn't sound like the question being asked.

BS

---

LabVIEW-built executables still run as VI's in the RTE, though.  Their identities have not been abstracted away into one single object or anything, and they still have name-based VI server access.

You can configure a build specification to include almost nothing, and require the VI files to be present in expected locations (i.e build specification's data or support directories).  By default, all items in an executable application build specification are set to be put in the same location as their caller, which results in most things going into the .exe file, internally referenced in a directory-esque form like crossrulz mentioned, "MyExecutable.exe\MySubVI.vi".

[mikeporter]

Your last paragraph is no longer (since V9) correct. Now the development directory structure is duplicated inside the executable.

You can optionally still tell LabVIEW to use the old flat structure, but there is no good reason to do that.

Mike...

[Michel_Gauvin]

Hello,

Lot's of answers, thanks. The 2 executables are LabVIEW built.  I have tried different path option but nothing is working, I must miss something simple here. I will try tomorow with two simple LabVIEW executabe and report the status.

Good night,

Michel