HiI wrote two vis that communicates through network streaming, They are working fine. I made an application (Build .exe) and try to run them as two stand alone applications. They can't allocates each other.Probably, the definition of the endpoint URL should be changed because of the building.Please advice.Gabi

Congratuations -- you have run into a very subtle point that NI has not adequately explained! The "formal" name of an endpoint is the following: ni.dex://host_name:context_name/endpoint_name. As NI explains somewhere, the protocol name, "ni.dex:", is not required. They also explain that, where the host_name is "localhost", it also isn't required. What is less clear is "What is the context_name?" This turns out to be the name of the application under which the particular endpoint is running. When you are running in Development mode, programming your application and testing it by pressing the Run Arrow, the application is "LabVIEW" (technically, it is "LabVIEW.exe", but the .exe is also not necessary). As this is the (undocumented) Default context_name, you don't need to put it in the string. However, when you build Executables, the context changes! To clarify, I built executables called "My Host" and "My Target" (mainly so there would be no mistake between the VI, "Host.vi", and the executable, "My Host.exe" instead of "Host.exe"). In Target.vi, I changed the Stream strings to start //localhost:My Target, and in Host.vi, I changed the specification for the Target URL to include ":My Target". Snippets showing these changes are included here. Incidentally, I could not get the Host and Target VIs you included in your ZIP file to work in Development mode, so I started over, taking the Host and Target VIs from my LabVIEW 2012 Examples directory, copying them to my LabVIEW folder in My Documents, and building a new Project. Note that, as written, this version of the code will work only as an Executable (since the context_name is no longer LabVIEW). If you want to write a routine that will work in both Development and Run-Time environments, you just need to examine some properties of the Application. I didn't think about doing this until I was already writing this note, which is why this code isn't in the earlier examples. However, it is probably better written as a sub-VI, as it should be used by both the Host and Target VIs. Good luck. Let us know if this fixes the problem for you. Bob Schor

LabVIEW

Network streaming - stand alone application

Solved!

You appear to have "hijacked" a thread from 2013. I suggest that you start a new Post, explaining what you want to do (be as clear about the "what" as you can), and also post your code showing what you have tried and explaining what didn't work. I'm fairly sure that the person who posted the Solution to this thread seven years ago considered this thread "finished", and won't be posting to it any further.

Bob Schor

Message 11 of 11

(1,994 Views)

LabVIEW

Network streaming - stand alone application

Re: Network streaming - stand alone application