call exe issue running with F5

[logatto]

Hi, I am developing a functional test mixed with Goepel Boudary Scan. To run boundary scan test I use the "Call Executable" steps. They calI different batch files. The batch files contain the command to send in order to execute the test.

When I run the batch file making a double click it goes immediately. When I am in TS editor, I select all the sequence steps and press "Run Selected Steps" (then it runs  the "Call Executable" steps --> batch files) they goes immediadely.

On teh same sequence when I run the test pressing F5 (RunTest) the call executable steps have some problem. I can see the shell DOS immediately but I have to wait more than 20sec before the command is executed. An this is repeated for all the call executable steps.

Setting a break point just after the call executable steps (at the end of the 20sec), if I run the batch file making a double click it goes immediately.

I also tried to use a Labview action insted of the "Call Executable" steps. The vi called the System Exec.vi function. But the results was exacly the same. Running tests from "Run Selected Step" everything worked fine, running from F5 each step took more than 20sec.

I also increase the RAM from 1G to 2G, but nothing.

Do you have any suggestion?

Thanks a lot. 

[asbo]

Do you see high CPU or memory load during the 20 second hang?

[logatto]

Yes, I checked.

During the 20sec hang the CPU usage goes to 0 and the Memory usage remain constant to 600M.

It does not seem to be an HW matter. As I tald you, if I set a break point and run the batch file making a double click it goes immediately.

What I noticed is that after I run the test pressing F5, also the "Run selected Steps" takes more than 20sec for each call. I have to close TestStand for working again the "Run selected Steps".

I attached an extract of the test sequence and an example af batch file. The Call exe step is inside SingleStep subsequence.

Thanks a lot.