From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
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.
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.
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.
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:
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