NI TestStand Idea Exchange

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

In our Company also hardware developer creates testsequences in teststand, so it would be nice, if there could be a small user interface to configure the values of the parameters for a subsequence.
The solution could be, if they drag and drop a sequence into their main testsequence, a user interface pops up to configure the parameters for this subsequence. So it would be possible to restrict the values with a drop down menu or Radio Buttons or to give some graphical help to choose the right values.


Or maybe i could create something similar to the IVI sequences, where i can click on a button and a small editor window is opened.

It will be good if a "Extract" sequence option present: When we select more than one steps in a sequence, show this option. Once you select extract option, new sequence should be created within the .seq file, and automatically insert a step "Sequence Call" which calls the new sequence.

In synchronization  Notification with Wait as an Operation, then there should be Time Out status (Optional Output, Available as a property now) based on which the user can take decision.

Forgive me for the cavalcade of suggestions this week...


One of my favorite options in the LabVIEW development environment is the "Find all Instances" context menu option, whereby one is able to locate all calls to the particular SubVI.


I have long wished that something similar were available in the TestStand Sequence Editor. I'd like to propose a "Find All Sequence Calls" context menu selection when right-clicking on a sequence in the Sequence pane. This could leverage the Find tool, but save the user from copying and pasting the name of the sequence. (And save the user from configuring the search options to narrow down the results) It'd be nice to be able to define the scope of the "find" operation to either the selected sequence or all sequences in memory, but I'd settle for a simple search of the open sequence.




Mr. Jim





Currently in TestStand, for a Numeric Limit Test, the "Numeric Format" applies to both the measurement and the test limits.  I would like to be able to have different numeric formats for the test limits and the measurement.  For example, I might want my limits to be %.2f (e.g. 1.23-2.34) and my measurement to be %.3f (e.g. 1.345) so that I can demonstrate a certain measurement accuracy.


Pulido Technologies LLC

I would like a new option in the Step Properties -> Run Options -> Results Recording Option.  The new option would appear for Sequence Call steps only and would allow the step to disable results recording for all steps in the sequence being called.  I would like this to recursive and apply even to subsequences within the sequence being called.Disable Recording of Steps in Sequence Call.jpg



If you get memory problems, you had to tune your reports options, result collecting, load / unload modules  .... Smiley Embarassed


These tasks are very long, you have to point all memory consumers first ... It pollutes your test sequence only for memory purposes ! Smiley Frustrated


When you try to modify the result reccording, you will also have problems for your report generation ... 


It should be nice to add a new feature allowing an automatic result list removing, after onTheFly reporting, ontheFly database writing have treted them ...


A kind of "OnTheFly and remove unused results"


When ontheFly reporting, and The OnTheFly database writing are over, the treated resultList should be put in a garbage structure !

Older test results could be removed if memory is needed ... Smiley Wink


I know this could be not simple ... but this could help very much, for big sequences creation. Smiley Happy


Thanks a lot. (TestStand memory dustman !)




As in the subject.


It 'd be good if developers could insert elements (right click on the array elements in the variable pane) in any place of the array, not only - as it is now - at the end.


A coworker of my is taking the TestStand training for the first time and I asked him what he thought.  He has been developing software in Visual Studio for some time now (C#,, etc).  One of his feedback was the extra steps needed to create variable seemed excessive.  His point gave me an idea that I thought would be very nice to have.


Currently, in the expression editor, when you start typing there will be a small popup suggesting existing variables to select.  Wouldn't it be nice that it also gave you the option to create the variable right there.


Say for example I'll need to place my module return data into a variable but I didn't think ahead and create a local variable.  Now, I am in the expressin editor and I start typing 'local.' and then the name of my none existing variable "newVar".  The little popup that shows the existing varialbes detects that what I've typed doesn't exist and gives me a new button where I can create it and assign a data type.  No going over to the variable editor window...



I'm frequently missing that steps are skipped when running sequences. It would be handy to see a steps' background color change when the run mode has changed to skipped or forced pass/fail.



Default log option for " Numeric Array - Graph" , String Array - Array but not formatted properly. Will be good if theres a option to display as table.


TS - Array.PNG

I would like the capability to be able to create my own customized dash board for my own custom step type.  For example,  I would like to create controls (Radio Buttons, Text Boxes, Tabs) on a form that looks similar to the "Call Executable" Step Type. (See Picture 1 attachment). In the default matter, I realize that TestStand allows only 1 button to be inserted on the Custom Step Type Settings Palette for a custom step type. Sure I can create my own custom GUI that allows the sequence file developer to enter the appropriate data in for the custom step type.







It would be nice to VIEW errors which occurs in the process Model or callbacks using a special dedicated window.


Recently, i have send updates to one of my customers, using FTP transfert.

The updates consists of processModel updates, dotNet assemblies ...

During the FTP upload by my final customer, the dotNet assemblies were marked, by windows 7, as "Bloqued" Smiley Frustrated. (For security reasons ...)

These assemblies were called in my process model.

When the final user tryed to launch his application (Operator interface), nothing occurs Smiley Mad! The dotNet assemblies calls fell in error, but without any message. I had to investigate using debugging tools to find out the problem.


It should be nice, in case of "anormal errors" in process model calls, or in callbacks (like frontend callbacks) to launch an error window to view this kind of errors.Smiley Wink


You may say, you should have test the errors and handle them correctlty ... and you're certainly right !

But i get a look to the default processModels provided with TestStand ... and they are coded as i do !!!!

So even with the 'default process model', if an internal dotNet error occurs (missing sub assemblies, no more ressources ... ) the same kind of anormal behaviour could occured !


So having the way to view process Model, or hidden callbacks errors will perhaps be interesting ! Smiley Happy


Thanks a lot.





It would be nice to be abble to define the report file name "using tags". Smiley Happy


For the moment the Report name is created automatically. You can't easily change the order of the filed you want to see in the filename.Smiley Sad

You can only modify the date/time position.


I would like to see something like this :


Reportname = [%T<YYYY_mm_DD HH_MM_SS>]_[TestSocket]_[UUT].txt






PS : I am using TestStand 2012 ... perhaps this already exists in TS 2013 ?





Now the Evaluate() command cannot resolve names when the name to evaluate is within the square brackets []. In other words if the name to resolve is a part of the index.


It would be demanded the Evaluate() doesn't have this limitation.  



It's a very likley to happen that during the test the one LV module is called more than one time. As well it is very likely to happen the during the development we have to modify the module itself by changing the input/output from the VI or the connector pattern of the VI. If we have to Reload VI Prototype in one or two instances it's fine but when the step is in more than two or three places it is very painfull to update all of them.


So, I'm proposing to extend the Step Settings-->Module menu by adding the button with action Reload VI prototype in all instances.



As in the subject. Now when you would like to do new line by hitting the enter, whilst you are in the Expression Browser - > Expresion field (marked with yellow), the Expression browser gets closed.


It would be good for visibility if the new line creation would be allowed in this field.





Exactly as in subject.


When code modules containing termination monitors receive the terminate signal, the arrow still pointing at them eventhough the current action is one of the action from the clean group.


It'd be good if the developers and operators could see the current operation as it is in real, not the last active from before termination.





The ability to type in a property string to search for:


properties finder.png