TCP/IP Fail

[ylflex]

Hi, I would like to ask a related question. If the LabVIEW application is built into an executable. How does it maintain TCP/IP listen? How to run that exe through ethernet message? My setup is: a PC broadcasting some ethernet message and that message will launch the exe file on local PC to run my NI equipment (also connected to that PC). Thanks!

[rolfk]

TCP/IP has no way to launch any process when some data arrives in a certain port. You have to start the application somehow in another way and it then registers a listen connection and sits there waiting for incoming requests.

[Bob_Schor]

One situation where TCP/IP is important in LabVIEW is with LabVIEW Real-Time, where there is a Host (PC) and a remote Target running a LabVIEW-compatible Real-Time Operating System.  The general idea is that the Target is always "running", and is configured so that when it boots up, it automatically starts running the "Target" part of the Real-Time application.

When I've built such things, the first thing that the Target does is start "listening" for a Host to connect to it using TCP/IP.  My targets have fixed IPs, so the Host (whenever it want to) simply starts, tries to connect with a Target at the proper IP, and if the Target is running, it allows the connection and we are off and running.

Bob Schor