Home > Community > Discussion Forums

LabVIEW Idea Exchange

Showing results for 
Search instead for 
Do you mean 
We've turned on a search before post feature in the LabVIEW Idea Exchange. This new feature will help cut down on the number of duplicate ideas in this space!

The NI Idea Exchange is a product feedback forum where NI R&D and users work together to submit ideas, collaborate on their development, and vote for the ones they like best. View all of the NI Idea Exchanges to post an idea or add your opinion on an existing one today!

Wait (ms) with error pass-through

Status: Declined
by Active Participant MarcoMauri on ‎07-12-2010 05:01 AM


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



by Trusted Enthusiast
on ‎07-12-2010 05:48 AM

Ala OpenG?



by Knight of NI Knight of NI
on ‎07-12-2010 09:57 AM

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


(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 Smiley Wink

by Knight of NI Knight of NI
on ‎07-12-2010 10:28 AM

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.

by Active Participant Manzolli Active Participant
on ‎07-12-2010 12:32 PM

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!

by Active Participant Neil.Pate
on ‎07-12-2010 03:09 PM

As mentioned, OpenG...


Lots of nice open-source useful VIs there.


Its funny, on advanced NI training they are now pimping VIPM :-)

by Active Participant Jim_Kring Active Participant
on ‎07-12-2010 03:39 PM

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

by Trusted Enthusiast Trusted Enthusiast
‎07-12-2010 03:46 PM - edited ‎07-12-2010 03:48 PM
  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!)
by Active Participant Neil.Pate
on ‎07-13-2010 06:20 AM

Jim, let hope!


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

by Member CrystalTech
on ‎07-13-2010 01:02 PM

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.

by Active Participant rex1030
on ‎07-20-2010 03:47 PM

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 Smiley Happy


Kudos to this idea Smiley Happy

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!
Idea Statuses
Top Kudoed Authors
User Kudos Count