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

Similar Messages

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

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

Building a simple User Interface

HI,
I'm interested in building a very simple User Interface. All I want to see is a panel with buttons and each button will execute a test sequence file.
1) Is it possible to create such a panel with CVI or LV and then call a sequence file which will be handled by TS?
In that case, I would expect to see TS panels while executing the sequence and once finished (or closed by the user) to come back to the original panel that calls the sequences.
2) is it better to create this panel with TS utility? (I have never done it and suspect it will not be a simple job).
Thanks
Rafi

You can do this in test stand if a simple interface containing just a prompt and buttons will do. In your main sequence, the first step is to create a MessagePopup step. Put a title like "Test Selection". Put a message like "Choose a Test". Label button 1 "test 1". Label button 2 "test 2", and so on. Create a local numerical variable called TestNum. In the post expression section of the first step, add the line Locals.TestNum = Step.Result.ButtonHit. You next step can be a sequence call to the first test sequence. Add a precondition that Locals.TestNum==1. The following steps can all be sequence calls to your other test sequences with preconditions of Locals.TestNum==x, where x is the number corresponding to the button hit in step one. When the selected test sequence is done, the main sequence will be repeated with the message popup asking for a test to run.
- tbob
Inventor of the WORM Global

Use networked Users.ini in deployed simple user interface

I'm using the Simple LabVIEW UI that comes with TestStand 2014. I have customised it to my requirements, but have a small issue. I want to deploy the interface to numerous production PC's but cannot workout how to get the interface to use a networked Users.ini, at Login on those PC's. Does anyone know how to make the user interface use a networked Users.ini? I know that in TestStand 2014 you can use the menus Configure>Station Options>User Manager to tell it where to find a networked Users.ini. I don't know how to make the Simple LabVIEW UI do the same thing. Hopefully I've missed something obvious and will soon be felling rather stupid.
Thanks
Colin

Colin,
This setting is stored in TestExec.ini. You can deploy this by following this link: http://digital.ni.com/public.nsf/allkb/E5E4FEADEFE6023D862571590000C5CC
Here's another link:http://zone.ni.com/reference/en-XX/help/370052N-01/tsdeploysystem/infotopics/includingcfgfiles/
TestExec.ini is just 1 of many cfg files for TestStand. They all need to be in the same folder. Generally the ProgramData\National Instruments\<TestStand>\Cfg folder. The exception is Users.ini. It is the only cfg file that can be in a different location (as you have discovered)
So I recommend pointing to the users.ini on your development machine and then adding TestExec.ini to your workspace. Then you need ot put it in the Cfg directory on the deployment machine. Be careful though because there are a lot of other settings stored in that file.
Hope this helps,

Simple User Interface Improvement

There is one aspect of the user interface that has always slowed my productivity in LR. The scroll bars located on the far left and right of the side panels are thinner than standard scroll panels in Windows programs. When I work with the interface at my normal operating speed, I usually miss the scroll bar 50% of the time when I try and click and drag them. I thought over time this issue would go away as I got use to this irregular aspect of the LR interface, but it has not during the years I have used LR starting with version one. Since many people have wide screen displays, it seems like having a normal width scroll bar would not sacrifice that much screen real estate and would benefit those of us with hand eye coordination that falls outside what was envisioned by the LR user interface developers. Perhaps it could be an optional setting.
Of all of the user interface improvements possible in LR, this one simple change would be of the greatest benefit to my productivity.
Thank you for considering it

Ken, I agree. In general, many of the user-interface elements of LR are fussy and non-standard in their behavior. A couple of examples: The scroll bars don't have up and down arrows at the end, making it hard in large catalogs to scroll by one line of thumbnails using the mouse. Scrolling the Library Filter Keywords column is particularly painful when it has a thousand keywords.
Adobe wants feedback to the product team submitted at the feedback forum:
http://feedback.photoshop.com/photoshop_family/products/photoshop_family_photoshop_lightro om
If you create a topic there, I'll vote for it!

Affichage Nom d'utilisateur Teststand dans le Teststand Simple IO (codé en Labview)?

Bonjour
J'ai une question à propos de l'utilisation de Teststand via Labview:
Pourquoi dois-je ajouter une longue tempo après Start Application Manager pour afficher le nom d'utilisateur dans le Teststand Simple IO?
Je dois obligatoirement mettre une tempo supérieure à 7 seconde (j'ai mis 9s pour être large) pour que je puisse afficher le nom d'utilisateur loggé après le démarrage de teststand.
Sans cette tempo, le refnum entrant dans le get engine est vide et j'ai une erreur.
Je trouve cette tempo anormalement longue alors je me pause la question si mon code est bon...ou pas, si cela est normal, ou pas...?
Pourriez-vous m'expliquer quand doit-on fermer une référence : à chaque méthode et propriété utilisée?
Merci pour votre aide
Lacoule
Attachments:
Simple IO + login Name.PNG ‏101 KB

Bonjour,
Ce temps permet à Teststand de se lancer. Il est donc normal de ne pas récupérer la référence par le GetEngine s'il n'existe pas encore
A propos des fermetures de références : il faut les fermer une fois que vous n'en avez plus besoin. Ainsi, si vous avez créé une référence et que vous l'utilisez avec plusieurs noeuds de méthodes/propriétés, ne la fermez qu'à la fin.
Cordialement,
Mathieu P. | Certified LabVIEW Associate Developer
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées techniques : des fondamentaux aux dernières technologies pour la mesure et le contrôle/comm...

In simple user Interface modify the sequence view to show only executing step

I want to see only the Single executing step in sequence view of the user interface
are there any egs for the same!!

This is relatively trivial to implement yourself. Handle the UIMessageEvent of the ApplicationMgr and when you get a trace UIMessage do something like the following:
if (uiMsg.Event == UIMsg_Trace)
    int notUsed;
    String currentStepName = "";
    SequenceContext context = uiMsg.Thread.GetSequenceContext(0, out notUsed);
    if (context.NextStepIndex >= 0)
        currentStepName = context.NextStep.Name;
    /// Do something with currentStepName like update an indicator control.
Hope this helps,
-Doug

Draw to User Interface in LabVIEW

Hello,
I would like to ask you what Control should I use if want to create a UserInterface like in VBAI State and Transition Editor:
or in StarSim:
Thank you for your help,
Machine Vision Techniques & LabVIEW Solutions - The solution is Yours!

mvTech wrote:
Hello,
I would like to ask you what Control should I use if want to create a UserInterface like in VBAI State and Transition Editor:
or in StarSim:
Thank you for your help,
Looks like tree control on the left, picture control on the right. You'll have to customize buttons to get the effect of toolbar buttons, that are flat, but pop out when you over. You do this by customizing the system control buttons. I think that covers everything you see there.
CLA, LabVIEW Versions 2010-2013

Accessing TS Watch view window in LabVIEW user interface?

HI All
I am trying to build TS user interface in LabVIEW. I want to give ability to user to debug sequence while running.(ability to put breakpoint and view the value of variables in watch view window).
Can we access TS watch view window in LabVIEW .I did not find any activex control for it.
If not how can you give user ability to debug sequence?
Does anyone have idea about this?

hi
I have tried using that.Call stack gives you option to view current execution from the list of executions.(Call stack in TS basically).
It does not give you watch view interface .
Basically I want user to give option to debug sequence . So on the execution view control he should be able to put breakpoint and then once execution reaches breakpoint , he should be able tov view variables values by adding them in watch view pane.
any ideas how to do this?

TestStand Simple OI does not close properly

Hi there.
We have build a test system that is running TestStand 4.2 and the code modules are created with LabVIEW 9.0. The SW is running on a PC with Windows XP.
We are currently using TestStand Simple Operator Interface (LabVIEW version) to run the tests, and it is with the Operator Interface that we are having a problem.
If we use the TestExec.exe file that came with the TestStand installation everything works fine. But we need to make some modifications to OI and if we open the project file and recompile the OI, then the OI will not close properly. It seems to shutdown the testengine and stop execution of the VI, but the window does not disappear until we move the mouse.
When I open the project file LabVIEW informs me that the project was last saved in version 7.1.1 and we are now running 9.0.
Can anyone tell me what is holding the window on the screen until there is activity on the mouse?
Solved!
Go to Solution.

I was looking through TestStand 4.2 known issues, and I found this:
ID# 148697
LabVIEW User Interface might hang when using LabVIEW events
A LabVIEW User Interface that registers ActiveX callbacks and uses an event structure might hang when the user interacts with a LabVIEW control or indicator. The hang is rare, but when it occurs, TestStand User Interface (UI) Controls remain responsive, but all LabVIEW User Interface elements appear frozen.
Workaround: Activate another application and reactive the LabVIEW User Interface.
Not exactly the same as I am experiencing but sounds similar - Does anyone know more about this issue?

'Design Patterns' for Application User Interfaces

I'm currently trying to unstick an architectural mess centred around a relatively simple user interface. The problem is thus:
The application has a number of toolbar buttons and menus, some of which require a specific frame or class of frame to be enabled. Some conditions are quite simple, others more complicated.
(Without going into any more detail, it should be possible to appreciate that this is a fairly common problem.)
For this application, I've created a large listener that accepts events from all over the program, converting them into state changes for UI controls. It feels messy, and (although it isn't finished) I suspect it'll be rather fragile.
JBuilder 4 does it by constant querying of application state - but this results in excessive CPU usage and apparant lag.
TogetherJ does it for menus by checking state immediately before showing the menu. This seemed like a good plan, but it's unsuitable for the Action/Button/MenuItem lashup I like to use.
My question is this:
In your opinion, how should an application be structured to reliably maintain the correct UI state at all times?

Check out the mediator pattern. It is pretty close to what you are describing, maybe the details you dig up on it will give you some new ideas?

Graphical user interface

Dear all
                i am trying to build a graphical user interface using labview 7.1 but i am new to it and finding difficulties.
                 my first window should contain two push buttons A and B(like ac machine, dc machine) when a user click on any of this button
                the next window should show another push buttons C and D,and this button should link to some VIs which should start running   by   clicking any of those two buttons
Thanks in advance to anybody who can help

This is a very general question, but as a general answer, different screen are commonly handled by using different pages on a tab control and programmatically switching between them (you hide the tabs themselves) or by using different VIs. Monitoring for user interaction is done by using an event structure which will allow you to execute code when a button has been pressed. There are quite a few examples in the example finder (Help>>Find Examples) and some templates (File>>New) for how to do this.
To learn more about LabVIEW, I suggest you try searching this site and google for LabVIEW tutorials. Here, here and here are a few you can start with and here are some tutorial videos. You can also contact your local NI office and join one of their courses.
In addition, I suggest you read the LabVIEW style guide and the LabVIEW user manual (Help>>Search the LabVIEW Bookshelf).
Try to take over the world!

User interface hardware

anybody can help me to I find a list of industrial hardware (panels etc, no PC) which I could use to create a user interface in LabView?
It would have to be "rough" but not too expensive. Regula PDA would not be ok
Thanks
Nicola

Try looking at IVC and Suetron. I haven't tried any of them.
Try to take over the world!

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.

Teststand Simple User Interface in LabVIEW

Similar Messages

Maybe you are looking for