Boolean 'value change' Event is occasionaly missed/locks front panel

[RavensFan]

Please post your VI so we can see what you are doing.  Normally, the button should be placed inside of its event case so that it can be read and unlatched automatically when the event occurs.  You wouldn't have to hit the button twice.  So I'm thinking there is some off about your VI architecture.

[Veeru]

Thanks Ravens Fan

I have attached the Vi

[johnsold]

You need to brush up on your understanding of dataflow.


Move the indicator to the right side of the event structure and move both the Ring and the OK button to inside the OK button value change case.

Lynn

[RavensFan]

Put your OK button in the event case.

Put your Ring control in the event case as well.  What happens is that the Ring control gets read right away, so it gets read with its old value before you have a chance to change it to something else and hit OK.

[altenbach]

Veeru wrote:

I have attached the Vi

In addition:

• What is the purpose of the lower shift register array. Does not seem to do anything useful.
• Also arre you sure you want to initialize it with an array already containing al element instead of an empty array?
• If you would make your ring I32 representation, you would lose 3 coercion dots in one strike!

Remember, execution highlghting is your friend. Use it to get a better understanding of dataflow.

[Veeru]

Thanks All