2018-12-04 (Tu) ModuKey

The diamond-shape key arrangement had the unexpected consequence of interfering with the nearest key. This problem happened on both halves of the keyboard. Differently shaped keys, including round keys, were considered, as well as cutting up some of the non-square keys or printing new keys.

Key interference

Two of the inexpensive blank keys were modified. The first tool was a razor saw, which can be seen below the round needle file which was also used. Neither of these tools were effective at reshaping the ABS keys.

Razor saw and file attempts

A sturdy scalpel seemed the best option for this modification. A Dremel may have also been a good choice for such fine work but the scalpel was an easy choice for modifying two keycaps and did not require an outlet or cleaning my desk.

The kind of photo taken right before an emergency room visit

Once cut away, the top of the keycap was entirely intact and felt the same, but the clearance issue was gone. There was no trouble pressing the key even while the keybelow it was fully extended and most prone to interference.

Key clearance

A black background, spotlight, tripod, and camera were set up to take a rotating shot of the keyboard, with all of its keys attached. At this point, the keyboard had received all of its major structural parts but needed programming.

Setup for a rotating photo animation

A burst shot was taken while the keyboard was spun by hand. A couple of the photos were of overlapping angles so they were deleted. The images were scaled in GIMP to reduce the file size, and turned into a single animated image. This keyboard has been named Lazy Brown Dog.

Lazy Brown Dog

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.