Hide disabled executions in Teststand 4 Operator interface?

Hi:
I'm customizing the Teststand 4 Full Featured CVI Operator interface.
When running in the Batch model, we often run on less then the full number of test sockets indicated in our model options.
In this case, the unused test sockets show up as disabled executions in the operator interface.
Is it possible to hide the disabled executions?
Thanks,
Dave

Hi:
I was working on the batch model TileWindows changes in parallel and had noticed the tracing problem as well. The TileWindows subsequence from your BatchModel fixes this problem - thanks.
However, I'm able to reproduce a run time error through a sequence of (perhaps unlikely) events:
* start a test sequence with 4 test sockets using the batch model
* run the first socket, terminate in PreUUT, don't restart the first socket
(only the initial TestUUTs execution plus socket 0 will be visible in the operator interface, as expected)
* run the second socket, terminate in PreUUT, don't restart the second socket
(only the initial TestUUTs execution is visible in the operator interface)
* run the third socket, terminate in PreUUT: run time error popup:
Execution is already closed. Not found in list of executions
Operation Failed. [Error Code: -17500]
I'm assuming this has to do with the PreUUT call being before the TileWindows call. Suggestions on how to get around this error? Do I need to force all socket windows back open before the TileWindows call to catch this condition?
Thanks,
Dave

Similar Messages

Why do I not see a 'busy' indicator in the operator interface?

Hi all,
Ok, probably a stupid question, but here goes.
I can run my tests (mostly VIs) in the teststand LV operator interface without problem. In fact, they run quite well. The problem is, when the user initially hits the 'single pass' button to begin testing, there is about a 20-30 second delay before the actual VI front panel appears, ready for testing. During this time, there is no signal that the operator interface is doing anything. No hourglass, no indicator whatsoever. The problem is that several users have continued to click the 'single pass' button, which causes more than one instance of the VI to open, and slows the testing down, and confuses the operator.
When I play with the LV operator in
terface on MY pc (not the test pc) I DO see an hourglass when I press the 'single pass' button.
Does anyone know where it went on my test machine? The test machine is a Win98. I'm using TS v2.0.1 and LV v6.1
Not a big deal, but would be nice to fix another user complaint!
Thanks in advance,
Dave Neumann

Nick,
I'm using the shipped version of the operator interface -- I haven't made any alterations to it at all.
I compiled the test engine in Teststand and then used the setup.exe and .cab files to install it on the test machine. When I did the compile, I included the 'common vi' folder (where the busy indicator vi is located on my development machine).
Any other questions, let me know.
Thanks again for your help.
Dave

How to disable the run-time popup menu in the sequence display on TestStand Operator Interface, that allow the use to skip the test?

How to disable the run-time popup menu in the sequence display on TestStand Operator Interface, that allow the use to skip the test?

Hello,
Regarding the skip/force pass/force fail options, when I set the ControlExecFlow to True in Teststand 3.1 and 3.5, in the Sequence Editor the menu options for skip/force pass/force fail are not active for Technician but, when I launch the Operator Interface logged with Technician the options are active. The problem is that if the technician sets one step to one of these options, and change the user to Operator, the test step remains skip/force pass.
Is there any possibility without modifying the Operator Interface (at programming level), to reload default values of the steps when changing the user to Operator?
Thank you,
Best regards,
paio

How to externally trigger the execution of TestStand with a start and abort button through a digital interface?

Hello,
I'm Currently evaluating TestStand as an alternative for an in-house developed Test Sequencer.
To start our own Test Sequencer we use a small box, connected to a DIO board. The box has a start button and an abort button. The box also has a pass, a fail and a running led.
The interface with this box is made via some digital lines of a PCI-DIO-96.
In our own Test Sequencer we have groups named Init, Run, Abort, Exit.
The Init group is executed at startup (only once). It is used to initialize all the HW and SW. -> I guess this is the Pre UUT Loop callback in TestStand.
The Exit group is only executed once at the end of the day when the application is terminated. It is used to free all the used hardware and cleanup all the resources. This probably is the Post UUT Loop Callback in TS.
When a product needs to be tested, the operator presses the "start" button which triggers our own Test Sequencer and the run and abort group are being executed (first the run group, afterwards the abort group).
When the product is being tested the "running led" of the little box lights up to indicate to the operator that the application is running. (only when the run and abort group are running)
The Run group has all the functional tests in it. (MainSequence)
The abort group is used to put everything back in it's original state after the test on this single product is done. (Post UUT)
When executing the tests and something goes wrong (operator gets stuck in a clamper, ...) the operator can still press the abort button and then the execution immediately jumps from the currently executing step in the run group to the first step of the abort group. So, when something goes wrong, immediately the abort group is called.
At the end of the run and abort group, if no errors occured, the "pass led" lights up. If one or more steps went wrong the "fail" led lights up.
This setup can also be used to test multiple product in parallel. At that time all the different parallel testers have such a small box which contains a "start" and "abort" button and a pass, fail and running led. (it is possible that they are all connected to the same PCI-DIO-96 board. )
My question:
Is it possible to do something similar like this in Teststand? If yes, is there an example available that shows me how to do this in TestStand? (externally trigger the execution of TestStand)
Typically, in the Init group (Pre UUT Loop) the digital interface box gets initialised.
In the Close group (Post UUT Loop) the digital interface box is taken out of scope.
Note: The PCI-DIO-96 board to which the digital interface box is connected will also be used in the rest of the developed application (MainSequence, ...)
What's really important for me is that I can create a process model that all the application developers in our organisation can use. I really don't want any of the application developers (limited software experience) to mess around in all the features of TestStand.
For them it's important that they just add the function DigitalInterfaceBoxInit () in the Pre UUT Loop Callback and the DigitalInterfaceBoxClose () in the Post UUT Loop Callback, and then everything works!
It is important that the appliation developers do not have to create any global variables, other functions, synchronisations, parallel sequences, ... in TestStand. All this needs to be done with a simple call to the DigitalInterfaceBoxInit function.
Thanks in advance for all the help!
Best Regards,
Dennis Vanotterdijk
[email protected]

Dennis-
Your application sounds very well suited to TestStand's abilities. I am also quite impressed with your knowledge of how TestStand's architecture is arranged when you are still just considering whether or not to use it.
I think that TestStand would work really well for you in this application. Like you mentioned it will provide you with a form of standardization for your application developers to work from. It also provides the flexibility for you to add your custom routines in many different places. TestStand also makes parallel and batch testing much easier in TS 2.0 so that you could develop one test for your product and execute different instances of it in parallel to test multiple products at once.
As for your specific question about how to c
ontrol TestStand using a DIO board. I think this is very feasible and should not be too difficult. Since TestStand provides you the ability to create a custom operator interface your operator interface could monitor the status of your DIO board and launch/abort executions based on the read values. Usually the executions are launched/aborted when a button on the GUI is pressed however, I do not see any thing different about basing the action on a DI signal vs a mouse click. I am sure your application is more involved than this high level description but from the sounds of it I think it is very possible to do with TestStand.
Based on my experience of building test systems with TestStand and your description of the application, I would feel very confident in using TestStand to achieve all the goals you mentioned. If you have further detailed questions on how one of your features might be implemented, feel free to contact one of our Application Engineers or email us at www.ni.com/ask
and we would be glad to help you.
Best regards,
Richard McDonell
National Instruments

Is it possible to shutdown TestStand LabWindows/CVI operator interface programmatically?

Hi,
Like the title says, I'm trying to find a way to shutdown TestStand operator interface automatically after sequence execution is completed.
Any suggestion is appreciated, thanks in advance.

Thank you for your reply.
I did a loop but it wouldn't work :s
I managed to create an ActiveX button to exit test stand.
I found an example within the TestStand Course I and II.
static void ExitApplication(void)
VBOOL canExitNow;
TSUI_ApplicationMgrShutdown (AppManagerHandle, &errorInfo,&canExitNow);
if (canExitNow)
  QuitUserInterface(0);
// the ApplicationMgr control sends this event when it is ok to exit the application.
HRESULT CVICALLBACK ApplicationMgr_OnExitApplication(CAObjHandle caServerObjHandle, void *caCallbackData)
ExitApplication();
return S_OK;
void CreateTSEngineHandle ()
GetObjHandleFromActiveXCtrl (panelHandle, PANEL_APPLICATIONMGR,&AppManagerHandle);
GetObjHandleFromActiveXCtrl (panelHandle, PANEL_EXIT,    &AppExit   );
TSUI__ApplicationMgrEventsRegOnExitApplication (AppManagerHandle, ApplicationMgr_OnExitApplication, NULL, 1, NULL);
TSUI_ApplicationMgrConnectCommand (AppManagerHandle, &errorInfo, AppExit, TSUIConst_CommandKind_Exit, 0,
            TSUIConst_CommandConnection_NoOptions, NULL);
TSUI_ApplicationMgrGetEngine (AppManagerHandle, &errorInfo,&EngineHandle);
TSUI_ApplicationMgrStart     (AppManagerHandle, &errorInfo);
TS_EngineGetGlobals(EngineHandle,NULL,&Globals);
This way I click my QuitButton and it calls the the ActiveXExitButton witch calls the ExitApplication function.
The ApplicationMgr control sends ApplicationMgr_OnExitApplication event when it is ok to exit the application.
Hope this was clear enough and I hope this may be helpfull for someone else.
I apreaciate all the help.
Regards,
Daniel Coelho
Daniel Coelho
VISToolkit - http://www.vistoolkit.com - Your Real Virtual Instrument Solution
Controlar - Electronica Industrial e Sistemas, Lda

Split execution window in Operator Interface

Hi,
I'm using the NI Parallel Model to test 3 UUTs and I want to use the LV Operator Interface. How can I configure or modify the LV OI in order to see my 3 sockets in paralel while my sequence run?
Thanks,
Angel

Unfortunately I can not. I developed it in my last contract job, and while I did keep a copy for myself, it was written in LV 8.20. I currently don't have a copy of LV8.2 so I can't even view it (my current contract uses LV 7.0). Also, I don't feel comfortable distributing the OI without modification because it does have company info from that contract job that I would want to remove first.
However, I can answer as many questions that I have answers to. In fact, I have posted on this forum asking/answering questions about creating that OI that may also answer your questions.
I would suggest using the LV simple OI as a starting point if you haven't already. Then create a copy of the controls are passed into the subvi "Simple OI - Configure ExecutionView Manager.vi". Create anoter copy of the subvi and pass all controls to that subvi the same as the existing one. The should get you started with a second execution viewer.
One other think I found with the example OI's is that the controls that are already there don't seem be resizable for some reason. I think I ended up replacing them (all the controls are in the teststand pallette of labview).
Hope this helps in getting you started.
Paul

Remove step icons from CVI Operator Interface to improve execution performance

The CVI Operator Interface updates the icons for each step (lower right) when tracing is enabled. Can these be stopped but the steps still visable and would this improve execution performance.

Hi Dave,
I take it you are using the old style Teststand Operator Interface.
The only way would be to modify the code in the exedisp.c, in UpdateOnStepChange() function. Just comment out the SetCtrlBitmap() function there are two calls in this function.
As to whether it is going to make a noticable different in performance, well that depends on the spec of the controller (PC), graphics card etc. you are using. But you probably wouldn't notice any diference.
Before you make any changes, copy the sub-folders from the NI folder to the User folder and work from the User folder.
Regards
Ray FarmerMessage Edited by Ray Farmer on 05-07-2005 06:29 PM
Regards
Ray Farmer

Unable to include Operator Interface in TestStand deployment

Hello. I have created a test system using TestStand 3.5.
There is only one sequence file, and this sequence calls several VIs
that I have created in LabVIEW 8.0. I would like to distribute
this test system to a target computer, which will then run the default
Operator Interface. No bells and whistles, just plain and
simple. However, I'm running into problems.
First, I created a Workspace file in TestStand. I then added a
Project to it. In the Project, I added all necessary files for my
project (the sequence file as well as all of the custom VIs).
Then I proceeded to follow the TestStand reference manual in order to
deploy my system.
For reference, text in italics is the reference guide and text in bold is my comments.
Deploying the TestStand Engine
1. Launch the TestStand Deployment Utility by selecting Tools»Deploy
TestStand System from within the sequence editor.
I did this, and set up my build how I wanted it.
2. On the System Source tab, enable the Deploy Files in TestStand User
Directories option.
This option collects files from the <TestStand>\...\User
directories, so that any customizations that you have made to process
models, step types, language strings, and so on, will be distributed to
the target computer.
I did this, and copied my Operator Interfaces\NI folder to Operator
Interfaces\User. This would assure (I hope) that I would have the
default operator interfaces included in my project.
3. On the Installer Options tab, enable the Install TestStand Engine
option.
Done.
4. On the Installer Options tab, click Engine Options to launch the
TestStand Engine Options dialog box, which you use to select the
TestStand components that should be present in the installer.
Done. Everything is checked.
In the TestStand Engine Options dialog box, expand Operator
Interfaces»Full-Featured in the tree view.
a. Click the X next to LabWindows/CVI to include the
Full-Featured LabWindows/CVI Operator Interface in the engine
installation. The X should become a green checkmark.
b. Click OK to accept the new settings and close the dialog box.
This is where things go wrong. There is NO Operator Interfaces box in my tree view. It simply doesn't exist.
I've tried several different builds using different strategies.
I've done builds with the CVI operator interface in the User directory,
and I've also tried copying over the files manually. On the
target computer, I've always gotten either an error message (Could not
open the TestStand Engine), or else TestStand opens in evaluation
mode. In both cases, my custom VIs and sequence files are nowhere
to be seen. Can anyone shed some light on this? It's
driving me a bit crazy!
Thanks very much,
Brett Gildersleeve

Hi Brett,
Whenever you deploy your TestStand application to target machines, you will always needs a license. The licenses for distributing TestStand are different than for distributing LabVIEW and LabWindows/CVI code modules.
LabVIEW does not require you to purchase any run-time licenses for a deployment system. You can even run LabVIEW VIs in VI format (not executables) from TestStand without using the development environment and without an additional license.
In order to run LabWindows/CVI code modules, you will need the LabWindows/CVI Run-Time engine which is also available free of charge.
Regarding TestStand, you will need a license for each machine that runs a TestStand sequence. TestStand has three types of licenses which are the TestStand Development System License, the TestStand Debug Deployment Environment License, and the TestStand Base Deployment Engine License.
TestStand Development System License
The TestStand Development System License is required for any test sequence development and/or editing of existing TestStand sequence files that you perform within the TestStand Sequence Editor or programmatically using the TestStand API.
TestStand Debug Deployment Environment License
The TestStand Debug Deployment Environment License gives you maximum flexibility for deploying TestStand and LabVIEW, LabWindows/CVI, and Measurement Studio-based systems. This license allows you to install the development versions of TestStand, LabVIEW, LabWindows/CVI, and Measurement Studio, along with any corresponding add-on toolkits, so that you can debug your test application on your deployed test station. This license does not include the ability to perform any development tasks within the TestStand Sequence Editor or programmatically using the TestStand API.
The TestStand Debug Deployment Environment License has debugging capabilities including settings breakpoints, monitoring variable values, and stepping into test code directly from the TestStand sequence.
(Note: This license does not provide the software but rather gives you the right to install a previously purchased piece of software on the target machine.)
TestStand Base Deployment Engine License
The TestStand Base Deployment Engine License is the minimum license required for all deployed TestStand-based applications. This license allows you to deploy the TestStand Engine, a TestStand Operator Interface, and TestStand sequence files to the single test station for which the license is applicable.
The TestStand Base Deployment Engine License provides simple sequence debugging capabilities, including setting breakpoints and single stepping through test sequences in your Operator Interface. You cannot save sequences and open the sequence editor.
I hope this clears things up.
Best Regards,
Jonathan N.
National Instruments

Problem in Teststand Operator Interface

I am facing problems when i try to run my sequence file from TestStand Operator Interface for LabVIEW. It gives either all tests as failed or skipped but the same sequence file when i execute from TestStand Sequence Editor it gives me correct results. I am not able to figure out what is the problem?? Somebody worked with teststand operator interface please help me to solve the problem.
Regards
Subramania Bharathi.

Hi,
Which version of TestStand and LabVIEW are you using.
Are you using a Customised LabVIEW Operator Interface or are you using the default version?
If you can provide a example of your Test Sequence File to help identify your problem.
Regards
Ray Farmer
Regards
Ray Farmer

TestStand 4.0 Operator Interface Changes Not Seen

Hi guys,
Ive worked with TestStand before, but now im trying to modify the operator interface (located C:\Program Files\National Instruments\TestStand 4.0\UserInterfaces\NI\Simple\LabVIEW). Well, i try to modify the VI in the project, but i cant see my changes when i run the VI. Ive tried building the executable and see that hte executable does get rebuilt, but none of my changes show up.
Also, how does the "entrypoint 1" button get renamed to something else when the VI actually runs?
thanks
jeff

Looking at the help, it appears that the TestStand button only uses the system color unless it is in toolbar mode. If you want to use a LabVIEW button instead, you can implement the button action by calling <SequenceFileViewMgr>.GetCommand(...).Execute().
This thread might help you determine when to dim or enable the button: http://forums.ni.com/ni/board/message?board.id=330&message.id=15720
Here is the button help:
BackColor Property
Syntax
Button.BackColor
Data Type
Color
Purpose
Specifies the background color for the Button control.
Remarks
When you set Style to ButtonStyle_ToolBar, this setting applies to the face and border of the button. When you set Style to ButtonStyle_Standard, the button face adheres to the system settings, and this setting affects only the border of the button.
See Also
ButtonStyles
ForeColor
Style

How do I limit the number of Operator Interface and Execution instances to one?

We have a problem in MFG. The operator launches to instances of the operator interface and executes the same sequence. A second scenario is where the operator is executing the sequence and then changes from the execution window back to the Sequence Display window and launches a second execution window. We need to understand how to limit the number of executions within an instance of the Operator Interface to one. We also need to understand how to limit the number of instances of the Operator Interface to one.
Regards,
Steve Easthope

Steve,
This is a duplicate post. Please reference your first thread.
Derrick S.
Product Manager
NI DIAdem
National Instruments

Send UI meassages from teststand sequence to Simple CVI Operator Interface with Asynchronous Timer

Hello,
Is it possible and how is it possible to send UI meassages from a teststand sequence to the Simple CVI Operator Interface with Asynchronous Timer which could be downloaded from NI Hompage. I use this problems because it is more stable than the standard OIs
regards samuel

This post could help:
http://forums.ni.com/ni/board/message?board.id=330&message.id=7567
Regards.

Operator interface execution window is not getting activated-cant terminate,abort

Hi all,
I have sequence running in the operator interface which pops up a panel.It remains visible for some time and the value in a control of the panel is getting updated periodically .It is done using threads.After the panel pops up, until it goes off i am not able to operate with the controls in the operator interface execution window(terminate,abort,break).I changed the floating style of the panel as 'active when clicked on'.
Regards,
Radha R

Radhu,
Is this panel part of the Operator Interface or a dll function call from within your sequence. It sounds like its modal to the operator interface.
Regards
Ray Farmer
Regards
Ray Farmer

TestStand Error only when using Operator Interface

My testStand sequence runs correctly when I run it from the seqEditor, but when I run it from our Operator Interface (modified version of the simpleOI example), I get the following error,
"Error Message: Parameter 'Input Files': System Level Exception. [Error Code: -17502]
Input Files is a parameter of the LabView vi being called, and is an array of strings. The VI executes correctly even when called fromthe OI, but when it returns to TestStand (when called from the OI) the error occurs.
Thanks for any info and help on this. Also any info on why the simpleOI would cause an error would be appreciated too.

Hi Ray,
Here are some answers to your questions.
This VI that error's, is it part of the simpleOI or part of the Sequence File being run by the simpleOI?
---- The VI is part of a sequence file that is called by the OI.
If it is in a Sequence File, does this run in the default OI?
---- No, it's part of a new set of test sequences for our equipment.
What does the simpleIO do with the data contained in Input Files?
---- The data is just passed to another VI to load our input vectors.
What version's of TestStand and LabVIEW are you running.
---- I believe it's LV 8.5.1 and TestStand 4.0
What sort of modification have you done to the simpleOI example?
---- I think we only added our new sequences, a Operator info popup, and a few more buttons (Pass/Fail light, Change Op Info). And we removed some unused code to make it more simple.
Thanks again for your help.
Billy

How can I view TestStands Operator Interface front panel, from a VI, while a test is taking place.

I need to view the sequences and steps that are displayed during a test session while running TestStand. Except I would like to view this in a LabVIEW front panel

JD,
I'm not sure if you're asking to be able to view the actual code module's front panel (ie. VI front panel) while it's executing, or if you just want to see the steps and overall sequence in a VI front panel. If the latter is true then you can use the simple LabVIEW operator interface that ships with TestStand, as Dennis mentioned in his answer. This would indeed be a great place to start if you want to add any further functionality to the operator interface. If the former is true and you want to see the actual VI front panels of the steps as they execute, you can check that box "Show VI Front Panel" from the "Specify Module" window in TestStand.

Hide disabled executions in Teststand 4 Operator interface?

Similar Messages

Maybe you are looking for