Enclosure modeling has been problematic by coincidence or fault. Models seemed to render properly but the printing software refused to create printable data. The previous model, which used internal ledges for the screws would print without issues but the lid on the new model was not recognized by the printer’s software. When the lid was rendered it was nothing more than a basic cube surrounded by four wings for the bolts to pass through. Several things were tried like rendering the lid and enclosure separately and copy-pasting the screwWing code rather than the use<> statement. All results were the same.
A second enclosure module was planned which would have cones on the outside of the enclosure near the lid. This version would print without supports due to the cone shape and not require long bolts to span the whole height of the enclosure.
Downloadable Files:
Rotating view of enclosure
A second enclosure module was planned which would have cones on the outside of the enclosure near the lid. This version would print without supports due to the cone shape and not require long bolts to span the whole height of the enclosure.
Downloadable Files:
- Common OpenSCAD files
- Servo footprints for OpenSCAD.
- Arduino Code for wired keyboard
- Spreadsheet for chords.
- Wrist mount
- Terminal board
- Input voltage
- USB
- Make base for keyboard
- Spacers
- Magnet mounts
- Integrate:
- Enclosure for each controller
- Potentiometer access
- Activation switch
- Debug
- Test
- Refine
- Repeat
- Write instructions
- Compress and link to all files
- OpenSCAD files
- STL models
- Arduino code
- Make diagram with every part labeled
- Schematic for servo controller
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 f
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-10-13 (Tu)
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 f
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-10-13 (Tu)
Comments
Post a Comment