2018-11-25 (Su) ModuKey

The first side of the keyboard had been wired, it was time to start on the second side. Of course, the buttons have not been installed, but the sign on the back of the PCBs says, "SOLDER SWITCHES LAST," which is there for a good reason. PCBs from the first side were fastened in place with wood screws.

Fastening the boards to the wooden platform

An ordinary 4-conductor coiled phone cord was salvaged for this project to become the connecting wire between the halves of the board. Phone cord is ideal because it can be ordered inexpensively, it is still a common commodity because of the prevelance of VOIP phones, the coiled wire is great for a flexible out-of-the-way cable which looks nice. Coiled USB cables can also be used in this case used if they have all four conductors. One end was bulked up with electrical tape so it would stay secure inside a nylon wire strap. 6.35mm (1/4") straps were used. They are a common item for running television cabling.

Coiled phone cord attached to one side of the keyboard

The second side of the keyboard was attached in much the same way. Each wire was assigned to a specific pin. In this example, the white wire was Vcc, the pink wire was SDA, the blue wire was SCL, and the yellow wire was GND. In the same way that the first board to be wired was a 1x4, the second half also connected to a 1x4. Since the data lines were meant to be in parallel, it didn't matter where I tapped off the data and power pins, in this case, they came directly from the controller.

Coiled cable run between keyboard halves

ModuKey on GitHub

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

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

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

All information on 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.