About state 10, what does it mean?is it shown in the table?

Do you see it in the table?

You have a state machine that only needs three defined states. But the implementation WILL have at least four states. So the question is how to deal with any unused states. The second slide explicitly indicates that the table is treating anything associated with that state as a "don't care". That may or may not be reasonable, but it is how they have chosen to do it.

 

State {10} means the state where G1=1 and G0=0. It does not show up in the table, because it is an unaccounted for state. You inadvertently introduced a new behavior that was not specified in the table by taking the XOR of G1 and G0. This unspecified behavior that might be difficult for a future engineer to debug. It is a bad practice and should be avoided.

BTW:

G1 ⊕ G0 = G1⋅G0' + G1'⋅G0

Your addition of the G1'⋅G0 term creates the additional unspecified way for T1 to get set equal to 1.

 

State {10} means the state where G1=1 and G0=0. It does not show up in the table, because it is an unaccounted for state. You inadvertently introduced a new behavior that was not specified in the table by taking the XOR of G1 and G0. This unspecified behavior that might be difficult for a future engineer to debug. It is a bad practice and should be avoided.

BTW:

G1 ⊕ G0 = G1⋅G0' + G1'⋅G0

Your addition of the G1'⋅G0 term creates the additional unspecified way for T1 to get set equal to 1.

No matter what he does he will be specifying a new behavior that was not specified in the table.

 

No matter what he does he will be specifying a new behavior that was not specified in the table.

Yeah -- what we said.

 

Ok I get it. Thanks a lot guys.