Start Asynchronous Call for a Remote VI

[Chickentree]

I was trying to use Start Asynchronous Call for a remote VI on another computer but it didn't work. Then, I came across this post. 

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Allow-Remote-Asynchronous-Calls/idi-p/1662414

Is it still true for LabVIEW 2015?

[Sam_Sharp]

I don't know if it's true or not in LV2015 - I would have expected the idea to have been closed off if it was now available/implemented.

Why do you want to do this? I'm mostly just curious - but I could see there might be memory/performance issues around just allowing you to run/instantiate asynchronous VIs in another process?! You'd also have to ensure that the asynchronous VI you are calling is actually reentrant in the executable. Why don't you use another inter-process communication method to launch the asynchronous VIs (e.g. tcp/ip?)?

[Chickentree]

Hello Sam_Sharp,

All I wanna do is to start and stop a DAQmx VI on a remote computer from a TestStand sequence on the main computer. The VI has a loop for DAQmx Read. Shared variables are used for data communication between the remote VI and TestStand once the VI is started by Call by Reference. Is there an obviously better way?

[Sam_Sharp]

I don't think it's an obviously better way...but we have written a test station that has some continually running VIs that we can interact with from the TestStand sequence - we did that using TCP/IP to 'enqueue' a message to the running VI.

Of course, calling a VI remotely which then launches your asynchronous VI would also work.

[Bob_Schor]

Before Start Asynchronous Call (I'm thinking LabVIEW 7.0), there was VI Server, which allowed you to run VIs on remote platforms (such as when running LabVIEW RT on a PXI).  Fortunately, I've moved beyond LabVIEW 7.0, but we did run and communicate with VIs on remote platforms using VI Server.

Now, we use Network Streams to set up bilateral Queued Message Handlers on both Host and Remote, and send messages back and forth to (for example) tell the Remote to "Do Something", and have the Remote tell us "I've done it, now what?".

Bob Schor