What a mess!
1. Try to keep the size of your diagrams to one screen. Scrolling around to see what is going on makes understanding (and troubleshooting) a VI very difficult.
2. Get rid of the local variables. They break dataflow, may lead to race conditions, and make it difficult to tell what the program is doing. The WIRE is the variable. Controls and indicators ( and local variables linked to them) are merely the user access point to the value of a variable (the WIRE).
3. The main program has 3 infinite loops running in parallel. At least one of them has no delays or waits and likely will hog the CPU resources. How do you stop this program? Someone on this Forum once said, "Stopping a VI by using the Abort button is like stopping a car by running it into a tree." It works but it has (undesirable) consequences.
4. The AVS_Main.vi has a 10 second wait in the lower case structure which runs in parallel to the event structure. This will make things very unresponsive to events.
5. Sequence structures are almost always unnecessary. Stacked sequence structures should be avoided because they hide code, are hard to extend or modify and result in right to left wiring. Use dataflow. Use a state machine.
Now to the core of your question.
6. While it is possible to set up an event structure in a subVI to respond to user actions on the main front panel, it would probably be better for you to have the event structure in a loop of its own in the main VI. Look at the Producer/Consumer (Events) Design Pattern.
While I cannot be sure what your program is supposed to do, I think it can be done with two while loops in a Producer/Consumer pattern, without sequence structures, without local variables, and with diagrams no larger than one screen.
Lynn
)
