LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Time Delay vs Wait


@billko wrote:


I use this a lot for exactly the reasons you described.  Furthermore, I also show it as an icon so it's not so unwieldy.


Right, I do too.

 

I did it this way to show that there was not a reset terminal on the Time Delay Express VI 

========================
=== Engineer Ambiguously ===
========================
Message 21 of 23
(490 Views)

The other difference you've failed to mention is that the Express vi cannot output the ms Timer value so there is no means to check if it returns late(Due to OS Scheduling) or early(due to ms timer rollover)

 

So, while it still performs exactly as it did in LabVIEW 7 Express, the Express.vi should probably not be used for new projects(Depreciated) in favor of Stall Dataflow.vim or Wait on Hi Resolution Timer.vi


"Should be" isn't "Is" -Jay
0 Kudos
Message 22 of 23
(481 Views)

@JÞB wrote:

The other difference you've failed to mention is that the Express vi cannot output the ms Timer value so there is no means to check if it returns late(Due to OS Scheduling) or early(due to ms timer rollover)

 

So, while it still performs exactly as it did in LabVIEW 7 Express, the Express.vi should probably not be used for new projects(Depreciated) in favor of Stall Dataflow.vim or Wait on Hi Resolution Timer.vi


For waits that I measure in seconds, I usually favor the express VI, but for waits in (approximate) milliseconds, I will use the stall.vim.  And once I even used the stall.vim on a wire that was NOT an error wire!

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 23 of 23
(469 Views)