How to Make a USB Laptop Keyboard Controller

104,678

256

229

Introduction: How to Make a USB Laptop Keyboard Controller

This Instructable will provide a step by step procedure for building a USB laptop keyboard and touchpad controller. I created this guide and video to hopefully make it easier for people to re-purpose an old laptop. A typical laptop keyboard relies on the motherboard for the keyboard scanning and touchpad interface. I use a Teensy microcontroller mounted on a connector board to take over this function. Teensies are often used by the mechanical keyboard enthusiasts at Geekhack and Deskthority and the TMK or QMK software is the most popular controller code. The TMK/QMK code is a bit of an overkill if you just want a simple USB keyboard but it will certainly provide all the features you could ever need. If you would rather write your own keyboard software using Arduino, the Teensyduino functions give you total USB control. Whatever software you decide to use, it will require a key matrix that maps out how your keyboard is wired. One approach, (that I never want to do again) is to exhaustively check every connector pin combination with an ohm meter while holding down each key. I did this when I converted a Sony Vaio into a Raspberry Pi laptop. An Instructable from alpinedelta disassembles the keyboard in order for the connections to each switch to be visually traced back to the connector. Instead of taking the keyboard apart or using an ohm meter, this Instructable will load the Teensy with an automated continuity tester. The Teensy will report over USB, the two pin numbers that are connected when you press a key. After every key has been pressed, the results can be transferred to a row-column matrix and used by the TMK/QMK keyboard controller software or a home-brew Teensyduino routine. The touchpad code described in step 22 can be added to the keyboard routine to create a composite USB device.

I will include download buttons for many of the files in the Instructable but all the files are located at my GitHub repository. The best way to download files from a GitHub repository is to navigate to the top level of the project (USB_Laptop_Keyboard_Controller in this case) and click the green "Code" download button on the right. Choose the Download ZIP option from the Code pull-down menu. The ZIP file will contain the entire repository content, not just the code but also the board layouts and PDFs. 

Step 1: Keyboard Cable Specifications

Laptop keyboards use a flexible printed circuit (FPC) that connects all the key switches in an array of rows and columns as shown above. The keyboard controller drives each row low, one at a time while reading the columns (with a pull up resistor) to see if any switch is pushed. The two bins of laptop keyboards shown above are from Re-PC, a local recycling store. About 75% of the keyboards have FPC cables that end with exposed metal traces on one side and a plastic backing on the other side. The plastic backing plus the FPC material typically measures about 0.30 mm thick. A typical keyboard without a number pad has 24 or 25 signal traces with a 1 mm pitch. If there is a number pad, then it’s common to have 26 traces with a 1 mm pitch. It can be difficult to measure the pitch between traces so another method is to measure the width of the entire FPC cable and use this formula:

Pitch = Total width / (N + 1) where N is the number of pins

A few of the keyboards at Re-PC had 28 to 34 traces and some had a 0.8mm or 0.5mm pitch. There were also keyboards with dual FPC cables. I have included support for all of these variations. Connectors for keyboard cables are readily available from companies like Aliexpress, Mouser, or Digikey. The number of signal traces, the pitch, and whether the contacts are on the top or bottom are the parameters you will need when ordering. There were some old keyboards in the bins with rigid printed circuit board connectors and some other keyboards with specialized connectors soldered to the end of the FPC cable. These keyboards will not be the focus of this Instructable but a few examples will be given.

Step 2: Modify Your FPC Cable As Needed

Some FPC cables need to be modified to fit in a generic connector. Locking nubs on the side of the cable are easy to remove with scissors. If the FPC traces don't line up with the connector pins, use an X-ACTO knife to trim along the side of the cable. The Dell Latitude D630 keyboard needed the most modifications. It had a solder-less connector on the end of the FPC cable that was easily removed. Then I pulled off the extra thick plastic backing that was glued on the end of the cable and cut a notch on the side to align the contacts. To bring the thickness back to normal, I glued 2 pieces of paper to the end of the cable.

Step 3: Teensy LC FPC Connector Assembly - Surface Mount or Thru-Hole

I designed a circuit board using Eagle for the Teensy LC that routes its 26 I/O pins to 26 surface mount pads for an FPC connector with a 1mm pitch or a 0.8mm pitch. I created a second circuit board for keyboards that have a 0.5mm pitch. For those that don't want to solder surface mount connectors, I created the board shown on the right for thru-hole FPC connectors. A connector with up to 26 pins can be soldered to these boards based on your needs. For connectors with less than 26 pins, solder starting at pin 1 and leave the unused pads at the other end blank. I avoided using the 27th Teensy LC output because it’s connected to an LED and 27 pin FPC connectors are rare.

After soldering the FPC connector to the board, I soldered 4 header posts to the board to support the corners of the Teensy and then I soldered the Teensy to the header posts. The last step was to connect the rest of the Teensy I/O signals to the board with 30 gauge wire. I used wire instead of header posts to make it easy to reroute I/O pins or cut the Teensy off the board. If you buy a Teensy LC with pins, it will not have pins on I/O's 24, 25, and 26 so you'll need to add them.

Step 4: Teensy 3.2 or 4.0 FPC Connector Assembly

I designed the back side of the board for a Teensy 3.2 with 34 I/O signals and an FPC connector with a 1 mm or 0.8 mm pitch. A different 3.2 circuit board is available if you have a 0.5mm pitch.

Whichever side of the board you mount the Teensy on, you must solder the FPC connector on the same side.

*****Update for the Teensy 4.0********

I created a new circuit board for the Teensy 4.0 that routes its 34 I/O signals to pads for an FPC connector with a 1 mm or 0.8 mm pitch (see pictures above).

If your keyboard uses FPC pin 34, you must disconnect the LED near I/O 13 on the Teensy 3.2 or 4.0 in order to avoid interfering with the keyboard scan. I find it easier to unsolder the current limit resistor right next to the LED instead of unsoldering the LED itself.

Solder the FPC connector to the 3.2/4.0 side of the board and then proceed to the next step.

Step 5: Teensy 3.2 and 4.0 Surface Mount Pads

The Teensy 3.2 and 4.0 use surface mount pads for I/O signals 24 thru 33 so it’s a little more work to solder them to the board. Solder “flying leads” to the surface mount pads on the Teensy 3.2 or 4.0 and then pass each wire thru the corresponding pad on the board for soldering. Finish the assembly by soldering wires to the remaining I/O signals.

For those that dislike flying leads, I redesigned the Teensy 3.2 board and Teensy 4.0 boards so that header pins can be used for the surface mount pads. The pictures above show how to modify a 2 x 7 right angle header. Note that you can still use flying leads with these boards.

For the Teensy 3.2, cut the header down to 2 x 6, then partially pull and cut the two pins on one end so they are straight as shown above. These 2 pins will help align the header. A small perf board with holes can also be used to hold the header in alignment while soldering the surface mount pads. You will need a long soldering iron tip in order to reach the pads.

For the Teensy 4.0, pull out the 4 right angle leads at the ends and replace them with 4 straight pins that will hold the header in the correct position. The remaining right angle header pins are a touch too long so I recommend they be trimmed in order to not overhang the surface mount pads of the Teensy 4.0.

Step 6: Order the Board and Components

You will need header pins, wire, solder, flux, and a USB cable for this project in addition to the board, connector, and Teensy described below:

  • Pick the Teensy that you want to use based on the number of signals on your keyboard cable. The LC is the lowest cost Teensy but is limited to 26 I/O's. The 4.0 is the newest and fastest Teensy. The 3.2 is my favorite because it is 5 volt tolerant. The ++2.0 is the oldest Teensy in this group and it has the most I/O's. The Teensy LC is $11.65, the 3.2 is $19.80, the 4.0 is $22.80 plus shipping from PJRC. The ++2.0 is no longer available from PJRC but there are clones available at AliExpress for $14.99 plus shipping.
  • Decide how you will route the FPC cable to the Teensy connector board and then examine whether the contacts at the end of the cable are facing up or down. It's common to flip the FPC cable 180 degrees so it ends up underneath the keyboard. The surface mount FPC connectors from AliExpress, Mouser, and Digikey can have top or bottom contacts (see example picture above). Besides right angle connectors, there are also vertical connectors. Here are 3 examples for the possible locking mechanisms; spring loaded with no locking bar, flip down locking bar or slide a locking drawer sideways. You should check the thickness at the end of your FPC cable with a micrometer. A common thickness is 0.30mm but sometimes it's less and you'll need to increase the thickness with tape or a piece of paper.

The following paragraphs describe the various circuit boards that you can use for this project. The Eagle circuit board files have a .brd extension and can be downloaded from my repo. These files are accepted by some board fabricators such as OSH Park in North America and Eurocircuits in Europe. Three boards from OSH Park will cost $18 to $30 depending on the size. Also at my repo are the zipped Gerber files that I translated from the Eagle files. Gerber is accepted by all board houses such as JLCPCB in China. They will produce 5 boards for about $10 with economy shipping to the U.S. They use a HASL (aka HAL) surface finish which is not as good as the ENIG finish used by OSH Park. I have had no trouble with the JLCPCB HASL finish. The different PCB surface finishes are explained by Optimum Design Associates and Eurocircuits.

  • To use a Teensy LC or 3.2 with a surface mount 1mm or 0.8mm pitch FPC connector, use the Keyboard_Scanner_LT2.brd or zip file. This board has pads for a 2 bit level translator in case you want your Teensy LC to talk to a 5 volt PS/2 touchpad. If you don't want the level translator, leave these pads empty. The Teensy 3.2 is 5 volt tolerant so it doesn't need a translator. The hole spacing for the Teensy 3.2 backside I/O signals are spaced for right angle header pins or you can use flying leads.
  • To use a Teensy 4.0 with a surface mount 1mm or 0.8mm pitch FPC connector, use the Keyboard_Scanner_4p0.brd or zip file. For 0.5mm pitch FPC connector, use the Keyboard_Scannmer_4p0_0p5.brd or zip file. The hole spacing for the Teensy 4.0 backside I/O signals are spaced for right angle header pins or you can use flying leads. The Teensy 4.0 is not 5 volt tolerant so use the 2 bit level translator on the Teensy LC side of the board if you want to control a 5 volt PS/2 touchpad.
  • If your keyboard needs a 0.5mm pitch FPC connector, use the Keyboard_Scanner_LT_0p5.brd or zip file. This board will work with a Teensy LC on one side or a Teensy 3.2 on the other side with flying leads.
  • If you don't want to solder a surface mount FPC connector, I designed a board for a thru hole FPC connector. This board uses a Teensy LC and can take an FPC cable with up to 26 pins on a 1mm pitch. Use Eagle file Keyboard_Scanner_LC_thruhole.brd or the zip file for this board. The connector hole pattern on the board is designed for this AliExpress or Digikey connector.
  • The Teensy ++2.0 (clone) is still available from AliExpress so I designed a board that will connect it to an FPC connector with either a 1mm, 0.8mm, or 0.5mm pitch and up to 36 pins. You must un-solder the LED located on the Teensy ++2.0 so that it does not interfere with the keyboard software. The Eagle board file Keyboard_Scanner_2pp.brd and the gerber zip file are at my repo.
  • Some old keyboards have a 1.25mm pitch FPC cable so I made Eagle file TeensyLC_1p25.brd. It will take a thru hole connector with up to 26 pins and a 1.25mm pitch like these from AliExpress.

Step 7: Low Profile Connector Board

A Teensy with header pins that is mounted on an FPC connector board may be too tall to fit in a thin laptop case so I designed the board shown above. The Eagle board file, "Teensy3p2Cutout.brd" can be downloaded from my repo. A Teensy 3.2 will fit in the cutout and U shaped header pins on each side will hold the Teensy in place. These pins will tie Teensy I/O numbers 0 thru 23 to the connector board. Teensy I/O numbers 24 thru 33 are on backside SMD pads and must be connected with jumper wires. I used "U" shaped header pins from Ali Express that have a width of 6mm (even though their documentation shows a 5mm width). The board will work with 1mm, 0.8mm, or 0.5mm pitch FPC connectors with up to 34 pins. The Eagle file "Teensy3p2CutoutFlip.brd" rotates the Teensy 3.2 180 degrees so it can fit in a cutout on the right side instead of the left (see picture above). Use this board if the USB connection is on the right side of the laptop base. The left cutout and right cutout boards route the I/O signals the same as the Keyboard_Scanner_LT2 connector board and will use the same Teensy 3.2 software. If you would rather use a Teensy 4.0, it will also fit in the board cutout. If you wire the backside I/O numbers 24 thru 33 per the silkscreen labeling, you can use the Teensy 3.2 matrix decoder software to get the correct translation. The Teensy LC can also be used in this manner with jumpers for I/O numbers 24 thru 26.

Step 8: Load the Continuity Tester Into the Teensy

  • Follow the PJRC link for installing Arduino and Teensyduino on your computer.
  • Download the Matrix_Decoder Arduino code. Use file Matrix_Decoder_LC.ino for a Teensy LC, Matrix_Decoder_3p2.ino for a Teensy 3.2, Matrix_Decoder_4p0.ino for a Teensy 4.0 or Matrix_Decoder_2pp.ino for a Teensy ++2.0.
  • Load the Matrix_Decoder code into the Arduino integrated development environment (IDE).
  • Connect a USB cable from the Teensy to the computer. Your computer should automatically load the necessary USB drivers.
  • In the Arduino IDE, under “tools”, "board", "Teensyduino", select Teensy LC, 3.2, 4.0, or ++2.0 depending on what you’re using. Also under “tools”, select USB type: Keyboard. If you forget to do this step, you will get an error message that says "Keyboard was not declared in this scope".
  • Compile and load the Matrix_Decoder code into the Teensy. If it’s your very first time loading the Teensy, you’ll have to push the button on the Teensy to enable the loader.
  • Disconnect the USB cable from the Teensy.
  • If you are using a Teensy ++2.0, you must unsolder the LED on the Teensy so it does not interfere with the scan.

Step 9: Load the Key-List File in the Editor

Open a text editor on your computer. I like to use Notepad++ on Windows or Geany on the Pi because they have column editing.

Original Method:

There are two “key-list” text files you can download, named Keyboard_without_number_pad and Keyboard_with_number_pad. The “key-list” file should have every key that you will push followed by tabs to make the results more readable and easy to copy into a spreadsheet.

New Method:

Marcel Hillesheim has written a Python program that takes much of the manual labor out of my original process. The latest version of his program includes a menu which selects the Teensy LC, 3.2, or 4.0 (but not the Teensy ++2.0). The Python program is at his GitHub repo along with two blank key-list files that use the PJRC key codes. If you're comfortable running Python, download the key list text file (with or without number pad) and the matrixgenerator Python program. It will save you a lot of time.

Modify as needed:

You may need to modify the key list file slightly to match your keyboard’s keys. A non-US keyboard can still use this routine, just make a list of your keys and the Teensy will report pin connections. The GUI key is either the "windows key" from a PC or the "clover key" from a Mac. Place the cursor to the right of the very first key in the list as shown above. This will determine where the Teensy begins to display the pin numbers as you push each key.

French computers require the shift key to be pushed in order to display the numbers 0 thru 9. I have made French matrix decoder code for the Teensy LC, 3.2, and 4.0 that takes care of the shift key so that numbers are displayed instead of @ " ' ( - _ etc. You can find this code at my Github repo.

Step 10: Connect the FPC Cable

Inspect your FPC connector to determine the correct orientation for the cable.

If your FPC connector has contacts on the bottom like the picture on the left, use your finger nail to gently lift the connector locking bar to the open position. Slide the FPC cable into the connector with the bare metal contacts pointed down (closest to the board) and the plastic backing strip pointed up. Lock the cable to the connector by gently pushing the bar down. The locking bar mashes the bare metal of the FPC cable down against pins on the bottom of the connector.

If your FPC connector has contacts on the top like the picture on the right, use your finger nail to slide the locking bar to the right. Insert the cable into the connector with the bare metal contacts pointed up and the plastic backing strip pointed down. The orientation is opposite from the first picture because when the locking bar is slid to the left, it pushes the cable up against pins on the top of the connector.

Connect a USB cable from the Teensy to the computer and wait 20 seconds for the Teensy to be recognized as a USB keyboard. This delay is in the code to make sure your computer is ready to receive numbers from the Teensy. If numbers are reported on the screen before any keys are pressed, these pins are shorted together and must be fixed. It may be a solder short on the connector which you can check by retrying without the keyboard connected. If it is still shorted without the keyboard, use flux and solder wick on the shorted connector pads. If the short goes away when the keyboard is removed, these pins are most likely ground pins that are tied together in the keyboard and must be excluded from the routine. Adjust the max_pin or min_pin values in the code to allow the routine to skip over these pins. Another reason to reduce the max_pin value is because some of the FPC traces may be visibly tied together as shown in the picture above. The original motherboard controller used these shorted pins to identify the language of the keyboard but the Teensy code will report the short and then hang.

If your keyboard has shorted pins that are in the middle, adjusting max_pin or min_pin will not fix the problem. In that case load the Matrix_Decoder_LC_alternate, Matrix_Decoder_3p2_alternate, or Matrix_Decoder_4p0_alternate routine. These routines allow you to exclude any pins necessary to avoid shorts.

If you are using a Teensy ++2.0 and you get the numbers 1 and 15 reported on your screen, you forgot to unsolder the LED located on the Teensy. The Teensy 3.2 and 4.0 will report 1 and 34 as shorted if you are scanning a 34 pin keyboard cable and the LED has not been removed from the Teensy.

If certain keyboard keys do not give a response when pressed, it is usually caused by a bad solder connection, tarnished cable, or misaligned contacts. To prove the code will report all possible pin connections, use a small flat screwdriver to momentarily short pads 1 and 2 at the FPC connector, right on top of your solder joint. Move on to pads 2 and 3, 3 and 4....., proceeding up to the last two pads, taking note of any pad numbers that don't work. For the pads that don't give a response, reheat the solder joint on the FPC connector pad and if necessary, at the header pin on the Teensy. For the Teensy LC, don't forget to add header pins on I/O's 24, 25, and 26. Use the pin translation table in step 14 to map the FPC pin number to the I/O number on the Teensy. Keep fixing your solder joints until you get a response for every pin when you short them with a screw driver. If some keyboard keys are still not working, there may be a bad connection to the FPC cable. Gently clean the FPC cable with an eraser if the metal traces look tarnished. Use a magnifying glass to inspect inside the FPC connector to see if the contact points are in alignment with the cable traces. You may need to trim the side of the FPC cable to get the proper alignment. If alignment looks good, push down on the FPC connector or lift up on the cable while trying the bad keys to see if you can sometimes make them work. You may need to add a thin piece of paper or tape to the plastic backing on the FPC cable to get a tighter fit. Erratic keys can sometimes be fixed by popping off the key cap and cleaning with isopropyl alcohol. Sometimes the keyboard has a bad key switch that will not give a reliable response, no matter what you do. The only solution is to replace the keyboard.

Step 11: Test the Keyboard

Press each key, one by one on the test keyboard as listed on the editor screen. The Teensy will send two pin numbers over USB that were connected when the key was pressed. The Teensy will then send a down arrow to position the cursor for the next key. If you make a mistake, just use your PC keyboard and mouse to erase the error and re-position the cursor. After pressing every key on the keyboard and confirming that pin numbers were given for all, save the finished file for analysis. At this point you've created a very thorough keyboard tester.

The original key list on the left gives every key and the results are in columns for transfer to a spreadsheet. Marcel's key list on the right uses the PJRC key names to make it easier for his Python program to build the matrix. If a key is listed that is not on your keyboard, use your mouse or arrow keys on your PC to move the cursor to the next key. The Python program jumps over the unused keys so there's no need to edit them out manually. If you want to assign Media keys (a key event associated with the Fn-key), push the media key (do not push the Fn key). The letters "FN" are between the media keyname and the pin numbers to let the Python program know this belongs in the media matrix.

Step 12: Determine Input and Output Pins

If you are using Marcel's Python program, it will automatically determine the input and output pins. The completed pin list file should be in the same directory as the Python program so the start up menu (shown above) will list it. To load and run his Python 3 program on a Raspberry Pi 4, use the Thonny IDE under the programming tab. The results will list the FPC connector pins that are inputs (columns) and the pins that are outputs (rows) plus it does the translation to the selected Teensy I/O numbers. The key codes are automatically placed into arrays for easy cut and paste into a USB keyboard routine (see matrix examples above).

Sometimes a strange keyboard will confuse Marcel's program and not everyone is familiar with running Python. For those cases or if you are using a Teensy ++2.0, you should use my original manual procedure. The following instructions will determine the keyboard pins based around the Modifier keys; Control, Alt, Shift, GUI, and Fn. As a general rule (that is not always followed) 8 of the keyboard pins will be inputs to the Teensy and the remainder will be outputs. The Modifier keys usually have an output row all to themselves which allows these keys to be held down while other keys are pressed. This avoids a sneak path which would cause ghosting as described in the PDF below. These “rules” are not always followed (especially by the Fn key) so you may need to do some trial and error as you build the matrix. I have lots of keyboard examples at my Github repo to help you out.

Control-Left and Control-Right will have a common pin between them. Example:

Cntrl-L 19 20

Cntrl-R 20 22

The common pin, Pin 20 in this example, will be a Teensy output, and 19 & 22 will be inputs.

Similarly Alt-Left and Alt-Right will have a common pin between them, just as Shift-Left and Shift-Right will also have a common pin. Example:

Alt-L 7 24

Alt-R 7 15

Shift-L 21 23

Shift-R 23 25

The Alt common pin will be a Teensy output, and 15 & 24 will be inputs.

The Shift common pin will be a Teensy output, and 21 & 25 will be inputs.

The GUI key is usually a single key as in this example;

GUI 9 26

Search all the other pins in the list to see if 9 or 26 are used on other keys. In this example, pin 9 was not used for any other key which means it will be a Teensy output and 26 will be an input. Sometimes both pins are used for other keys but one of the pins is used for common keys like letters and numbers and the other pin is used for less-common keys like page-up. In this case the pin used for common keys will be a Teensy input and the other pin will be an output. Note that the GUI key will still work if you swap the pins.

The Fn key is also a single key as in this example;

Fn 12 18

Using the same approach as the GUI key, search all the other pins to see if 12 or 18 are used on other keys. In this example, pin 12 was not used for any other key therefore it will be an output and 18 will be an input. If both pins are used on other keys, follow the same rules as the GUI example. Sometimes both of the Fn pins are used by common keys which means you can pick either pin as an input and the other as an output.

The eight input pins for the HP DV9000 example keyboard have been identified as; 15, 18, 19, 21, 22, 24, 25, and 26. All other pins will be Teensy outputs. Make a keyboard matrix table like the one shown above with the 8 input pins across the top in ascending order and all the other pins as outputs on the side, also in ascending order.

The orientation of the keyboard matrix is just my personal preference. You can swap the rows/columns and inputs/outputs if you want. Swapping pins may be necessary if you have a rare laptop keyboard that has diodes in series with each switch. With diodes, you need to make sure the cathode (first pin listed) is designated an output from the Teensy and the anode (second pin listed) is designated an input to the Teensy.

Sometimes only 7 pins can be identified as inputs because two modifier keys share the same input pin (usually the Shift-R and Control-R). I've even seen keyboards that had the same two input pins for the Shift, Alt, and Control keys so after determining the GUI and Fn input pins, only 4 inputs were identified. For some keyboards, the input pins are grouped together (i.e., 17 thru 24) which makes it easy to fill in the missing pins. Other keyboards have no grouping of pins which means you’ll have to begin filling out the matrix even though some input pins are missing. The remaining input pins will be revealed when some of the keys can’t be placed. Pick one of the pins from these keys as an input and continue filling out the matrix. If you get stuck, go back and pick the other pin instead.

Keyboards with dual FPC cables are the easiest to figure out because the input pins are on the cable with fewer pins and the output pins are on the other cable.

Step 13: Fill the Matrix With Keys

To manually fill the matrix, place each key name at the row/column intersection of the pins as shown in the HP DV9000 keyboard example given above. The modifier keys are in bold to make it easy to see that they have a row all to themselves. This keyboard followed the “rules” exactly.

You don't need to fill out the matrix if you're using Marcel's Python 3 program.

Step 14: Translate FPC Pin Numbers to Teensy I/O Numbers

Marcel's Python program automatically translates the FPC pins to the Teensy I/O's. If you are using the manual method, you will need to use the Teensy LC, 3.2, or 4.0 tables shown above. The Teensy ++2.0 uses the manual method. Notice that there is an LED on the Teensy 3.2, 4.0, and ++2.0 that must be removed if you are using that I/O pin.

Step 15: Load a USB Keyboard Routine Into the Teensy

A Deskthority post from "flabbergast" describes using the ChibiOS development environment to configure TMK for ARM based processors like those used on the Teensy. A toolchain such as the GNU ARM Embedded Toolchain is used to compile the Teensy code. You will need to install the ChibiOS development environment per these instructions. The teensy_lc_onekey example details the steps to create a working TMK build. The QMK keyboard routine is based on TMK and it also has ChibiOS support for the Teensy LC and 3.2. QMK offers timestamp based debouncing with various options set when compiling. There is a Complete Newbs Guide for QMK.

Jay Thompson has created a QMK fork that gives all the information for his Teensy 3.2/Lenovo T420 keyboard project. Jay provides his build environment setup and the make instructions so you have an example to modify for your keyboard.

Gordon has made a Hackaday.IO project called "QMK Powered Laptop Keyboard" which details the "gymnastics" of using QMK.

The TMK/QMK keyboard software is very powerful with tons of features but it can be confusing, (at least to me). As an alternative, I wrote an Arduino USB keyboard routine using the Teensyduino “Micro-Manager” functions. There's just 1 file to load using the Arduino IDE and it's only about 385 lines with lots of comments. I'm a hardware guy so expect ugly code but it provides a basic keyboard controller with 6 key rollover that you can modify to suite your needs. Key debouncing is handled using a 30 msec scan rate. The files named "Instructions for modifying the Teensyduino LC code, Teensyduino 3p2 code, Teensyduino 4p0 code, and Teensyduino pp2p0 code" describe the changes you need to make for your matrix. The instructions also detail how to use the results from Marcel's Python program.

Every keyboard listed below has a folder at my repo containing a Teensyduino USB keyboard routine giving you lots of examples. Pick the one that's closest to your keyboard and use its code as your starting point, (they're all based on the same basic routine). The 1525, 2100, and DV9000 folders also have Marcel's completed key list file and the results from his Python program. The D630 folders include a Teensy 4.0 keyboard controller routine in addition to a Teensy 3.2 routine. The Sony Vaio PCG-K25 folder includes a Teensy ++2.0 keyboard controller routine in addition to a Teensy LC routine. If you are using any of the other keyboard routines as a starting point for a Teensy ++2.0, you must change the "int" arrays to "unsigned int" or it will give compilation errors.

IBM380ED - Brian Chan and I teamed up to convert an IBM 380ED keyboard and trackpoint to USB as shown in this video. The code, Eagle files, and project description are in a folder at my repo. This project was documented at Hackaday.IO and Hackaday.com. Stephen designed a stand alone case for the 380 that you can 3D print with his files at thingverse. Brian has converted his IBM 380ED into a KVM, documented at Hackaday.IO.

Commodore 64 - Olga modified my code for a Commodore 64 keyboard. The Teensy LC code, key list files and project description are in a folder at my repo.

Compaq 286 - Olga also modified my code for an old Compaq 286 keyboard but he did much more. Now the program will take the pin number results from running the keylist text file so you don't need to create a key matrix. The code and PDF description are in a folder at my repo.

Blackberry Q10 & HP Jornada & Atari Porfolio - T Caschy has modified my Teensy code to work with these keyboards. The code is in a folder at my repo.

Lenovo Y480 - Luigi Caradonna has modified my Teensy LC code to work with a Lenovo Y480 with an Italian layout and backlight control. The code is in a folder at my repo. Luigi also made a stunning marble base for this keyboard. Pictures are in the "I made it" section at the end of this Instructable.

Apple eMate 300 - Billy67 has modified my Teensy code to work with an Apple eMate 300 keyboard. The code is in a folder at my repo. Pictures are in the "I made it" section at the end of this Instructable. Check out his very thorough video plus reviews from Cult of Mac and The Register to see how he made a Raspberry Pi laptop from an Apple eMate 300.

Apple iBook G3 Clamshell - Billy67 used my special connector board for this keyboard. See step 18 for the details.

Apple Powerbook models 100, 140 through 180, and 520 - Billy67 used a Teensy 3.2 to talk to these Apple keyboard and trackball units. Pictures are in the "I made it" section at the end of this Instructable. The trackball uses an Apple Desktop Bus (ADB) interface that is controlled by the Teensy after it scans the keyboard matrix. The Teensy code for the Powerbook 100, Powerbook 520, and for Powerbooks 140 thru 180 are at my repo.

GriD 1550 - SimonT192 has modified my Teensy LC code to work with a GRiD 1550 keyboard with a UK layout. This laptop has a rotary encoded "IsoPoint" mouse which has been converted to USB using a Teensy LC. The code for the keyboard and mouse are in a folder at my repo along with a PDF describing the operation. Watch Simon's YouTube video for a very detailed description of his "Aliens Sentry Gun" GRiD laptop build. Hackaday featured his project as well.

Thinkpad T43 - Nat has modified my Teensy code to work with a Thinkpad T43 keyboard and he has created a new Teensy 3.2 connector board using KiCad. The code, layout, and PDF description are in a folder at my repo.

Psion MC400 - Zedstarr used my Teensy LC code on the mechanical keyboard from a Psion MC400. His website gives all the details including a video link.

Logitech K120 - The original controller from this desktop keyboard was replaced with a Teensy 4.1 and documented at Hackster.

Step 16: Non-Standard FPC Cable Connectors

If your keyboard has a non-standard FPC cable like the Thinkpad and iBook connectors shown above, the task becomes more challenging. If you can't find a mating connector at Aliexpress or any other site, your only alternative is to remove the connector on the laptop motherboard. A common method is to put flux and low melt solder such as ChipQuik SMD removal alloy on all the joints, then use a soldering iron or hot air rework station. You will need to make a board layout that routes the Teensy I/O signals to your keyboard connector. I like to do a preliminary layout on paper first in order to place the parts and route the signals with the fewest via's. It's easy to assign the Teensy I/O pins in software based on whatever pin order makes the layout work best. It's tempting to make the layout next, but do the schematic first so your layout will have air-wires showing you how to route each trace. I didn't make a schematic for the keyboard scanner board because of the confusing front side LC/back side 3.2 routing. The downside of not having a schematic was the lack of any verification that the layout was electrically correct. I had to triple check everything before sending the file out for fab.

Eagle, KiCad, PCBWeb Designer, EasyEDA, and DesignSpark PCB are some of the free layout tools that are available. Sparkfun has excellent tutorials for Eagle schematic and layout. Also look at the Adafruit tutorial on creating parts in Eagle because you'll need to make a package and symbol for your connector. After you get your layout fabricated, you'll need to change the Matrix_Decoder software to work with the new I/O pin-out.

Step 17: Teensy 3.2 and LC Controller for a Lenovo Thinkpad T61 Keyboard

A perfect example of a non-standard FPC cable is the 44 pin connector used on the Lenovo Thinkpad T61 keyboard shown above. There are at least three web sites that detail how to make a USB controller for this Lenovo keyboard. An Instructable from rampadc uses a connector board with some glue logic and wires to an Arduino. A later Instructable from rampadc uses a single board with an MSP430 microcontroller. Mark Furland from Tome uses a connector board with wires to an Arduino. Mark's web site states that a Digikey WM6787CT-ND connector will work with the keyboard FPC cable. It lacks the plastic guides at the ends that guarantee the pins are in alignment so it takes a few insertions to get it positioned correctly. The Digikey connector saved me from having to unsolder the motherboard connector. It was pretty easy to search online and find a schematic for this laptop due to its popularity. Without the schematic or the info from rampadc, I would have been doing a lot of probing with an ohm meter to determine the ground pins and narrow down which pins needed to be scanned for the key matrix. I really like the feel of this keyboard which made it worth the effort to design the Teensy 3.2 circuit board shown above. I modified the Matrix_Decoder scanning software to only scan the 8 input pins and 16 output pins from the matrix. The scanning software produced a connection list that was turned into a key matrix table using the same steps described earlier in this Instructable. The Fn switch has its own two pins on the connector that are scanned separately from the key matrix. The Trackpoint on the keyboard needs PS/2 clock and data signals from the Teensy plus a reset signal when power is applied. The Teensy 3.2 is 5 volt tolerant so it can directly drive these signals. All of the T61 3.2 files and documentation are at my repo including a zip'ed gerber file for fabrication at JLCPCP. Nathaniel has modified my Teensy 3.2 board design for an IBM T43 keyboard which has a larger 40 pin connector. All of his design files can be found in a folder at my Github site. Pictures of his board are at the end of this Instructable in the "I made it" section.

I wanted to build a standalone T61 Keyboard on a wood base but the 3.2 circuit board needed the connector and Teensy re-positioned so the circuit board would be hidden underneath the keyboard. I figured while I'm at it, I should change over to the LC and save some money. The Teensy LC has fewer I/O signals and they are not 5 volt tolerant so I needed to make some design changes. I added a TLV810 to generate a reset for the trackpoint plus a couple BSS138 FETs as level translators for the trackpoint clock and data. To save an I/O pin, I wired the Fn switch into an empty cell in the matrix so it can be scanned with all the other keys. There was one Teensy I/O pin left to drive the Caps Lock LED. The finished LC circuit board is shown above. All of the T61 LC files and documentation can be downloaded from my repo including a zip'ed gerber file for fabrication at JLCPCP. For an even smaller Teensy LC T61 controller board, check out Martin Refseth's Github repository. He has taken my LC board design and shrunk it down to be the same size as the Teensy. A picture of his board is at the end of this Instructable in the "I made it" section.

Step 18: Apple IBook G3 Clamshell

"Billy67" has used my code and circuit boards to convert several Apple keyboards to USB. Many are documented in the "I made it" section at the end of this Instructable. One of those keyboards is from an iBook G3 clamshell which has a special 40 pin connector on the end of its FPC cable. Because of height restrictions in the clamshell laptop, the Teensy must sit inside a cutout in the board. Wires or "U" shaped header pins tie the Teensy I/O's to the connector board. Billy did some experimenting and found part number HDR127MET40F-G-V-SM-DR mates up with this keyboard perfectly. To build a prototype, he etched his own circuit board with fine pitch traces drawn freehand with an ink pen (wow, that's hard core). If you're like me and haven't used PCB etchant in a few decades, you're going to want a circuit board file to send to a fab house. For this reason, I created the Eagle layout file "iBookG3Clamshell.brd" for sending to OSH Park and a zip'ed Gerber file for fabrication at JLCPCB. These files are available at my repo. Billy fab'ed the board at OSH Park and assembled it with a Teensy 3.2 and connector (see above). Billy has added power, ground, clock and data wires from the Teensy to a PS/2 touchpad (from a Dell). The keyboard and touchpad Teensy code for the iBook G3 is at my repo.

Step 19: Keyboards With Two FPC Cables

If your keyboard has two FPC cables, you may be able to insert them side by side in one FPC connector or solder two FPC connectors on the board as shown above. It's common for one FPC cable to have top contacts and the other to have bottom contacts. Use some JB-Weld epoxy on the connector legs and unused pins to help secure it to the board. Some other two cable options are:

The Keyboard_Scanner_Dual board shown above uses a Teensy LC on one side for keyboards like the Panasonic Toughbook CF-48 which has 2 separate 1mm pitch FPC cables that are on top of each other (not side by side). The other side of this board is for a Teensy 3.2 with 1mm and 0.8mm pads for FPC connectors placed side by side. This Eagle file can be downloaded below or from my repo. To order the board from JLCPCB, use the gerber zip file at my repo.

If you don't mind soldering a lot of wires, you can use the FPC breakout board shown above for one of the keyboard FPC connectors and put the other keyboard FPC connector and a Teensy on the regular board. Wire the breakout board to the Teensy per the tables on Step 14 so you won't need to modify the software. The front side of the breakout board will accept an FPC connector with up to 18 pins and either a 1mm or 0.8mm pitch. The back side of the board is for a 0.5mm pitch FPC connector. This approach will allow you to place the breakout board in whatever location is needed by the keyboard cables. The FPC_18pin1mm.brd Eagle board file can be downloaded below or from my repo. It only costs $3.75 to order 3 boards from OSH Park. The gerber zip at my repo can be used to order from JLCPCB.

Your final option is to make a new layout like I did for the Lenovo 380 Keyboard shown above. A complete design description and Eagle board/schematic are at my repo. This could serve as a starting point for a new board layout and you can add other circuitry like a trackpoint interface or backlight connector.

Step 20: Building a Keyboard Base

The easiest way to mount your keyboard is to use the base from the original laptop, (see the Fujitsu case above). If you're not going to use the original laptop case, you can build a custom base out of various materials. Luigi Caradonna has made a stunning marble base using the CNC milling machine from his work. If you are lucky enough to have a 3D printer, you can make a custom case like TheGreenMamba's beautiful X61 Thinkpad keyboard. His 3D print files are at thingiverse. tcaschy has made a few 3D printed cases including the one shown above for a Blackberry keyboard with a Raspberry Pi Zero and LCD. Harjoc used acrylic to make a cool see-thru base. The Thinkpad T43 keyboard shown above has been mounted on a wood base by "Than the FIT man". All of these projects are documented further in the "I made it" section at the end of this Instructable. I made a Thinkpad T61 keyboard base using 3 sheets of 1/4" plywood. Each sheet had its own cutouts to provide a cavity for the Teensy and wire routing. I've also built wood bases for the Toshiba 2415 keyboards that are documented at my repo. Warren has chiseled a wood base for a Dell Inspiron 1420 that is pictured on the PJRC forum with code at his Github repo. The Fujitsu Lifebook 755Tx keyboard has a thick backside so it can sit on a desk without any case. The picture above shows how I routed the dual FPC cables into a project box that houses the Teensy 3.2. The Fujitsu keyboard project documentation is at my repo. The Logitech K120 keyboard can be re-wired for control by a Teensy as shown in the picture above and documented at Hackster.

Step 21: Keyboard Backlight

If your keyboard has a backlight, it can be controlled by the Teensy, as long as you have a spare I/O pin left over. The backlight brightness will be controlled using a pulse width modulated (PWM) signal that drives the gate of an N channel FET (see schematic above). The N-FET will handle the high current needed by the backlight LED. Only certain Teensy I/O pins are PWM capable so you may need to swap an I/O from the keyboard. Swapping I/O's is easy if you use wires instead of header pins to mount the Teensy to the board. The backlight signals from the keyboard usually come out on a small FPC cable that is separate from the row/column keyboard cable. You can glue a small connector on a blank board and solder wires to it but the fine pitch makes it difficult. I have designed two small connector breakout boards that make it easier to hook up the backlight cable. The Eagle board files can be downloaded below or from my repo and cost less than $3 to fabricate at OSH Park. One board will take an FPC connector with up to 10 pins and a 0.5mm pitch like this Molex connector. The other board will take an FPC connector with up to 8 pins and a 1mm pitch like this Molex connector. On the backside of each board are pads for a 1206 style current limit resistor and an MMBF170 N-FET. I’ve used a ½ watt, 22 ohm resistor but you should experiment to find a value that gives good brightness without excessive current. Set your ohm meter to diode mode so you can determine which pins are the anode and cathode. There are usually multiple pins for each in order to handle the current. Wire the anode pins to 5 volts and the cathode pins to the pad labeled “Drain” (which goes thru the 1206 resistor). The N-FET source is tied to the pad labeled “Ground” and should be jumpered to Teensy Ground. The pad labeled “Gate” should be jumpered to the Teensy I/O pin that will drive the PWM signal. Your code will need to set the PWM frequency. Don’t make it too low or it will flicker. To set the PWM on pin 23 to 400Hz, use the following:

analogWriteFrequency(23,400);

The PWM duty cycle can range from 0 (fully off), to 255 (fully on). To set the PWM on pin 23 to 80%, use the following:

analogWrite(23,205); // 205/255 = 80%

Use a variable for the PWM duty cycle so it can be modified with an Fn-Function key press.

Step 22: Touchpad/Pointing Stick

The PS/2 signals from a laptop's pad/pointing stick can be converted to USB with an off-the-shelf converter as shown in numerous videos. If you also want to convert a laptop keyboard to USB, then it makes sense to combine these tasks with a Teensy and only use 1 USB port. PJRC has created mouse functions in Teensyduino so the USB coding is easy. I wrote code for the Teensy that bit-bangs two I/O pins to make the clock and data for the PS/2 bus. You can download my PS/2 code below or from my repo. In the Arduino IDE, under "Tools", set the code to the Teensy model you are using and to "Keyboard+Mouse+Joystick". Compile and load the code into the Teensy. The code sets the pad/pointing device to be polled at a regular rate to see if any movement or button presses have occurred. This makes it easy to merge in with the keyboard scanning code, which also repeats at a regular rate. The Thinkpad T61 shown earlier uses this method to merge the keyboard and PS/2 trackpoint code. The Dell Latitude D630 keyboard code below or at my repo has also been merged with the touchpad code. It can be difficult to figure out the clock, data, power, and ground pins if you don't have a schematic so I wrote a step by step procedure to identify the pins. This guide also describes how to use a level translator for the clock and data signals when using a Teensy LC or 4.0. The schematic for the translator is shown above. For a quick and dirty cable solution, the clock, data, power, and ground wires from the Teensy can be soldered directly to pads on the board. If the board has an FPC connector and cable, you can use one of the breakout boards from the previous step to provide access to the 4 signals that go to the Teensy. An example of a breakout board for a Toshiba 2415 touchpad is shown above. The composite keyboard and touchpad code for the Toshiba 2415 is at my repo.

For you "real" coders, the interrupt driven trackpoint routine at Martin Prochnow's Github repo is more efficient than polling. Martin's interrupt trackpoint code has been merged with the keyboard scanner for a Thinkpad T420. Check it out at Ben's Github repo. Ben's repo also has Altium circuit board files for the T420 which has a few more keys and more connections than the T61.

A trackball, touchpad, or mouse that uses the Apple Data Bus can be converted to USB using the Teensy code at my repo. This code was merged with the keyboard scanning circuitry for a Mackintosh Powerbook 140 shown in the "I made it" section at the end of this Instructable.

I2C touchpads are becoming more popular in modern laptops. This 2 wire clock and data bus can be directly driven by the I2C pins of a Teensy so no bit-banging is needed. My Hackster.IO touchpad tutorial describes how to determine the touchpad's I2C address and registers using a Raspberry Pi. Example I2C Teensy code for a basic touchpad and for a very complex Azoteq TPS65-201A-S touchpad can be downloaded from my repo and merged into a keyboard scanning routine. The Azoteq touchpad shown above has tons of features described in it's datasheet and it only costs $5.70 at Mouser.

Before pads, nubs, and trackballs became popular, the GRiD 1550 laptop of the 1980's used a metal rod below the space bar called an IsoPoint. The rod can be spun clockwise or counterclockwise for the Y cursor movement. This spinning rod is rotary incremental encoded with 2 signals. The rod will also slide left or right for the X cursor movement which also has two rotary incremental encoded signals. The Teensy code at my repo translates these 4 signals into USB. A complete description of this project is at my repo.

If your trackpoint/pointing stick does not output a serial bus, it may only provide the 4 signals from its strain gauge resistors. The Dell D630 pointing stick has four 4K ohm strain gauge resistors that change resistance enough that the ADC in the Teensy can see the voltage changes above the noise. The Dell D630 pointing stick code and PDF are at my repo. Old Thinkpad trackpoints like the one on the 380 can also be converted to USB but its strain gauge resistors need to be amplified as documented in my Hackaday.IO project.

Some Fujitsu laptops have a pointing device called an Ergo Trac instead of a touchpad. This sensor uses magnetic field detection technology. The picture above shows the 4 connections that normally go to a controller chip on a CA20290-B40X daughterboard but it can also be driven by a Teensy 3.2. The Teensy code at my repo drives a reference logic pulse to the sensor and reads the resulting pulse voltage with two ADC channels. The voltage is converted to USB mouse movements. The sensor part number is FID-828-100/20 and it can still be purchased on EBay and other sites.

Step 23: Conclusion

The next step after getting the original keyboard and touchpad working is to add a video converter card to drive the LCD and make a keyboard, video, mouse (KVM). A KVM is often used to troubleshoot servers and the one shown above is from a Dell D630 laptop. I also added a Raspberry Pi inside the case to make a stand alone laptop. This build is described in my KVM Instructable. The Toshiba 2415 laptop shown above was converted into a KVM in order to display the HDMI video from a desktop PC as well as send the keyboard & touchpad data over USB. The documentation and code for this build is at my repo.

If you really want a challenge, check out my Instructable to make a "Battery Powered Raspberry Pi in a Repurposed Laptop". In addition to describing the Lithium battery charger shown above, there is Pi software to read the battery status registers over an SMBus and display a fuel gauge.

I hope you find this Instructable useful for re-purposing your old laptop. Leave a comment below if you have any questions, comments, or corrections.

Good Luck

Frank Adams

First Time Author

Participated in the
First Time Author

31 People Made This Project!

Recommendations

  • Microcontroller Contest

    Microcontroller Contest
  • Halloween Contest

    Halloween Contest
  • Fandom Contest

    Fandom Contest

229 Comments

0
WayneSallee-com
WayneSallee-com

10 days ago

What program are you putting your keyboard matrix in?

0
Billy67
Billy67

Reply 6 days ago

I'm sorry, I don't quite understand the question? Teensyduino is what I used to program the matrix into the Teensy.

0
WayneSallee-com
WayneSallee-com

Reply 6 days ago

I see now that you used one of the "Example_Keyboards" ino files, and then edited it, putting your own matrix in.

0
WayneSallee-com
WayneSallee-com

12 days ago

I built a laptop using a desktop motherboard, and I am now in the process of getting a laptop keyboard to work.

When I use the Matrix_Decoder_4p0.ino on my Teensy 4.1, each pin number is doubled. So if I connect pin 2 to pin 3, the output says 4 6.

0
WayneSallee-com
WayneSallee-com

Reply 11 days ago

I partly fixed the code. I think I will rewrite it without the array.

0
WayneSallee-com
WayneSallee-com

Reply 11 days ago

I got it working. It was a problem where con_pin was used in one some parts of the code, but not other parts of the code. I also added LED blink whenever pins are activated. LED blink can be easily disabled if someone wants to use pin 13. I also changed it to show real pin numbers, so that pin 0 is given as pin 0 instead of pin 1 (obviously the next stage would have to be adjusted for that). I also adjusted the key print out, making it simpler with less code, and also so that it can handle as many as 99 pins.

What's the reason for the con_pin array? I have not removed it yet.

0
WayneSallee-com
WayneSallee-com

Reply 11 days ago

Oh I see what the con_pin array is for. It's for the adapter board that you designed, so that it fits the order that you hooked up the teensy pins to the keyboard cable. I'm not using that, I'm going to be hooking it up with wires.

0
Maykro
Maykro

Question 16 days ago

hi, i want to order an board on JLCPCB, so i need the board sizes, but i get an error when opening Keyboard_Scanner_2pp.brd in Eagle. Can you please tell me the size of the board or how to open it?

0
Maykro
Maykro

Answer 15 days ago

i found out why the error was happened
"files were broken because of something obscure in the way github misbehaves when asked for a single file. Eagle had no way to know that. It can't even know you got those files from github, never mind exactly how you did so."
I download all git project and .brd loaded successfully.
source:
https://forums.autodesk.com/t5/eagle-forum/how-to-...

0
noobyme
noobyme

Question 1 year ago

Hi this might be a stupid question, but why did you use teensy instead of buying the microcontroller(saw some atmega stuff for a lot cheaper in other guides) on its own and other components? Teensy seems to cost quite some bit(bc of shipping too lmao). Also I cant believe you still reply after 3 years, what a helpful guy.

0
WayneSallee-com
WayneSallee-com

Answer 27 days ago

What mirocontroller are you talking about?

0
Frank_Adams
Frank_Adams

Reply 26 days ago

The Teensy LC uses the MKL26Z64VFT4 Cortex-M0+ and the Teensy 3.2 uses the MK20DX256VLH7 Cortex-M4 from NXP Semiconductors. The ATMega32U4 or ATSAMD21E18 are some other possible microcontrollers. They need to have enough digital I/O's for your keyboard's FPC cable and need built in hardware for keyboard USB HID. Besides having to solder one of these surface mount devices to your own board (that you designed), you will also have to come up with a way to program the boot loader so you can use the Arduino IDE via USB. It's a lot of work so I find it easier to use a Teensy which has taken care of all these tasks. In addition, the Teensyduino library has more keyboard coding features but it only works with a Teensy.

0
Frank_Adams
Frank_Adams

Answer 1 year ago

I chose the Teensy because I had past experience with them. You can certainly use other less expensive controllers if you want.

0
noobyme
noobyme

Reply 1 year ago

I see, thank you for replying!

0
WayneSallee-com
WayneSallee-com

27 days ago on Step 1

You wrote:

"Pitch = Total width / (N + 1) where N is the number of pins"

That should be:
"Pitch = Total width / (N - 1) where N is the number of pins"
0
Frank_Adams
Frank_Adams

Reply 27 days ago

I just measured 3 FPC keyboard cables and in each case, using N+1 gave me the correct pitch.
28mm wide/(34pins + 1) = 0.8mm pitch
27mm wide/(26pins + 1) = 1.0mm pitch
25mm wide/(24pins + 1) = 1.0mm pitch
It's easier to visualize if you think of a 2 pin, 1mm pitch FPC cable. It will measure 1mm from center of pin 1 to center of pin 2. It will measure 1mm from center of pin 1 to the left edge and 1mm from center of pin 2 to the right edge. The total width of the cable is 3mm. The formula gives: 3mm wide/(2pins +1) = 1.0mm pitch

0
WayneSallee-com
WayneSallee-com

Reply 27 days ago

Yea, I see now.

You did say "measure the width of the entire FPC cable" not "first pin to last pin". :-) I was thinking first pin to last pin. First pin to last pin would be -1, but as you correctly stated, width of cable is +1.

0
Sweettastic
Sweettastic

Question 4 weeks ago on Step 4

Due to the chip shortage I'm finding it hard to find the teensy 3.2 or 4.0, but PJRC has some 4.1 in stock and I was wondering how hard it will be to modify this project to fit that board? I know it won't fit directly onto the pcb you've created but I can solder leads to the respecting pins. I'm mainly concerned about the software, im not much of a programmer and I vaguely understand what you are doing with the program. I just wanted to know if ill need to do some modification to the program or if I just plug up the pins right it should work?

0
Frank_Adams
Frank_Adams

Answer 4 weeks ago

Yes you can use the Teensy 4.1 with my software and it will work fine. You can use a board made for a Teensy 3.2 or 4.0, even the ones with a cutout (but the Teensy 4.1 will not be down in the cutout). First wire I/O's 24 up to 33 (depending on how many you need) to the board with jumpers using the translation tables on step 14. These wires will be easier to deal with before the Teensy is pined down to the board when you add the connections for I/O's 0 thru 23. Let me know if you have any more questions. When you get it working, upload a picture so others can see your build. Good Luck.

0
daisuke
daisuke

Question 5 weeks ago

Hi Frank. Thanks for the great article.
I have a Vaio P with Japanese keyboard and am considering following your guide.
In fact, I haven't ordered anything yet, but before I do, I would like to hear your take on the following question.

The Japanese keyboard has some special keys. (These are keys that tell the Japanese input program) And after installing and checking the Arduino IDE and Teensyduino, there is no "Japanese" in the Arduino IDE menu under Tools -> Keyboard Layout.
I am prepared to have to modify the program and go through some trial and error, but is there any chance of getting it to support Japanese-specific keys?