|
|||||||||||||
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
)
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.
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!
> 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.
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.
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 ![]()
You must be a registered user to add a comment here. If you've already registered, please log in. If you haven't registered yet, please register and log in.
Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
My Profile | Privacy |
Legal |
Contact NI
© 2011 National Instruments Corporation. All rights reserved. | E-Mail this Page
|
||

E-Mail this Page