NI TestStand Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

Please include Wait(x mSec) or Delay(x mSec) operation as one of the method in sequence context, so that this can be used in Function Statement step, Post action of any step to force the step to wait for few mSec after completing it's operation. This is to avoid explicit inclusion of Wait step and majorly useful during looping a step and provide delay between each iteration.

I'd like to be able to specify the username, password, and local & remote paths by expression:

 

18787i328326F4E8289180

It would be very handy to have a jump list of recent/pinned files for TestStand.  This could also include simple tasks like creating a new sequence file.

 

Current:

 

Current TS.png

 

Proposed:

 

Proposed TS.png

Defining a custom step type is an iterative process getting the Post Step VI, Edit VI, Step Type Fields, etc. all matched up and working together.  I often tweak controls and indicators throughout the process.  If I have defined the substeps in TestStand, that means reloading the VI prototype throughout this iteration.

 

Custom Step Type Properties.png

 

Reload Proto.PNG

 

If my controls/indicators are numerics, strings, or arrays of either, the existing parameter values are retained during the reload.  Containers are different, however.  If the cluster input of the VI is unchanged between the exisiting prototype and the reloaded version, the container parameter values are retained.  My complaint is that if one element in the cluster changes, the entire container gets thrown out during the reload.

paramter assignments.PNG

 

In this particular case, all I did was change a cluster element from an array to an element.  Nothing else (cluster labels, etc.) changed.  Because of this, the entire container gets thrown out during the reload along with 30+ values that I had assigned.

 

Unfortunately, I find myself doing this multiple times during development so the time it takes to re-type everyhting adds up over the entire dev cycle.

 

My idea is to have container values retained (similar to non-container values) during a VI prototype reload.

 

Thanks,

Jacob

Currently there is only the "Create type from struct" button available, when there is an parameter, that requires an array of structs, in a .NET call

2016-07-13_15-53-49.png

 

What would be nice, is to have the features available, that are available when passing clusters to labview:

2016-07-13_15-58-35.png

 

That is: 

  • The Add Array Item button
  • The Delete/Delete All Item buttons
  • The feature of 'uncollapsing' a struct and setting the values for each field in the struct.

 

When a 2d array is added to the report as table, you get the following table:

 

 

[0][0]  00

[0][1]  01

[1][0]  10

[1][1]  01

 

It would be better to have a table like this:

      [0] [1]

[0]  00  10

[1]  10  11

 

Currently this needs to be implememented in the stylesheet. But for a lot of users, this is a complex workaround.

 

 

Background --

I LOVE the autocomplete feature within any of the formula windows.  Start typing Locals.F, and it allows you to autocomplete to Locals.Foo.

 

However, if you have Locals.Foo1, Locals.Foo2, Locals.Foo3, etc, you need to keep typing until you get enough to uniquely match the one you want, or start using the arrow keys in the list (or select with a mouse).

 

The problem is that if you just type Locals.F, the list of items that shows up is the entire list of Locals.*, in the order they are in Locals.*  In reality, once I've typed Locals.F, I should only get the locals variables that start with F, so I don't need to down arrow through all the other Locals.Bar1, Locals.Bar2 that are inbetween Locals.Foo1 and Locals.Foo2 (because for some weird reason I really want the order of my locals variables to be Foo1, Bar1, Bar2, Foo2, Foo3).

 

So, let's restrict the autocomplete function to only show the items that match what I have already typed, or at least regroup the matching variables at the top of the list so they are easier to select from.

 

Even better would be to have it context aware.  If the formula I am typing is "Locals.MyNumber = 3.1415 * Locals.F", and Locals.Foo1 is a string, Locals.Foo2 is an array of booleans, and Locals.Foo3 is a number, then it should skip over Locals.Foo1 and Foo2 because the context requires a number.  Foo1, Foo2, Foo3 should all be in the list of items to choose from if I want to arrow up or down in the list (or use a mouse to select), but Foo3 should be the "defaulted" item that is used if I just hit enter after Locals.F.

I know that I can write my own sequence analyzer tasks, but I think this one should be default out-of-the-box from NI:

 

Add a sequence analyzer warning task that checks for usage of obsolete methods / properties / events.  This way we can use sequence analyzer to help find them and make our code easier to upgrade with future versions of TS

 

Otherwise, trying to find all the obsolete "stuff" is REALLY REALLY annoying -- a lot of searching

 

obsoleteAnalysis.png

Since our projects involve several developers working in tandem, we manage all project relevant data under SCM (Source Code Management). This way sharing and exchange of data between developers is much easier. To ensure that all developers can access and use the same TestStand Components – especially the language directory – the TestStand configuration directory is also under SCM control.

During the development process if a developer checks out the project folder, for example to „C:\ProjectX“, then the language folder is available under „C:\ProjectX\TestStand\Components\Language“.

 

TestStand ProjectX.jpg

 

In Teststand there is an option to point the configuration directory to a custom directory. To do this, go under the Station Options – Preferences – Configuration Directory,  and change the default path to our custom checkout path.

 

Station Options.png

 

However, even changing this setting, the language files are still get loaded from the default configuration path. In other words, assigning new custom path (which is „C:\ProjectX\TestStand\Components\Language“) seems to have no effect and the older default location (which is „C:\Users\Public\Documents\National Instruments\TestStand“) keeps getting selected instead.

This means, every developer has to copy the ProjectX TestStand folder into the default location manually a SCM update.

 

Suggested solution: make the whole default location directory changeable, to point to a custom directory. Thus during development of different projects, it is much easier to switch between the projects and to have the possibility to check out the code from a SCM to only one directory (and continue working with them).

Hi,

 

As in the subject: Get the focus out from the OK button in the Expression Browser window.

 

Now, when you write an expression in the Expression Browser and you'd like to go to new line by hitting Enter, instead of going to new line the Expression Browser closes down.

 

O course we can use Shift+Enter combination to get to the new line, but the habit is to hit the Enter key.

 

However, if the focus would be not on the OK button but inside of Expression window the problem would dissapear.

 

K.

In the report options, when you have selected to include measurements and insert graphs, it would be nice if TestStand could provide an option to display multiple numeric limit test measurements in graphical form. To expand on that, when the value goes outside of a limit, it would be nice to have a red point on the graph to show where this occurred at. 

 

mnlt.jpg

The Sequence File Documentation Tool allows you to create documentation in the file formats HTML and text.

 

It would be nice if it could also create XML based documentation similar to report generation. Selecting a style sheet will ensure that the XML file is presented in a certain way using a browser.

 

Norbert

It would be nice if Teststand came with a pre built sequence or example to Generate a Test Report of UUT Results that are already in the database.

Currently Custom Icon can only be placed under 

 

C:\Users\Public\Documents\National Instruments\TestStand 2014 (32-bit)\Components\Icons

and

C:\Program Files\TestStand 2014\Components\Icons

and also from 

search directory option for icon (New Idea)

 

If icons can also be loaded in path mentioned search directory, It help a lot in handling things among a large ATE Team (50 Test Developers)

 

11111.png

 

Although BuildTSD allows for builds from the command line, they are still not automatable because someone must be logged in for the run to work. All of our other build tools (Visual Studio, Eclipse, MPLAB, Quartus, NIOS, Matlab, etc.) allow for headless, remote, automated builds which support our move toward continuous integration, continuous deployment, and agile development.

When you are running an execution and you want to check if a step will execute or not depending on the precondition you have to go to the step, browse to the precondition, copy it and paste it in the Watch View...

 

Wouldn't it be great if you could add your step precondition the the watch view with a single click (like VS "Add Watch")... ideally I'd have another entry in the menu below called "Debug" ot "Watch View" with submenu-items: "Add Precondition to Watch View", "Add Pre-expression to Watch View", "Add Pre-expression to Watch View"

 

ideaxchange.png

 

Vote for me!!!

 

<<- N --.>

Can we have the UI show a different status for a disabled socket?  It shows the socket as "Completed [Passed]" if I disable a socket when running the batch model.  This seems misleading.  It should say "disabled" and maybe have a null symbol icon or something to signify that it didn't actually pass any test.

Create a step type that is similar to the multi-numeric limit step type except that it handles the 3 basic data types: Numeric, String, Boolean.

 

We use sub sequences as our "tests".  Because we don't like indentations on our reports and all of the information is relavent to the "test" and we want it grouped it would be nice for the step type to handle those basic datatypes. Also, the report looks messy with all the indentations....granted that could be overcome with some tweaks to the style sheets and such.

 

You could have a BooleanArray, StringArray and NumericArray as step properties to hold the data source info.

 

This step type would eliminate all of the test types.

 

See attachement.

Right now it is pretty easy (Thanks guys!!!) to go from a variable that is of a custom type, and find it in the types palette.

viewtype.png

 

This is great, and it should just stay the way it is.

The problem comes when you have an array of type "FOO".  When you try to do this trick on the array of type FOO, it doesn't work.  Arrays of type "Foo" are common enough, and it would be great to be able to go directly to the type definition for the array element, something like this:

 

viewtypearray.png

(I could see removing the "Types" selection right above the new element circled in red -- it has limited functionality even now).

 

Every so often it turns into a mess of trying to do math in TestStand.  Or manage arrays (finally got some of that cleared up in TS2012).

LabVIEW "solved" some of that by implementing formula nodes, which are kinda just like the expressions we currently have in TestStand.  Then they realized that formula nodes didn't have all the functionality that users needed, and why not just expand to a "industry standard" and implement MathScript.  Why can't TestStand do the same?  Build the MathScript engine into the TestStand distribution, and allow us to write expressions (or at lest a 'mscript statement step') in mscript format.  This would help remove pressure from adding more functionalty to the TestStand API (since a lot of it would already be built into mathscript language).

 

I could imagine writing a statement like Locals.MyArray = Mscript.ones(15)