11-22-2010 10:56 AM
I'm having problems using VI Server on a target machine that only has the Run-Time Engine. I can run the executable on my machine just fine, but when I run it on the target PC I get:
11-22-2010 12:11 PM - edited 11-22-2010 12:14 PM
Probably firewall. It runs as an executable on your development machine?
A
11-22-2010 12:16 PM
Oh, do you have the server running on the target system? That would also do it.
A
11-22-2010 12:18 PM
No dice, turned off the firewall and still the same problem.
11-22-2010 12:20 PM
Also, no server running on the PC. In fact, it's a fresh install of XP (minus the Run-Time engine and DAQmx).
11-22-2010 01:24 PM
If there is no server, then you won't be able to connect. 😉
Suggest you install that. 😄
A
11-22-2010 01:27 PM
Where is the link for the server? I've been looking for that but I can't find anything that is specifically "VI Server". I thought it got installed with the Run-Time engine.
11-22-2010 02:29 PM - edited 11-22-2010 02:34 PM
Please forgive me, I've not seen this way of setting up a local thread before. If I'm reading this correctly, you are opening an application reference to the current execuable. In which case, the probem is not TCP. The problem is in your build file. You need to add a Dynamic VI to your build file (what one, I'm not sure, the file name is being spit out by that RSE-10 block). If you don't, the vi will not be available to your executable so it cannot run it.
May I ask why you are doing it this way? Is it something that was made by someone else and that is how they said it is to be executed? If not, why not just make a subVI with a connector pane? It is much easier and uses less resources as it doesn't have to generate a new thread stack.
A
11-22-2010 03:10 PM
The problem is the VI server. I can do a command of 'telnet 127.0.0.1 3363' on my PC, but not on the target PC. When I close LabVIEW on my PC, the command fails, I think LabVIEW has to be open to use the VI server, it won't work with executables.
11-22-2010 03:30 PM
Are you trying to talk to another process? If not, remove the Open Application block from your diagram. The open VI block will open the VI that is local to the process.
If you are trying to talk to another process, let me know and we'll see if we can figure out something else.
A