NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Running a test sequence without TestStand window

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

0 Kudos
Message 1 of 8
(5,723 Views)
Update: I've found the "Distributing a User Interface" in the manual. Looks like I can modify the labview "Simple OI" vi for what I need.
0 Kudos
Message 2 of 8
(5,720 Views)
The operator should be using a User Interface program and not the sequence editor. There are both Full-Featured and simple examples in several languages that you can modify in way you want. There is information on the user interfaces in chapter 9 of your TestStand Reference Manual. In case you have never read the manual (and why not?), it's accessable from Help>Guide to Documentation.
0 Kudos
Message 3 of 8
(5,719 Views)

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

0 Kudos
Message 4 of 8
(5,703 Views)

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?

0 Kudos
Message 5 of 8
(5,696 Views)

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.

0 Kudos
Message 6 of 8
(5,693 Views)

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

Josh W.
Certified TestStand Architect
Formerly blue
0 Kudos
Message 7 of 8
(5,689 Views)

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. 

Message Edited by paulmw on 07-22-2009 09:29 PM
0 Kudos
Message 8 of 8
(5,670 Views)