At 09:38 AM 7/23/01 -0400, you wrote:

>I completely agree on the use of a state machine but I have to wonder what
>your definition of a 'typical' encoder is.

Yes, I was speaking in the context of the OP, or IOW, a typical
*mechanical* shaft encoder used for manual setting.  Of course the
state machine can be implemented in software or hardware.

>It would seem that among the different types of encoders available, there is
>a wide variation in what the specs of a typical encoder would be.

Agreed! Even on a high-speed encoder as used in motion control, I think
it's worth looking at the phase difference though, as it directly affects
the timing, particularly if software is being used.

Best regards,
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Spehro Pefhany --"it's the network..."            "The Journey is the reward"
speff@interlog.com             Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog  Info for designers:  http://www.speff.com
Contributions invited->The AVR-gcc FAQ is at: http://www.bluecollarlinux.com
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.