This diagram is used to specify graphically a mode automaton (Automaton). An Automaton is composed of several modes (or sub-states) and transitions to go from one mode to another one. A sub-state can be either other another Automaton, or an And State, or a Final State (or leaf state). There are two kinds of transitions:
An And State allows to compose synchronously several states (at least 2). A Final State is used to express the behavior of a state using a Data flow Diagram and/or a Clock Relations and Dependences Diagram. An Automaton has at least one sub-state. To define the initial state of an Automaton, right click on the wanted initial state and select the Set the Initial State action.
An History can be added to an Automaton or to an And State. If the target of a transition is an Automaton (or an And State), it means that the Automaton (resp. all sub-states of the And State)will be reinitialized before their execution (start its execution at the initial state). To restart from the last state of the Automaton (resp. all sub-states of an And State), the target of the transition must be the History of the Automaton (resp. And State).
Local signals can be declared in an Automaton (or And State). These signals are shared by all sub-states of the Automaton (resp. And State). When Local signals declared in an Automaton are defined in several sub-states of the Automaton, do not forget to use partial definition links to define them. A partial definition is a Dataflow Connection with the Use Partial Definition set to true.
To parametrize each of these elements, right-click on any graphical object and select the Property View. For more information, refers to theParametrization of model objects section (select the Advanced tab, to view the attribute and references of each model object).