NI TestStand Idea Exchange

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

When there are a lot of variables defined an Sequence / Sequence File, it would be nice to beable to group them to help use and readability.

group_of_variables.png

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

Hello,

 

It should be nice to be abble to view the UIEvents directly in TestStand SeqEdit.

 

This could be helpfull during debugging a sequence.

 

The idea could be done like a Debug / Trace window.

 

It should also be interresting to have such a "UIEvent callback" in the process model. 

 

Manu.net 

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.

I have extended the multi-numeric step type to use the string and Boolean comparisons.  We have several tests that require string verification to match the exact string and to verify the string format. Therefore I have added the ability for the multi-numeric step type to use string comparisons, including regular expression for string testing. 

 

 

  Multi-Measurement.JPG

MultiMeasurement 2.JPG

 

Hello,

 

It should be nice to be abble to refresh the STEP default options, according to it's STEP TYPE.

 

=> This should be made using a "REFRESH TYPE" command in the contextual menu (Right CLICK) of a STEP.

 

 

Manu.

Right now I can configure search directories in TestStand, but I am limited.  There are 2 types: either an absolute path, or a "programatic" value (think <current sequence file directory>, <TestStand Public Directory>, <Windows Directory>, etc).  However, these "programatic" values cannot be modified.  I would LOVE to be able to configure a new search directory of "<Current Sequence File Directory>\LabVIEW_files\*", or "<Current Sequence File Directory>\..\Code Modules", but TestStand doesn't support adding modifiers to the ends of those paths.

It would also be nice to be able to specify <Current Process Model Sequence File> as another value.

This would help greatly with being able to move files around, and limiting the total number of search paths, and limiting the cross-linking of finding the wrong code modules for individual sequence files.

I have a bunch of times that I need to round a numeric variable in TestStand

example: Locals.A = round(Locals.B)

 

However, it's actually more complicated than that because I need to round it at the Nth position after the decimal point (for example).   This means my expression becomes something like Locals.A = pow(10,-Locals.Digits) * round (Locals.A * pow(10,Locals.Digits) )   (for Locals.Digits == 3, this means that Locals=A becomes 0.123 when Locals.B is 0.1234)

This is a lot more code than I really want to write.  If I am doing the same thing in MS Excel, I just say $B5 = round($B4,$A$1) or something like that.  Notice how the digits of precision to round to is built into the round function.  I'd love if TestStand round function could be expanded the same way

Round(Number, [option], [Digits])

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

I know that I can deploy station globals by adding the ini file to my workspace but when deploying them I want the Station Globals to be merged with the existing station globals on the deployed machine.  Please add this as a feature to the deploy utility.

 

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.

We found a need to customize the NI version of this step to give more functionality.  Our edits updates to allow multiple response text boxes (up to 10), and we added an option to configure the response to be a list controls rather than simple strings. Just added a Boolean to switch to list box and then the user just gives comma separated list of options with the default item first as the initial response string.

Modified Message Popup

This is a simple change to the step and allows far greater flexibility for the step type (also it was easy to make the step upgradeable from the exiting step version maintainign the functionality if one or no string responses being used).

These features are very useful for collecting all UUT information during PreUUT rather than having to throw up popup after popup or create a custom module with a popup in it.  Would be great if these features could be included in the standard NI step.

When working with multiple long sequences it would be nice to bookmark locations making it easy to find where you were previously working.  The bookmark could be line highlighting or an icon on the left gutter.  Bookmarks would be saved with sequence.  Multiple colors or icon would be available.

 

 

SequenceEditorStepHighliting.jpg

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

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

Sometimes, it is useful to have "access to TestStand applications" without showing a GUI.

So it would be nice, if there were an additional example in the User Interfaces folder (in addition to Full-Featured and Simple) which does not display an UI during execution. The control over "which sequence is to be executed" should be primarily done by command line parameters, popup panels as alternative.

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

Currently you can right click the insertion palette and change the position / menu items that are shown / hidden in the insertion palette from a context based dialog box. (can also be done from the same box in the type palettes view).

It would be useful to be able to modify this programatically.

Currently you can only programatically play with the typepalettefilelist from the engine property object and insert new ones or remove old ones.

If a sequence file is loaded that has a step type in it that is not currently loaded by a type palette file, then it shows up in the insertion palette (as it should do), but if the testexec.ini file says this should be set to "hide" then it is hidden.

 

Thoughts

Thanks
Sacha

The default process models internally enable/disable the PostResultListEntry callbacks in ways that aren't intuitive to users seeking to quickly edit a callback to customize/override behavior. 

 

It would be nice to see that instead of simply turning off the callback (leaving users to wonder why their override doesn't work like all the others, except if they read the help/ or think to turn on 'on the fly reporting') as part of the process model based on the options....

 

(1) leave the callbacks on and move the 'on the fly' logic into an IF defined section within the sequence

 

(2) make a second PostResultListEntrys  style callback that's explicitly for 'on the fly' that is in addition to other PostResultListEntry behaviors that a user may want to enable/add.

 

I've had several customers now who have designed custom event loggers / reports around the ProcessModelPostStep callback (with some rather convoluted logic where they dig for results)  simply due to the fact that they couldn't understand why their PostResultListEntry callbacks didn't work.... or that they didn't feel comfortable editing the process model in order to remove the logic that force the callback to be disabled when not 'on the fly' and also keep the 'on the fly' reporting unharmed if they want it later.

 

Cheers,

 

Elaine R.

It would be great to have an OTB TestStand type to support LabVIEW complex numbers, at this point (TS4.1) you have to map each component individually even if you create your own type with the same components.

 

Thanks!

 

<<-N->>