'keyboard - thanks guys :)'
|Hi chaps (and the one or two gals as well),
Thanks to those who replied about the minimal AT type keyboard, I'll
chase this up over the next few days. I've been involved in a design
project for a Mobile Data Terminal which is now on a web page at the
following URL http://www.memo.com.au and we are likely to use a
small PIC to handle AT keyboard to RS485 to make it compatible with
the MDT's operating system and scripting language. If you have any
queries about the MDT I'd be happy to answer them - incidentally,
the unit uses the 68HC11 as it was the lowest cost one around that
allowed external 32K EPROM, 32K SRAM and has 512 bytes of EEPROM
on the CPU along with lots of A to D and reasonable speed etc...
(Couldn't find a PIC big enough and at that stage it wasn't my
decision either as to which CPU we ended up with).
Thanks again and Regards from
Perth, Western Australia
Some say there is no magic but, all things begin with thought then it becomes
academic, then some poor slob works out a practical way to implement all that
theory, this is called Engineering - for most people another form of magic.
> - incidentally, the unit uses the 68HC11 as it was the lowest cost one
> around that allowed external 32K EPROM, 32K SRAM and has 512 bytes of
> EEPROM on the CPU along with lots of A to D and reasonable speed etc...
> (Couldn't find a PIC big enough and at that stage it wasn't my
> decision either as to which CPU we ended up with).
Wise choice. Horses for courses. 68HC11s are used in most of the
sophisticated bar code and/ or "keyboard wedge" appliances I have here,
using significant amounts of code space and/ or RAM. Why use PICs?
Only because they may be more AVAILABLE(!) and/ or cheaper than the
68HC11 and MAY execute faster. However, using the serial EEPROM or RAM
devices loses all such speed advantage.
More... (looser matching)
- Last day of these posts
- In 1997
, 1998 only
- New search...