From: princekcs on
why is it necessary to clock on rising and falling edge when reading a
quadrature encoder?



---------------------------------------
Posted through http://www.EmbeddedRelated.com
From: Stef on
In comp.arch.embedded,
princekcs <princekcs(a)n_o_s_p_a_m.gmail.com> wrote:
> why is it necessary to clock on rising and falling edge when reading a
> quadrature encoder?

It isn't.

--
Stef (remove caps, dashes and .invalid from e-mail address to reply by mail)

Bahdges? We don't need no stinkin' bahdges!
-- "The Treasure of Sierra Madre"
From: D Yuniskis on
princekcs wrote:
> why is it necessary to clock on rising and falling edge when reading a
> quadrature encoder?

When do you want information from the encoder?
What information do you *want*??

<hint>
From: Tim Wescott on
princekcs wrote:
> why is it necessary to clock on rising and falling edge when reading a
> quadrature encoder?

Homework?

It isn't always necessary, but paying attention to all the edges gives
you a more robust system.

How do you want to do it? Does your preferred method give exactly
correct readings if the encoder suddenly reverses, if it experiences
switch bounce, or if it "camps" on one spot with one channel stuck in a
state and the other constantly transitioning?

--
Tim Wescott
Control system and signal processing consulting
www.wescottdesign.com
From: Walter Banks on


princekcs wrote:

> why is it necessary to clock on rising and falling edge when reading a
> quadrature encoder?

You can decode with one edge only. If you use both edges then
the resolution of the system will double.

Walter..