A text file was started which outlined the important measurements for the enclosure. Those measurements were added by referencing a dimension drawing found online by searching for "1602 LCD dimension." Once the appropriate variables were assigned some of the basic shapes were programmed without entering them in the OpenSCAD program. There was an advantage to this and a disadvantage. The advantage to programming with no error checking was that there was no temptation to check for errors so the workflow was uninterrupted. The disadvantage was that compounding mistakes, such as measurements which relied on previously entered measurements, were potentially huge.
Once the code was put into OpenSCAD some of the mistakes were corrected such as the placement of mounting holes for the LCD screen. These holes were visually investigated and appeared consistent with the dimension drawing used as a reference. No port for power was modeled since the method hasn't been decided. A hole may be drilled in the existing version unless other changes are needed in which case it may be reprinted.
To do:
The rest of the posts for this project have been arranged by date.
Text file containing beginning of enclosure code
Once the code was put into OpenSCAD some of the mistakes were corrected such as the placement of mounting holes for the LCD screen. These holes were visually investigated and appeared consistent with the dimension drawing used as a reference. No port for power was modeled since the method hasn't been decided. A hole may be drilled in the existing version unless other changes are needed in which case it may be reprinted.
3D model of enclosure front and back
To do:
- Debug code
- Reduce jitter in timing
- Hardware
- Make power supply go to servo power
- Add 5-6V power in
- Make code public
Design enclosureScreenPotentiometerPowerButtons- Print enclosure
- Draw schematic
The rest of the posts for this project have been arranged by date.
A list showing of all the final posts of COMPLETED projects.
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-03-10 (Tu)
2015-03-10 (Tu)
Comments
Post a Comment