Hi all, I've been working on a large application that performs the familar tasks of providing a GUI for test initialization, automated test execution, and a GUI for interacting with the test as it is being executed. My basic archetecture is a state machine, but in an effort to improve GUI response I've implemented event structures. But since I have essentially two separate applications sharing the same front panel (initialization and test), how can I make sure that both sides have stable, fast responses to user actions? The attached VI is a sketch of what I've come up with. Basically I have two event structures in different states of the main state machine, each handling events from one side of a front panel that has been divided by a vertical splitter bar. In order to prevent the front panel from locking, I disable the controls on the "inactive" pane (ie: the initialization pane when the VI is executing the test state). This prevents events from occuring when they can't be handled by the associated event structure. In the example there is a button on each side that switches from one pane to the other, alerting the user by illumnating an indicator lamp on the active side. The real program handles the switch automatically, but as long as all the controls for each task are on their own pane, any switching logic could be implemented. Anyone see any pitfalls with this idea or better methods to accomplish the same thing?

Some courses and learning paths on NI Learning Center may not appear on learner dashboards. Our team is actively investigating.

If you encounter access issues, please contact services@ni.com and include the learner’s name, email, service ID or EA number, and the list of required courses.

LabVIEW

State machine with multiple event structures

There was an excellent thread on Lava about just that. It was almost like watching King Kong and Godzilla going at eachother.

=====================
LabVIEW 2012

Message 11 of 12

(1,448 Views)

Author

Wow. That is a great thread. Though, being trained as a mechanical engineer, it's left my head hurting a bit. I'll have to read through it a few dozen more times, but the two commentators in that thread are dealing with exactly the dilemmas that I've encountered (but not yet understood) through using "Hector" for my current application.

Thanks again everyone.

CLAD

Message 12 of 12

(1,433 Views)

LabVIEW

State machine with multiple event structures

Re: State machine with multiple event structures

Re: State machine with multiple event structures