NI TestStand Idea Exchange

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

LabVIEW recognizes any cluster of <Bool, I32, String> as an error cluster.  TestStand should recognize this as well and default any such cluster output to Step.Result.Error.

 

With the addition of the Silver controls in LabVIEW 2012 "error out" was changed to follow the style guide recommended naming convention of leading caps and is now labled "Error Out"  which is not intercepted and assigned to step.result.error.

A nice feature of reporting is the ability to form the report file pathname using an expression.  However, since the path is resolved before the client Sequence file is executed, you cannot use properties populated in the client sequence file as part of the report pathname. Currently the only way to accomplish this without modifying the model or reportOptions callback is by including the <UUTStatus> macro in the path expression, which enables a portion of the process model which copies the report to a new path based on the result of the UUT:

 1.png

 

I propose that we add an option to force the report path to be re-evaluated after the client sequence to allow users to include properties evaluated in the client sequence file in the report file path without needing to include the <UUTStatus> macro.  (basically exposing the ReportOptions.NewFileNameForEachUUTStatus property in the dialog)

 

2.png

  • Have a spec that declares the name of the measurements signal?- Drag-n-Drop from the doc to the Limits>Measurement name field. no need to copy, select, enter field, paste
  • Know what module you want for the step? -Drag-n-Drop from Workspace or Explorer window to Module Path. I browsed there allready and can start slinging modules in
  • Have a list of Parameter Values in a file? -Drag-n-Drop into the value field. No need to retype and we know the data type allready- add the "" around string litterals (And why am I trying to get in between them anyhow pray-tell? TestStand can put the back-it put em there once allreadySmiley Wink 
  • Know what parameter or operation you want in the Expression?- Drag-Drop into the expression field or the expression builder.
  • Duplicating Limits or selecting a comparison? Drag-n-Drop into TestStand

Drag-n-Drop

Drag-n-Drop

Drag-n-Drop

Drag-n-Drop

Drag-n-Drop

Drag-n-Drop.....Sooooooo easy

 You can copy the value of a selected variable to another element.

CopyValue.png

 

But you cannot paste the value into the selected element in an easy manner.

No_Paste_Value.png

 

What you have to do is click into the selected variable’s value field and then Paste, but this doesn’t produce the correct result (for strings anyway)......

 

PasteValue.png

 

You end up with is double quotes!!!

 

Resultant Paste.png

 

Also if you had ‘Copy Value’ on multiple selected elements and pasted them then you get

 

multiple selection.png

 

So it cannot handle multiple selections.

 

It would have been better if you could have selected the place where you wanted to paste the value(s) and a new menu item became available ie ‘Paste Value’.

 

New_PasteValue.png

 

This way should also be able to handle multiple selections.

 

The problem with double quotes shouldn’t occur and should be corrected with the current pasting of values.

 

Hello,

 

It would be nice to add some more expressions to the SequenceCall STEP, when this one has the "Specify by expression" set to true.

 

I would like to be abble to set the folowing parameter by expressions ...

 

  • Use Current file

 

Manu.net

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 

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

 

When you use an edit step to modifiy the values contained in your step inputs/outputs, the fields are not updated with the new values. You have to close the step tree branch and reopen it to see the updated values. A good idea would be to refresh the step section after the execution of an edit step !

Update step val after Edit Step

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.

I'm taking a bunch of steps and trying to put a "If" flow control step around them. 

Kinda like this:

TS_StartIf.png

 

But what I end up with is just a If/End statement in the middle of the steps that I selected (well, after the first step in the selection)

 

TS_ResultsIf.png

 

What I would have liked to see is this:

 

TS_wantedIf.png

 

Whare the If/End wraps the steps that I selected.

I don't quite know how best to handle the situation where the steps you have selected are not sequential (there's an unselected step in the middle), but that could probably just behave how it is now.

 

The built-in Wait step currently causes TestStand to simply stop at that step until the specified period has elapsed. For steps longer than a few seconds, it would be nice to have some sort of indicator to show how much time is left to wait (and to show that the computer hasn't locked up on those waits that are more than 15 seconds).

 

It would be really nice to have a check box option to show some sort of wait indicator, even if it was simply using the progress indicator in the lower right corner of the screen (something that simple could even just always be enabled).

 

On a related note, could the progress bar be made wider so that there is more resolution as to how much progress has been made? If there was a ten minute wait for something, the bar would be moving very slowly and hard to tell progression was being made.

I had an entire test created in TestStand that used the String Value Test step type extensively. A labVIEW VI was called and the test step looked at a String output to determine whether the step should pass or fail. This worked well, however...

 

After the test creation was complete, the VI that was being called was modified to include an additional boolean output parameter that indicated a special situation where the test should fail. So, all of the test steps had to be converted from a String Value test type to a Pass/Fail test type (which evaluated an expression comparing the original strings and also whether the additional boolean output was true or false.

 

Since there wasn't really much difference between the two types, I expected this to be rather trivial. Instead, I had to re-create every step in the entire test (that this affected, of which there were hundreds) because there doesn't appear to be a way to change a String Value test to a Pass/Fail test.

 

If there was a way to simply switch to a different type of validation (such as from a String Value test to a Numeric or Pass/Fail test), then you wouldn't have to re-create the step name, VI selection (and variable setup), pre-conditions, post-conditions, post actions, additional results, comments, step settings, etc. This was quite a lot of work for what seemed to be such a simple thing!

 

I've been frustrated by this before as this situation occurs on regular basis (although usually only a step or two at a time), but this latest episode required almost a complete test rewrite.

Currently, if you create a step type and name it OnNewStep, it will execute when an instance of the step is created.  This is pretty confusing to new users - why don't we just have an OnNewStep substep type (like prestep, edit, etc)? Custom steps would then just be meant to be called manually using the Step.ExecuteSubstep() Method as documented in the help.

 

onNewStep.png

 

We could keep the "onNewStep" custom step functionality to maintain backwards compatibility with older step types. 

I think it would be a cool idea to put an extra configuration entry point in the Sequential Model (or all the shipped process models) by default.  Inside of it would be a simple call to an empty callback.  This way users can override the callback to get custom sequence file configuration setting. 

 

This would be useful for storing info like: DAQmx addresses, GPIB addresses, etc... off to a file.  Sorta like machine specific configuration info.  That way during execution the file can be read in and used.  However, if it's empty then people can use it for whatever they want. 

 

I understand that I can go in there and edit the process model and make my own but it would be nice to just have the default already there.

 

You could call it Sequence File Configuration or something.

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

If you double click a LabVIEW step in TestStand, currently it will sometimes enable you to edit the name of the step.  I think it would be better to have a double click open the LabVIEW VI that is called by the step as that feels more natural then right clicking the step and selecting edit code.

 

 

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