NI TestStand Idea Exchange

Post an idea

Add feature to allow commands and sequences created in Tools->Customize->Customize Tool Menu->Add Tools Menu Item.
When customer creates a command or sequence in this section he would like to put it in the toolbar for quick access , TestTand does not allow this task. TestStand allows the toolbar customization for items that are TS native basically

TestStand Container Parameter

Hi,

it can be a simple and stupid question, but I don’t get why, when I define a container as a parameter of a sequence called in the main sequence. That parameter can’ be expanded to fill the different field with the variables that I need. I created also custom type variable for trying to achieve this aim but nothing. I thing that passing a container as parameter can be helpful in particular when you need to pass a lot of variables regarding the same “object".

Best Regards,

Zuc

Download All

View All (3)

View All (1)

View All (2)

Array Literal Support for Named Types

I would like to ask to add named types support for TestStand array literals. The current behavior is described as follows:

Declares a one-dimensional array of numbers, strings, Boolean values, object references, or containers. If all elements are of the same type, the result array is an array of elements of that type. If all elements are not of the same type, the result array is an array of containers.

I would like it to be more or less like this:

Declares a one-dimensional array of numbers, strings, Boolean values, object references, containers, or named type. If all elements are of the same type, the result array is an array of elements of that type. If all elements are not of the same type, the result array is an array of containers.

The problem with the current implementation can be seen on the screen.

It is not a bug (BUG 1828580 to be more precise), it is a feature.

If I call a python function within the TestStand Python adapter the arguments for the functions must be according the order of the function which isn't Python like. This means the order of the arguments in TestStand must be exactly the same as in the Python function, the name of the argument is ignored.
It would be really nice if the TestStand Python adapter would support Keyword Arguments as well.

https://www.scaler.com/topics/python/types-of-function-arguments-in-python/

View All (2)

Background

Under the Installer Options tab, there is a button called Advanced Options.... (help linked)and then a section for TestStand Specific Settings. This section allows a user to specify where the configuration files will be located when running the TestStand runtime engine on a deployment machine. See screenshot of help discription and then of the utility below:

Help

TestStand specific settings.PNG

Screenshot of Deployment Utility Section

Deployment Utility Advanced Options.png

Recommended Change to Documentation

When looking at the help documentation, it does not detail what each of the possible destination directories are pointing to. However, if we move to the Distribution Files tab section of the help, there is a detailed list. See this example link here https://www.ni.com/docs/en-US/bundle/teststand-api-reference/page/tsref/installation-destination-options-distributed.html

I recommend making a quick link to this same page to clarify the directories that can be specified for Cfg files.

View All (3)

Empty Array Literal

Currently, there is no unambiguous solution for passing empty Array of X (where X is a different type than 64-bit Floating Point) as a sequence parameter. If we use {} it is assumed to be of type 64-bit Floating Point. To have an empty Array of Strings we can use ambigues Split("",""). I have no idea how to pass e.g. empty Array of Signed 64-bit Integer without creating empty variables.

It would useful to have Empty Array Literals of a particular type e.g.:

{} - default

{}i64 - for Signed 64-bit Integer

{}ui64 - for Unsigned 64-bit Integer

{}s - for String

{}b - for Boolean

{}r - for Object Reference

{}c - for Container

{}TYPE_NAME - for type definition where TYPE_NAME is type definition name; e.g. Path.

Python adapter dict or json datatype

Property loader JSON support

Add a Filter in the Sequence Editor

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)

View All (8)

The concept of TestStand, a sequence. Sequences of groups. Sequences of Sequences.

Pre Sequence, Post Sequence, Pre Test, Post Test. Run as a process, iterates on product instance. Single Up, Multi Up. Is incredibly flexible.

The paradigm is for test. No reason to constrain it to test processes. The paradigm cannot be adapted for an process that runs sequences, and iterates.

Test Stand can be used as a vehicle to build and manage pipelines for Machine Learning Processing. For both training and inference.

For example - I want to do some ML training with hyperparameter tuning. Queue up the variants and run the sequences, compiling the results.

Better Yet, Andrew NG is pushing data centric AI. Use test stand to queue up data variants, train and eval a model. Auto generate the results.

The BIG Tech platforms all support data pipelines.

TestStand has it built in.

NI TestStand Idea Exchange

Quick Preloading Modules when no source for PPL

Native support for maps or dictionaries in TestStand

Add feature to allow commands and sequences created in Tools->Customize->Customize Tool Menu->Add Tools Menu Item

TestStand Container Parameter

Make watch expressions savable and loadable

Deployment Utility : LabVIEW Packaged Library Version Locked to Deployment Version

Deployment Utility File version auto-incrementation option

Array Literal Support for Named Types

Python adapter supporting keyword arguments

Add link in TestStand Deployment Utility Help For Clarity

Empty Array Literal

Support for multiline comments in Sequence steps

Python adapter dict or json datatype

Property loader JSON support

Add a Filter in the Sequence Editor

Expose SeparatorChar property in NI_NewCsvFileInputRecordStream configuration pane

Order Types Alphabetically in Type Selection Context Menu

Add teststand custom step database connectivity functions to automatically retry if a lost connection is encounter

TestStand Sequences for Machine Learning Pipelines

Modificacion de variables en un vi.exe