Labview GUI with TestStand

[mrbean]

I'm using LV8 and TestStand 3.5.  I would like to create a custom GUI that does most of the typical TestStand events (i.e. allows user to login, select sequence file, runtime data to file and scroll box, print results, run sequence), but also allows the operator to request asynchronous information from the (hardware intensive system).

I noticed that LV8 has quite an assortment of TestStand VIs.  Should I work in LV8 or TestStand for my high-level GUI?  If in LV8, I'm not sure how the TestStand VIs are used.  The documentation in LV8 doesn't exactly help me much.  Is there a GOOD resource for examples and/or literature?  If I work in TestStand, do I copy one of its default Operator Interfaces (code) to the user directory and modify it there after?  I assume there is a CVI version and a LV8 version of the basic OI somewhere.  Ultimately, I know I'll want to use TestStand's sequence editor to create my sequence, and it will step through all the different LV8 VIs I create (once I get a clue).  But I'm having trouble with the architecture.  Who should run the show?

[Dennis_Knutson]

First, I would highly recomend you take a TestStand class to get you over some of these basic hurdles you seem to be having. Have you gone through the shipping tutorial yet?

If you want to create a custom operator interface with LabVIEW, it has to be developed in LabVIEW. If you want to create a custom operator interface in CVI, you would have to use CVI. If you wanted to create a custom operator interface in VB, you would have to use VB. The TestStand editor is for creating test sequences. For help, open the TestStand Bookshelf from the Help menu and read the "Using LabVIEW with TestStand" document. Information on the TestStand VIs, how to call LabVIEW steps, and how to create a user interface is all there. The source code for LabVIEW, CVI, etc. operator interfaces is in the TestStand 3.x\Operator Interfaces\NI|Full Featured and \Simple Folders. If you want to use one of these as a starting point, copy them and move them somewhere. There's even a folder called \OperatorInterfaces\User already created for you that you can use.

I would suggest that you stick with the TestStand interface for the time being. Get all of your steps written and get the sequence debugged there. Then you can move on to create the custom operator interface. Depending on what you want to do with the operator interface, you may or may not need to modify your sequence. If you know exactly what kind of customization you want to do with the operator interface, post back with those kind of details.

[Bob_Y.]

I think your main question is: should I have TestStand call LabVIEW or LabVIEW call TestStand?  I would not venture a guess as to which is better for your application and skill set. 

I am much more comfortable in LabVIEW, but calling into the TestStand engine seems like work.  For me, I would lean toward writting it so that TestStand is started and calls LabVIEW for a UI. 

Hope that this helps,
Bob Young

[RayFarmer]

Hi,

If you are going to create a Operator Interface GUI, then you will have to do this in LabVIEW. TestStand, does not have the means to create a GUI, it has a runtime engine and an API which you can invoke from your application, whether that is written in LabVIEW or some other language.

There is plenty of help in creating a GUI in the TestStand Help and Using Teststand with labVIEW manual. Also there are example GUI's in the TestStand OperatorInterface folder and on the NI website.

And as Dennis suggest, attend one of the TestStand courses.

Regards

Ray Farmer

[mrbean]

Since my company doesn't recognize the value of training (translation, cheap skates), I have to rely on the proven veterans out there.  Now for my question.

Although I may just use the default TestStand-LabVIEW user interface, I'm trying to make a small modification just to understand the theory.  I copied the contents of the folder TestStand 3.5\Operator Interfaces\NI\Full-Featured\LabVIEW to TestStand 3.5\Operator Interfaces \ User \Full-Featured\LabVIEW.  Is this correct?

Then, I opened the LabVIEW project file entitled, Build Script.lvproj and modified a couple of the text messages (no functionality behind them) in About Box.vi and Top Full OI-Top Level.vi.  I did a save all, and ran the TestExec application file in the same folder.  When I open the sequence file I created (really basic), I don't see any of my modifications.  Any suggestions as to why?

Also, are the sequence editor and operator interface at all tied together?  What I mean is, if I open my sequence in the sequence editor and press F5 to Run UUTs, I don't see anything resembling the operator interface ever show up.  Am I correct in that I have to (in the sequence editor) create a deployment to then see the top level OI?

[daijoubu]

No, the sequence editor is a separate application from the operator interface.  To see the changes you made to the operator interface, you would need to run TestStand 3.5\Operator Interfaces \ User \Full-Featured\LabVIEW\TestExec.exe.  You will need to build this exe if you have made any changes to the source vis.

You do not need to create a deployment to see the OI.  It is installed alongside the development system.  You will need a deployment of some sort to install it on another computer.

[mrbean]

So, if I am in the sequence editor and I select Test UUT, it will simply run the steps within my sequence.  It has no link to the operator interface.  Is this correct?

[RayFarmer]

Hi,

That's correct.

Regards

Ray Farmer