NI TestStand Idea Exchange

About NI TestStand Idea Exchange

Do you have a feature idea for how to improve NI TestStand? Submit and vote on ideas now!

  1. Browse by label or search in the TestStand Idea Exchange to see if your idea has previously been submitted. If your idea exists sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea. Be sure to submit a separate post for each idea. Note: the TestStand Idea Exchange is not the appropriate forum to submit technical support questions.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see implemented!

The TestStand R&D team is committed to reviewing every idea submitted via the TestStand Idea Exchange. However, we cannot guarantee the implementation of any TestStand Idea Exchange submission until further documented.

Top Authors
cancel
Showing results for 
Search instead for 
Did you mean: 
JÞB

LabVIEW steps Shoud recognize Green clusters.

Status: Completed

I'm not exactly sure when this was implemented, but it appears to work for me. If you create a VI with an Error indicator wired to the connector pane and drag it into TestStand, the Error Out is automatically mapped to Step.Result.Error.

 

Thanks for the feedback!

Trent

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.


"Should be" isn't "Is" -Jay
4 Comments
RayFarmer
Trusted Enthusiast

One would hope this would be picked up as a matter of course when Teststand 2012 comes out so as it works with labVIEW 2012.

Regards
Ray Farmer
WireWeaver
Active Participant
Status changed to: Completed

I'm not exactly sure when this was implemented, but it appears to work for me. If you create a VI with an Error indicator wired to the connector pane and drag it into TestStand, the Error Out is automatically mapped to Step.Result.Error.

 

Thanks for the feedback!

Trent

https://www.linkedin.com/in/trentweaver
TomOrr0W
Member

I can confirm that this works with LabVIEW 2016 and TestStand 2016.

 

@WireWeaver: Also, I didn't know that you could drag a *.vi file into TestStand to add a step, so kudos to your reply for a potentially useful shortcut.

WireWeaver
Active Participant

I think dragging VI's to make a step has been around since 2012 - it also works with DLLs, .NET assemblies, and Python Scripts (as of 2019). Also worth mentioning in 2016, a similar mechanic was added for creating sequence call steps with sequences:

https://zone.ni.com/reference/en-XX/help/370052AA-01/tshelp/infotopics/2016whatsnew/

 

https://www.linkedin.com/in/trentweaver