Well, if you have LabVIEW 8, you can use the shared variable to pass data from one exe to another. You can also use ActiveX. There are the methods Get Control Value[Variant] and Set Control Value[Variant]. There are other ways such as TCP/IP, Datasocket, reading/writing to shared files, etc.
Also, why does it have to be LabVIEW exe files? You can do it but keeping them as VIs makes some of the options a bit simpler.
Well, I don't have LV8. May be I can try out ActiveX/Variant. Would be helpful if you post any link or code demonstrating the same. No issue to use only lv instead of lv exe.
Already achieved it thru sharing files, but I want it in a different way. Datasocket/TCP/IP examples were tried, I took the server-client example, and configured in TS. but once opened, step one (server appln) is not returning so unable to execute step two (client appln).
that brings me to this version: If I have two exe running and both call with vi-server the same (LV2-Global) vi you should be able to share information. Without race conditions
Here is a very simple example that uses the methods I mentioned for a second VI to get/set values from another. I haven't really done much tan a small experiment, but you can also invoke the methods in TestStand with the ActiveX Automation Adapter. You can search the forum for examples of this.
If your first VI is not returning, then you haven't called it correctly. One way do it is to put it in it's own sequence and in TestStand, when you deine the sequence call, have it run in a new thread.
The example is working fine as long as it is run on labview. But now the problem is if I convert both (first and second vi) to a .exe, then they are not passing data between each other. Can you tell me if that is possible or not? or am I doing something wrong. The reason that I want to convert it into .exe is I do not have labview installed on the client machine. It only has the runtime installed.
If you are using the runtime engine or activeX system on you target sysem, then they still should work.
What are you using on the target system for you labview steps?
Right now, I am trying to execute both the VIs on my machine only. The only thing that is changed is that both the VIs are converted to .exe files.
A small doubt, will the path given in the second vi make any difference. As such, I m assigning the path of first VI in the second.
The paths have to be spot on, dont forget when an exe the path of the vi will be ...\someexe.exe\myVI.vi, therefore you will have to allow for this.