10-17-2012 02:57 PM
@Ben wrote:
Hi Charles,
It USED TO BE POSSIBLE to use FTP to transfer VIs to remote machines then afterwards use VI Server to open (with complete file path) and run the VI on the remote machine.
Ben
It still is, if LabVIEW is running. Correct me if I'm wrong but doesn't LabVIEW have to be running before you can connect to the port and tell the application instance to open a VI? I *think* the OP wants the host machine to kick off a known VI on the remote machine where there was no LabVIEW process running before hand.
10-17-2012 03:05 PM
@Charles_CLA wrote:
@Ben wrote:Hi Charles,
It USED TO BE POSSIBLE to use FTP to transfer VIs to remote machines then afterwards use VI Server to open (with complete file path) and run the VI on the remote machine.
Ben
It still is, if LabVIEW is running. Correct me if I'm wrong but doesn't LabVIEW have to be running before you can connect to the port and tell the application instance to open a VI? I *think* the OP wants the host machine to kick off a known VI on the remote machine where there was no LabVIEW process running before hand.
Last time I did it it was for RT so the rule maybe different there.
But I seem to remember a story by Jeane-Pierre Drolet talking about forgeting code at home but he did know the static IP of his home machines so he invoked VIs on the home machine to read the file to his work machine.
But i am getting old and memory is failing.
Ben
10-17-2012 03:07 PM
@MikeBowen wrote:
Yes, please do.
Thanks
Mike
Mike, the best example for asynchronous call and forget is actually a shipping NI example. Either search "Call and Forget" in example finder or goto:
C:\Program Files (x86)\National Instruments\LabVIEW 2012\examples\viserver\AsynchronousCallByReference\AsynchronousCallAndForget.VI
10-17-2012 03:20 PM
We have 2010, but I found an online reference that should get me there. Thanks