LabVIEW Simple operator interface deployment

Hi All,
I try to deploy a TS 3.1 application with a LV 7.1 Simple OI. I successfully (no errors) built the OI executable and created an installer with default options. I also built the Deploy TestStand System and created an installer with default options, except I selected only User Interface->Simple->Labview (no development system). I installed them on the target machine without any problem. The problem appeared when I ran the OI; it reported "Error 97 occured at Unknown System Error in TestStand-Set TestStand Application Window.vi->Simple OI-Top-LevelVI.vi. Possible reasons: Labview: Null Refnum was passed in as input".
I beleive this happened because the "Application Manager", "SequenceFileView Manager" and "ExecutionView Ma
nager" ActiveX Controls, which were required by the OI, were not present on the target PC.
Obviously, TestStand Deploy did not distribute them.
Does anybody know how to distribute these ActiveX controls or have a successful experience of distributing the LabVIEW Interface?
Thanks.

PPascal,
We've seen this error before, and it usually fixed by a simple reinstall. You could also possibly just run a repair on the TestStand engine within add/remove programs and this should also fix the problem. Please try this and post back if this does not fix the problem for some reason. Thanks and have a good one.
Adam B.
Applications Engineer
National Instruments

Similar Messages

Clear report in report window of simple operator interface

Hello,
hello I want to clear the report-window of the simple operator interface at the beginning of each UUT test.
I want that there is nothing inside this window while testing a UUT. Only at the end of a test I want to show the actual report
How is this possible?
regards samuel

Report.Reset should replace the current report data with the data in the string you specify, which in your case should be blank.
Do you have a PreUUT Sequence in your Client Sequence File?
If not try adding the first step in the attached sequence below the Report.Reset step in your PreUUT sequence. You may need to add the second step as well (below both new steps). Not sure if the second step is required. The first step tells the teststand engine that the report has changed, the second tells it to refresh all windows.
Regards
Steve
There are 10 types of people in the world that understand binary, those that do and those that don't.
Attachments:
UI Update.seq ‏18 KB

Programatically Loading Several Sequences Using LV Simple Operator Interface

I am playing around with the supplied LV(2009) Simple Operator Interface for running TestStand (4.2) and hoping that someone can point me in the right direction.  I know this may be too generic for a concise solution, but hopefully I can get some suggestions on the best approach for this. Here is a short description of what I am trying to accomplish.
I am testing 2 unique UUTs on a single test fixture that is controlled by a PCI-7831R DAQ. Each UUT will have a unique serial number and report generated. Therefore, I am using 2 unique sequence files created using TestStand. Basically, I want to be able to read in a barcode on the test fixture and have the operator interface load the 2 unique sequence files based on information contained in the barcode. The operator will then hit a button to start the sequence file executions.  I want the first sequence file to run and test the first UUT. Once the first sequence file is finished, I want the second sequence file to load and run on the second UUT.
I can use the simple operator interface to load both sequence files. I then have to select the combo box to select which one I want to run. This works fine, however, I am trying to automate this so that the operator doesn't have to open the files and continually use the combo box to select sequence files.
Any ideas or suggestions would be greatly appreciated.

I have figured out a solution (for my initial application at least) of programmatically loading the sequence files. When the operator interface first starts, there is a prompt where the user will scan a barcode that is loaded on the front of the fixture. For all of our product lines, we will have a unique format for the fixture barcode. Included in this barcode is a product specific software ID number. I create a folder with the same software ID number and store the sequence files there. I then parse the barcode and open all *.seq files in that folder. I have this working correctly now.
Once the sequence files are opened, the user must scan each UUT ID barcode before installing them on the fixture. The intent is to have both UUTs installed on the fixture at the same time so they can be tested serially.  If, however, they do not scan one of the UUTs, it will not be tested. Basically this is due to the fact that they may want to run only a single board. Once all of the UUT barcode scanning has been completed, I have another button that will execute the sequence files using the 'Single Pass' execution entry point. I agree that the 'Single Pass' and 'Test UUTs' points should be hidden from the user. Once the execute test(s) button is pressed, it will check each UUT barcode to make sure that it is valid. If both UUT's have valid barcodes, it will run the first UUT and then the second using the 2 sequence files that were previously loaded, otherwise, it will run only one or the other. The UUT(s) will then be removed and the process starts over again from the UUT ID barcode scanning. They will not have to scan the fixture barcode again since the correct sequence files have already been loaded.
Currently I have the UUT/Sequence File associations hard-coded in the UI. I will need to put my thinking cap on so that as we increase the product lines (several are already in the pipeline) we can use the same UI without any modifications. Scalability is King!

Labview Simple User Interface

I would like to know how to add a simple LED indicator in the TestStand Labview Simple User Interface that would display the Sequence Status( PASSED or FAILED ) ?
I'm using TestStand 3.1.
Thanks a lot
Olivier

Hi Olivier,
There are several ways to implement this.
The quick and easy method would be to read the ItemText from the Executions ComboBox control. Then scan it to see if it contains "Passed".
(see attached VI)
An alternative is to setup a TestStand UI Label Control, Using the ExecutionViewManager you can set a CaptionSource to the UUTStatus. This will then contain the UUTStatus of the currently selected execution. This is similar to above except the string will only contain the UUTStatus string, not all of the details in the execution string.
However a "more complete" method would be to setup a Callback VI for UIMessages, when the UIMsg_ModelState_TestingComplete is recieved, the UUT status can be retrived. (Refer to the TestStand Help file)
The callback (assuming it has a reference to the LED) can then set the value of it.
This method is prefered over the above 2 because you do not need to poll the TestStand controls to get the status information. When the TestingComplete event occurs, TestStand will execute the Callback VI.
I hope this helps.
Simon Holman
Software Engineer
Certified LabVIEW Developer
Certified TestStand Developer
measX GmbH & Co. KG.
http://www.measx.com
Attachments:
Simple OI - Top-Level VI (Quick).vi ‏191 KB

Simple Operator Interface hungs up while executing a testsequence

Hello,
My operator interface hungs up sometimes while executing a testsequence.
It hungs up every time after the PostUUT has passed
The attached error description is available
can anybody help me
regards samuel
Attachments:
errors1.rtf ‏2566 KB

Ray,
I have created my own PreUUT.
In this PreUUT I call the dll for the PopUp windows to enter serial numbers and to select specified UUTs etc...
Yes I have tried to single step through the sequence but then the Problem doesn't occure. (I run it than in the Teststand developer environment) The problem only occures when I use my modified Operator Interface on the second computer. (on my first computer it works without problems)
My suspicion is that my modified simple operator interface makes the problem
what can be the problem? what dlls does the simple operator interface use? Is it possible that on my second computer some standard teststand or Lab Windows CVI dlls are not up to date?
regards samuel

Including Limits, Measurements in Simple Operator Interface UI

Dear Experts,
I am in the process of modifying OPerator Interface such at that it must also display Low Limit,High Limits,Measured Value, Units. I am sure that it is possible only through expressions. I want this Limit columns value to be updated during runtime i.e., it must display the same value as we use to enter using Edit limits for Numeric test, Measured value should be the value in Step.Result.Numeric or Step.Result.NumericArrya.
I could just manage to create a parameters in each Sequence & Subsequence Parameters.Limits.Low, Parameters.Limits.High,,Parameters.Limits.Unit & just hard code the values in these. But for Parameters.Measurements i could get values in runtime using RunState.Sequence.Parameters.Measurement. I know this is not more efficient way. This might work only for Action, Numeric Limit.
For reference i have attached Simple OI Top Level.vi(where i have made some modifications) all other supporting files you can find in TestExec.llb. I hope i have explained my problem. If anyone find any confusions in understanding please let me know.
If someone tried this before please share your knowldege. Expecting your greatest support.
regards,
Bharat
Attachments:
Simple OI - Top-Level VI.vi ‏177 KB

Hello Bharat,
Adam is out of town right now. It looks like the error you are getting is occurring because you do not have the TestStand 3.0 UI controls installed for LabVIEW. You can check this by making sure that you have a TestStand subpalette in both your Control Palette and Function Palette. If you do not, you can go to "Start >> Settings >> Control Panel >> Add/Remove Program". Find the entry "National Instruments Software" and click "change". Find "TestStand 3.0" in the list of NI software installed on your computer. Click on "modify". This will launch the installer. Follow the steps and make sure to enable support for LabVIEW 7.0 (there is a step with a tree of features that you choose to install).
I took the liberty of saving the latest VI that was posted to my computer. I opened it with LabVIEW 7.0. This was verified by going to the "About" LabVIEW Dialog box that displays the version. I was running on the TestStand 3.0 engine. Besides the fact that you can only have one engine active on a computer at a time, I added a message popup to my TestStand 3.0 Front End Callback so that it would display when an instance of the engine is created. I did save the VI again and am not attaching it to this post. It should certainly work with LabVIEW 7.0 and TestStand 3.0 if everything is installed correctly.
Thank you for contacting National Instruments. Take care and good luck!
Regards,
Aaron B.
National Instruments
Attachments:
Simple OI - Top-Level VI.vi ‏177 KB

Updating system time with simple operator interface

Hello,
I need to update system time on the simple OI but when I use "Get system time and date.vi". The indicator on the front panel doesn't get updated every second, there is delay of atleast 5 secs. I tried using parallel while Loop method as well but still the problem persist
Any ideas guys?
Regards
Prav
Solved!
Go to Solution.

See attached simple OI modified to display time and date. When I run It, the update on indicator is like this 16:21:04-->16:21:09 (delay of 5 secs).I tried in time out event as well but no sucesss.
Attachments:
example.vi ‏69 KB

Error Loading a VI of a sequence in operator interface (Error Code -18002)

I am deploying a teststand sequence using LabVIEW adapter. After deploying, while running this sequence in operator interface in the deployment computer, I get an error saying that a particular step could not be loaded. This step calls a DIO initialization VI which basically uses DIO Port Config.vi from Traditional DAQ 7.4.4 version. Please see the attached image.
Software Versions Used: Teststand 4.0.1f1, LabVIEW 8.5, Traditional DAQ 7.4.4, Simple OI shipped with Teststand, windows XP
From couple of links from www.ni.com, I did following actions in my development computer:
1. Compile All the VI in LV 8.5 using Mass Compile including Traditional DAQ LLBs, simple operator interface etc.
2. Check if any VI or step is not broken.
After getting the error, I tried opening the same sequence in sequence editor in deployment computer (I am also including sequence editor with the deployment utility), I checked DIO Initialization step. I see the warning in step indicating that the VI is either broken or one of its sub is not located. I tried using Reload VI Prototype, it asks for LVDAQ.dll which is also bundled in my deployment files. After specifying this dll, I can run this sequence without errors but after I exit from sequence editor, it does not save the changes and I get the same error in Operator interface as well in sequence editor after re launching. Also I dont want to reload VI prototype as I dont expect some to do this change after deploying the testsequence.
Kindly help.
Thanks in advance.
Nirmal
Attachments:
Auto_Cal_18002 Error11.JPG ‏25 KB

I found solution for this. While creating the workspace for my sequence and other files, I used to include all the files including the LabVIEW VIs. Doing this, DIO Config VI seemed getting confused while searching for LVDAQ.DLL in the deployment computer.
I tried only including the test sequence and letting the teststand deployment utility select the VIs from the specified directory resolved this issue. I observed that in this case, all the sub vi and the support dlls gets placed in the support and data folder respectively. This resolved the issue.
Regards,
Nirmal

Sequence file path programmed in operator interface

Hello,
I do not want to load the sequence file with the button OPEN_FILE etc.. for example how it is done in th Simple Operator Interface. I want to programm the path and the sequence file name in the Operator Interface. How can I do this that the correct file will be loaded
regards
samuel

I try to explain what you have to do without an example, because it is realy simple, and so we have no version dependency ;-)
I used the "simple operator interface" installed with TestStand (..\National Instruments\TestStand 3.x\Operator\Interfaces\NI\Simple\LabVIEW\TestExec.llb\Simple OI - Top-Level.vi). I added the method mentioned above in front of the Event-Structure (See attached picture) and added a path-constant, to define which Sequence should be loaded automatically.
Try this out. It works fine on my machine (LabVIEW 8.2.1, TestStand 3.5, but should be independent of Versions as long as you have TestStand 3 and LabVIEW 7 at least).
Hope this helps!
André
Message Edited by Andre_Saller on 04-25-2007 11:34 AM
Attachments:
Autoload.jpg ‏167 KB

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

Why I get an error when running a sequence using the LabVIEW operator interface ?

I have a simple TestStand sequence calling LabVIEW vis that is giving me an error when I run it with the .exe version of the LabVIEW operator interface and I set TestStand to run the vis using the 8.2.1 runtime engine instead of the development adapter. I made a change in the operator interface to open a vi programatically and get the value of a control, this vi is also used in the TestStand sequence I am trying to run. Could this be causing my problem ?
Thanks

Hello Verdulken,
I have a few additional questions:
Does your application function correctly when running the LabVIEW operator interface you have created as a VI in the LabVIEW development environment (i.e. does this problem only occur when the LabVIEW operator interface is run as an executable)?
What is the error that you are receiving?
Regarding the VI that you open programmatically, do you open it in a visible manner (i.e. use the Show front panel when called option from VI Properties)?If so, do you also close this VI after it finishes (i.e. use the Close if originally closed option from VI Properties)?
Does the error occur on the step that calls this very same VI again later in the sequence?
Does your application function correctly if you use the development adapter for all of your calls?
Thank you in advance for this information,
Matt G.
National Instruments
Applications Engineering

Why are my LabView Dialog Boxes no longer modal when using the Example LabVIEW Operator Interfaces?

Hello,
I have a step in my sequence that pops up a modal LabVIEW dialog box. My LabVIEW vi uses the TestStand - Start Modal Dialog.vi and TestStand - Stop Modal Dialog.vi as described in the example and it works as advertised when I'm using the TestStand Development environment however when I use the sample Operator Interfaces distributed with TestStand the Dialog boxes lose focus. I have the VI Properties->Window Appearance set to Dialog and have followed all of the instructions I could find for making a dialog modal. I've also reviewed all the documentation I could get my hands on including previous posts on this board and didn't see anything obvious.
Does anyone have any suggestions as to what I may be missing? Has anyone else experienced this problem and come up with the solution?
I am using LabVIEW 8.0 along with TestStand 3.5.
Thanks,
RG

Hi RG,
Running the example modal dialog in the teststand3.5 examples folder and using labVIEW8.0, I notice that when the Dialog is displayed its not active, but it is modal to the OI. Clicking on the Dialog panel makes it active. If you try to click on the OI panel behind, you can not. Is this what you are seeing?
I am using the Full labVIEW IO as supplied with TestStand and the example VI in the modal dialog folder is as supplied.
The LabVIEW Adapter is still configured to use the active labVIEW developement environment.
If I run the same example, only this time using LabVIEW7.1, the Dialog panel is active.
There is a patch to take it to labVIEW8.01, at this moment in time I am not sure what the update fixes.
There does seem to be a problem with TestStand3.5 (engine) and LabVIEW 8.0.
Regards
Ray Farmer
Regards
Ray Farmer

Problems in Operator Interface for LabVIEW

Hi Ray,
I am using LabVIEW 7.0 and TestStand 2.0 version. I am using the default operator interface for labVIEW provided in the TestStand and i am using custom step types in my sequence file.
This sequence calls a VI, which transmits strings that i specify from the serial port to the NI-7831 RIO Fpga Card for differnt baud rates. The same sequence is working fine when called from Sequence Editor but it is not working when it is called from Operator Interface for LAbVIEW. It justs either fails the test or skips them. Please tell me if there is any solution for it. I have attached the sequence file and the vi that i am calling from my sequence file.

Hi,
You forgot to attach your sequencefile and VI, but never mind.
I think the problem maybe that because you are using the default Operator Interface.
If it still the one in the NI folder, then you will have to re build the testexec.exe application using your LabVIEW 7.0 Application Builder. The default exe file has been built using LabVIEW 5.1.1
Before you start, copy the LV folder from OperatorInterfaces\NI\ to OperatorInterfaces\User.
Load the testexec.bld file in your Application Builder and rebuild testexec.exe.
Launch your new testexec.exe from the User\lV folder and retry your test sequencefile.
Hopefully that should cure your problem.
Regards
Ray Farmer
Regards
Ray Farmer

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.

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

LabVIEW Simple operator interface deployment

Similar Messages

Maybe you are looking for