01-19-2011 06:56 PM - edited 01-19-2011 06:57 PM
(please stand by ;))
01-19-2011 07:01 PM
@Chknrckd wrote:
I've tried wiring it without the case structure, and the event structure triggers that the comparison has changed, even though it goes from false - false - false, and so on.
I need the output of an or-gate in one loop to trigger the the event in the other loop. so the event structure is running in parallel to the other while loop. When the 'or' gate in the while loop changes from false to true, i want the event structure to trigger and stop. hope that makes sense
As I said, a writing to a signaling property will fire the value change event even if the value did not actually change.
The specifications are still incomplete. Should the upper loop stop too? What is the purpose of the outer loop? Currently it can be deleted without change in VI function.
01-19-2011 07:02 PM - edited 01-19-2011 07:02 PM
double post. ignore this
01-19-2011 07:04 PM
the outer loop is not necessary, but i need BOTH of the loops to stop. the one without the event structure stops witha stop button to an or gate, to the end. and the other one with the event structure needs to stop based on the output of that or gate.
sorry this is complicated - looks like my 'simplifcation' of my program didn't help too much.
01-19-2011 07:27 PM
01-19-2011 07:30 PM
wow perfect! you're a life-saver. i was close - just missing one little thing. Thanks everyone!