LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Trying to be lazy: using vi server between applications

A few quick notes since I'm working on something similar (4 years later):

 

If this was ever valid...

server.tcp.servic="My Computer/VI Server"

 

...this would be the correct INI entry, today:

server.tcp.serviceName="My Computer/VI Server"

 

adding something other than 3363 (used by default by the IDE, Integrated Development Environment) for the EXE is another option:
server.tcp.port=3362

 

I created a constant off the strictly typed VI reference since (at least this is my understanding) the strictly typed VI reference is linked to a disk location and pulls the VI into memory.  So, because a VI with that name is already forced into memory by the strict constant you might not actually be running the VI you think you are inside the EXE with your method.  To force LabVIEW to use the path you provided, I've used a strict pane reference instead (right click any strict VI reference and Create Constant).

 

Make sure to provide a unique port or service name when you open an application reference.  Else, you're refering to the IDE, not the EXE.

 

remote testing example.PNG

Message Edited by LabBEAN on 06-15-2010 12:01 PM

Certified LabVIEW Architect
TestScript: Free Python/LabVIEW Connector

One global to rule them all,
One double-click to find them,
One interface to bring them all
and in the panel bind them.
0 Kudos
Message 11 of 11
(964 Views)