LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

event structure misses events

Gotcha, thanks that makes sense.  Let me give it a try.

 

Thank you!
Christopher

0 Kudos
Message 11 of 15
(611 Views)

I usually use 3 loops, one for input (Event Structure, Producer), one for processing (Queued State Machine, Consumer), and one for updating the front panel display.  I've always used a Functional Global for the front panel values, that way I can update it anywhere in my system and the front panel will update as fast as I allow the display loop to run.  Unless an event just does one quick thing I never process anything in the Event Structure.  That's what the consumer loop is for.

 

Kelly Bersch
Certified LabVIEW Developer
Kudos are always welcome
0 Kudos
Message 12 of 15
(609 Views)

Pickering wrote:

There is no way to make the event structure store up events and execute them when it is not busy?


Yes, that's exactly what the event structure does - it maintains a queue of pending events. I wonder if you could solve your problem simply by unchecking the "Lock front panel until the event case for this event completes" option for the dynamic event case?

0 Kudos
Message 13 of 15
(586 Views)

@nathand wrote:

 I wonder if you could solve your problem simply by unchecking the "Lock front panel until the event case for this event completes" option for the dynamic event case?

 

You cant lock front panel for dynamic events.


CLA CTAChampionI'm attending the GLA Summit!
Subscribe to the Test Automation user group: UK Test Automation Group
0 Kudos
Message 14 of 15
(579 Views)

@.aCe. wrote:

You cant lock front panel for dynamic events.


 Knew I should have checked that before I posted! Oh well. Thanks for the correction.

0 Kudos
Message 15 of 15
(567 Views)