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: 

Wait (ms) with error pass-through


Maybe this has been already requested elsewhere and I'm missing it....

but it would be useful to have a Wait (ms) with connectors for error in and out.

This can help keeping the BD clean...



Trusted Enthusiast

Ala OpenG?



You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
For he does not know what will happen; So who can tell him when it will occur? Eccl. 8:7

Knight of NI

We also have the "time delay" express VI. Do a "View as icon" and you're almost there. 😄


(Back in ~'96 I actually made such a delay myself to introduce small delays between GPIB calls. The icon had an image of a snail on it ;)) 

LabVIEW Champion. It all comes together in GCentral GCentral
What does "Engineering Redefined" mean??
Knight of NI

Though I don't have it installed at the moment, the traditional DAQ palette (counter, I believe) has had the wait with error in/out function for many years.

Active Participant

I did myself one subVI, just like the MarcoMauri idea. Adding error terminal to the standard function will not hurt anyone and will be back compatible with existing code, so kudos!

André Manzolli

Mechanical Engineer
Certified LabVIEW Developer - CLD
LabVIEW Champion
Curitiba - PR - Brazil
Active Participant

As mentioned, OpenG...


Lots of nice open-source useful VIs there.


Its funny, on advanced NI training they are now pimping VIPM 🙂

All your base are belong to us.
Active Participant

> Its funny, on advanced NI training they are now pimping VIPM 🙂


I hope that someday we can even use OpenG and VIPM during CLD exams!  I bet we'll get there.

JKI Blog
Trusted Enthusiast
  1. For completeness, would you expect an error cluster on "Wait Until Next ms Multiple", "Tick Count (ms)", and "Get Date/Time in Seconds"?
  2. My mind is blank right now, but can anyone list any functions that are guaranteed not to generate an error yet use an error cluster (in order to allow data flow enforcement)? ("Clear Errors" doesn't count!)
Wirebird Labs: Expert Toolkits for LabVIEWDeploy, by Wirebird Labs: Expert Toolkits for LabVIEW
Active Participant

Jim, let hope!


I am still surprised the number of LV developers I speak to who have never heard of either.

All your base are belong to us.

I sized mine to one terminal height since the error in and out are the only flow terminals required.  The "mSec to wait" and "cancel wait" is sectioned in the bottom middle.  This allows other terminals to flow from the previous VI to the next VI without having to go around the Wait VI.

Active Participant

I have wanted this implemented for a long time. Sequence structures are frowned upon but sometimes you need to wait a bit after you do something. To accomplesh this 'dataflow enforcement'  i have even made a subvi that looks like this inside:


Somehow creating this subvi always feels necessary and pointless at the same time, like some logical conundrum. lol.

I love the openG vi's but I always fear someone would come along and try to use my code that hasn't installed the openG functions and my VIs would be broken with a mystery "?" stuck in important places 🙂


Kudos to this idea 🙂

[will work for kudos]