Why won't a event structure respond to a value indicator?

[d1sturbanc3]

"Now that you are using "value Signalling" I think the issue is as mentioned by Ton.

I think you are destroying the User Event before it is detected by the sub-VI. Try only detroying the user event AFTER the sub-VI returns.

Ben"

I don't see how I'm destroying the user event. The user presses stop. Process control turns true. It won't change back to false until the program ends. This ensure that it will change to false as the last action. As you can see the only when "track read end" and all my other process ends, will process control turn false again. "track read end" turns true as when the while loop ends.

Message Edited by d1sturbanc3 on 03-03-2008 09:59 AM

[Ben]

HI D1,

Rather than re-invet the wheel please take a look at this Community Nugget authored by Ton.

It sure helped me understand dynamic events and hopefully it will help you as well.

Ben

[d1sturbanc3]

Thanks Ben... Actually, I based my program off that thread. I couldn't get it working with normal events and searched the forum and found that thread. I'm doing almost exactly what he did except I'm using an indiciator (LED) instead of a stop button.

[Ben]

Hi D1,

I only answer Q's durring short breaks here at work so I can't debug what is happening.

I suggest you strip down your code to the basic elements and post a small zip in the earliest version of LV you have.

Someone with a more recent version than LV 7.1 (like me on this machine) maybe able to take a quick look and advices.

Please keep in mind that all of the "gold bar" contributors here are just volunteers so you have have to make things easy for us to help you.

Just trying to help,

Ben

PS Try to keep your screen shots small. Some people will not even look at a thread that is multiple screens wide.

Message Edited by Ben on 03-03-2008 10:22 AM

[TCPlomp]

Well,

this is the first time I see a VI locked up by dataflow.

Your three event structure need to be executed in a particular order: A-B-C. Each of the events will lock op the front panel, and prevent the other event from being triggered.
It is better to have one event structure with three event cases.



Ton


Message Edited by TonP on 03-03-2008 08:01 PM

[d1sturbanc3]

Thanks... I appriciate all the sugestions. I'm new to Labview, and I know there are better coding practices, which I've yet to learn. Right now I'm not touching the Ring or the File path. I'll put them together in a single event.

This is what I've updated to.. I figure out how to unfreeze the front panel during the event loop. Everything stops but the dynamic event.

This is the event


This is where I set the process control via signal value







Message Edited by d1sturbanc3 on 03-03-2008 01:32 PM