11-07-2011 07:21 AM
Hello,
As we all know, it is possible to test multiple instances at the same time using one sequence file.
However, I do not want this, and want to disable this feature.
So only one test can be run at the same time.
Does anyone knows how to do this?
Thanks in advance,
Jeroen
11-07-2011 08:18 AM
Is this what you mean:
/useExisting
Instructs the application to use the existing running instance of the application instead of opening a new instance, as shown in the following example:
SeqEdit.exe /useExisting
11-07-2011 09:48 AM
I do not think so.
I will try to clarify:
In the sequence editor, you can press the start-test button, and a test will start.
When you press the start button again, it will start a second test, which runs next to the first test.
When you press the start button again, it will start another test etcetera
I do not want this, I want to be able to run only 1 test at the same time.
Is this clear enough?
But thanks for you reply anyway!
11-08-2011 03:00 PM
I have had this requirement before, using a LabVIEW user interface. To overcome the issue of operators starting multiple instances, I would disable the TestUUT's button. I used a post UI message call in the process model before pre uut and after post uut callbacks to notify the UI that a test was running. I think you could just put the postUIMessage in setup and cleanup of mainSequence and it would still work. Alternatively, use a StationGlobal boolean and check it is false at the start of the test before immediately setting it true. Set it back to false in cleanup. If it is true at the start of the test, then it must be running already, so abort. This second method is not ideal and it is asking for a race condition. I would be happy to hear of any alternative solutions...
All the best,
Michael.
11-08-2011 03:17 PM
I forgot to add:
I also replaced the pre and post UUT dialogues with LabVIEW dialogues so I could make them modal. A hidden pre uut dialogue was the main reason users would mistakenly start a new execution.
Michael.