NI TestStand Idea Exchange

Post an idea

The property loader step allows the source location to be defined via an expression. However, if that expression does not evaluate to a file on disk at compile time you get an error. This isn't always desired behavior, for instance, when used in a plugin architecture.

The current workaround is to include a dummy file which could unnecessarily complicate the software & deployments. A dummy file also has the potential to mask errors that should be presented to the user.

The only validation TestStand does of the property loader source location file is that it exists. It doesn't do any validation on the file contents. So is there any benefit? TestStand properly throws an error if the expression doesn't evaluate to a valid file.

Alternatively, a developer could deselect the sequence analyzer rule "Property Loader source should be proper", but this would disable it for all analysis not just the ones that use expressions

View All (4)

Hello,

CSV Input Stream allow to parse CSV files to input data into a Stream Loop for instance. By default, the separator is a comma (,). I use a non english version of Excel to edit a CSV file, and every CSV format write a semi-colon as separator (;):

A;0;0;2
A;10;30000;5
A;20;15;7
B;75;42;1
B;100;12;0

Using an expression, I am able to dynamically (at run-time) change the property SeparatorChar:

Locals.MyInputStream.AsCsvFileInputRecordStream.SeparatorChar = ";"

I think it could be more convenient to have a direct access to this parameter in the configuration pane, allowing also to check the content of the file before execution with Parse Record Prototype funtions.

Best regards,

View All (3)

Currently, if you create a step type and name it OnNewStep, it will execute when an instance of the step is created. This is pretty confusing to new users - why don't we just have an OnNewStep substep type (like prestep, edit, etc)? Custom steps would then just be meant to be called manually using the Step.ExecuteSubstep() Method as documented in the help.

We could keep the "onNewStep" custom step functionality to maintain backwards compatibility with older step types.

View All (8)

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.

Add Tools to Custom Toolbars

View All (3)

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)

Create Custom Data Type from Variable Pane

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)

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

Looping inside the Expressions

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)

step properties copy / paste

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

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)

View All (1)

NI TestStand Idea Exchange

Remove Property Loader Source Location File Requirement

Clickable Links for Cross Referencing Steps or Sequences from an Expression Comment

Expose SeparatorChar property in NI_NewCsvFileInputRecordStream configuration pane

Make "OnNewStep" its own subStep type

Order Types Alphabetically in Type Selection Context Menu

Step Types for NI-DAQmx

Add Tools to Custom Toolbars

Tool to create Sequence from Highlighted Steps

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

Create Custom Data Type from Variable Pane

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

Looping inside the Expressions

step properties copy / paste

Ability to create user built-in StepTypes

Add ability to search for instances of custom data types

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

Display sequence in a tree structure

Define Variables as Constant

Enable mouse button navigation

User Defined Expression Functions