A support rod was added to the back of the pieces in parallel to the common axle. This support rod was added by drilling through all the pieces and adding nuts as the rod was pushed through the holes. Adding rods produced a sturdy structure and allowed the keys to press easily but adding rods was tedious and required time consuming alignment.
Changes were made to the model so the axel would use a common bolt size, #6. This allowed for less specialized hardware which was easy to find and less expensive. Simple flanged spacers were purchased as well which added distance between the pieces without the need for numerous lock nuts. For a common axel a long #6 bolt was run through the axle holes, washers, and flanged spacers. A nut was placed on the other end and left loose, a lock nut would be ideal. This arrangement produced reliable button presses.
To do:
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.
Rear support rod and common axle
Changes were made to the model so the axel would use a common bolt size, #6. This allowed for less specialized hardware which was easy to find and less expensive. Simple flanged spacers were purchased as well which added distance between the pieces without the need for numerous lock nuts. For a common axel a long #6 bolt was run through the axle holes, washers, and flanged spacers. A nut was placed on the other end and left loose, a lock nut would be ideal. This arrangement produced reliable button presses.
Easy to assemble version with inexpensive hardware
To do:
- Revise model and reprint
- Add electronics
- Figure a way to mount
- Figure a way to move hinge pieces
- Make model and OpenSCAD code public
- Write keyboard code
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.
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 in this blog, or linked by this blog, are 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 claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
2015-07-26 (Su)
Comments
Post a Comment