LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How do we link multiple stop buttons to make one master stop button?

I think you should use Wait On Notification with a timeout instead of Notifier Status. Don't be concerned about the speed differences unless you are running into performance issues. Usually there is something else in your loop that will be much slower than a notifier timeout. If you are doing any kind of instrument or file IO then the notifier will have timed out long before those things were done. Other times you have code in a loop that executes extremely fast but you want to intentionally slow down the loop. Polling is a good example of a situation where you would do that. Slowing these types of loops is how you actually increse performance. Setting the notifier timeout to 100mS or something is a great way to keep the loop from using all your CPU. Without a notifier or queue you need to use the Wait mS function.

=====================
LabVIEW 2012


0 Kudos
Message 21 of 23
(1,154 Views)

I also have a queue that will be limiting the loop speed, so I hope to have that be the rate-limiting step.

 

Thanks!

 

0 Kudos
Message 22 of 23
(1,140 Views)

If you already have a queue you might as well use that to stop the loop. Some people just wire the dequeue error out to the stop terminal. Better yet create a stop message and enqueue that.

=====================
LabVIEW 2012


0 Kudos
Message 23 of 23
(1,136 Views)