The executables will use the same default port for the VI server as the
development environment unless the port is changed. Thus, if the
development environment, or other LabVIEW executables, are running on the
same computer, there will be a conflict. On the executable to be remotely
controlled, under the Tools>Options menu, set the VI Server:Configuration
for TCP/IP protocol and enter the port number wired to the Open Application
Reference function in the calling vi. Under VI Server:TCP/IP Access, enter
the IP address of the calling computer. Under VI Server:Exported VIs, enter
* for all vi's or the name of the controlled vi. Now stop the executable
and look for the .ini file that shares the name of the executable. It
should have your VI Server settings saved. All remotely controlled
environments, whether development or run-time, that are on same computer
need a unique VI Server port number set in the Options menu to avoid a
conflict.
"lmd2" <x@no.email> wrote in message news:173467@exchange.ni.com...
> I have two VIs on differnt PCs communicating by VI server. The server runs
the remote VI, inserts values into two controls, and then retrieves the
values from two indicators. This works fine. When I build the VIs into EXEs
it doesn't work. I have read that two differnt ports must be used, but this
isn't entirely clear. My server VI(exe) uses an "Open Application Reference"
function allowing me to call the client on port 3364 rather than the default
3363, but the client VI has no VI server functions, all it does is take an
SCXI measurement and expose the reading - is the "2nd" port implied (i.e.
the default) or do I need to explicitely add VI-server functions (to which
VI) to get this working? And which machine do I redefine the "VI Server:
TCP/IP" value to port 3363, the client or the server? Is there an
application note that goes more into how to configure two EXEs for VI Server
functionality?<br><br>thanx for your time.<br>lmd2