Enrique wrote in message
news:506500000005000000F34E0000-1005954886000@exchange.ni.com...
> So, I think what you are trying to say is that the configuration you
> described in the answer to this question (case structure, inside a
> while loop, shift register, ...) has several variations, and one is a
> state machine.
Not really, only the simplest example case could be a state machine- and
that only because it would be written for the hell of proving that a case
structure in itself can represent a very limited state machine, where the
state of one input governs the output states. In real cases, the state
machine is the "glue logic" and not the case structure. Generally in complex
programs I do, I have a state mach
ine sub-VI that's called either in a
"housekeeping" frame or inside the enclosing while loop before the case
structure is reached. This takes a Boolean array of the various conditions
along with a truth table and outputs a number corresponding to the current
state of the system. This number determines which frame of the case
structure is to be executed next. Essentially the case structure is a list
of tasks that must be done in response to the conditions identified by the
state machine.
Most "state machine" apps don't require this level of complexity, but it's
still the case that the state machine is that which determines what the case
structure will do next, and the case structure is just the set of tasks to
execute in response to particular situations.
> If other variations are appropriately defined, here you have something
> for an article or something.
That implies time to write. And afterall, to most people the distinction is
as relevant as the difference between mass and weigh
t.
