next up previous
Next: Using TTM's Up: Modeling the Two-Pusher Example Previous: Modeling the Two-Pusher Example

Using the R&W Framework

In order to create the plant model P, we first identify the independent subsystems, which are simply Pushers 1 and 2. Figure 5, shows the automaton for Pusher i, called tex2html_wrap_inline1985 . The states of tex2html_wrap_inline1985 are I(i), M(i), and E(i), indicating Pusher i's initial, middle, and extended positions, respectively. State I(i) is both the initial and final state.

   figure622
Figure 5: tex2html_wrap_inline1985 : Automaton for Pusher i, (i=1,2)


The plant model is given by: tex2html_wrap_inline1991 . The controllable events are tex2html_wrap_inline2897 , and the uncontrollable events are tex2html_wrap_inline2899 .

   figure632
Figure 6: tex2html_wrap_inline1991 : Plant Model for Two-Pusher Example

In Figure 7, we give the recognizers for requirements (i) and (ii) of Specifications I. Note that they are are already self-looped. tex2html_wrap_inline2907 represents the forbidden state tex2html_wrap_inline2909 specification. We can think of state A as the resource (``space'') which the two pushers are to share. Initially, this space is available, and then it can be ``used up'' by Pusher 1 (through event tex2html_wrap_inline2913 ), or by Pusher 2 (through event tex2html_wrap_inline2915 ). Notice that when this resource is being used by Pusher 1 (Pusher 2), the system is in state B (C), from which event tex2html_wrap_inline2921 ( tex2html_wrap_inline2913 ) is not allowed. That is, there is a mutual exclusive use of the resource by the pushers. The recognizer tex2html_wrap_inline2925 gives the sequence of events that will move the workpiece through the desired positions.

   figure642
Figure 7: State Machines for Specifications I(Self-looped)

Our next figure, Figure 8, shows the legal states as specified by requirement (i) of Specifications I. This is obtained by constructing tex2html_wrap_inline1993 .

   figure652
Figure 8: tex2html_wrap_inline1993 : Legal States

Finally, the legal language, shown in Figure 9, is obtained by constructing tex2html_wrap_inline2933 . For simplicity, we have ignored the ``A,'' ``B,'' ``C'' labels of the states in tex2html_wrap_inline2255 . Also, to avoid a crowded graph, some states appear twice (those which are boxed in).

   figure664
Figure 9: tex2html_wrap_inline2241 : Generator of Legal Language for Two-Pusher Example.


The reader can verify that tex2html_wrap_inline2241 is a controllable language. This means that there is no uncontrollable event which is possible from some state in P, but which is not possible in the corresponding state of tex2html_wrap_inline2253 . In the specific context of our example, from every state in tex2html_wrap_inline2253 containing position Ei, the uncontrollable event zi, which is always possible in P, remains possible in tex2html_wrap_inline2241 . However, notice that tex2html_wrap_inline2241 contains the following blocking states: tex2html_wrap_inline2957 , tex2html_wrap_inline2959 , tex2html_wrap_inline2961 , tex2html_wrap_inline2963 , tex2html_wrap_inline2965 , and tex2html_wrap_inline2967 . Upon ``deletion'' of these states (i.e. by disabling the appropriate controllable events), we obtain the recognizer for a proper supervisor S, as shown in Figure 10, and the control pattern given in Table 1:gif

   figure676
Figure 10: S: Proper Supervisor for Two-Pusher Example.

tabular682


next up previous
Next: Using TTM's Up: Modeling the Two-Pusher Example Previous: Modeling the Two-Pusher Example

Luz E. Pinzon
Wed Oct 15 18:10:49 EDT 1997