LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

start stop loop

Solved!
Go to solution

You can hide a control by setting its visible property to false.

 

Ben64

0 Kudos
Message 11 of 22
(1,042 Views)

thanks, but I was wondering if it was some better method

0 Kudos
Message 12 of 22
(1,040 Views)

Have a look at the Master/Slave and Producer/Consumer architectures from new - VI from Template and from the LabVIEW examples. It might look more complicated at first but it can save you a lot of time later.

 

Ben64

0 Kudos
Message 13 of 22
(1,031 Views)

Instead of an extra boolean and local variable, you could create a local variable of the gauge and do the comparison in the second loop. Keep it lightweight!

 

 

0 Kudos
Message 14 of 22
(1,029 Views)
Solution
Accepted by gringo63

send it as a bool notifier, no switch involved...

ledblinkingMOD.png

0 Kudos
Message 15 of 22
(1,019 Views)

Tanks, this is intersting.

At first glance, seems to work, but in fact a strange thing happens, the two LEDs lambegguano with the same frequency, whereas I would like them each with their own. The problem is caused by waiting for the notification from the second cycle. I think I will use the smallest delay in the main loop ( none in the second) and using some math with remainders I can arrange the leds blinking rates. Pheraps it would be better to use queque instead notification.

0 Kudos
Message 16 of 22
(1,000 Views)

at first glance, seems to work, but in fact a strange thing happens, the two LEDs blinks with the same frequency, whereas I would like them each with their own. The problem is caused by waiting for the notification from the second cycle. I think I will use the smallest delay in the main loop and then I causing the remains as I'm arranging the flashes

0 Kudos
Message 17 of 22
(997 Views)

Wire a 200 constant to your wait on notification

ledblinkingMOD_BD.png

0 Kudos
Message 18 of 22
(991 Views)

betobeto33 wrote:

At first glance, seems to work, but in fact a strange thing happens


So why did you mark it as solution? Seems way overengineered for such a simple task and, as you noticed, it is constipated. 😄

0 Kudos
Message 19 of 22
(990 Views)

Also notice that you can use a single loop running at the greatest common divisor of the different blink rates. Now you don't even need to communicate between different loops. 😄

 

Here's a quick draft. Modify as needed.

 

 

Download All
0 Kudos
Message 20 of 22
(973 Views)