System exec.vi stops all execution!!!

[asc01001]

Hello!

Why does the system exec.vi stop all other execution?

I tried to FALSE the "wait until completion" input but then it can not open my .exe files. It just opens the CMD and writes out the path I declared for the .exe file? I can then run the VI normally.

If I have TRUE on "wait until completion" then the .exe file opens but everything else halts.

There is many topics of this issue but I could not find the solution. Any suggestions?

Why does it just display the CMD and not whole .exe file??

[Ray.R]

Hi asc01001,

Can you describe what you are trying to do?  This way we can better understand and provide more accurate suggestions.

The one question I would have is : "are you calling multiple instances of the SysExec vi?"

Also, can you tell us how long the executable is supposed to run and if it returns values, etc..

Thanks,

JLV

[asc01001]

Hi!

What I need to do is basicly to open an .exe program and just leave it there. This program would be a "story" for it self after calling.

I am developing an testsystem and for that I use many other programs like Ethereal, Unity, Ip2kprog, SerialMaster. Now I do not want to minimaze the Front Panel and Block Diagram and search for the icons of these programs every time I need one. What I did is to have a button on the FP of every of these programs and when I need them I just klick at the icon and they should opened and run like if I opened them via Start->Programs->Ubicom->Unity, for example.

So the program should be opened as longest I feel they are needed, and I want to close them when I want.

One example of executions would be:

I start program my processor with the IP2kprog so I click on the button and it starts fine, but then I want to listen on the Ethernet-traffic for this execution and I want to start the Ethereal program, BUT then the FP is blocked. This is why I have to open the programs and just leave them there as longest I want. They shuold not have anything more to do with LabVIEW after opening.

Hope this explains my situation better.

[Dennis_Knutson]

What exactly are you passing to the system exec function? To start a different program, all you should have to do is provide is the path and name of the exe in the command line input (i.e. c:\folder\junk.exe). If you do this and set wait until completion to false, the program should start and the LabVIEW program will not pause.

[asc01001]

Hi again!

I must have all inputs to the system exec.vi otherwise I got run-time error or my .exe files would´t execute.

I attached a file to this message, please change the paths to some .exe files on your computer and test if it gets stucked for you too.

Like I said, after opening the programs should not have anything more to do with LabVIEW, that is my purpose.

[Dennis_Knutson]

As I said, you just need to pass the path and name of the exe to the command line input. Do not wire cmd to it and do not wire the name of your exe to the standard input. In your example, have a string constant of ethereal.exe and set wait until completion to false.