On 1/2/06, Scott Dattalo <scott@dattalo.com> wrote:
> My routine requires 3-bits per switch, or 4-bits if you wish to track when
> a switch changes states (which is something you requested in your original
> post). You have 64 switches, so 64*4 = 256 bits = 32 bytes are required. I
> don't think you need to bother saving the raw, scanned values. The
> de-bounce routine is so short that you can just call it whenever a scanned
> value is obtained.
>
> I think the easiest approach is to turn the routine into a macro and
> in-line it with your scan code. Unroll the scan loop to simplify things
> even more. I don't know the details of your code, but you probably can
> even write a macro to scan your matrix.

Hi Scott,

Thanks for the code. I haven't had the chance to try it yet. At the
moment I'm focusing on getting my front panel PCB laid out and made. I
need an actual matrix keypad to test with anyway. I'm currently trying
to find the time to visit a friend who owns the full version of Eagle
as the free version won't let me do a board as large as I need it
(roughly 8" square).

I will keep you all posted!

Josh
--
A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools.
        -Douglas Adams

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist