TestStand Full Featured Labview OI - Documentation?

[aaronb]

Can anyone point me to any documentation/examples out there for the TestStand Full-Featured Labview OI? I have tried looking just about everywhere and can't seem to find any good documentation/explainers on how the OI works and how to customize it. I am new to TestStand OIs and am trying to create an OI that allows me to run up to 6 different UUTs independently at the same time. I can't figure out how to wire in each individual Execution Entry point and am looking for examples and/or documentation. I also need some help with Progress bars and test status indicator LEDs.     

[aaronb]

Below is an example front panel of what I am trying to accomplish. Most of the controls are not connected of course :-). I am trying to have one window with 6 different executions shown within it. Each execution would be seperate from one another and you would be able to view each just by clicking on the tab for that particular test fixture. The only thing that would be common is that each execution would be running the same sequence file. The individual test fixtures could be at different points in the test sequence and could have different start and stop times for each. For instance....test fixture #1 could be loaded with a UUT and started into test then while it is running test fixture #5 could be loaded with a UUT and started into test. In the meantime when test fixture #1 has finished testing I could load another UUT into test fixture #1 while test fixture #5 is still running. etc etc

[MatLaroche]

You might want to look at Chapter 9 of the TestStand Reference Manual.

C:\Program Files\National Instruments\TestStand 4.2\Doc\Manuals\

Otherwise, I'm mostly searching in the NI TestStand Help when I'm using the API.

For progress bar, I think this one is an example:

C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.2\Examples\DisplayingProgressAndStatus\UsingLabVIEW

I would recommend starting with the simple OI, not the full-featured.

You don't need all those features if you don't plan to edit and develop sequences in your OI.

It's also easier to understand and to customize to your needs.

For the parallelism, you can look at the ParallelProcessModel.seq to give you an idea, but usually from experience, you end up doing 6 "Test UUT" entry points that are launched individually by an event (ex: a click) from the OI.

Good luck.

-Mat

[MatLaroche]

I just saw your picture. Definitely stay away from the full-featured...! Take a look at the simple, you are actually doing 6 simple in one...

So you want to actually launch the seq with the entry point when the click event happens on the button.

Get your process, get your sequence file, Engine.NewExecution and link the execution to the good executionViewMgr (you should have 6 executionViewMgr, one for each uut). Only one applicationMgr though!

Connect the sequenceView to ExecutionViewMgr to see the execution, do the same for the reportView.

When this part will work, you'll have to use UIMessages between your sequence or process model AND the OI. This way, for example, you can light the green LED for a pass (after MainSequence call back in process model, etc.).

-Mat

[MatLaroche]

I'm assuming the UUTs are independant (with test hardware for example).

[aaronb]

Mat - yes the test fixture hardware is independant except for the PC obviously.