ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

enabling of timeout in Open Application

I would like to control B.exe from A.exe through Open Application in the same computer (localhost).

I expect some delay time in A.exe to prepare B.exe for 60 sec (default timeout) but it took only a few seconds.

Under this situation, a user should take care of the sequence or timing of executing applications not to have a connection error.

 

I suspected to open the network port before executing Open Application but same result after clean booting of computer.

*)This problem was shown in LabVIEW environment, too.

 

How can I enable the timeout (60 sec)?

 

labmaster.

0 Kudos
Message 1 of 3
(1,208 Views)

Hi labmaster,

 


@labmaster wrote:

I expect some delay time in A.exe to prepare B.exe for 60 sec (default timeout) but it took only a few seconds.

 

How can I enable the timeout (60 sec)?


Why do you expect "some delay time in A.exe"?

Why do you expect a default timeout of 60s?

What exactly took only a few seconds?

Where did you set a timeout?

Why don't you show some (simplified) code example?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 3
(1,206 Views)

Thanks for your questions.

 

The error I met came from Open VI Reference.vi not Open Application.vi.

If I didn't prepare B.exe, why didn't Open Application.vi show an error? (useless setting of timeout)

and How to escape the error from Open VI Reference practically? I mean waiting for preparation of B.exe.

 

labmaster.

 

Why do you expect "some delay time in A.exe"?

-> Both applications should be launched to communicate each other. But there could be a delay for launching applications.

 

Why do you expect a default timeout of 60s?

-> The default value of timeout in Open Application is 60 s. The same eror even for inifinity timeout (-1).

 

What exactly took only a few seconds?

-> There was an error after a few seconds in executing Open Application.vi in A.exe (before launching B.exe).

In previous experience with TCP/IP communication, a code wait for timeout rightly.

 

Where did you set a timeout?

-> Timeout of open application.vi

 

Why don't you show some (simplified) code example?

-> see the attachment which a part of A.exe.

0 Kudos
Message 3 of 3
(1,158 Views)