Step 13: Notes on measuring things

The enclosure was designed with Rhino, which is currently available for free on OS X while they are testing and developing the app.

Before designing an enclosure, we had to measure every component we were sticking inside. In theory, different devices are built using their local measurement system (metric everywhere except for the USA). In practice, we found that every device came to a fairly round metric value in millimeters, even the Blue Snowflake microphone.

There are mainly two kinds of measurements we had to make: side lengths, and mounting hole positions. To make all these measurements we used a standard digital vernier caliper. For side measurements, it’s helpful to get a basic bounding box of the area that the component occupies. This will keep your components from hitting each other once you place them inside the enclosure. For the mounting hole positions, it’s important to accurately measure the hole diameters or you might create something that’s too loose or tight for the component. Instead of adding or removing small amounts from your measurements to account for design features like tight and loose fit, use your first pass at measuring to create a set of measurements that are as accurate as possible. Later it’s possible to revise these measurements after printing material tests.

When measuring mounting holes, measure them all from the same reference location rather than relative to one another. This keeps your measurement errors from accumulating.

The hardest component to measure was the Blue Snowflake which had three mounting holes in a circle that seemed to be at non-grid positions. To measure these, we measured the distance between the center of the three holes and created a triangle with those side lengths. In the end, we didn’t mount the Blue Snowflake using those holes.

<p>can you answer me please i am in eighth grade and I am making this for language arts. ASAP</p>
<p>how long did this take you</p>
<p>may price more than 10 k INR</p>
<p>What is the total price of this?</p>
<p>i really like the design. very well made! </p>
<p>ain't there a video for it? i wanna see it moving @_@ please :|</p>
Does someone have the message: &quot;Cannot read property 'HITId' of undefined&quot; when executing app.js ?
<p>Have you ever considered turning this into Wheatley from Portal 2? that is my ultimate goal for this.</p>
<p>I did some computer vision on the raspberry pi. For instance face detection and feature tracking. I am working on improving it until it is not using all of the raspi computation power, which is currently the case.</p>
<p>Great project and instructions.</p><p>Im confused on how the noodle actually processes events. What is the response time? Can I make it automated or does it have to have a real person always?</p>
<p>Response time from Mechanical Turk is around 5 minutes, but if you follow this Instructable in general and then substitute your own Turk form that posts directly you a dtabase/service you have set up, then you can get the response time down much lower (maybe 30 seconds).</p><p>Some basic things can be done automatically (like motion detection or basic speech to text) but we were focusing on the manual things.</p>
<p>Am sorry if i skipped but i found no video of your robot. A video would be really nice.</p>
<p>There isn't a video, mainly because the pictures are more representative :) The video would mostly show it playing sounds or putting pictures on the screen, or doing something more digital with the network.</p>
this is amazing! It never ceases to amaze me what people can do with a raspberry pi - you are a genius
<p>Need a video of the robot please!</p>
Oh,so intreseting
<p>Great job!</p>
<p>Amazing. You should enter in a contest. You'll be sure to win something</p>
Love it.

About This Instructable




More by lmccart:Noodle: a crowdsourced robot 
Add instructable to: