Data between states of the states machine

[RSibagatullin]

So I have two tables that I generate in one state of the state machine.  My question is what is a proper, aesthetic way to propogate these two tables into one another state of the state machine. Please see the attached  code.  State machines rock!

[jon_mcbee]

One nice way to pass data in a statemachine is to bundle up your controls in one cluster and your indicators in another cluster.  This way you just have to use two shift registers (one for each cluster) and bundle and unbundle as necessary.

[RSibagatullin]

But I need to pass only the data from one state to another. Wouldn't be the shift register an overkill becasue I will have to route  the signal through all states?

[jon_mcbee]

The shift register is the right tool for this job.  It follows the left to right data flow paradigm, unlike other solutions (such as using a local variable).  I am sure you will get a few other opinions but I think that the shift register is the way to go.

[Ray.R]

The shift register IS the way to go. 

RayR

[Ben]

Action Engines are a way of encapsulating a Shift Register.

There are some advantages to using an AE as apposed to a single cluster in a SR.

1) The data is availabel to other state machines running in parallel.

2) They reduce the clutter making your state machine easier to understand.

3) For large data sets a AE can perform better since it can make more efficient use of memory (provided you fallow all of the rules).

Ben