You write:


Are you 100% sure about this? I don't have contradicting examples, but I 'd like to see some proof.

Yes, this is part of the definition of a Mealy Machine. This is why people refer to the Synchronous Mealy machine as being a Moore machine; the output isn't dependent on the input, so they reason it must be a Moore machine.

http://en.wikipedia.org/wiki/Mealy_machine

http://en.wikipedia.org/wiki/Moore_machine

http://www.jflap.org/tutorial/mealy/mealyMachines.html

and since I don't want to just quote websites, here's a quote from Digital Design: Principles and Practices 3rd edition by John F Wakerly:

A sequential circuit whose output depends on both state and input as shown in Figure 7-35 is called a Mealy machine.(pg. 551)

 

Question on Post #5, the lock.

Why is S3 jumping back to S2 when an incorrect bit is seen, shouldn't it jump to the beginning? Otherwise, once the 10 is known, only 11 needs to be entered for the "lock" to open, rather than the full 4 digits, in order.

To be more pedantic, add a counter so the "enter code" light (or bad code light) @ s0 flags a bad code after any 4 digits that aren't correct?

Yes, it is kind of misleading, if you have a preset conception of what a passcode is. Either be very specific about what you want your machine to do beforehand, or call it a language acceptor/recognizer.

Usually a keypad will buzz in distress if you input a wrong set of exactly four numbers.

Okay, so I changed it to be called a sequence recognizer, which is funny because that's what all the image names are called. I don't know why I called it a passcode recognizer when I obviously was calling it something different....

Oh well, should make more sense now!

 

Yes, this is part of the definition of a Mealy Machine. This is why people refer to the Synchronous Mealy machine as being a Moore machine; the output isn't dependent on the input, so they reason it must be a Moore machine.

http://en.wikipedia.org/wiki/Mealy_machine

http://en.wikipedia.org/wiki/Moore_machine

http://www.jflap.org/tutorial/mealy/mealyMachines.html

and since I don't want to just quote websites, here's a quote from Digital Design: Principles and Practices 3rd edition by John F Wakerly:

Yes, it makes sense now that I gave it a second thought. Thanks.

 

So, how long do these things typically stick around for review?

Just wonderin'. (I'm only slightly antsy)

 

Suggestion:

A state machine for a simple robot. 2 switches for feelers, two motors cross fed by "feeler switches". Think BEAM Robots which are simple state machines, and may appeal to a wider audience. Just a thought, not that I'm lazy (though that's part of it. )

 

Suggestion:

A state machine for a simple robot. 2 switches for feelers, two motors cross fed by "feeler switches". Think BEAM Robots which are simple state machines, and may appeal to a wider audience. Just a thought, not that I'm lazy (though that's part of it. )

Hmmm... that would be a good one.... If I hadn't already written it, I would have used that. My main reason for not doing it now is that I'm lazy.Well, that and I have other articles in the works

Well, If the topic ever comes up again, I will use it. Perhaps in a later section....

 

I think my article did over a month to appear in the e-book. Don't be hasty master tshuck.

 

I think my article did over a month to appear in the e-book. Don't be hasty master tshuck.

I expected longer.

Very well, I shall put this thread from my mind.....