2020-02-05 (W) RFIDKeyboard

To add a scanner to an existing keyboard, I would need to get a USB port on the inside. I saw three ways to do this. The first way was to run a second wire alongside the cord. The second option was to install a hub inside and route it to both devices. I decided on a third option, which was to find a model with the hub built-in. The particular model was an Elsra PK-2068, which I liked because it had programmable and relegendable keys.
Keypad disassembly

Three of the four screws holding the Numpad were visible, and the fourth was under a sticky footpad. Every screw was a standard Phillips head. Inside was a plastic membrane under the keys and a PC at the top, which chips on both sides. One chip was for the USB hub, and the other was for the keyboard functions. The rest of the components were supporting pieces.
Internal circuit board

I would repurpose one of the keyboard's two USB ports for the RFID scanner. I removed the USB connectors from each side so I could link them. USB 2.0 and below only has four wires, two power, and two data, so matching them was easy.
USB removed from RFID scanner

Fortunately, the scanner's board and components were thin, so the combined thickness of the two would still fit inside the case, although it would need modifications. By this point, I had been working on the project for hours and hours, and it was late. I was making foolish mistakes, like singeing the plastic membrane and permanently disabling one of the buttons. I stopped for the day before I wrecked anything else costly.
Scanner and keyboard PCBs

The rest of the posts for this project have been arranged by date.
First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.