When to use TestStand

For simple test flows, what TestStand does is fairly easy to implement with a custom software framework. Is there a rule of thumb as to what kind of application makes sense to use TestStand? I have studied TestStand for about 20 hours now, and I have found it difficult to learn. I don't want to add an extremely complex, single-purpose software tool to my test flow if I can accomplish the same thing with my existing general-purpose tools (LabVIEW in my case).
At one point I had assumed that TestStand was to enable sequential programming to LabVIEW, but I have since learned this can't be the reason. It is not hard to build a command interpreter with LabVIEW that interprets a text file, and can handle data logging, variables, conditional branching, etc. Is TestStand just for users who lack the programming sophistication to build this kind of application themselves?

LabVIEW can be a bad solution for a sequential type of operation (like executing the steps of a test flow) if you only use a long string of vis. A test flow is a long list of events that happen one after another, and it needs to very flexible and configurable. If you just chain together a bunch of VIs, you would get a LabVIEW program 30 screens wide. This is very bad. When I was a LabVIEW n00b I assumed that TestStand had been invented to solve this problem.
I was able to make a solution using LabVIEW to implement test flows without using TestStand at all. I didn't really need to use LabVIEW, I could have used C or any other language. This program was for test set "A". This program works by using a state machine that loads a list of commands from a text file into a queue and executes the commands in order.
I have another test set (platform "B") that I am updating with new software. I am not sure whether to re-use my old state machine code, or to try TestStand. At this point I am very disappointed with TestStand. It is very difficult to learn. It has aspects like "models" and "callbacks" that add complexity but are not useful for my application. The default user interface and data log format do not fit my needs, so I would need to replace the stock data logging and user interface elements with my own.
So my question to people that use TestStand is, what is the advantage to using this tool vs spinning your own solution? What is supposed to be the core value of TestStand? What is the advantage of spending 100 hours learning TestStand and spinning my own custom interface vs creating my own test flow sequencer?

Similar Messages

NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

This problem seems similar to the post "Resource not found error in executable on development machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards.
I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010. The code was using a custom executive and my task was to rewrite the test using TestStand 2010. I reused the majority of the old code. The old code used NI-5660 to control the 5600 and 5620. When I run my sequence using the LV Development System and TestStand, it runs without any issues. When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues. It warns that the nipxi5600u.dll was not initialized correctly. Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter. The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again.
I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace. I also used Dependency Walker to track down the problems with the nipxi5600u.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32). I have also performed a Mass Compile to make sure everything was running in LV 2010. If I skip the steps involving the 5660, my entire sequence runs fine.
The previous code was running with the LabVIEW Run-Time Engine without any issues. Is there just a step I am missing? Has anyone seen anything like this before? I can send screenshots of errors to provide more detail if necessary.

I have tried some more things and still can't get it to work. I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs. This did not change the results.
When I try to run my sequence, The first error I get is shown in Error 1445.bmp. This happens when I try to use the NI 5660 initialize.vi. If I click ignore, the next error I see is shown in Error -20551.bmp. When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp. When I close TestStand, I get the error LabVIEW Fatal Error.bmp.
Attachments:
Error1445.JPG ‏164 KB
Error -20551.JPG ‏174 KB
Error loading nipxi5600u.JPG ‏9 KB

Vi works in LabVIEW, but not when executed by TestStand.

Hi everybody. I'm using LabVIEW 8 with the Sound and Vibration
Toolkit, and TestStand2. I am planning on using TestStand to
execute a series of performance tests on an audio processing
board. When run independently, the vi (which I have attached
here) runs correctly, and returns a value for the parameter being
tested. In this case it is SNR.
However, when executed by TestStand, the vi seems to run correctly, but
returns a value of "NaN". This causes TestStand to fail the test.
Does anybody know what is going on here? I've checked FAQs and
help files, etc... Why would the vi work on its own but not in
TestStand?
Thanks.
Brett Gildersleeve
Attachments:
SingleChannelSNR.vi ‏173 KB
Test Sequence.seq ‏15 KB

Hi Ray, Thanks for the reply.
Basically, when I run the VI on its own, I see the SNR value appearing
both in the SNR indicator and in the Test Data Out cluster under
Numeric Measurement. The rest of the indicators are empty
(string, report text, status, code, source). My waveform graph
shows an FFT of the signal.
However, when running the exact same VI through TestStand, I get NaN as
the output. The FFT of the signal is NOT displayed in the
waveform graph... strange. No errors are received.
In order to make it easier to debug, I replaced all of the analysis functions
with functions included in LabVIEW 8. Now everybody should be
able to run it. I do a simple THD test this time around. With the VI running
on its own, I get a value of 1.8 as the THD and the Numeric Measurement of Test Data
Out. However, whenever running the test with TestStand, I get a
value of NaN.
Same problem.
Any suggestions?
By the way, what exactly do you mean by "wiring
up the Error cluster and feed in to the Error Out."? I'd
like to try it out, but I'm not sure exactly what you mean. I
already have the Error out cluster wired up, I think.
Message Edited by TheSleeve on 05-22-2006 12:12 PM
Attachments:
SingleChannelTHD.vi ‏159 KB
Test Sequence2.seq ‏15 KB

Is it possible to step into a CVI dll when called by TestStand?

As the question says: "Is it possible to step into a CVI dll when called by TestStand?"
I am sure Ray F. may have a few tricks up his sleeves... Hope you see this post, Ray!
I compiled a dll using CVI. The dll is called as a test by TestStand.
I do have an "exe" version of the code that I use for debug with a testbed, but the behaviour is not the same as testing the actual target while running TestStand. My goal is to get as close as possible to the real events.
Thanks,
JLV

Sorry about that,
There are two ways as I was saying:
1. You can configure the CVI adapter to Execute Steps in a External Instance of CVI (requires CVI 6.0 or greater).
Only go to Configure->Adapters and select the LabWindows CVI adapter and click on configure and select the corresponding option.
After that set a break point in the step that you want to debug.
An external instance of CVI will be launched where you can set break points and step into the code.
2. From CVI Specifying an external process:
In CVI go to Run Specify External Process and enter the seqEdit.exe as the program name (you have to browse to the location <TestStand>\Bin\SeqEdit.exe).
As the argument you enter the name of the sequence file you want to debug.
Now just select Run->Debug SeqEdit.Exe
The Sequence Edtior will be launched and you can set break point in your CVI code and step into it when the step is executed.
Check the Using LabWindows/CVI with TestStand reference manual for more information.
I hope it helps you to get started.
Regards.

Using Teststand, need to know how to select a different active x servers in the labview adapter configuration...

Hi,
When I open TestStand using a seq. file, I can see all the VI's that are called, but when I try to open them for editing, I see this message;
"The labview adapter is currently configured to run tests in an environment that does not support editing VI's. In order to edit or create VI's, you must select a different labview Active X server in the lab view adapter environment"
So, I clicked on all the options allowed to me in the "Module Adapter" (is this the same as the drop down menu (by default)"Labview Standard Prototype adapters") but I was still unable to open the VI�s for editing�
Anyone know how or why?

Hi,
You will find the option under Configure | Adapters...then select the labview and press the configure button.
So if you are not able to do this then it could be because your system doesn't have the LabVIEW development system or you do not have adminstrator rights (Teststand login) or it could be that your VI's have been saved without diagrams.
What are you logged in as?
Do you know if you have labVIEW?
Regards
Ray Farmer

Preuut and postuut sequences are not executing when run using UI. They run when using the sequence editor.

I am using TestStand 3.5 and LabVIEW 8 in a Windows XP environment.
I have a sequence that runs properly when run from the sequence editor. I have made a few minor mods to the simple Operator Interface that ships with TestStand. When I run my sequence using the modified Operator Interface, the PreUUT and PostUUT sequences do not execute. Only the main sequence executes. This also happens when I run the demo sequences that ship with TestStand.
What am I missing?

Hi,
It sound like you are executing the sequences without the process model, do you get a report at the end of the execution?
What are these minor mods you have done?
Regards
Ray Farmer
Regards
Ray Farmer

Memory leak when I use function with bstr_t type

Hello,
I use Visual C++ 6 and TestStand 3.1.
I use the tool: Purify from Rational Instruments to detect memory leak in my code.
When I use in my code, functions from the TestStand API using bstr_t types: GetValString, GetType... memory leaks appear.
Do you have an idea to solve this problem?
Thanks

Breizh,
Etes vous sur que le problèmes soit lié au type bstr_r ?
Pouvez vous me faire parvenir un exemple de code mettant en oeuvre la fuite mémoire?
Raphaël T.
NI FRANCE
Cordialement,
Raphael T

Crash in application by using TestStand 4.0 and CVI labWindows 8.01

Our application often crashes in two areas:
1) Often crash in the case:
    During running, if there is poop, like error message, you want to debug by opening other programs,like notepad.
    It shows error signature:
    AppName: operator Interface.exe     AppVer. 4.0.0.326, ModName cvirte.dll
    ModVer: 8.1.0.271         Offset : 000b9c8a
2) Often crash at the end of test, when generating TSV file.
     AppName: operator Interface.exe     AppVer. 4.0.0.326, ModName msvcr80.dll
    ModVer: 8.0.40727.762       Offset : 00008a8c
We use TestStand 4.0 and CVI LabWindows 8.01. The program is running in our customized operator interface.
But I tried using the default TestStand operator interface, it crashed too.
Also we found it is related PC too. One PC in our lab crashed often, but it actually newer PC with bigger RAM. (Pentium(R) 4 CPU 3.2GHz), 3.19GHz, 0.99 GB of RAM)
The one crashed Less often is Pentium(R) 4 CPU 2.80GHz, 2.79 GHZ 504 MB of RAM.
Hope you can help us to find out root cause.
Thanks

Hi Doug,
Thanks for your reply.
Answers to your queries:
1. We are not calling any DLLs from our sequences.
2. We are only using LabVIEW modules and the VIs are called under LabVIEW development environment and not using Run Time engine.
3. In our case it is always seqedit.exe which crashes. LabVIEW never crashed. Hence I think its TestStand whose memory is getting corrupted.
We are trying to narrow down the issue as suggested by you.
By the time, we have observed a strange thing while the sequence editor crashed.
In our sequence we call a thread which calls a VI to run continuously and collect the data from other modules.
What we observed is that, when the sequence editor crashed (the popup appeared), it was still executing the sequence (running a loop). I was able to break the execution and debug it. All the variables were also having proper values.
But the VI which was running in a separate thread was in surprising state. That VI was showing as executing but actually it was not running any of its code. I tried to put probes inside that VI but they were not updated (meaning that part of code was not runnning). I tried to stop the VI using the abort button but no help. It was not having any effect. I also clicked on the Pause button. The button turned red but the VI didn't halt at any part of code (actually the VI was not at all executing). An other VI which was called by another thread was working properly. I could see it by putting probes in that VI.
If your thought about the memory corruption is correct, is it possible that this VI is somehow corrupting the sequence editor memory?
I am not sure, but I think wherever the sequence execution may be, but the above mentioned VI is always in this state at the time of crash.
I tried to reproduce this scenario locally but it ran without problem for hours
Probably I am still not able to properly reproduce it. I'll work on it further and let you know the outcome.
Regarding your last question, We are using LabVIEW notifier. A VI is called which waits on LabVIEW notifier from another VI. That code is pretty simple it just obtains a notifier and waits on it indefinitely.
Please let me know your views on the above mentioned issue.
Thanks,
- Kaustubh

When to use parallel models?

I am using TestStand to control test execution in a thermal chamber. I am unsure which process model best suits my needs (sequential, parallel, or batch). My requirements are as follows:
Up to 4 UUTs will be tested using a single test system. Each UUT shares assets in the test system. An entire sequence of tests will be run repetitively on each unit for a period of 24 hours. Within the 24 hour period, a single control signal is received from the thermal chamber indicating when tests should be run. (run for two hrs, soak for two hrs; run for two hrs, soak for two hrs �). Typically (prior to using TestStand) the test controller would run all tests on UUT#1, then all tests on UUT#2, then all tests on UUT#3, and so on. At the completion o
f this cycle, testing for UUT#1 would occur again. Each UUT has its own data report generated.
I know the parallel process model allows for the removal and/or addition of UUTs at any time during the test sequnce. Although that is a nice feature, it is not a necessity.
I would appreciate some advice on how to handle this situation. How can I affect the �infinite looping� of an entire test sequence for this multi-UUT environment?

Maz,
in the TestStandI course they stated that the serial model is for serial testing of one UUT after the other. The parallel model could somehow be assumed as multiple serial models running in parallel. The batch model is somehow inbetween or extra. It handles the test of a whole batch of UUTs in parallel, where there are some things to be tested in common.
Of course everything can be coded in every process model, but this would give up a lot of the built-in comfort.
In your case I would choose the parallel model, except there are some steps that need to be done on the whole batch at the same time. Consider some UUTs that must all pass a voltage test where you have just one DMM, and must be cooled down when all are done. This would be a batch model.
HTH and Greetin
gs from Germany!
LuI

What files does TestStand add to a computer when a new TestStand application is deployed?

What files (names and directories) are created when a new TestStand application is installed on to a computer? Does TestStand create a new set of files each time that a new application is installed?

Hi,
This depends on how you configure the installer. TestStand 2.0 and 3.0 contain different methods of deploying a TestStand system. Could you tell us what version of TestStand you are using?
Bob

Why use testStand

I have two questions.
1.) Why should I use TestStand instead of developing my own GUI that I have complete control over? What are the Pros and Cons of using TestStand?
2.) When using testing let's say I create a profile for a Technician to have limited access and to where he can't change the code. During test I have TestStand configured to stop on failure. Will I be able to log in as an Admin and begin to troubleshoot or will I have to finish the test as a technician and then log in as an admin after the testing is finished? This is very import for me to do during a test. Especially since some of our tests can take a very long time.

To question #1, With TestStand I have found that you can still have "complete control" over the GUI. It all depends on where you want to start. I think the biggest pro that TestStand has is it gets you a jump start into developing a test without the initial overhead of developing the "common" functionality (reports, loops etc). This jump start assumes that you are not going to change some of the underlying, out of the box, functionality. For example, you can start testing right away if your needs can utilize the existing process model and Operator Interface (OI). With that said, TestStand still provides all the options you would need to create your own test environment built on the TestStand API. You can create your own custom interface with the operator. This can be developed in multiple languages (LabVIEW, C++, C#, etc). You can create your own process model specific to your needs. So, don't think that TestStand will impede you from having full control. It will just be in a different format. As for Cons, I'll leave the meat of this to someone else. I have not found any Con for using TestStand (except maybe the price)
For question #2, Out of the box, I am not sure if it will perform exactly as you describe. A well written, custom operator interface and/or test sequence, should possibly perform the tasks. I question at what level you will need to "change the code" after the test has started or if you are just looking for debug tools (such as pausing, stepping, changing flow and interacting, etc) which TestStand definitely has. Also, you describe a "stop on failure" but indicate in the next sentence not having to finish the test. In this example, would it be fair to characterize that are you describing more of a pause on failure condition? In which case, you login in, while paused, and perform any debug capabilities authored under the permissions of your login level(?). For the example I just describe I think that changing the user via the login-logout mechanism built into the OI and sequence editor will terminate the current execution. This doesn't mean that you can not change the user and permissions; just that you will have to develop a new means, again, most likely a customized OI.

How to play Windows AVI file using Teststand

Hi,
I'm trying to play a Windows AVI (*.avi) file using the Windows Media Player, launched by
a Teststand CallExecutable type step.
When the step executes, the Windows Media Player app. starts o.k., but the file to be played
causes an error which states the file type is not recognised.
Yet if the AVI file is selected in Windows Explorer, it runs fine, i.e. the file type is associated with
Windows Media Player.
If the 1st error is ignored, a 2nd is displayed. This states the file cannot be played, and suggests that
the path may be incorrect or the server is unavailable.
When configuring the Teststand CallExecutable step, the Argument Expression field contains the full
absolute address of the AVI (*.avi) file to load and play.
I have also tried using an expression and also placing the AVI file in the same directory as the
Windows Media Player .exe, but the file will still not play.
If I use the Run utility from the Windows Start menu, I can enter the same details on a single command
line, and the AVI (*.avi) loads and plays just fine.
What should I do to get Windows Media Player to run the AVI (*.avi) file using the Teststand CallExecutable step ?
thanks,
Gary.

Gary -
FYI, with TS 3.5, the MessagePopup step can also display html files. The html file can reference the player control and tell it to run immediately. The html code looks like this:
<HTML>
<HEAD>
<TITLE>Multimedia Control Page</TITLE>
</HEAD>
<BODY LANGUAGE = VBScript>
<p>
My header text
<p>
<object classid="clsid:6BF52A52-394A-11D3-B153-00C04F79FAA6" id="WindowsMediaPlayer1" width="300" height="200">
<param name="URL" value="c:\windows\clock.avi">
<param name="rate" value="1">
<param name="balance" value="0">
<param name="currentPosition" value="0">
<param name="defaultFrame" value>
<param name="playCount" value="1">
<param name="autoStart" value="-1">
<param name="currentMarker" value="0">
<param name="invokeURLs" value="-1">
<param name="baseURL" value>
<param name="volume" value="50">
<param name="mute" value="0">
<param name="uiMode" value="full">
<param name="stretchToFit" value="-1">
<param name="windowlessVideo" value="0">
<param name="enabled" value="-1">
<param name="enableContextMenu" value="-1">
<param name="fullScreen" value="0">
<param name="SAMIStyle" value>
<param name="SAMILang" value>
<param name="SAMIFilename" value>
<param name="captioningID" value>
<param name="enableErrorDialogs" value="0">
</object>
</p>
My footer text
</BODY>
</HTML>
Scott Richardson
National Instruments

Dis-advantages of not using Teststand source control feature.

I'm in the process of creating a Workspace file for our project, primarily because we want to use the Teststand Deployment Utility.
Included in this process is the choice to use Teststand's source control features.
So far we have been using Microsoft's Source Safe application directly to provide source control with no problems.
But now, having tried to incorporate Teststand's source control feature, which utilises Source Safe, I find myself getting bogged down in a tedious and time consuming process which I feel will eventually cause more confusion and errors than it prevents.
If we choose not to put the files in Source Control when the Workspace file is created, do we run the risk of problems at a later stage ?
Thanks.

Hi Gary,
there's no "risk" as such, however by not useing some sort of source code control or configuration management, you are making a definite commitment that you will not roll back to a previous version, and you'll be doing your own backups, and making sure that if several people require access to a particular file at the same time, that only one person is going to be allowed (by agreeing to it) to modify the file.
There's nothing that says you have to go through the TestStand sequence editor and the other workspace and projects to do the source code control.
If you prefer, then use Visual Source Safe as a stand alone interface, and check out the files by hand to your local drive, and then work on them, and then check them back in once you're finished.
Of course, you have to make sure that your relative and absolute paths are correct when you do check out the files.
By going through the TestStand sequence editor to check in and check out files, it's more convenient for most people, since they don't have to dive around two environments (TestStand and VSS) to get to the point of being able to modify a file, or even find out if someone else is modifying it.
Hope that helps.
Thanks
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

AVG Secure Search appears when I use Google Search from my Home page only.

My home page is the Firefox default page with the Google searchbar. I like getting occasional messages from Firefox when I log in so I don't want to change my homepage. However, when I use the searchbar ''on my homepage only'', I get the unsatisfactory AVG Secure Search results.
UPDATE: I now realize all the troubleshooting information I included in my original question appears under the "More System Details" link next to the question, not in the body of the question. I have copied it here to make it easier to see what I have already done to try to solve the problem, as well as describe the one clue I have that may be relevant:
I have tried all the fixes on various threads, but my about:config is now pristine (no avg or isearch mentions; keyword.url is default). Closest solution is that at https://support.mozilla.org/en-US/questions/866327 , which requires changing my home page.
Oddly, AVG Secure Search is ''not'' a problem when I use the Google toolbar or search from the Google website, only when I use the search bar that appears on my home (start) page. This is true even when I return to my home page--if I search from the Google search bar in the middle of the page, I get sent to AVG Safe Search. (isearch.avg.com).
I read in one thread a suggestion to delete my chromeappsstore.sqlite file in my Profile folder. As promised, Firefox created a new one when I restarted it; however, the search bar in the middle of my home home page did not work at all. Tried this three times before restoring my original.
I do not have an application that will open a sqlite file, but I tried doing so in Excel and found a cell containing the following:
emoh.:moz-safe-aboutsearch-engine{"name":"AVG Secure Search","searchUrl":"http://isearch.avg.com/search?cid={7A3C25A0-E345-4507-AA31-D98F596A81A9}&mid=c48135235ba247d18ac1d14b344db451-addd29eab2809954d5abdf0b991a5b911a297819&ds=is015&lang=en&v=10.0.0.7&pr=sa&d=&sap=dsp&q=_searchTerms_"}
I have no clue what that means, but it is the only thing I can find related to Firefox that still mentions AVG and isearch.avg.com.
At this point my best guess (but it is a guess) is that the chromeappsstore.sqlite file is a key to the complete solution, but I do not have enough knowledge to go beyond and address it. I appreciate any help you anyone can offer.

Here is the way to get rid of the problem once and for all:
http://forums.avg.com/ww-en/avg-forums?sec=thread&act=show&id=196402#post_196402

1)Now I use Lightrom 5.7 how to upgrade to 6 or CC? 2) What is the difference between 6 and CC vercion? 3) When I used lightromm 3, I could see inEXIF the distance in meters till the object I took, in the later virsions that function disappeared, it is ve

1)Now I use Lightrom 5.7 how to upgrade to 6 or CC?
2) What is the difference between 6 and CC version?
3) When I used lightromm 3, I could see in EXIF the distance in meters till the object I took, in the later virsions that function disappeared, it is very sad I am stiil waiting and hope that it would be possibble in the new versions. Or this indication may possible by setting?

1)Now I use Lightrom 5.7 how to upgrade to 6 or CC?
Purchase the standalone upgrade from here: Products
Download CC version from here: Explore Adobe desktop apps | Adobe Creative Cloud
2) What is the difference between 6 and CC version?
See this comparison chart: Compare Lightroom versions | Adobe Photoshop Lightroom CC
3) When I used lightromm 3, I could see in EXIF the distance in meters till the object I took, in the later virsions that function disappeared, it is very sad I am stiil waiting and hope that it would be possibble in the new versions. Or this indication may possible by setting?
Rob Cole's ExifMeta plugin displays the Subject Distance field (and much more). Unfortunately, his Web site appears to be down again. He used to be very active here, but he hasn't posted in several months.

When to use TestStand

Similar Messages

Maybe you are looking for