Delay in running sequence file from user interface

[Adarsh]

Hi,

I have a TestStand sequence file which calls more than 60 different LabVIEW modules from 2 LabVIEW project files(Relative path method has been used to call modules). If I run this sequence file from TestStand, TestSTand is taking lesser than 5 secs to load and start executing the steps, but if run the same seq file from LabVIEW user interface its taking more than 2 minutes.

What could be the reason?

More Info:

TS version : 4.5.0.310

LabVIEW: 2010

In UI Run button has been bound to 'CommandKind_ExecutionEntryPoints_Set' with set point 2(Run UUT)

Run Environment: Development

Thank you

AP

[dug9000]

Are modules already preloaded in both cases (i.e. how long does it take the second time you run)? Is your LabVIEW UI also running in the development environment? Do you have multiple calls to the save VIs? What are your paths relative to? Do you have any custom search directories? Are these comparisons both on the same machine?

-Doug

[Adarsh]

Hi,

Thanks for the reply. Please find my answers in bold letters.

Are modules already preloaded in both cases (i.e. how long does it take the second time you run)?

No, They are not preloaded, but I can’t manually load the files. It takes less time in sec run.

 Is your LabVIEW UI also running in the development environment?

Yes.

 Do you have multiple calls to the save VIs?

Yes in some places

 What are your paths relative to?

Sequence file

 Do you have any custom search directories?

No.

Are these comparisons both on the same machine?

Yes.

Adarsh

[dug9000 · Accepted solution]

This is a known issue that occurs when both the UI and the code modules are running in with the same LabVIEW runtime engine, or both are running in the LabVIEW development environment, or the UI is running in the development environment and the VIs are running in the same version of LabVIEW's runtime engine as the development environment being used. There are a couple of things you can do that should help.

1) If you build your UI into an exe so that it is using the LabVIEW runtime engine and your code modules are using the LabVIEW development environment then this problem should go away and you should see speeds similar to the TestStand sequence editor. In this case the UI and the code module VIs are running in separate processes.

2) TestStand 2010 sp1 mitigates this issue somewhat for the case in which you load the same VIs mutiple times by caching the information it needs from labview rather than getting it again for each step which uses the VI. This will only make a significant difference if you have a signficant number of steps calling the same VIs.

Hope this helps,

-Doug

[Adarsh]

Hi.

Thanks for the reply.

Its working !!!!!

Thank you

AP