From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

NI TestStand Idea Exchange

Post an idea

View All (8)

Hi,

I have a table in file globals (2D array).

Each column of the table has an associate variable in file global.

For i want my custom step to run N time which is the number of rows in the table.

In each iteration, i want to take each value of the row and assign the value to the asscoiated variable in file global.

so, i want to have a looping mechanism in the expression.

I guess it is not explicitly present right now. Right now, i use teststand API to update the variable.

It would be nice to have looping in expression. This will improve my custom steps performance.

Regards,

Muthuraman S

View All (2)

View All (3)

NI has gone through a lot work to get the IVI Components integrated within TestStand as step types. I was wondering why NI has not incorporated the NI-DAQmx technology into TestStand as step types. I realize most TestStand developers would just create TestStand Adapters in the sequence step written in CVI or LV to interface to NI-DAQmx functions. Even the more advanced TestStand Developers would create their own custom step types to interface to NIDAQmx. I have just done that to where I have created a framework of custom DAQmx step types that I use as a small subset from all the NIDAQmx functions used from the NI-DAQmx library.

View All (1)

In some cases it could be handy, if you were able to convert a container you've constructed in the variable pane into a type directly from the variables pane.

One case could be, if you chose to store some settings in the sequence file, but the settings are dependent upon fx equipment or the product variant. It can be handy to have a variable with the settings, and an array of settings specific to various configurations from which you can choose. But the 'settings' container and the type in the array of settings containers, of course have to align. And this is best achieved by a custom data type.

Often sequences start out for one configuration only, and later on the need for multiple configurations occurs - and that's why I think it could be handy - if you were able to convert a container, already in the variable pane, into a custom data type.

View All (4)

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)

The Step Type Messaga Popup .

Usually I use the same text in the Step Name for the Title Expression

and for a long time now I have used NameOf(Step) in the Title Expression so as not to have to duplicate the Step Name.

Now that Templates are available I can save a copy this version to use instead of the default step type. But thats only true for my development PC.

This may not be saved on other development PC.

What would be nice if the default value for Title Expression was NameOf(Step) instead of "untitled".

regards

Ray Farmer

A nice feature of reporting is the ability to form the report file pathname using an expression. However, since the path is resolved before the client Sequence file is executed, you cannot use properties populated in the client sequence file as part of the report pathname. Currently the only way to accomplish this without modifying the model or reportOptions callback is by including the <UUTStatus> macro in the path expression, which enables a portion of the process model which copies the report to a new path based on the result of the UUT:

I propose that we add an option to force the report path to be re-evaluated after the client sequence to allow users to include properties evaluated in the client sequence file in the report file path without needing to include the <UUTStatus> macro. (basically exposing the ReportOptions.NewFileNameForEachUUTStatus property in the dialog)

Hi,

I think this Thread should be placed here.

http://forums.ni.com/t5/NI-TestStand/How-to-create-a-build-in-User-StepType/m-p/1134151

The aim of this is that users can create the same powerful steps like that once which comes from NI.

Biggest enhancement of this would be that i can get rid of the "edit" - button and there is no floating panel

somewhere else.

The second enhancement is that i may use drag and drop between the edit and variable panel (if this is neccessary).

Like Manooch_H I am interrested in comments, too

Regards

Juergen

View All (3)

The MOST annoying part of working with TestStand is the fact that the developer has to re-enter e-v-e-r-y bloody value for a given parameter when the prototype changes in a LabVIEW VI. I seem to recall that older versions of TestStand would allow the user to do that, but the more recent version don't. Maybe my mind is playing tricks on me and this was never possible..

In any case... When dealing with two parameters which have over 300 (yes!! THREE HUNDRED) entries, this is a bloody nightmare!! Doing it once is nightmareish.. Doing it multiple times is a death sentence!!! Sidenote: I inherited the code and cannot change its structure...

In this particular case, the valeus are all Locals.

The first idea on this subject is to allow editing the original parameters when making changes to a prototype (LabVIEW or any other source). Or as the sister idea to this one, allow to Copy & Pate the contents of a container! See this thread!

View All (1)

It would be nice to have some kind of Custom Step which gets triggered when a step is deleted from a sequence. Something very much similar to "OnNewStep" which is triggered when a Step is dropped into the sequence.

We may have an option, say, "OnStepDeletion" to detect the deletion of a step. This will be very helpful in many of the step usages.

The TestStand Flow Control Steps like "IF" and "FOR" use the "OnNewStep" to create an "END" step along with them when they are dropped. But there is no means to automatically remove the created "End" when the "FOR" or "IF" Steps are deleted from the sequence. The proposed "OnStepDeletion" can be handy in such cases.

I hope you all will support this idea as it will make many of the functionalities more efficient.

Regards,
Nitz

(PS : Forgive me if anyone has posted this idea already. I couldn't find any such posts)

View All (1)

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

How can we help?

Please enter your information below and we'll be intouch soon.

This field is required

Preferred communication method

Email Phone call

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

NI TestStand Idea Exchange

Order Types Alphabetically in Type Selection Context Menu

Make "OnNewStep" its own subStep type

Looping inside the Expressions

Allow the sequence parameter to be used with default value if none specified

Step Types for NI-DAQmx

Display sequence in a tree structure

Create Custom Data Type from Variable Pane

Ability to drag and drop sequences from the Sequences pane into the steps pane

Tool to create Sequence from Highlighted Steps

Add ability to search for instances of custom data types

Change the Default Title Expression from "untitled" to NameOf(Step)

Add option to force the report file path expression to be evaluated after the client sequence executes

Ability to create user built-in StepTypes

Property loader JSON support

Enable mouse button navigation

Define Variables as Constant

User Defined Expression Functions

Allow to edit parameter when prototype changes

Add some OOP feature to a seqeunce

Custom Step to detect "Step Deletion"