07-22-2009 11:58 AM
Hi all,
This seems like a simple question but I can't seem to find any information on it. Is it possible to run my test sequence file without opening up TestStand and clicking "Run" in the debug toolbar? The TestStand window and all of its options are too overwhelming for the end user (Test Operator). It would be great if I could just call the test sequence so that it runs through my popups and Labview interfaces without the TestStand window.
It seems the Deployment option is simply for copying the environment to another computer. Is there a way to run tests without the TestStand window, or any other way to simplify the GUI without just closing tabs of the UI Configuration?
Many thanks!
Chris
07-22-2009 12:49 PM
07-22-2009 12:51 PM
07-22-2009 01:45 PM
Thank you for the response, Dennis.
One crucial limitation of the Full-featured and Simple OIs is that the user needs to be able to change FileGlobals and save the test as a new sequence file. There will be multiple types of the UUT and each will need its own test file with configurable parameters. That is why the Sequence Editor seemed like the best solution.
Is there a way to save new sequences using these OIs in order to expand the number of UUT models the test will support?
Thanks again,
Chris
07-22-2009 02:50 PM
I shudder to think about giving any of my operators the ability to modify a single thing.
Maybe you could write a program that is accessed from the Tools menu?
07-22-2009 03:04 PM
Just to make sure you realize this, the TestStand Full UI examples (as of 3.5 or 4.0, I forget), can function in operate-mode or editor-mode.
You can put one in editor mode by passing a /editor command line argument or setting ApplicationMgr.IsEditor to True.
By default, you can also toggle between editor and operate mode by hitting ctrl-shift-alt-insert. Note that it doesn't make sense to put a simple UI example in editor mode since there aren't any editing controls. Editor mode requires the presence of a sequence editor license.
07-22-2009 04:11 PM
One other thing that you might find helpful is that all the TestStand UIs, and the Sequence Editor (since 4.0) accept command line arguments. That means that you can create a shortcut and include extra command line arguments that will automatically start a sequence running. Note that this will still show the window, so it may not be perfect for your needs, but I thought I'd mention it as an alternative.
Accepted Command Line Arguments
07-22-2009 09:28 PM - edited 07-22-2009 09:29 PM
Tomahawk1277 wrote:"the user needs to be able to change FileGlobals and save the test as a new sequence file. There will be multiple types of the UUT and each will need its own test file with configurable parameters. "
I am guessing here, but in your particular use case but I would hope that the operations described above are repetitive and require modifying the same fields each time following some procedure (written or tribal-knowledge). If that is so, you could create an automated sequence file generator that would load the existing sequece file as a "template" and it would modify the values entered in by the operator via popups and such. That new sequence file could then be saved and executed to test the device. Both of these, the generator and the actual test sequence, can be run in the same "Simple OI" with out the need of all the editor capabilities.
Check out the "Sequence Builder Tools" example provided with TestStand to get an understand of how this would work.