Control an event in one executible from another executible

[Terry_S]

Looking for some ideas from the experts:

I want to create two executibles, one is a image capture application (App1)  and the other (App2) is specific to a test we are performing.  What  I want to be able to do is trigger my image capture event (or change the status of a boolean) in App1 from App2.  App1 needs to be a standalone executible as it is used for many other test that we perform.  App2 could be may different applications that are written for a specific test.  Both applications will be running on the same computer.  As I am the delveloper of the applications I can add whatever is needed to make this work.

Thanks

Terry Sopkow

[crossrulz]

Talking between application instances is definately a challenge.  The simplest way I have heard was to use TCP/IP to communicate between the applications.

[camerond]

---

@Terry_S wrote:

Looking for some ideas from the experts:

---

I'm no expert, but:

Why don't you just set up App1 so it can be called as a subVI from App2, and a second variation as an executable, with wires to the inputs for App1 and user-input controls on the executable (or however you need to get input in both cases). As long as they get the same answers from the same inputs, what's the problem?

---

 As I am the delveloper of the applications I can add whatever is needed to make this work.

---

Add salt to taste and serve warm, with red wine.

Cameron

[JÞB]

Since a simple boolean value passed between applicaitions on the same PCs all you need a single process shared variable.

[aputman]

I'm not an expert either....

If you want simple, write to a text file in the temp directory.

[paul_cardinale]

Like this:

[aputman]

Avast AV blocked this file when I opened zip.

[Yamaeda]

1. Interprocess communication is simplest done by a textfile, although it requires polling of a directory or use of systemevent to register dir-change.

2. Network shared variables is easy to implement but doesn't feel as open and expandable as the 3rd option. (It also lends itself to polling, but should probably be the most fitting in this case)

3. TCP/IP send commands between any and all programs and from any language.

/Y

[Terry_S]

Sorry to bother you Paul, but could you save this for Version 11.

Thanks

Terry

[paul_cardinale · Accepted solution]

Oops.  That original .zip file had an old invalid version of the .lvproj file.

Here it is with the correct .lvproj, and downconverted to LV11.