TestStand execution is slow after deployment.

[Winther]

Hi.
We have created a TestStand sequence using mainly labview vi code modules. The test sequence is complete and is running as it should in the sequence editor.
After I used the Deploument Tool to build an image which could be moved a production PC, something went wrong. The test sequence will still start and it seems to run fine, but the execution is extremely slow!
It doesn''t matter if I run on the production PC or on my computer (where the sequence was created). I can run the sequence from the development location, and everything is ok, I then close the sequence and load it from the location created by the Deployment Tool and it runs slowly...
It is not because the tracing speed is set to slow, and it seems to be the vi''s themselves that are executing slowly. Almost as if the "Highlight Execution" is on.

Any idea what is going on...?

Best regards
Stephan.

[Winther]

After more testing it seems that the problem starts, when the sequence reaches steps that uses GPIB and COM port communication.

But why is it only after deployment that these steps slow down...

What happens during deployment other that copying files and updating links?

[Anand_Jain]

Winther,

I have a couple of questions to help figure out what is happening

• What versions of TS and LV are you using?
• On your development machine, are you executing the test sequence from the deployable image folder, using LV's development system or the LV Runtime Engine?
• On your production PC, are you executing the test sequence using LV's development system or LV Runtime Engine?
• Are you able to reproduce this issue in a simple case?

Regards

Anand Jain

National Instruments

[Winther · Accepted solution]

Hello Anand and thanks for your reply.

I just found the answer to my problem yesterday.

We have a vi event logger that is used during development/debug and it is supposed to be disabled afetr the build - it was not.

The logging function uses a VI server wich it could not find after the build and then timed out repeatedly - causing the slowdown.