Can test stand execute LabVIEW executables ?

Can I refer to LabVIEW executables in testand -> I can run VIs developed in LabVIEW through Teststand with only the LabVIEW runtime engine on the host computer ?

What version of TestStand are you using and what version of LabVIEW are you using?
Scott Richardson
National Instruments

Similar Messages

How to get the value of the global variable of test stand in labview User interface?

Hi.
Can anyone Please share examples and tell me to how access the test stand global variable using labview user interface.
Solved!
Go to Solution.

I'm not surprised that what you are doing doesn't work. The Start Execution UI Message is triggered when the user clicks a button to start an execution. Realize that most executions go through a process model. So you could be looking at the sequence context of the process model and not your client sequence file.
I recommend reading that link I posted above. UI Messages are your best bet but you cannot just piggy back on an existing UI Message like this. They may not be getting sent at the time you need them to be. The only way to ensure you get what you want is to trigger one yourself at the right time.
Regards,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Configure Event Callbacks in test stand using labview

Hi,
I was going through Full OI - Configure Event Callbacks.vi in the test stand example. Can you please explain me how the vi works and what is techniwue behind it?
When i open the individual VI's in the reference, I could see more that 1 control in the front panel. But Only the user parameter is wired in the vi? Why is it so?
Regards
Gopal

Hi Gopal,
When the TestStand Engine fires events, this VI specifies how your Operator Interface will respond. For example, let's examine the first event callback registered in Full OI - Configure Event Callbacks.vi , Exit Application. When the TestStand Engine receives the message to shutdown, and then finishes its neccessary shutdown procedures, it will send a message to the Operator Interface. For the Operator Interface to receive this message, it must "listen" for it. In LabVIEW, this is done by Registering an Event Callback. See the links below for details on how to implement this.
The answer to your specific question is in step 7 of the first link below. When TestStand sends the message to LabVIEW, there is information that is always passed. The other input controls contain this information. To create a VI that always includes these controls, right-click on the VI Ref input to the Reg Event Callback Property Node, and then select Create Callback VI.
Here are two references that talk about handling ActiveX callbacks in LabVIEW in general:
Registering and Handling .NET and ActiveX Events
Register Event Callback (Not in Base Package)
Cheers,
David Goldberg
National Instruments
Software R&D

Test Stand LabView adapter 8.6 run time will not run 8.5 VIs

I’m trying to run a script I developed with a dev computer on
a regular PC set up with a Test Stand User Gui, and run times for Test Stand
and Labview.
With the Test Stand Labview adapter set to 8.6.1 all of my
ENA(Agilent Network Analyzer) calls fail for “VI Version is too early to
convert to the current LabVIEW version.” The ENA library is written in 8.5. If I set the adapter to 8.5.1 then all of the
VIs developed in 8.6 fail. In addition
it will not run any VIs that I save back to 8.5. I installed a demo Labview development
version (2010?) and everything ran fine with the adapter set to Development
System.
I am not sure what to try next to get it to run on the
regular PC, any hints.
Test Stand = 4.2
LabView = 8.6
Running in windows XP
Solved!
Go to Solution.

One of the many things I tried was saving the ENA library to 8.6, but I could not get it work.
This is the Original library I installed and was trying to Convert (8.0 upgrade agena.zip)
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=001CE83736F3674BE0440003BA7CCD...
I am about to try this one. (8.2.1 Upgrade)
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=74D1F1D4EB5268E8E04400144FB7D2...
I am pretty new to labview so I am not sure how to make the save to previous version workfor libraries, but I can easily do it with individual VIs. For libraries, it creates a new directory, and puts in all of the files and then asks me about saving the lib files as something else. This is where I think I get it wrong. I tried it again today and got the same results.
I greatly appreciate the Help
Brian

Test Stand Evaluation

Hi.
I would like to get some feedback regarding using Test Stand with Labview.
Currently I am using Delphi Interface as my Excecutive Engine and Active
X server to communicate with labview. The data logging, PLC I/O and Login/logout
are part of Delphi Inteface. The labview is used only to execute the actual
test. Now by switching to Test Stand, would that benefit me in any way.(For
instance: Does Test Stand(LV Server) allows me to run single or multiple
Vi's, without creating 'exe')?

There could be lots of advantages to switching to TestStand, but it depends on your application.
1. If you deploy your applications to several different environments or uses (board test, system test, service, field service, etc.) then TestStand allows you to customize different "process models" for each environment. The actual test code is contained in a sequence file. Since the process model is shared by all sequence files, it is a great place to put the common functions such as UUT identification and data logging. Even if you don't need different process models, keeping all this code in one place makes it easier to maintain. There is no compiling with TestStand, so you can change the process model and the changes will take effect in all your applications.
2.
TestStand allows you to easily call many different types of code, not just Labview. You can call CVI, DLL's, EXE's, and ActiveX. I recently saw an article about a way to call Perl code. Again, the value of this depends on your application.
3. If you want to integrate your application with a database, TestStand has great database tools. The database logging utility allows you to log data to any table format.
4. If you are loading test limits from an external source, TestStand makes it easy with a tool called Property Loader.
I suggest you get a free demo copy and try it out. TestStand is incredibly powerful.
Mark ([email protected])

How to Remove in/out port for Test Stand VI

Ok - This is probably something stupid, but i can not really find a basic example to understand what's wrong.
I just want to create a Test Stand VI, that in adition to the basic IO, use extra IOs for configuration for example. Here is what i do
1 - Create a new Pass/Fail VI from Test Stand
2 - LabVIEW start by itself, show my VI
3 - I put a basic "Not" logic, and connect the input to the logic
4 - Save
5 - Reload the Prototype in TS, and here my new input does not shows up.
I do not believe that i can make this any simpler. Could someone explained what is wrong here.
Solved!
Go to Solution.

When you create a VI using the "Create VI" function in TS. Output ports are not connected and still shows up in TS.
I attached the simplest example in the world. What i expect to get in TS after i update the prototype is to have the same output as the initial one + an new input that allow me to control my output flag.
Attachments:
PassTest.vi ‏9 KB

Test Stand and MAX Settings

I am using test stand and Labview 7.1. I used Express VIs to setup my RS232 communications in numerous VIs that I call from test stand for different types of tests. I have the same product, but with different baud rates. Is there a way in test stand to change the baud rate settings in MAX for Com1? I tried to create a Labview program to do it, but once a sequence runs that has the Express VI I/O Control it must start a new VISA session and I loose what was set up and it reverts back to the MAX settings for Com1. The only time The VISA setup vi I created appears to work is when I converted an Express VI (or opened the Express VI's front panel). And messed with the code.

Hey,
I would suggest using the VISA Configure Serial Port to configure the port and then calling the Express VI using the VISA Resource Name Out from the configure VI.
Regard,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~
Attachments:
setbaudrate.vi ‏36 KB

Is there any way I can convert a Test stand sequence and corresponding vi's to an executable?

I need some creative ideas on how I can convert a test stand sequence into an executable in the shortest possible time. I know that beats the entire purpose of using TestStand but I need to have a way to do this. Is there no other way i can accomplish this without writing a sequencer in LabVIEW and rewriting all of my code in LabVIEW??

There is no way i know or can think of to move all components from a TestStand application into a single EXE. Running TS in an application means that you should/must work highly unitized during developement and deployment.
In general:
-> Custom UI will become "The EXE" for the enduser. This involves the link for startup on desktop/start menu.
-> TS Engine, ActiveX Server, will be attached to the UI.EXE OS process when launched by the UI. Will never be part of the UI.EXE.
-> TS Compontens (e.g. process model, language files, ..). Will never be part of the UI.EXE.
-> Custom Components (e.g. modified process model components, reporting, ...). Very unlikely(never) to become part of the UI.EXE.
-> Custom Sequences. Will never be part of the UI.EXE, but extension can be changed to other than .seq.
-> Code modules called by custom sequences. Unlikely (but possible) to be part of the UI.EXE. Should be implemented and tested to run within the RTE (runtime engine) of the appropriate programming language. It is not par design, that the deployment system has the development environment of that programming language installed.
-> License information. TS requires at least the Base Deployment License installed and activated (requires NI License Manager software). RTE of modules might also include licensing and possibly activation fees.
Why is there the requirement to have a single, monolythic EXE (hard to handle!) at all? If it is about the deployment process, you know that you can provide a single MSI (Microsoft Installer) with all required components using the TestStand Deployment Utility?
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Test executive and Test stand deployment cost

Hello,
would some NI support engineer kindly answer below questions ? i would be obliged.
we have been running customized Test executive built from Test executive toolkit. We are now making decision as to whether We should migrate to test stand or keep the existing structure? Here are some questions:
1) in case We switch to test stand, do We still need to buy runtime engine license ?
2) can we call executables in Test stand ?
3) stating from ground zero, what is the deployment cost estimate between Test stand and customized test executive scenarios, from end user point of view ?
-Ahmed

Hi Ahmed,
To answer your questions:
1) You will need to have a deployment (runtime) license for all the machines that you plan on running your application on. However, you will only need a full development license for the computer that you are actually developing the application on. You can see a full explanation of the different types of TestStand license in the document "When Should I Purchase a License for my TestStand System?"
2) In regards to calling executables, TestStand has a builtin step to call executables making it extremely easy to do. You can download an evaluation copy of TestStand here to see how easy it is to use as well as see the simple Call Executable Step.
3) In regards to price comparison between TestStand and a customized test application, this really depends on the project. Each project can have a different cost. However, you can take a look at this cost analysis to get a general idea of one example of cost comparison. This is just an example and also compares an older version of TestStand.
For more specific information about cost, please contact a sales representative at (888) 280-7645.
Thanks,
Caroline Tipton
Data Management Product Manager
National Instruments

Coverting an application from test executive to test stand.

I have used LabWindows CVI and the "test executive" toolkit to develop production test applications. The production operators who use the programs like the look and feel of the interface.
I want to convert to Test Stand so that I can support solutions written in languages other than CVI. How do I modify the test stand user inteface so that I get an identical operator interface?

Hi Tom,
You can also convert your CVI test executive sequence files into Teststand sequence files. Under the Tools menu in the TS Sequence Editor you will find a wizard that performs the task for you. It will take the CVI callback functions and generated the equivilant TS Callback sequence calls. You may still have to make some manual changes, but you wont have to completely regenerate your original test sequences from scratch.
Regards
Ray Farmer
Regards
Ray Farmer

Can labview call a test stand module

Having problems with a test dll that runs in test stand, but I get errors when trying to use the wizard in labview, however I can use the call library function node to protypye it. Problem - the function openComserialPort(char* comPort, ErrStruct & err), how do you difine the parameters for the ErrStruct & err part.
next Question, since this Dll runs in Test Stand, is their anyway to export to work in LabVIEW.
Solved!
Go to Solution.

Here's a description of the dll, to start off, I have a circuit board with a microprocessor on it, that has control for a radio module. During test I need to program this board serially through its' TX and RX lines on the processor. The dll given to me, which was written for test stand, has functions to enable me to do this programming. There are basically 11 function contained is this Dll.
Initialize Dll, (no errors),
open serial port, (no errors),
getStandardTable, which sends a command for the microprocessor to send back its information-> get assertion error
WriteHardwareVersion -> Sends the version and revision number -> assertion error.
ColdStart -> Which resets board statistics variables -> assertion error. Now, this function prototype is ColdStart (errStruct & err); So I prototype like I did for the above error struct, but still got an assertion error, which leaves me to believe, that , or vendor, has a bug communicating, or sending the commands via serially, to test this, I could use the serial examples contained in LabVIEW, however I don't know the command set of the microprocessor, or could there be something else wrong, Any ideas will be appreciated.

I want to write a program in LabView then pass the test results to teststand to check if it pass or fail without displaying the test stand program,

I want to write a program in LabView and create an execute but I want to be able to pass test results to test stand to find it the unit pass ar fail the test then save the data to a database. How would i go about it.

What's confusing is your statement that you want to do this "without display the test stand program". You can minimize the TestStand UI to the task bar but if you don't want TestStand to be running, how can TestStand evaluate the result. Explain a little more please.
In the message body of your post, you just say you want to create a LabVIEW exe and pass the results to TestStand. What I would recomend is that instead of an exe, you create a dll and use TestStand's DLL adapter to call it and return the results. TestStand will evaluate it and do the logging.

Labview and Test Stand

Hello Everyone:
I would like to get some feedback (from his/her practical experience ) using
LabVIEW and Test Stand together. Any comments regarding this matter would
be greatly appreciated.
Thank You.

Robert,
TestStand package is built to work with other NI software products such as LabVIEW and LabWindows/CVI.
You can write your test code as LabVIEW VIs. Those VIs do not have to be compiled into executables. You would simply use a LabVIEW Adapter which allows TestStand engine to call LabVIEW VIs.
One very useful feature of TestStand is that it allows you to debug VIs when called from TestStand. TestStand's execution pauses and you can use LabVIEW's debugging tools to debug VIs.
From my personal experience, the two packages together work great. A large number of people are already using this combination to increase productivity. To read further about TestStand, you can check out the following usergroup dedicated for TestStand (natinst.public.teststand.general
) by visiting http://zone.ni.com/dev_exchange/newsgroups.htm.
Adeel Malik

Responding to commandKind event - Test Stand/Labview UI

Hey guys hey. I have a control on a Labview/Test Stand UI that I want to change the attributes of based on if the user is logged in or a sequence file is loaded. How can I create an event that will fire when the user logs in or out or a sequence is loaded or unloaded etc. I have tried firing an event when the ActiveX control Login|Logout mouse click is up, but the event never fires. I assume that's because the CommandKind_LoginLogout is attached to that control and maybe overrides the event? My version is TS 4.1, LV 8.6, OS XP. TY
Solved!
Go to Solution.

Hi ET,
This option may work for you. You can edit the Configure Event Callbacks.vi to include three extra events, a SequenceFileOpened, SequenceFileClosed, and UserChanged. This will capture when someone hits one of the three buttons and execute the code in the callback VI. You can modify the connector pane of the VI or the bundle for user parameters to include a reference to the control of interest, and pass the reference into the user parameter option so it is available in each callback VI. You can then wire this up to a generic property node to modify the attributes of the control you created the reference for. I have attached a screenshot of the modification of the Configure Event Callbacks VI. I hope this option works for you!
Cheers,
Kelly R.
Applications Engineer
National Instruments
Attachments:
SequenceUserEventCallback.png ‏23 KB

How can I get Test Stand to print failues only?

Rather than getting a large report file with hundreds of passes and only one failure, how do I configure Test Stand to only print the failures to the report?

Hi,
the engine callbacks are simply a sequence that gets called when a particular thing happens (i.e. Post Step).
There's three types
SequenceFile (for steps that execute in that sequence file whether it's a client sequence file or a process model)
ProcessModel (for steps that execute in the client sequence file run under this process model, but NOT the steps in the ProcessModel)
Station (for all steps on that installation - found in the StationCallbacks.seq sequencefile)
If the engine callback appears in more than one of the three places, then the lowest one (seq file->proc model->station listed lowest to highest)is used.
In your case, you could use any of them depending on your architecture.
Personally, r
emoving from the resultlist is easier than working out whether to add to it, but that gets tricky when you have steps which loop.
If you decide to make up your own add, then the PostStepFailure is the callback sequence to use (go to edit->sequencefilecallbacks). You'll have to add a new element to the resultlist, and start fleshing it out with the result container of the step (which you still have access to as a parameter) plus the TS container.
This would go into the Runstate.Caller.Locals.ResultList[x]
Also, don't forget to disable the result collection on all the steps in the test sequence, plus all the ones in your poststepfailure callback, since you're doing your own.
I'm attaching what I've done so far as an example - not quite finished, but it's done the TS container. Just now need to do the actual result container.
I'll keep working on it but for now you can see what I'm getting at.
Hope that gives you a kick start with the callbacks bit
Sacha Emery
National Instrumen
ts (UK)
// it takes almost no time to rate an answer
Attachments:
collect_only_failures.seq ‏31 KB

Can test stand execute LabVIEW executables ?

Similar Messages

Maybe you are looking for