NI TestStand Idea Exchange

When putting values into an array of number local variable, there is little documentation specifying the correct way to input values in an array. The documentation needs to be improve and/or the error message that pops when evaluating your statement should be fixed to better demonstrate the problem. The current error states "Variable or property types do not match or are not compatible. This value will cause a run-time error." A getting started documentation that addresses variable syntax would also be helpful, these ideas will improve ease of use for people working in TestStand. The typical syntax when working with arrays is the use of a bracket [] and the error that appears when using a bracket for arrays is even less helpful. Attached is an image of an example of the fixed error that would demonstrate this problem more thoroughly (The red highlighted section would be a potential change to the errors).

Hello,

Could we add a feature to allow the example programs that ship with TestStand 2012 to open up in Windows Explorer directly after clicking an separate option from the help menu?  Currently a help article comes up with a list of the example programs.  Upon clicking a link on one of the example programs the path to the example relative to the <TestStand Public> folder is revealed.  I think it would be easier from a usability stand point to add the ability to open the examples folder for review straight from the menu. 

Cheers!

Shawn S.

Running batch model sequences it would be nice to be able to "Step Into", "Step Over" or "Step Out" for all testsockets with one click instead click instead the need to click on each testsocket before stepping into/over/out.

When developing code for the customization of the User (Operator) Interface, I would like the capability to provide my own custom dialog box for “Loop on Selected Steps” by overriding the standard dialog box that TestStand provides. TestStand provides this standard dialog box when the command kind “Loop On Selected Steps Using” is executed.

The problem in our production environment often is our production technicians are required to (manually) perform interactively with a series of sequence steps and repeat those steps 29 times (Our strict regulatory guidelines). Most of our technicians are technologically challenged in our production environment. In our environment, I have developed the TestStand User Interface to where the TestStand Execution and Sequence Views are hidden to production operators but visible to the developers (engineers) and administrators for trouble shooting capability.

If a custom dialog box cannot be done, at least provide the capability to where I can programmability change the properties of the “Loop On Selected Steps”. At least allow the dialog box to be programmability set to where I can set the number of loops, set the stop condition, stop expression, enable/disable the controls or hide the dialog box without the operator needing to manually entering those values into the dialog box.