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
3 Kudos
Josh_W

Make Update VI Calls Tool Work on Type Palettes

Status: Declined Submitted by Active Participant on 03-22-2011 02:19 PM 6 Comment

The Update VI Calls tool only works on sequence files right now.  I'd like it to also work on Step Types in type palettes.

 

Here's the situation where it would be useful for me: I'm working on a set of custom step types for a customer, which use VIs as Edit-Substeps and Post-Substeps. Some of these VIs are shared between multiple step types.

 

The issue that I'm having is that if a customer requests a change to one of these shared VIs (for instance, to add another input or output), then I have to go through and manually update all of the substeps in all of the referencing step types. I've already had a situation where I missed an update of an edit substep. This didn't show up in our automated testing, because it is only run at edit time, but caused an error for the customer which they didn't know how to interpret. Our testing process now has to include manual opening of every single edit substep to make sure they all still work before every release.

 

As part of my validation before a release to the customer, I run the Update VI Calls tool to make sure that there are no broken VIs in the sequence files I'm shipping. The Update VI calls tool already makes sure that I've updated any step modules, but it doesn't catch if I've forgotten to update a Step Type's substeps.

 

And yes, I know, I could write my own tool to traverse a type palette and do the updating myself, but I'd like to see this integrated into the existing tool.

 

 

View All (5)
1 Kudos
pulidotech

Different Numeric Format for Measurements and Limits

Status: Already Implemented Submitted by Active Participant on 07-05-2017 01:34 PM 2 Comment

Currently in TestStand, for a Numeric Limit Test, the "Numeric Format" applies to both the measurement and the test limits.  I would like to be able to have different numeric formats for the test limits and the measurement.  For example, I might want my limits to be %.2f (e.g. 1.23-2.34) and my measurement to be %.3f (e.g. 1.345) so that I can demonstrate a certain measurement accuracy.

 

Pulido Technologies LLC

View All (3)
2 Kudos
V_T_S

Change in LabView typedef should be automatically resolved by TestStand

Status: Duplicate Submitted by Member on 11-28-2012 11:08 AM 2 Comment

It is very common to use a typedef as input or output terminal for any VI. If such VI is used in TestStand either as custom step or in a sequence, then teststand requires a relink of step/sequence whenever the typedef values are modified.

 

Teststand need to resolve this differences automatically, rather than expecting user to relink sequences.

2 Kudos
Perry_S

Timed LabVIEW Message box without buttons

Status: Declined Submitted by on 03-17-2012 10:17 PM 6 Comment

Recently I have had a number of customers ask me if there was a way to create a timed Message box that did not have buttons on it. Of course I told them that there wasn't any. Their requests did get me thinking and I can see that there are times when a timed message popup could be useful. Essentially it would just display a message and go away after a select period of time. I would love to see one. 

 

Regards,

 

Perry S.

 
Labels:
1 Kudos
jrasco

Allow Containers to be Set/Get by Property Value VIs

Status: New Submitted by Member on 07-13-2016 12:59 PM 2 Comment

The "TestStand - Set Property Value" and "TestStand - Get Property Value" VIs do not have containers as an option.

 

Set-Get Property Value.png

 

Is this something that can be added?  I can see requiring a cluster input being part of the Set/Get VI that requires the user to match the names/data types of the container.  This is similar to Bundle By Name where you have to provide an input cluster.

 

PS - While you're at it, please add Array of Containers as well.

Labels:
2 Kudos
RyanWright

Add Sequence File Types to Variable Pane

Status: Declined Submitted by Member on 03-07-2011 11:37 AM 4 Comment

It would be really nice if custom types for a sequence file were displayed in the Sequence Editor variables pane (in addition to being displayed in the Types window).

 

TestStand Types Suggestion.png

Labels:
1 Kudos
Bluegraf

Improve Documentation of Flow Steptypes

Status: New Submitted by Member on 06-17-2015 05:09 AM Comment

According to this forum discussion the Flow step types behave different compared to other step types, making customization hard:

 

http://forums.ni.com/t5/NI-TestStand/Where-does-logic-for-flow-control-step-types-live/td-p/2607349

 

Rectifying the behaviour of the Step types may be out of reach as this would dig too deep into architecture.

But there is a lack of documentation of the behaviour of these steps. E.g. just to mention the fact that step type functionality is in those cases tied to the step type name would help a lot.

1 Kudos
sandyy

Support for creating locals for Image type

Status: New Submitted by Member on 04-30-2015 12:24 PM Comment

Would be great to have Local of type Image. Right now image is saved and retirved for analysis or convert to array to use in other steps.

 

Something similar like the idea ;

 

http://forums.ni.com/t5/NI-TestStand-Idea-Exchange/Support-for-Creation-of-Enumerated-Type-Variables/idi-p/1256014

1 Kudos
XA-LSTOM

STEPS TYPE FOR ALL IVI CLASS

Status: New Submitted by Member on 04-13-2015 10:08 AM Comment

Under TestStand Sequence Editor, a lot of IVI Class are not encapsulated in Steps Type.

It should be interesting to have IVI Step Type because the development and the maintains of a Hardware Abstraction Layer is complex and requires a lot of time.

Under Labview all IVI class are presents. Why not in TestStand?

 

 

 IVI2.png

 Xavier

Test Architect - Alstom Transport

 

1 Kudos
MimiKLM

Add the possibility to define the datatypes described in .net assemblies.

Status: Declined Submitted by Active Participant on 09-01-2014 06:31 AM 1 Comment

Hi,

 

As in subject: add the possibility to define the datatypes described in .net assemblies.

 

Now developers, when they create veriables, can choose from between number, string, boolean, object reference and cointainers and arrays of these as well as from between DatabaseColumnValue, DatabesePropery Mapping, Error, Path, Expression, NI_LimitMeasurement, NI_MSgBoxFontData, NI_LV_DeployLibraryItem, NI_TDMSReference, IVI and LabVIEWAnalogWaveform, LabVIEWDigitalWaveform, LabVIEWDigitalData, LabVIEWDynamicData, LabVIEWClusterArray,LabVIEWIOControl.

 

These two groups of data types are called Custom Data Types ( number, string, boolean, object reference)  and Standard Data Types (rest of them).

 

I'd like to vote the .net types of data which are defined in .net assemblies were accessible from Standard Data Types menu along the LabVIEW datatypes.

Labels:
View All (5)
1 Kudos
StephenGerads

Support use of relative path for image file pathname in message popup step options.

Status: Already Implemented Submitted by Member on 04-21-2011 09:07 AM 14 Comment

Support use of relative path for image file pathname in message popup step options.

Relative paths make reuse and maintanence easier for me.

Image file pathnames are the only part of my code that breaks when I rename my project directory.

Labels:
View All (2)
0 Kudos
vrv

Enumeration of string/expression type

Status: New Submitted by Member on 11-17-2020 05:23 AM Comment

It would be nice to have the option of making an Enumeration of Expression type and be able to use the Enumeration directly in an Evaluate() expression.

vrv_0-1605611723913.png

 

The expression might look like this investigating if "operator" have technician rights Evaluate(Enums.MyConstants.Techincian)

0 Kudos
nclark

Override a Type Def to Cluster Pass - LabVIEW Action Steps

Status: New Submitted by Member on 10-01-2019 03:28 PM 2 Comment

I'm working extensively with LabVIEW VIs and Test Stand, and one of the most helpful features existing is the ability to configure a TestStand type to pass its data to and from a LabVIEW Cluster.

 

I think a great way to expand upon this would be to allow the developer to override specific variables within the LabVIEW cluster.

 

For instance, say I have defined a TestStand type with 5 total variables, all of which may pass to a LabVIEW cluster. If my LabVIEW cluster has at least the same number and type of variables, then this cluster passing has no issue.

 

However, if my LabVIEW cluster has 6 variables, then the TestStand type can only account for its defined five variables, and I am effectively locked out from the sixth variable. I cannot edit the sixth variable, nor can I assign it a default value (see Ex1_broken.PNG)

 

This wouldn't cause an issue if I could override specific variables within the cluster passing. That is to say, if I were given access to that sixth variable from the example, then I could assign it to a local variable. The other five variables would still be satisfied by the TestStand type, and no errors should be generated by the step. (see Ex1_fixed.PNG for what I envision this to look like)

Download All
View All (6)
0 Kudos
David_Grucza

Add Teststand type libraries to give namespace to types.

Status: New Submitted by Member on 08-01-2016 10:56 AM Comment

This idea must already be on here somewhere, but a search did not find it.

Currently, it is necessary to give all types a unique name. So if I have multiple products, all with similar data types, I need to add a prefix to like types. This is the same as LabVIEW used to be. Why not allow for type libraries? This likely means a rewrite of code that loads and manages types, so I can understand why NI would be hesitant.

Labels:
View All (2)
0 Kudos
paolo75

Precondition on Multiple Numeric Limit Test for each measurement

Status: New Submitted by Member on 04-28-2016 08:56 AM Comment

To have shortest TS Sequence will be great the possibility to apply specific precondition for each measurement in Multiple Numeric Limit Test

 

Paolo

Labels:
0 Kudos
NIExpert

Allow Custom LabWindows/CVI workspace or project from TestStand

Status: New Submitted by Member on 01-19-2015 12:14 PM Comment

It would be very useful to be abe to specify a custom project or workspace when creating a new test using the LabWindows/CVI adapter. 

 

This would allow developers to always ensure that  any custom macros and source files are always included during development

 

 

 

 

0 Kudos
NIExpert

Use 4x2x4x4 connector for TestStand LabVIEW vi templates

Status: New Submitted by Member on 01-19-2015 12:09 PM 2 Comment

The vi templates should use the NI reccommeded 4x2x2x4 connector

 

Also sequence Context should be a required connection and there should be some default documentation

0 Kudos
MimiKLM

PropertyObjectType.TypeName - extend the list of returned types.

Status: Declined Submitted by Active Participant on 09-01-2014 08:08 AM 1 Comment

Hi,

 

Now, the PropertyObjectType.TypeName property returns the type name of the named type only.

 

I propose to extend the list of the returned type names to ALL types: build-in, custom named data types, standard named data types.

 

Moreover, it would be good if the NI can be more clear in documentation reminding users what the named type is, as it can be mixed up with the build-in data types.

 

K. 

View All (3)
0 Kudos
SpeeRose

Implement execution timeout option in Adapter Module Configuration/Setting

Status: Declined Submitted by Member on 05-06-2014 10:48 PM 2 Comment

This would be a useful feature to recover from a unreposive code module. Particularly useful, if the code module communicates with the firmware inside the DUT which could become unresponsive due to unforeseen erronous conditions.

 

This option should be optiional. It should be configurable with different timeout values. Once set and configured, then TestStand shall stop executing the code module, return from it and generate an error.

View All (2)
0 Kudos
Hassan_Atassi

Custom Data Type Passing

Status: Declined Submitted by Active Participant on 02-20-2012 06:12 PM 1 Comment

When creating Custom Data Types, in the properties you have the options for "Cluster Passing" "C Struct Passing" and ".NET Struct Passing" by default all of these are disabled.  If find it to be a useless extra step to enable them, and don't see any reason why they can't be all enabled by default.

 

Regards,

Hassan A

Labels: