Tutorial on teststand user interface to cvi

I haven't used the CVI to TestSand User Interface since 2004. I've been put on an upgrade project to go from Windows 2000 to Winows 7, TestStand 3.0 to TestStand 2010, and CVI 7 to CVI 2010. Now I have to make the old UI work.
Are there any good tutorials out there on the CVI user interface for TestStand?
More specifically, I'm trying to figure out why the TS_EngineGetResourceString doesn't work now? (more specifically how does TS_EngineGetResourseString work)
Thanks
"Lockheed" Joe
Testing Blog"

Hey Joe,
Here are some great resources for you to check out on building user interfaces. The first link is an example and the second is more of a general discussion on interface development. If the forums ever don't suffice, you may be able to find more information by searching NI's website for 'Cvi User interface TestStand'. Just another great spot to check for answers.
Simple CVI User interface for TestStand
Best Practices for NI TestStand User Interface Development
Hope this helps,
Luke W

Similar Messages

Send CurrentUser Name to TestStand User Interface

Dear All,
I am using the TestStand User Interface (LabVIEW) to execute the test sequence file (TestStand).
I need to show the current user name (i.e. the user name what we enter in TestStand Login window) in the TestStand User Interface VI. Please let me know the way to get the login details (current user name & privilege) from TestStand to TestStand UserInterface VI.
Thanks & Regards,
Sathish kumar D
Solved!
Go to Solution.

Hey Sathish,
I found a forum post from earlier this year with a similar question, and I think it will apply here as well. See it here: http://forums.ni.com/t5/NI-TestStand/Monitoring-activity-of-Login-Logout-button-in-LabVIEW-Simple-OI...
Basically, you can connect to the UserName caption of the Application Manager to display the username. Let us know if you have any further questions about it!
Daniel E.
TestStand Product Support Engineer
National Instruments

Why do I get -18001 Errors using Customised TestStand User Interface

Hi all
I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
If anyone
has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
Thanks
Dave

David,
I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
LabVIEW : VI is not executable.
An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
2) The same error will occur when
a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
Building The Operator Interface
The following are steps if you are using a LabVIEW operator interface.
1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
Creating a LabVIEW Run-time Server
If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
Assembling the Test VIs for Run-Time Distribution
This distribution process uses one of the shipping TS examples that calls LV VIs.
1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
3) Confirm that the sequence runs without problem.
4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
6) Set the target directory to be something distinct like C:\temp\AssblVIs.
7) If you are using TestStand 2.0 skip adding Dynamic VIs
8) Save with or without diagrams. Its your choice.
Change Search Directories
Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
1) In the sequence editor select Configure>>Search Directories.
2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
3) Close the Edit Search Directories dialog box.
4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
1) In the sequence editor select Configure>>Adpaters.
2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
Distributing Components
-To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
-To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
-You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
Hope this helps.
Regards,
Kitt
=========================================
Title:
Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
Components that need to be distributed:
TS engine
Operator interface
LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
LabVIEW run-time engine
LabVIEW test VIs
Test sequence files
Actions before distributing:
It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
Assemble the test VIs for distribution.
Update the TestStand search directories so that the sequences reference the assembled VIs.
Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
Test the distribution components on the development machine.
Enter section headings, separating each section with a line break:
TS Engine Component
Operator Interface Component
LabVIEW ActiveX Server
Configuring the LabVIEW Standard Prototype Adapter
LabVIEW Run-time Engine Component
Assembling your Test VIs for Distribution
Note
TS Engine Component
With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
Operator Interface Component
You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
LabVIEW ActiveX Server
You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
Configuring the LabVIEW Standard Prototype Adapter
When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
LabVIEW Run-time Engine Component
If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
Assembling your Test VIs for Distribution
After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
Links: See Distributing LabVIEW Test VIs below
Note
Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
==============================================

How to get to learn using TestStand User Interfaces

I am starting to work with TestStand and I was looking into using the User Interface. I know that a couple of examples are provided and that there is a couple of sections of literature on the subject, but there does not appear to be a very helpful (get started from scratch) type of documentation that I can find. Does such a thing exist? If not, what is the best way to get started?
Solved!
Go to Solution.

You can currently do this in the Full-Featured UI without any modifications. It's kind of a hack though:
So assume that an execution is running. The user clicks the Break button and wants to rerun a step with different parameters. So now your execution is paused somewhere below the step. Right click the step and select: Set Next Step to Cursor. Now in the Variable window look for the variable that is being passed as a parameter to that step. Say for instance Locals.Foo is being passed to your VI. Change the value of it and click the Resume button. This also assumes that you are passing either Locals or FileGlobals to your VI. You may have to have Administrator privileges to do this.
If this isn't good enough then there are ways to accomplish what you want in a cleaner manner.
One way is to build your sequence file such that if a certain condition occurs then retry with new values or values from a file which can be changed by the user. This is what I would recommend because it will be the cleanest and the easiest.
Another way is to build into your UI like you are asking about. The problem with this is at a certain point the user will click Break or a Stop button that you have put on there. This will stop the execution at some point (who knows exactly what point unless you write code to specify a point). Then they would have a pop up or something that would allow them to select a step. Then for each step you'll have to have some code or a parser or something that will determine the parameters and valid values they can be and ask the user for those. This is all doable but would be quite a task. You will have a long ways to go in understanding the TestStand API in order to accomplish this. In fact there would be so many API calls with numerous ways to attack this problem.
Whichever way you choose to go you will always have the TestStand forums or NI support.
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

How can I tile up the execution window in the Labview Teststand user interface

I am using the Labview User interface provided with the TestStand development environment.
Running the BatchUUT.seq Example using the TestStand Sequence Editor, you will see that the Execution Window will be divided in 4 windows showing the execution status of the 4 UUTs.
Running the same Sequence using the provided Labview User Interfaces (Simple or Full-Featured) will just show one window with the execution status.
Is there a way to tile up the window to display the execution status in the Labview User Interface?

Try something like this:
You wouldn't use random numbers of course, but rely on already opened clones. So you would extend the "Manage Clones" to manage the data for the window position, but set it for each clone in the way the screenshot shows.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

How to execute a sequence without using an User Interface

Hi,
I have programatically generated a TestStand Sequence File. I used C# and the TestStand API. I opened the .seq file in the default TestStand User Interface and the Sequence File runs perfectly.
However, when I created a NewExecution using the Engine object created in the porgram, it seems that the sequence never starts execution. Please look at the following code snippet:
// TSStep and TSSequence was created before
TSSequence.InsertStep(TSStep, 0, StepGroups.StepGroup_Main); SequenceFile TSSequenceFile = TSEngine.NewSequenceFile();
TSSequenceFile.InsertSequenceEx(0, TSSequence);
TSSequenceFile.Save("SeqGen.seq"); Execution TSExecution = TSEngine.NewExecution(TSSequenceFile, "Seq_0", null, false, ExecutionTypeMask.ExecTypeMask_Normal, System.Type.Missing, System.Type.Missing, System.Type.Missing);while (TSSequenceFile.IsExecuting == true) ; // this flag never changes to false
TSEngine.ReleaseSequenceFileEx(TSSequenceFile, 0);
I know the sequence is not being executed because a COM Server (written as a Local Server in a .EXE) should start when the step within the sequence be executed.
Any ideas why the sequence is not executing properly ?
PacSoft

Hi Pacsoft,
Check out this example,
I posted it in a former thread.
Note: Also downloaded the .seq from the former thread! NEVER acept savings to Ni. -INI files !!!
Greetings
juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=
Attachments:
ConsoleApplication2.zip ‏55 KB

Error -17501 flxCVIadp.dll when starting CVI full featured user interface on Windows 7

We see the following error dialog when we launch the CVI full-featured user interface (TestExec.exe):
"Error:
Unable to load test environment adapter 'flxCVIadp.dll'. Run setup to re-install or remove this adapter.
Could not connect to TSAutoMgr.exe server. DCOM permissions might be incorrect because of configuration changes for remote execution. To fix this issue, ensure that the current user is in the default DCOM access permissions or that no users are in the access permissions section of the dcomcnfg.exe dialog box. You can use the dcomcnfg.exe program, located in the Windows System directory, to change DCOM access permissions.
Error code: -17501, Unexpected Operating System Error."
When this error happens, we can't run any calls to CVI code from within the User Interface.
We are running Windows 7. We don't see the error if we run TestExec.exe from the default location:
C:\Users\Public\Documents\National Instruments\TestStand 2013\UserInterfaces\Full-Featured\CVI
We get the error message if we copy the CVI directory to somewhere else on the C:\ drive (C:\MyUserInterface for example). The error happens when we run TestExec.exe directly, but it does not happen if we are already running Labwindows/CVI and we launch TestExec.exe from CVI.
We are seeing this error with both TestStand 4.2.1 and TestStand 2013 running on different PCs. This error happens on Windows 7, but not Windows XP. Though we get the same error with our custom user interface, we see the same error with the stock CVI full-features user interface provided by NI.
Any ideas about why we can run this from the TestStand directories, but not any directory on our C:\ drive?
Thanks,
Peter

Hi Peter,
Based on the error messages it looks like this might be a Windows 7 security issue, which would be why it doesn't occur on XP since security is handled differently in that OS. Have you gone into dcomcnfg.exe and checked the DCOM permissions as described in the error message?

LW/CVI 2009 user interface browser missing

Just getting back into LabWindows/CVI after many years. Using 2009 version.
Going through the tutorial located http://www.ni.com/pdf/manuals/373552g.pdf
When I double-click on the.uir file, the panel opens up, but I do not get the User Interface Browser and the Attribute Browser has replaced the Library Browser.
Apparently, this is the default behavior for 2009 contrary to the figures in the tutorial.
How can I get the User Interface Browser to appear and put the Attribute Browser to the right hand side?

The User Interface Browser and Attribute Browser being on the right hand side are both new addtions for LabWindows/CVI 2010. The behavior you're seeing in 2009 is expected and can't be changed.
Kevin B.
National Instruments

Update Station Globals from LAbWindows/CVI user interface

Hi,
I am having a requirement such that i need to update a station global variable to true or false based on the click on a button present in User Interface.
My Setup:
Labwindows/CVI 8.5
TestStand 4.2.1
Please advice me.
Solved!
Go to Solution.

Hi,
first thing, why have you posted this query twice, http://forums.ni.com/t5/NI-TestStand/Update-Station-Globals-from-CVI-UI/m-p/1317023
to be able to update a StationGlobal, you first need to get a reference to the Engine, this can be done using ApplicationMgr.GetEngine()
Once you have that reference you can then get a reference to the StationGlobals by the use of Engine.Globals(). this returns a PropertyObject.
So now you can use the SetVal methods to set your boolean, eg PropertyObject.SetValBoolean("MyBoolean", 0, True)
hope this helps
Regards
Ray Farmer

Labwindows/CVI 7.1 Remote user Interface using Enterprise Connectivity Toolkit

I have an application programmed in Labwindows/CVI 7.1 controlling an Electromagnetic Instrument.
Now am interested in extending its usability by adding remote user interface.The goal is to have the application available to be accessed
to remote users through website,with multiple users viewing it but one user controlling the instrument remotely at any given point.
Since the possible methods would be 1.ActiveX 2.TCP/IP 3.DLL
Which is the best technique to implement this with out having to manipulate much of my code also do we have any documentation available ?
Thank you
Solved!
Go to Solution.

Hi Mutha,
This functionality was a part of the orignal Internet Toolkit for CVI. However, the web server part of this was removed and isn't included in the Enterprise Connectivity Toolkit. You might consider using LabVIEW with the Remote Front Panel feature.
Cheers,

Developing a User Interface with ADF Faces - Tutorial - Questions

Hello everybody,
I am a forms developer and I am totally new to ADF.
I started from the tutorials : Developing Business Services with ADF BC and Developing a User Interface with ADF Faces...
Everything was easy and very clear, as far as the material covered in the tutorial is concerened.
But when I tried to modify a little bit the application, to perform a different task... disaster!!! :-)
One of the "simple" things that I tried to do -for example- is :
In the login.jspx, where we have created an ADF Parameter form (that accepts as a parameter the customer ID) and
retrieves in the next page the Orders of the specific customer.... to Display a message, such as "+Customer Does Not Exist+"
if the user types in the parameter form an not existent customer ID...
I understand that I should use a validator.... But I cannot find the list validator (from query) in the bind variables not in the ADF Parameter Form Fields....
Does anyone know?
Regards,
Maira Kotsovoulou

Dear Grant,
CustomerID is in the UI Project, and appears as a part of an ADF Parameter Form... and I can not find key exists in the UI Validators....
CustomerID in the .entities is a bind variable in a query. select ... from customers where customer_id = :p_customer_id. Again KEYEXISTS validator is not available in the bind variables sections... Only in the attributes!!!
I understand that the "normal" behavior in a query with bind variables where there is no match is to display nothing as it does!!!
But I was just wondering, if I could even trap that before I display the empty form...? Or could I display a text in my ADF form, that says no rows... (as I can do in an ADF Table???)

Has anyone seen the TestStand 3.5 User Interface disappear during testing?

The user interface disappeared while a test sequence was executing. The Windows Task Manager showed LabVIEW (8.2) and TestStand running but nothing was present on the taskbar for TestStand and the window could not be found. This has only happened once but I am being pressed to explain this hence the question.

plf,
By user interface you mean an operator interface?
If this is the case, what operator interface are you using?
Have you seen this several times?
What kind of sequence were you executing?
Regards.
Antonio Lie.

Background color of TestStand 2012 User Interface Reverts Back to Default After Changing

I changed the background color and other properties of the Execution and Sequence TestStand Controls in the TestStand 2012 User Interface example code. When I execute the Top Level.vi the TestStand User Controls revert back to their default colors/properties. I saw this problem in the list of TestStand 2010 known issues, is it also a known problem in 2012?

Hey kelsayd,
I just tried changing the color of the user interface controls in my user interface (from TestStand 2012) and saw the same behavior. I believe this is because the controls are ActiveX controls and do not permit the same level of customization as LabVIEW controls. I did find this KnowledgeBase article, which mentions the issue and gives one possible solution to the issue: http://digital.ni.com/public.nsf/allkb/4E40FA5AEAF3937B86256E89007C74C4?OpenDocument
Hopefully that will help show how you can set this up, and let us know if you have any further questions about it!
Daniel E.
TestStand Product Support Engineer
National Instruments

Teststand Simple User Interface in LabVIEW

Hello Community,
I am designing a user interface for Teststand by using the simple example vi provided. The name of the file is Top-Level VI.vi
I am trying to understand how the vi works inorder to make changes and ran into a few questions that I was hoping someone could answer for me please.
To start I add my sequence file and click "Test UUTs". Then a dialog box pops up asking to enter the serial number of the UUT, where and what causes that to happen in the code? After I enter my serial number it runs my sequence code and at the end another message box appears specifing in a green or red whether the UUT passed or failed. Where and what causes the Pass/Fail Boxes to happen in the code?
Thank you
Kevin
Solved!
Go to Solution.

The S/N dialog is part of the process model.
For the Sequential Model (SequentialModel.seq), the default S/N dialog in found in the 'PreUUT' sub-sequence and implemented as a DLL call.
The PreUUT sub-sequence of the SequentialModel is a callback, so you can override it in your own test sequence.
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

LabWindows/CVI Remote User Interface

I have an application that I would like to modify to enable running the User Interface Panel from a remote
computer. I have found articles on doing this with LabView. Can this be accomplished using LabWindows/CVI 7.0/7.1 ?

Hello Hornsbyr,
It is possible to have run remote front panels in LabWindows/CVI. First you would need the CVI Enterprise Connectivity Toolkit as an add on to 7.0 or 7.1. A web server is included in the Enterprise Connectivity Toolkit. By setting up and connecting to the web server, you will be able to monitor and control the operation of your front panel through a web browser. The INET_RegisterPanelAutoUpdate function is used to export a LabWindows/CVI user interface panel onto the Web. Once a client requests the image of the panel, the server periodically sends an updated image of the panel.
The image of the user interface is sent as a JPEG image, but as stated in the LabWindows/CVI Function Help, the JPEG will not include your UIR's menu bar, title bar or borders.
I have attached a document that further describes how to control your front panel remotely.
Also, here is a link to the product pricing sheet: http://sine.ni.com/apps/we/nioc.vp?cid=11128〈=US
Wendy L
LabWindows/CVI Developer Newsletter - ni.com/cvinews

Tutorial on teststand user interface to cvi

Similar Messages

Maybe you are looking for