Execution of TestStand-Sequence in LabVIEW via TS-API: Different Execution times for same sequence

[TobiKi]

The behavior does not occur if I'm using a compilated User Interface (.exe).

I try to explain it a little bit more detailled with the former mentioned NI-example (https://decibel.ni.com/content/docs/DOC-38982), so we have a reasonable base for our discussion.

If I download and compile the former mentioned NI-example the sequence is executed as expected. There are no time-deviations between two consecutive executions of the same sequence. So far everythings okay.

My problem occurs if I use the uncompiled Top-Level-VI included in the respective Project file. In case I stop the execution of the VI between two executions of the same sequence, I get the described timing deviation. (The VI is still opened in LabVIEW between the two executions.)

Because my intention is to implement a VI that opens and executes a sequence file autonomous, the second described application seems to be more interesting for me.

And I wonder why the uncompiled version of this application behaves different to the resulting executable?

Regards

TobiKi

[TobiKi · Accepted solution]

I have solved my problem and want to share my results on this forum. Maybe someone has useful comments on how to optimize or improve my VI, especially the error handling.

The VI is based on the example obtained via the following link:

https://decibel.ni.com/content/docs/DOC-34171

The attached VI "ExecuteSinglePassTest" can be used to start a "Single Pass"-Test of a TestStand-Sequence. The inputs are the Name of the Sequence ("Sequenz-Name") and the respective folder ("Sequenz Dateien Verzeichnis"). During my tests the former observed behavior (longer execution time) did not occur anymore.

Thanks to "Norbert_B" for his helpful efforts! 🙂

[LV_user1]

Hi

Can some one please convert it to 2012 ? I want to refer the code.