Call Executable - Close command prompt

[OnlyOne]

Hello,

i am running the Call Executable step that executes a batch file.

In the batch file another exe file is called.

Now the question is: How can i close the appearing cmd window (which contains the batch-file command) so that the teststand-sequence can contine?

Currently teststand is waiting at the call executable that the called program is returning.

I tried the option "Wait for exit = No Wait" but this does not help.

Thx

[SercoSteveB]

Strange, even pausing with the No Wait set!!  Are you able to post more information?

[OnlyOne]

You can reproduce this by creating a batch file and write the text "notepad" inside.

When running this file then Notepad is started and the command-window is opened until you close the notepad window.

This happens also identical if you run the batch-file direct from the windows-explorer.

Is there any way that this does not happen?

Thx

[SercoSteveB]

Way ahead of you dude.  I did some testing before my previous post (I don't use the Call Executable step very often).  I created an EXE (in LabVIEW) and a Batch File that calls my LV EXE.  Created a TestStand sequence with a Call Executable step that calls my batch file.  I tried it with "Wait" and "No Wait" and I am not seeing the behaviour that you are describing which is strange. 

[OnlyOne]

Can you test what happens with "notepad" in your batch-file?

Is your lv-exe also still running and CallExecutabel can continue? strange

[SercoSteveB]

The CMD Window opens, running the Batch file, and Notepad is launched.  When I manually close Notepad, it closes following by the CMD Window. 

If I set the Call Executable step To "Wait for Exit"  TestStand pauses at the Call Executable step until I close Notepad (and the CMD Window has closed). 

If I set the Call Executable step To "No Wait"  TestStand does not pause at the Call Executable step.

[OnlyOne]

Ok, my fault. Its working here too.

I thought that the command-window whould be closed when setting to "No Wait"....

But it works as it should when changing the Wait-option.

[SercoSteveB]

Cool. I guess your EXE is not returning?