NI TestStand Idea Exchange

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

I was debugging on a test station and had several watch expressions.

When I came in this morning they were all gone, someone else used that station and deleted them.

 

I think it would be good to be able to save the expressions in a file and be able to load them.

An additional feature would be the ability to load them from a sequence step.

It would be helpful to be able to change the font colors that are displayed for steps in the sequence editor.  This would allow users to identify steps quicker for more efficient editing and debugging.

 

StepColors.PNG

Please allow the TSDU to password protect Sequence Files on build.  This functionality is already present for VI's in the LabVIEW Options.  Why not make this possible for the Sequence Files as well?  If I need to protect my VI's with passwords, I probably would like to do this with my sequence files as well.

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

When using VI Analyzer, one can type "#via_ignore TestName" (e.g. "#via_ignore Spell Check") and then that VI/object won't have those specific test results when running VI Analyzer.  I would like to see this type of functionality added to TestStand.  For example, an individual step could have in its comments "#sa_ignore TestName" (e.g. "#sa_ignore NI_FileByExpression")

 

Pulido Technologies LLC

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.

 

Issue.png

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

For simple operations would be nice to have possibility to drag and drop functions from LV functions palette directly (default step type can be Action)

 

Match pattern insert.jpg

When choosing a VI for a step, if you browse into a PPL, the view shows the directory structure inside of the PPL.  A better view would match what LabVIEW shows: the Virtual Folder layout.

 

I tend to keep my library VIs in a flat directory structure, but organize them in my project with Virtual Folders.  But the PPL view in TestStand just shows the single directory instead of the nice organization that I set up in the project.

It would be really helpful to have a diagram showing the order in which process model callbacks execute for the sequential, parallel, and batch models and their relations to the various test sockets.  The TestStand documentation does contain a list of the model callbacks, but it would be nice to have them in a diagram format so that a developer doesn't have to open the process model files and figure out that information.

TestStand's LabVIEW interface could benefit by being able to programmatically get and set LabVIEW Class Objects using the Get Property Value.vi and the Set Property Value.vi.

 

After much toil with this subject, I've finally come to the conclusion that I cannot get a LabVIEW Class Object from TestStand using LabVIEW. I've tried both the Get Property Value.vi and a combination of property and invoke nodes to no avail.

 

Capture.PNG

The output messages are a good way of sending status messages from the test solution to the end user.  However the control is not available as one of the controls that can be added to user interfaces.

OutputMessage.jpg

Can this control be made available to be quickly added to a UI and linked to the execution view manager.

Also adding some kind of API interface to be able to capture these messages to a log file would remove the need to implement any custom logging mechanisms.  If possible ability to open multiple file logs within the engine at the same time with each file given some kind of filter rules (for example Severity=”error” or ExecutionId=5).  If logs had to be attributed to an execution ID then they could automatically be closed when the execution ended, otherwise the user would have to manually close each file which could get forgotten and TestStand end up with lots of open file references.

Dear NI community,

let me, please, propose the following idea.

 

It would be great, if it is possible to open sequences of the sequence file in different tabs. Currently, only sequence files are opened in separate tab. But, if you need to go between sequences (or subsequences, depends how you name them) of the one sequence file (let's say, to copy-paste some steps from one sequence, to another), one has to click on the sequence in the Sequences tab, and it will be opened in the Sequence View tab, and, meanwhile, the another (previously selected) sequence is not seen. And, one has to click between them in the list there and back, and it's not possible to see two sequences one-to-one at the same time.

 

This is similar to MS Word feature "Open New Window", when one can see the same document but in two windows at the same time. It can increase usability of the sequence editor, and make development a little bit faster...

 

Thanks in advance.

As NI has acknowledged (here, here) for more than 5 years, the Build .sql File button creates schemas with errors.  This is even true for the default schemas in the left of the dialog.  Would be great if NI would go ahead and correct this.  BTW - to create default tables in the meantime, a developer should use a SQL file located here:  <TestStand>\Components\Models\TestStandModels\Database

 

 

TestStand Database Options Dialog.png

The fact that TestStand has now a Python adapter is just amazing.
One thing I'm currently missing is the dict or json datatype which can be used to transfer bigger property data between the python script and TS.
Currently tuple is supported but is limited especially if you have a array property with container in it.

It would be nice when entering in the Find: control to beable to pop open the Variable dialog (as in the expression editor) to select variable names. It could be linked to the Limit Search to: control. Like wise on the Replace control when that window appears. 

 

I know you have that drop down facility on this control but that only remembers what you have previously entered.

 

Find_Replace.png

For TestStand Sequence Analyzer, all the results information/reports include status, user, computer, file, time and results.  However there's nothing to link to what version of the sequence file you actually analyzed (it just has the path to the file analyzed).  It would be very helpful for compliance tracking if the results/reports also included the sequence file version. 

I can add my own test to log this as information, but it would probably be helpful to others if it was included as part of the results header information.

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

I would like to see commands like AllOf, AnyOf, AND, OR, etc. work with boolean arrays as inputs.

It is common to want to place a shortcut to a TestStand User Interface or even a TestStand sequence file on the Windows Desktop for each user of a computer.  This is done by placing a shortcut in the Windows All Users Desktop directory.  Currently, the TestStand Deployment Utility only allows you to create a shortcut on the current user's Desktop.  It would be really nice if the TestStand Deployment Utility allowed you to also create shortcuts on the Windows All Users Desktop so that everyone using the computer could see this shortcut on his or her Desktop.

Custom TestStand UI suggestion.

 

I would like the same functionality as with Sequence Editor when double clicking on Sequence Call step (already configured) and it goes into the Subsequence directly and you can view the SubSequence.

 

I would like to see that functionality in the TestStand Custom UI when double clicking on the Sequence Call step with Sequence View Manager and it goes into the Subsequence so it can it viewed. 

 

This would come in handy when debugging a subsequence and setting break points in the subsequence and then viewing variables during execution.