ChefGroovy
Electrical
- Jan 14, 2003
- 14
I work for a keyboard manufacturing company. We currently use pneumatic robotic "heads", with 132 individual plungers to test each key and its associated scan code. All ran on IBM XTs(!!) with dos 3.3. This stuff is old old old. The interface to the robots is two custom built cards, circa 1983 or so.
I am currently working on a new system to control the head via the parrallel port. And upgrade the computers to 486. I have the circuit built that will fire all the plungers and all is well and good, but I can't decide how to read the scan codes.
The real question is, anyone know of a circuit where I can read the scan codes of a keyboard via the parrellel port? I know I could use the regular keyboard port to do it, but then when a keyboard is under test or being debugged I wouldn't have a keyboard. Would much rather do it over the Par Port.
I could also use the mouse port to read the scan codes, which I do on the "manual" audit tests we do. But this is still not as neat and self contained as it should be. Eventually would like whole system to be on windows written in vis basic, so mouse port would not be availiable.
Any help or input greatly appreciated
Dan Shaffer
jdshaffer@qx.net
I am currently working on a new system to control the head via the parrallel port. And upgrade the computers to 486. I have the circuit built that will fire all the plungers and all is well and good, but I can't decide how to read the scan codes.
The real question is, anyone know of a circuit where I can read the scan codes of a keyboard via the parrellel port? I know I could use the regular keyboard port to do it, but then when a keyboard is under test or being debugged I wouldn't have a keyboard. Would much rather do it over the Par Port.
I could also use the mouse port to read the scan codes, which I do on the "manual" audit tests we do. But this is still not as neat and self contained as it should be. Eventually would like whole system to be on windows written in vis basic, so mouse port would not be availiable.
Any help or input greatly appreciated
Dan Shaffer
jdshaffer@qx.net