LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be 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 to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  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 in a future version of LabVIEW!
Showing results for 
Search instead for 
Did you mean: 

Add virtual error terminals to any VI

Status: Duplicate

I suggest having a feature that would allow us to add "virtual" error terminals to any VI by right-clicking any VI and selecting "Add Virtual Error Terminals...". These virtual terminals would do nothing more than act as pass-through tunnels to facilitate data flow. This would allow us to minimize the use of sequence structures:



Knight of NI

There are already some ideas that deal with errors on the wait function, but your idea is more general.


I don't know yet is we really need this, but I would not want it to overlap the icon. What if the subVI already has other inputs and outputs defined on the lower corner connectors???


These dataflow connectors need to be outside the regular icon. There probably should be some sort of shell around it. For example, it could look like "call by reference node", but without the reference terminals. It could extend below the icon instead of above.

LabVIEW Champion. It all comes together in GCentral GCentral
What does "Engineering Redefined" mean??
Trusted Enthusiast
Trusted Enthusiast

Looks virtually identical to the second part of this idea.

Active Participant



The idea is very good.


I would only place the virtual connectors below or somewhere else ...

Because if connectors already exists at the same place it would be a problem.


Trusted Enthusiast

This is related to "Sequence Containers" to force execution flow without data dependancies. The Sequence Container would allow any wire to constrain execution order, not just the Error Wire.

Wirebird Labs: Expert Toolkits for LabVIEWDeploy, by Wirebird Labs: Expert Toolkits for LabVIEW
Community Team
Status changed to: Duplicate

Duplicate of ...


You could have accomplished the same by using a single frame flat sequence around the "wait" with the error wire going through it.

I don't really see that as using up either that much BD space or that many mouse clicks.

The fact that beginners sometimes oversue the flat sequence where it isn't appropriate doesn't mean it has no appropriate uses.