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

[d1sturbanc3]

I'm trying to figure out this dynamic events structure usage. I can't get the event to respond to value change in an indicator, but I can get it to respond to a value change to a stop button. Basically, all I'm trying to do is to stop my program. My program stop under 2 condition, if there is an error or an user  presses a stop button. I have the error status and stop button or together.

This will stop. My stop button is called Program Stop.

This won't stop. My stop button or error is called Process Control.

Thanks


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

[JB]

Use a Value(Signaling) property node (instead of a Value property node, a local variable or the terminal) to change the value of the variable.

Post back if this shouldn't solve your problem.

[smercurio_fc]

Also, there is no need to use a local variable inside the event case to get the value of the Boolean. See that list of items on the inside left border of the event structure? "NewVal" is the value of the Boolean, so use that instead of the local variable.

[TCPlomp]

Maybe you destroy the user event reference before the event structure has reacted?
We need some info about the subVI.

Ton

[d1sturbanc3]

I changed the process control input to val sign shown below... but the entire program stop responding. I can't even click stop.






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

[smercurio_fc]

Please upload your VI. It's diffiicult to tell what's going on from just screenshots of only parts of the program. Methinks you have two loops running, and one loops is dependent on data from the first, which it never gets 'cause it's still running.

[d1sturbanc3]

My subVI is not really anything right now. All I want it to do is stop when it's told to stop.

So it's like this.






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

[d1sturbanc3]

I think uploading my entire VI is just going to make it even more confusing. But go ahead and take a look at it.

[Ben]

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

[d1sturbanc3]

"Use a Value(Signaling) property node (instead of a Value property node, a local variable or the terminal) to change the value of the variable.

Post back if this shouldn't solve your problem."

hmm maybe this is interesting.. I changed it to Value signaling... and for process control. If I don't do any events off it, it works fine. If I apply an event based on it's value change... the whole program locks up. I can't change anything.