Value Change event on a boolean LED

[Jarrod_S.]

I would strongly recommend against having two event structures. I can't see any reason in your VI that would necessitate that. But regardless of whether you want to trigger an event from one event structure to another or just one event case to another, there are two ways to do it:

1. Register for a Value Change event for some control (even a mock control that's hidden on the Front Panel). Then write a value to it using the Value (Signaling) property node.

2. User Events. These are events that are not bound to front panel items or user interaction (despite their name). They are purely programmatic. This process is much more complicated than #1, but is more flexible and offers better performance in many aspects. You can look here for more information.

Also, you seem to be reading excessively from global variables. You might want to rethink whether this is necessary. In some situations you are reading from the same global twice in the same loop. A better idea would be to read it once then split a wire off that line to make a copy of the data.

[NicholasWittebol]

I had changed the global reads after posting, because I realized it wasn't optimal. I've also got the event triggering using the Value Signalling property.

Thanks for your help! Another problem solved!