Stranded copper wire replacements
To save room in the enclosure the servo wires were trimmed and soldered directly to the Arduino. This saved considerable room because of the bulky plastic connector which was difficult to fit inside the enclosure due to its rigidity. The stiff wires going between the controller and distance sensor made fitting everything together more difficult than with the flexible wires.
Severed and tinned servo wires
Directly soldered servo wires
A layer of electrical tap was applied to the back of the distance sensor to act as insulation as before. Since the distance sensor and Arduino were pressed together closely it was important to keep them electrically insulated. The most recent enclosure was printed which did not have a rounded hole to pass a USB cable through but instead had a rectangular hole to fit a coaxial power connector. The small coaxial power connector was glued in place using super glue and holding it stationary until it dried with spring-loaded tweezers. Small tabs on the power connector were trimmed off so the face of the connector would sit flush with the outside of the enclosure.
Layer of tape applied to distance sensor
Coaxial power connector being glued in place
Files for Self Contained Haptic Distance Sensor:
- Arduino code
- STL model for enclosure
- The OpenSCAD files below are not necessary unless you want to change something
- OpenSCAD code. Download all files below
- Design way for servo cam to push on user without rubbing
Replace all potentially faulty wires
- Debug program
- Get reliable readings from distance sensor
- Correspond distance readings to servo rotation
- Using floating limits
- Take rotating photo of device
- Write instructions
The rest of the posts for this project have been arranged by date.
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 email@example.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.