NI TestStand Idea Exchange

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



Recently I wanted to iterate through ALL my subproperties in the container.


I've discovered that the function GetNthSubPropertyName accessing only first level of subproperties and it doesn't get deeper into hierarchy.


I wonder if it could be an extension to this function - and to all similar functions - allowing iterating automatically over ALL subproperties. For example a new option could be applied here.


Need a search option for searching for TPS like DLLs and providing the Function names of each call.  Also providing a count of each time a function / method is or is not called within a set of sequence files.


It would be very useful to be abe to specify a custom project or workspace when creating a new test using the LabWindows/CVI adapter. 


This would allow developers to always ensure that  any custom macros and source files are always included during development





The vi templates should use the NI reccommeded 4x2x2x4 connector


Also sequence Context should be a required connection and there should be some default documentation

For TestStand Sequence Analyzer:

if you open a sequence analyzer project file in sequence editor and make changes, Undo does not work.

Make Undo work for sequence analyzer project (.tsaproj) file changes.


Right now TestStand Sequence Analyzer only supports Relative Paths with respect to the .tsaproj file.

Change this so we can specify path as Absolute when selecting the file to analyze.


Recently I've discovered misleading TestStand behavior.


In the case where in the sequence we have two steps with the same name and we'd like to refer to the SECOND step via its name like shown below:




TestStand allows us to do this, but during the execution, this reference is bind to the FIRST instance of the step:




In this caseTest D should fail showing result 12 not 10.


So, TS allows me to pick a step I want, however it looks like TS binds it to the first match on the list; so it is a lie.


In my opinion TS should either:

--don't let me do this, or

--implicitly bind it using unique step ID.


Anyway the current behavior (TS2014) is ambiguos and shall be treated as a bug.

In thw Sequence editor, in Tools -> Update VI calls  - > Type of calls To Update -> Process Standard VI Calls another two entries could be added in the combo box. Apart from existing:

    * Report Problems Only (No Changes Will Be Made)
    * Reload Prototype if Modified
    * Force Prototype to Reload

These two options below shall be consider to be added.

    * Resave (recompile?) Code Module (VI)
    * Resave (recompile?) Code Module (VI) with all dependencies

I think this feature could be used in case like happened to me:

I had to update one of my global TypeDefinition (*.ctl) which is called by a lot of VIs from my project. When I did it, a lot of VIs were suddenly unable to load under RTE. So, manually I had to open every VI called by TS and do Open and Save (accepting recompiling) actions. I don't have to tellyou that was very boring and long task...



In the bottom right corner of the Sequence editor window (or in other place if you find more suitable) please display information about type of the adapter server.


For example for LV Adapter it would be information about whether Adapter is set to wok with LV Development System, LV Runtime Engine or other executables. For HTBasis Server it would be HTB Runtime Server or HTB Development Server.




During the development I have to often switch between LV Dev environment and RTE. To do that you have to click three times to go trough modal window to get this information. If you do this often it's getting painful. 



As in subject: Enable implicit cast numbers to string in OutputMessage function.



If you add an array as a parameter to a sequence, you have the option of setting the array bounds. If you set the array bound to [1..3] for example and call this sequence and try to access the array element [3] there is an array out of bounds error. It looks like arrays as parameters with the size N are always seen as an array with the bounds [0..N-1]. Maybe it makes sense to change this to the expected behavior!

The current keyboard shortcut for Undo in TestStand and LabVIEW is "Ctrl+z", which is pretty standard in most programs.


In TestStand the ReDo shortcut is "Ctrl+y", but in LabVIEW the ReDo shortcut is "Shift+Ctrl+z". Both of these are relatively common among various programs, but it would be nice if the two programs used the same shortcut for such a simple and common task.


In LabVIEW, "Ctrl+y" already does something else (VI History), but in TestStand, "Shift+Ctrl+z" does not seem to have any functionality. This means that "Shift+Ctrl+z" could also be used in TestStand without breaking any backward compatibility ("Ctrl+y" could also cause a Redo action to avoid breaking that functionality for those who are accustomed to it).


Other NI software may benefit from this standardization as well, but I am referring to LabVIEW and TestStand in this post.


I know it's a simple thing, but as much as one switches back and forth between the two integrated programs it would be nice if this was common functionality!



How about a Mac version of TestStand? I understand there is a Mac version of LabView.