LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

System Exec use all resources system if "wait until completion" is true !

Hello,

 

I use the function "System Exe" since a long time to launch various executables since Labview.

The " waint until completion " boolean is true, because I have to wait the end of the external executable to continue.

 

Big problem: the function " System Exec " use all resources system, by waiting for the end of the external program.

 

Is it a bug of this function ?

In my example, "System Exec" launches only the notepad (LV 8.2 on XP)

 

Thank you for your suggestions.

 

AC

 

 

AC
Download All
0 Kudos
Message 1 of 4
(3,106 Views)
That's a known issue that kind of has to do with the way Windows apps work. Use the "Run Application" VI from the lvwutil library. I think the "System Exec +" from that library will work just as well. The difference between the two is that the "Run Application" VI has a timeout.
Message 2 of 4
(3,078 Views)
The way you use System Exec.vi is wrong.  See attached VI.
LabVIEW takes 0% resources on my laptop when waiting for Notepad.
 
 
George Zou
 
George Zou
Message 3 of 4
(3,063 Views)

Thanks to both for your speed.

In fact I had simplified my vi to target the problem.

I use System Exec to launch another executable, made possibly with labview, but with passage of parameter. (Ex: - " / string:init ").

In the literature Labview it was made with the method cmd / x / c start by putting twice the path of the executable.

In this method a waiting time in the recent system exec function was effectively missing.

But effectively, today, it is enough: "c:\myexe.exe" - " / string.init " to launch and to pass a parameter.

 

You have both reason and I thank you sincérement.

Very cordially.

 

Sorry for my English....

 

AC

AC
Message 4 of 4
(3,046 Views)