A second Vibrating Distance Sensor prototype was built using similar parts. This build was simplified by the fact that one prototype had been built and some of the steps had been streamlined in the first version. Since the build was more streamlined pictures were taken regularly in order to write a comprehensive set of directions.
After building the device and filling the gaps with silicone the program failed to function properly despite being tested during construction. This failure to operate could be due to some semi-conductive properties of the silicone caulk causing shorts on the sensor and controller. Conductivity will be tested when the silicone dries.
Files for Vibrating Distance Sensor:
The OpenSCAD files below are not necessary unless you want to change something
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.
Final look of device while drying
Photos to be used in instructions
After building the device and filling the gaps with silicone the program failed to function properly despite being tested during construction. This failure to operate could be due to some semi-conductive properties of the silicone caulk causing shorts on the sensor and controller. Conductivity will be tested when the silicone dries.
Files for Vibrating Distance Sensor:
The OpenSCAD files below are not necessary unless you want to change something
- OpenSCAD code. Download all files below
- Enclosure. Open this one
- Distance sensor footprint Support file
To Do:
- Construct second prototype
- Get prototype working
- OR
- Build another prototype and use different potting compound
- Write instructions
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-05-05 (Tu)
2015-05-05 (Tu)
Comments
Post a Comment