LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

user event led blink

Solved!
Go to solution

I was practicing with user events from a Core 3 example out of the course manual. I did not use the blinking.vi like NI uses, instead  I assigned a true boolean value to the blinking property node for the Event Fired LED that I would like to blink one time during the user event after the Fire Event button is pushed. But for some reason,the LEd does not blink. I've tried applying a true boolean, and writing the value of the control from the Fire Event boolean on the front panel for when he Fire Event button is pushed,  but neither seems to be having an affect on the Event Fired LED. Can anybody tell my why this isn't working?

 

The vi was done in version 11.

0 Kudos
Message 1 of 8
(3,878 Views)

Hello. I am the original poster but did not see away to edit the post. I just wanted to add a jpg of the vi.

0 Kudos
Message 2 of 8
(3,865 Views)
Solution
Accepted by mechqueen
Thr problem is that you don't understqnd what the blink property does. It causes the boolean to blink at a 1Hz rate. Your code turn the property on but then turns it back off 25ms later. It never get the chance to blink.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 3 of 8
(3,852 Views)

Changing my timing got me a lot closer to the one blink. Thanks.

0 Kudos
Message 4 of 8
(3,844 Views)

Hi. I played around with using a flat sequence structure inside the user event case and that worked even better. The shorter the time on the Wait Function, the faster the "blink" for indication. Thanks again! 🙂

 

 

0 Kudos
Message 5 of 8
(3,827 Views)
The best solution is to not use sequence structures -- ever -- for anything.

Feeling like you need a sequence structure is an indication that you haven't learned to think in dataflow yet. Use data dependencies to gate the execution of code.

Mike...

PS: are you the Melissa McQueen who is the CLAD at Boeing in WA?

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 6 of 8
(3,817 Views)

It works great now, so I'm not sure what's wrong with using sequence structures. I was just trying different options for an example given in the labview course manual. And I do understand data flow, thank you very much. If the sequence structures are there, why not play around with them. I know it's not the only solution.

0 Kudos
Message 7 of 8
(3,785 Views)

@mechqueen wrote:

It works great now, so I'm not sure what's wrong with using sequence structures. I was just trying different options for an example given in the labview course manual. And I do understand data flow, thank you very much. If the sequence structures are there, why not play around with them. I know it's not the only solution.


 

We've been trying to convince NI to remove sequence structures and the horrible stacked sequence structures. 

So to follow your analogy, just because there are matches sitting next to gasoline does not mean you should light the matches.

You can...  I would not recommend it..

 

Relying on sequence structures, especially when mixed with Local Variables may lead to race conditions.  Although the program may work, it may not work reliably, meaning that the results may not be repeatable.  As a matter of fact, that would be a good exercise to try out.

Message 8 of 8
(3,775 Views)