NI TestStand Idea Exchange

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

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

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

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.

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 --.>

Since TS. 4.5 there is support for .net generics  

For me this was one of the biggest advancement of this release !

For future release it would we nice to have support in the foreach StepType to iterate

though the collection in state-of-art way.

 

At the moment you have to get the size and then use a for-loop

with indexing you desiered element. For doing this you have to use at least

two statements. With foreach and collection support no statement is neccessary.

 

Regards

 

Juergen

 

 

Hi,

 

Many times I need to run the MainSequence after a change somewhere in a subsequence. Because there is no shortcut key for that action (First go to the MainSequence then Execute->Run MainSequence) it is pretty time consuming. It would be nice to have that shortcut key in TestStand.

 

Best Regards,

Jick

I would like to be able to use multiline comments in Sequences. Something like step comment would be enough IMHO. See screens below.

 

As you may see on figure 2, current solution make comment difficult to understand.

 

Fig. 1. Sequence multiline comment fieldFig. 1. Sequence multiline comment field

 

Fig. 2. How multiline comment is displayed in Sequence stepFig. 2. How multiline comment is displayed in Sequence step

 

Fig. 3. Step multiline comment (shortened)Fig. 3. Step multiline comment (shortened)

 

Fig. 4. Step multiline comment (full text)Fig. 4. Step multiline comment (full text)

Hi!  Feature request that I hope is fairly simple to slide into the next rev.  It's incredibly frustrating that a Combo Box's values (for a control wired to the connector pane of a VI) aren't selectable like Enums and Rings in the LabVIEW Adapter.  Instead of seeing a drop down with selectable options, I have to open the VI, (open the control if it's a typedef), edit its values, then see what the values are, close that dialog out, close the VI, back to TestStand and put in the value.  This is all so I can just hard code a value.  This is crazy.  I tested this out in 2019 64-bit, btw, so maybe it's available in later versions, if so, please let me know.

 

Thanks for your time.

If you are using a custom environment file for TestStand 2016 and later, it would be great if, on startup, the splash screen indicated the loaded Env file name and path.

 

As you can see below, in our custom TestStand RTOI we are showing the loaded environment file on the splash screen when it loaded.  The TestStand 2019 splash screen is shown for comparison.

Download All

The concept of TestStand Environments was introduced in TestStand 2016 and allows you to define multiple configurations on a single test station or development PC. It would be nice if there was an option to link a sequence file to a specific environment, similar to how you can set a sequence file to "Require Specific Model" In the Advanced tab of the Sequence File Properties. When a sequence file is loaded, the engine could check to see if the required environment matches the current environment and:

  • Automatically relaunch the app in the correct environment
  • Generate an error
  • Prompt the user for an action
  • Other??

It would be nice to choose the behavior when a required environment doesn't match.

 

If anyone has other thoughts or use cases, please share below.

-Trent

Currently, for limits in numeric limit tests, I am using TestStand variables, values of which are stored in configuration file. These variables are directly set in limits fields, but units - are specified directly, explicitly. 

 

It would be nice to have possibility assign to Units field variable, which value will be unit itself. Then, units for measurements could be also possible to store in configuration file. But, unfortunatelly, now it is not possilbe to assign to units expression or variable.

 

TestStand_UnitsExpression.PNG

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

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.

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

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).

 

This method ensures that the correct test sequence and its corresponding DLL/VI/custom files are run.

 

This feature needs to be optional as during development phase this feature is not desired.

 

Configuration :

User selects the test sequence.

User (optional) selects related files like dll/vi/etc

The checksum of the package is determined and tagged with the sequence.

 

Execution:

User enables the checksum option.

User selects the above sequence to run.

Teststand automatically checks for the sequence checksum and also the checksum of the related files.

 

The sequence will run only if the checksum matches.

The current method of viewing the contents of a 2D array variable can be difficult to read if you have many elements.  My suggestion is to add a feature that allows a right click on the 2D array variable and select a popup to see the array in a row/column format.  It would be nice to able to edit the contents with this view as well.

 

I have uploaded an image of a TestStand view of an array and a LabVIEW view for comparison.  Looking at the LabVIEW version, by having the contents in a row/cool format, adding the scroll bars and index display, I can easily see my array contents.

Download All

It would be nice having feature to update sequence call names automatically

 

 23520iF0E0B5654DD74F4E

 

Why ?

When ever you create (or copy, too) a sequence call step

you have to rename it from "SequenceCall" to another name.

Mosttime the name of the Sequence is is in relation to the sequence.

For Example: You a have a Sequence "ABC" then the Step to it will be most "Call ABC"

So if there is a relation you should be able to rename it automatically.

 

Regards

 

Juergen

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.

 

Expression.PNG

 

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