07-05-2022 12:02 PM
@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
07-05-2022 12:40 PM - edited 07-05-2022 12:46 PM
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
07-05-2022 01:02 PM
@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!