<Thought I would add my two cents on this sub-topic - I use string driven state machines instead of enum type defs when I want to create a scriptable state machine. That is, the state sequence is driven by a text file that has information about what order the states are executed. This means the test sequence can be modified in the field using any text editor. Clearly, this flexibility is not always required (or even advisable) but when it is, it's really easy to implement in a string driven state machine.
Mark Smith ([EMAIL PROTECTED])> I also use files to define the state transition logic plus I use a second text file to define the outputs (actuator values) that change at state transitions. If you write your state logic properly, you can completely control the state transitions and the analog and digital output changes at state transitions, by simply changing the text files. Last year, I gave a talk on this at our local LabVIEW User's Group meeting. If you want, I can send you a simple program I used during the talk to illustrate my approach. The documentation is a little sketchy, but you can figure out what is going on by looking at the diagrams. Lewis Drake Process Automation Corporation Belle Mead, NJ 908 359-1011 www.processauto.com
