Compaq Pocket PC Keyboard: Difference between revisions
Antonizoon (talk | contribs) (Created page with "Like a Miniature Butterfly keyboard. Unfortunately, I only have a Viewsonic V37 Pocket PC (like [http://raydehler.com/p/viewsonic-v37.html/comment-page-5 this guy here]), not...") |
Antonizoon (talk | contribs) No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[File:Compaqipaq3800keyboard6.jpg|thumb]] | |||
Like a Miniature Butterfly keyboard. | Like a Miniature Butterfly keyboard. | ||
| Line 8: | Line 10: | ||
Since I don't feel like buying an HP iPAQ, The last resort is to desolder the matrix from the existing controller chip (which only has one data pin output anyway, so NKRO would be better), and plug it in a Teensy with Soarer's controller, which would convert it into a USB or Bluetooth keyboard. Now wouldn't that be neat. | Since I don't feel like buying an HP iPAQ, The last resort is to desolder the matrix from the existing controller chip (which only has one data pin output anyway, so NKRO would be better), and plug it in a Teensy with Soarer's controller, which would convert it into a USB or Bluetooth keyboard. Now wouldn't that be neat. | ||
== Output Schematic == | |||
Keyboard output is produced by a certain circuit board under the keyboard matrix. While it could be possible to interface directly with the matrix, I decided that it was more effective if I simply intercepted the scancodes that would normally go to the PDA plug, which uses just three cables and one data output. | |||
* <code>VCC</code> (Red) - 5V power supply. | |||
* <code>DATA</code> (Brown) - Evidently some form of scancode is coming out of here. But what? | |||
* <code>GND</code> (Gray) - Electrical Grounding. | |||
=== Scancodes === | |||
We can assume that this keyboard follows the PS/2 Keyboard Standard in some way, since manufacturers tend to be lazy, and it's Windows CE anyway. | |||
<blockquote>If it isn't PS/2 scancodes, we would have to devise a brand new keyboard converter using the Teensy LC. | |||
</blockquote> | |||
# <code>DATA</code> - Just plain ol' data on one serial input. | |||
# <code>NC</code> - No Connection. | |||
# <code>GND</code> - Ground. | |||
# <code>VCC</code> - 5V DC at 275 mA | |||
# <code>NC</code> - No Connection. | |||
# <code>+CLK</code> - Clock Signal. | |||
# NC | |||
It seems like there is no clock signal on this specific keyboard, though. This causes some problems for initiating a connection between the two under the PS/2 Protocol. We can only assume that somehow, the system is supposed to take care of that. | |||
http://www.computer-engineering.org/ps2protocol/ | |||
http://www.jkmicro.com/ps2keyboard_en.pdf | |||
=== iPAQ Connector === | |||
The first pin is connected to DATA. Well, what is this mysterious first pin? | |||
=== Chips Used === | |||
On the matrix controller board, there is a single monolithic IC Chip: | |||
* EMC <code>EM78P447SAM</code> (0131T BG1821) - An 8-Bit Microcontroller. There's not much useful information about the firmware inside of it, so it will just have to be a black box. | |||
Latest revision as of 21:26, 6 February 2018
Like a Miniature Butterfly keyboard.
Unfortunately, I only have a Viewsonic V37 Pocket PC (like this guy here), not an iPAQ. Thus, even though it uses the exact same dock connection, it is flipped the other way and has tabs that prevent a solid socket.
Therefore, I had to sand off the tabs and flip the dock connector around.
After I disassembled the connector, I could now plug it into the Pocket PC quite snugly, but it still didn't send any keystrokes. Even after I plugged in a power adapter that kind of fit, it still didn't work out. Maybe the Viewsonic just doesn't support keyboards? Maybe some kind of driver is necessary? (It is Windows, you know...)
Since I don't feel like buying an HP iPAQ, The last resort is to desolder the matrix from the existing controller chip (which only has one data pin output anyway, so NKRO would be better), and plug it in a Teensy with Soarer's controller, which would convert it into a USB or Bluetooth keyboard. Now wouldn't that be neat.
Output Schematic[edit]
Keyboard output is produced by a certain circuit board under the keyboard matrix. While it could be possible to interface directly with the matrix, I decided that it was more effective if I simply intercepted the scancodes that would normally go to the PDA plug, which uses just three cables and one data output.
VCC(Red) - 5V power supply.DATA(Brown) - Evidently some form of scancode is coming out of here. But what?GND(Gray) - Electrical Grounding.
Scancodes[edit]
We can assume that this keyboard follows the PS/2 Keyboard Standard in some way, since manufacturers tend to be lazy, and it's Windows CE anyway.
If it isn't PS/2 scancodes, we would have to devise a brand new keyboard converter using the Teensy LC.
DATA- Just plain ol' data on one serial input.NC- No Connection.GND- Ground.VCC- 5V DC at 275 mANC- No Connection.+CLK- Clock Signal.- NC
It seems like there is no clock signal on this specific keyboard, though. This causes some problems for initiating a connection between the two under the PS/2 Protocol. We can only assume that somehow, the system is supposed to take care of that.
http://www.computer-engineering.org/ps2protocol/
http://www.jkmicro.com/ps2keyboard_en.pdf
iPAQ Connector[edit]
The first pin is connected to DATA. Well, what is this mysterious first pin?
Chips Used[edit]
On the matrix controller board, there is a single monolithic IC Chip:
- EMC
EM78P447SAM(0131T BG1821) - An 8-Bit Microcontroller. There's not much useful information about the firmware inside of it, so it will just have to be a black box.
