operator interface

[OmarGator]

I am wishing to create a simple simple Operator Interface.

How do you call an entry point like “Test UUTs” without having to click an activeX button that has been linked to the start testing command.

Or force an exit or logoff or close a seq file without having to click a button.

We have an opening screen which displays in a tree control the seq files that the operator may load and run. These are the only seq files that they may run from this simple simple Operator Interface.

We want the Operator Interface to go straight from this screen right to the UUT loop to the Identify UUT popup and entering the UUT serial number. Bypassing having to click on a Test UUT button.

Then when the operator exits the UUT loop, it returns straight back to the opening select UUT screen where they may select a new seq file or the same or exit the program all together.

Can’t see to find how to call the entry point without the use of activeX buttons.

Jim D.

[James_Grey]

Test UUTS:

applicationMgr.GetCommand(CommandKind_ExecutionEntryPoints_Set, 0).Execute(true);

Single Pass:

applicationMgr.GetCommand(CommandKind_ExecutionEntryPoints_Set, 1).Execute(true);

You can use GetCommand and Execute to do anything a button or menu item does. Look at the ConnectCommand calls in the sample UI source code to see which CommandKind enumeration value is tied to a particular button.

Message Edited by James Grey on 09-17-2007 05:04 PM

[Joe_H]

I think what he is asking is the same thing that I am looking for. How do you get a regular control (LabVIEW) to run teststand commands without using the Active X controls supplied with teststand. Can this be done. I would love to have this functionality because themn I could tell if the button has been hit and start and stop things upon the hit without having to use callbacks and all types of other ActiveX stuff.

[Joe_H]

When I try to do it your way with a regular control it always throws an error no matter what I do.

[dowNow]

This is an advanced programming task. I can't really tell you how to do it here, applicationMgr.GetCommand is the way, but here's some context.

> How do you get a regular control (LabVIEW) to run teststand commands
> without using the Active X controls supplied with teststand.

I think the usual way, click a button in LabVIEW then call a subvi that does something. In this case the subvi will make some TestStand api calls.

> without having to use callbacks and all types of other ActiveX stuff... it always throws an error no matter what I do.

The TestStand api is nothing but ActiveX stuff and callbacks. ** Call tech support if you are getting errors and they will be happy to get you going. ** You'll have to take a couple days to learn about it, but it shouldn't be that hard. The TestStand II class has good Operator Interface examples. I would definitely not try to write one from scratch, find an example to modify, start with something simple and work up to the tree view thingie. There's a few that ship with TestStand, there might be others on the dev zone. It's kind of wierd how it all works but the advantage is it is scalable and though it takes awhile to get started it saves ** lots of time ** down the road.

Whatever you do, don't put a lot of code into your LabVIEW operator interface. The interface should be really thin and only used to start and stop executions and view the progress and status. For example don't ever put GPIB commands or any instrument or test fixture communication into the Operator Interface. That stuff should all be in your sequences.

[James M]

Hi Joe,

What error does it throw?

Regards,

[Joe_H]

Upon talking with tech support, we realized that you cannot use the CommandKind_ExecutionEntryPoints_Set with the applications manager control. You must use the sequence file view manager for this. If you look in the context help for teststand under command kind you will see a list that tells which command connects to which control.

thanks for the help

[James_Grey]

Sorry about that. I rushed that answer out too fast. I need to take my own advice and copy directly from the example UIs.