bb said:
thx chris....
adding uc was an option i thought about earlier but d cct handles lots
more function than just keypad reading...tis includes alarm,lcd
interface,relays n stuff...n i hv only 6 IO lines to spare.... besides...
the cct is already made finalize
wht i still dont get is tis
a) how to make a source code that will enable uc read d 5 input taken
from 74c922....74c922 takes in 16 values(from 4x4 matrix) and decode it
into a 4 bit binary code to the uc plus a DA line.....
do i hv to include d conversion table(from 16 to 5) in the program source
code?
b)how do i know
whts d approprite delay time for key bounce routine....if im using an
atmel89s8252..is there a mathematical calculation involved in estimating
it?
c)and finally in c -language....
is library file-> reg52.h, reg51.h and declaration term'sbit'....ANSI
standard...?
when i compile d program it gives me error..cannot define reg 52.h and
term sbit
im using turbo c++ 4.5
Hi, bb. In the data sheet, it shows how to calculate the debounce time
based on the caps selected. Read the data sheet.
You should be able to read the DA bit directly in C. Just jump on zero
or not zero. As far as the 4-bit pushbutton data, you can read the
byte, mask off the bits you don't need, rearrange if necessary (usually
the case -- somehow, it seems to be trivially easy to transpose bits on
a PC board), then shift as necessary to make it the low nybble. Then
just read the data. Or if it takes fewer instructions/time, read the
four bits individually, then multiply/shift as necessary and add to
form the data nybble. Your call.
I don't know the Atmel C compiler you're talking about. If you need
help with code, you might want to go to one of the Atmel groups.
I've found it usually helps a lot to read the manuals and data sheets.
Even if you spend some time looking, that's just a free opportunity to
learn something else along the way.
By the way, please take a chance to glance at this:
http://groups.google.com/support/bin/answer.py?answer=12348&topic=250
and also, please don't use TXT lingo unless you're posting from your
cell phone. Us older cripples find it somewhat obscure. I know -- our
problem, and we'll soon enough be dead. But if fossils can't
understand, fossils can't help, can they?
And it actually sounds more like the TXT lingo poster can't even take
the time or show the respect to express himself carefully. Whether
that's interpreted as panic, extreme hurry, or a lack of respect by the
person who's taking the time to help and craft a response, it probably
won't help the OP.
And a fossil might just answer:
havnt a clue wot U' spoutin', m8. hOp U git out of d car trunk s%n!
(
http://www.transl8it.com/cgi-win/index.pl for us fossils out there
;-)
Good luck
Chris