09-24-2012 08:33 AM
Chazzzmd wrote:If we treat the Test 1 - Test 10 as states and I already have the test execution themselves as state machines (Test 1 = state machine, Test 2 = state machine, etc.) I would have nested state machines correct? I've never done that before, are there any draw backs? Is this common? Things to remember? Links to literature you recommend?
There is nothing wrong with having a state machine inside of a state. I would make each test a subVI to make it easier to handle. As long as you can still handle errors, messages, timing, etc inside of each of your Tests, you'll be just fine.
09-24-2012 10:20 AM
@Chazzzmd wrote:
I believe the equal to 0? functions supplies the logic for dynamically building ...
Where exactly is an "equal 0?" function?
09-24-2012 10:24 AM
I meant equal TRUE, sorry.
09-24-2012 10:35 AM
What would happen if you would remove the "equal true?" and wire directly to the case structure?
09-24-2012 10:39 AM
I'm going to assume that's rhetorical 😉 . I haven't executed the code example yet, still building. A code snippet would of been great 🙂 But, hey I'm not complaining.
Chazzzmd
09-24-2012 11:08 AM
@Chazzzmd wrote:
I'm going to assume that's rhetorical 😉
Nothing retorical. An "equal TRUE" comparison simply returns the same value as the other input wire to the comparison, so it is a WEQ, or "wire equvalent code". Replacing it with a plain naked wire would give you the exact same functionality. 😄 If I see constructs like that, the rest of the code is probably also questionable. 😮
Here's a quick example that rattles through the states selected earlier. For this purpose, you could consider the "state progress values" as the substates of each state selected from the listbox. See if it makes any sense.
09-24-2012 11:23 AM
"Replacing it with a plain naked wire would give you the exact same functionality."...........that's why I said rhetorical 🙂
Thanks for the example vi you attached. I will give it a look. I'm always on the lookout to learn something new. You Knights are great for that. I have been able to get apok's upper example to work to my needs, I'm testing it out now. Will post back with update/solution marked.
Chazzzmd
09-24-2012 11:33 AM
Altenbach,
Makes perfect sense, awesome vi. Thanks for the link in the BD. I swear I tried that search string (Sequential execution of event structure) in forums and examples on ni.com this weekend. Oh well.
Thanks again for your (and everyone's) attention to this matter.
I have to mark this as the solution since it is specifically the answer to my posted question, although Apok has an acceptable solution just in a different way.
Thanks again,
Chazzzmd
09-24-2012 11:46 AM
@Chazzzmd wrote:
Thanks for the link in the BD. I swear I tried that search string (Sequential execution of event structure) in forums and examples on ni.com this weekend. Oh well.
The link just points to our discusion here so I can find it later when looking at the VI. 😄