event structure with local variable

[sruedat]

X.

Thanks

I don understand your example, because you need act in a actuator (ok button ) to fire the event. If I take your sample and change the OK button by NewDataReceived the problem continues. (It's posible that I'm an awkward)

altenbach

Thanks fantastic solutión, The x-asis is a bit complicated for my but I'm studing it..

[X.]

My example was intended only to show you what was wrong in your own VI, not to provide an optimal solution to your problem (which I don't know). I haven't looked at Christian's solution, but it sounds like it meets your needs. Without seeing what you changed to my suggested architecture, I can only guess what may be wrong.

The attached version attempts to follow your line of thought.

Note that the decision to turn on the "Data Received"  boolean only when the "Value Received" is different from the previous one is arbitrary. You may want to have it on at each DAQ loop iteration. My understanding is that your DAQ loop will get its "New Value" from a subVI of some sort. In this case, the "Value Received" will be an indicator and you will want to connect the "New Value" output for your VI to the "Value (Signaling)" Property of "Value Received" in order to trigger an event in the loop below. But again, then the "Data Received" boolean current behavior may need to be modified.

Anyway, hopefully this whole discussion will have clarified some basic LabVIEW concepts.