Shutdown Teststand 3.1 Engine Hangs

[rschalken]

I am using TestStand 3.1 engine in combination with Labview 7.1. Everything works fine until I run a sequence file. After this run the logout/login and the shutdown do not work anymore. The complete engine hangs. When I look at the description of the shutdown method it says;

<QUOTE> Closes opened sequence files and executions. This method also releases the TestStand Engine. <UNQUOTE>

So this method should close all files and executions! Can anyone help me?

Message Edited by rschalken on 01-25-2006 02:30 AM

[RayFarmer]

Hi,

Is this in relation to an Operator Interface developered by your self? If it is does the default setup run ok?

Does the sequence file run and then logout/login and shutdown fails, or the sequence file doesn't run?

Dont really understand your quote and what is it a quote from.

Regards

Ray Farmer

[rschalken]

It is a operator interface developped by myself with the start of the NI examples! When using the operator interfaces of NI I got the same problems! The sequence run works fine! Everything works fine only the login/logout and exit does not work (this because they both use the shutdown method). The quote is from teststand help file! I added this quote because I found a article at the NI site; "shutting down the Engine". This article says that I have to close executions and sequence files, but Teststand help file says that the shutdown method does this automatically! That is why I added.

[RayFarmer]

Hi,

Thats for the clarifications.

Are you using all the default process models, engine callback, frontend (login/logout sequence) sequencefiles?

Do you get the same problems if you use the SeqEditor.

Which language are you using, LabVIEW/CVI/C++.......and version.

Regards

Ray Farmer

[rschalken]

I use Labview 7.1 and I use an adapted process model. But I only changed some result handling. The Sequence editor works fine. As I said that the examples user interfaces of NI has the same problems! These also hang after running a sequence!

[RayFarmer]

Hi,

Have you tried switching back to the default process model and ensuring the everything is still working.

Regards

Ray Farmer

Message Edited by Ray Farmer on 01-25-2006 10:18 AM