Home Community Idea Exchange TestStand Ideas

NI TestStand Idea Exchange

Community Browser
Top Authors
View All
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Post an idea
60 Kudos
jeffh12345

Add the capability to express limits in +/-% of expected value in all limits

Status: Completed Submitted by Member on 06-29-2010 06:02 PM 9 Comment

Almost all of our analog measurements are specified in %: example

 

a Power Supply DMM measurement limit is 24.00Vdc +/- 5%

 

We typically have 100+ measurements like this in a project

 

 

Why not include it in the default step types as an optional selection?

I sure would use it, so would my team.

 

I agree that it should not alter existing programs using the default step, but I believe that this feature should have been in Teststand when it was first released.

 

I have run across this in both analog measurements, and the results from an ADC

Think a limit of 0x234 +3%, -7%

 

 

View All (4)
44 Kudos
Al.B

Create a TestStand Example Finder

Status: Completed Submitted by on 03-17-2011 01:20 PM 6 Comment

I have noticed that the TestStand shipping examples are often overlooked when looking for ways to accomplish things with TestStand.  This is not the case (as much) in LabVIEW and CVI, and I feel that this is because TestStand does not have an example finder.  I would like to see some method of accessing the shipping examples through the sequence editor environment, such as:

 

1-1.png

Another problem with the current setup is that the only way to know what the example demonstrates is the name of the folder.  This makes it easy to overlook examples that would be helpful. 

 

I propose adding a TestStand example finder with these features (in order of importance):

 

  • Provide a description for each example (most of this info can be pulled from the sequenceFileLoad callback dialogs in a lot of the examples)
  • have keywords for the examples, and allow searching
  • for more advanced examples, provide a batch file to load all necessary components 
  • Provide links to the NI community and developer zone to encourage participation
30 Kudos
RayFarmer

Tool to create Sequence from Highlighted Steps

Status: Completed Submitted by Trusted Enthusiast on 08-04-2010 01:38 AM 2 Comment

It would be nice to be able to create a new sequence from highlighting steps in a sequence and performing a right mouse click, "Create New Sequence...", this would be a kin to Create SubVI in LabVIEW.

 

This action could display a dialog to give possible options such as, to copy the Setup and/or Cleanup group, Create in a New SequenceFile or in Current SequenceFile, the option to Move or Copy highlighted Steps. It could also include creating any locals and /or  FileGlobals (if creating in a new SequenceFile) used by those highlight steps.

 

View All (3)
14 Kudos
alex_bauer

Option to store an independent TestStand configuration with workspace

Status: Completed Submitted by Member on 06-29-2012 04:51 AM 2 Comment

It would be great to have the ability to create an independent TestStand configuration that is valid in a workspace context. That would allow project specific search directories, StationGlobals an several other configuration items you normally don't want to share across projects on the same test station.

10 Kudos
Elaine_R.

Improve Sequence Analyzer CommandLine to allow for automatic report generation

Status: Completed Submitted by Active Participant on 04-18-2014 07:13 AM 3 Comment

Right now it appears the sequence analyzer has no really effective automation options?

 

I can use the command line to launch the Sequence Analyzer, but I really want to run this puppy headlessly against a codebase every 24 hours similar to how VI Analyzer works.  Ideally, yes, I'd love a full API, but for the short term, would it be possible to expand the command line?

 

what we have currently is:

AnalyzerApp.exe "C:\My Documents\MyProject.tsaproj"  to get the window open with the right project in it.

what would be seriously helpful would be to add: some sort of "-Run -Report "C:\Reports\MyProjectReport.xml""  additional tags?

 

In general I'd love for the tool to (1) launch, (2) run project, (3) save off file, and (4) close without further nagging on the part of a user.

 

 Extra kudos would be given if it could generate a standard-out message with some quick stats, if someone was feeling really gung-ho. Perhaps a # of rules, run and # of errors & warnings found?  I can just as easily rake the xml output, so these aren't required, but I am in dire need of a way to automatically _get_ that xml output.

 

If the tool already does these tasks than please feel free to say so?  I've combed the help in the versions I have installed, and so far have come up with nothing. I'm currently shopping around for a thin ui-robot to get the job done...

 

5 Kudos
RyanWright

Add basic file I/O functions to TestStand

Status: Completed Submitted by Member on 11-14-2013 10:47 AM 3 Comment

It would be nice if TestStand provided basic file I/O functions (open, close, read, write) to complement the other functions already available.

6 Kudos
Peter-R

TestStand Deployment Utility: Have the root directory as an Installation Destination in the Distributed Files tab

Status: Completed Submitted by on 02-23-2012 04:43 PM 5 Comment

Currently, the Installation Destination options are as follows: 

 

 

There is no way to install files to the root directory, or its subdirectories, with the exception of those already present in the Installation Destination. For instance, make it possible to install a file to the following directory: C:\ProgramData\IVI Foundation\IVI

 

View All (9)
3 Kudos
Skeptical

Sequence File Validation

Status: Completed Submitted by Member on 09-14-2010 01:35 PM 3 Comment

I would like a built-in tool in the Sequence Editor that would check my sequence file to verify that all expressions used in every step are valid and that all variables called exist. It would be nice to find errors during development/edit time rather than at run-time. I think this could significantly improve the usefulness of TestStand.

1 Kudos
RyanWright

TestStand - End Modal Dialog.vi should execute even if an error occurred before it runs

Status: Completed Submitted by Member on 05-16-2014 12:50 PM 2 Comment

The behavior of the TestStand - End Modal Dialog.vi should be changed.  The current behavior is for it to not execute if an error occurred before it runs.  Instead, it should always execute, even if an error occurred before it runs.  With the current behavior, if an error gets passed to the VI, it can cause TestStand to hang.  In general, close or end functions and VIs should always execute even if an error occurred before they run because unintended consequences such as errors, crashes, or hangs can happen if they don't execute.  Yes, you can use the Clear Errors.vi before the TestStand - End Modal Dialog.vi and Merge Errors function to work around this behavior, but it would eliminate the need to do this if the behavior of the VI were changed.

0 Kudos
RyanWright

File installation destinations should be the same as the default installation base directories in the TestStand Deployment Utility

Status: Completed Submitted by Member on 07-06-2015 12:40 PM 2 Comment

The TestStand Deployment Utility lets you select the following locations for the installation destinations of individual files:

 

File Installation Destination.png

 

However, you can select the following for the default installation base directory:

 

Default Installation Base Directory.png

 

It would be really nice if both lists of available installation locations were the same, both in terms of locations and naming conventions.  The most glaring omission in the file installation destination list is the Windows Volume location.

0 Kudos
L_A_B

Trim whitespaces in TestStand Step

Status: Completed Submitted by Member on 12-10-2012 02:29 PM 3 Comment

Hi!

 

I was working on a project which required LabVIEW 2011 and TestStand 2010. The software had lots of LV modules already created. I reused some of them. However, I needed to trim whitespaces in TestStand which were coming from the string outputs of these LV modules. Nevertheless, I was surprised to discover that there is no TRIM string function in TestStand at all. I had to create a simple VI which just trimmed the whitespaces. I couldn't modify the previously created modules because they were used elsewhere and could affect the outcome of the other test systems. Why does TestStand lack this simple functionality?

 

Regards,

 

L_A_B

 

View All (3)
0 Kudos
Mustanghipo65

Expression Checker for Sequence

Status: Completed Submitted by Member on 10-29-2010 11:56 AM 5 Comment

Having multiple engineers working on code is an issue for me when a person writing an expression doesn't check for errors. I myself am sometimes a culprit of this. The error doesn't show up until Teststand trys to evaluate it, some code will not show errors if the sequence flow doesn't access the step with errors.

 

It sure would be nice to have a tool that checks for expression errors either in the whole sequence file or a called sequence.

0 Kudos
WiMAX_Eng

New Idea Exchange?

Status: Completed Submitted by Member on 09-28-2010 07:03 AM 4 Comment

I'm bound to see backlash for this one but here goes!!

 

The idea exchange, forum and shipped examples are great for learning and resolving specific issues and requesting features and I use them a lot.  But as kind of a newbie what cool things can you actually do?  I'm talking about a different kind of idea exchange for the purpose of sharing what's possible or maybe how some API functions were used to create a particular feature.

 

Fire away !