> > ----- Original Message ----- > From: "Olin Lathrop" > To: > Sent: Saturday, October 20, 2001 1:43 PM > Subject: Re: [PIC]: Rotary Encoders > > > > > Providing the scanning is carried out quickly enough (likely to be > > interrupt > > > driven via a timer) I am assuming that I can include the encoder outputs > > in > > > the same matrix as the keys. > > > > That depends on the fastest realisting pulse rate from the rotary encoders > > and how fast you can scan all the inputs. The other thing to consider is > > that when a user is rapidly turning a knob, they probably don't care and > > won't notice a little slippage. Unless the knob itself is calibrated with > > indicators nobody will know. > > Yes, that's right. I'm using encoders in a level set application. Started > out with encoders with 15 detents and 30 pulses per rev. That turned out > (sic) too fast. I'm now only processing every 4th pulse, and it really feels > very natural, nobody notices that it only reacts to every 2nd detent click. > > Jan Didden > > > > > > > ******************************************************************** > > Olin Lathrop, embedded systems consultant in Littleton Massachusetts > > (978) 742-9014, olin@embedinc.com, http://www.embedinc.com > > > > -- > > http://www.piclist.com hint: The list server can filter out subtopics > > (like ads or off topics) for you. See http://www.piclist.com/#topics > > > > > > > -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body