Step 17: Enclosure problems

Even with significant testing, some problems with the enclosure remain.

1. The walls on the battery enclosure were too thin. We recommend 3mm as a minimum for working with Objet VeroWhite when doing light structural design like this enclosure. We tried to design snap-locks on the side of the battery container, but they broke off after sliding the battery in the first time. Likewise, some sharp corners on the battery holder broke off while transporting Noodle. In general: expect VeroWhite to deform more than you expect when it is thick, but to also be more brittle than you expect and break when it's thin. Our guess for a reasonable width was based on printing a palette of objects with varying widths, but it would have been helpful to bend each of these to its breaking point to get a feeling for the material's properties.

2. We didn't model the step up converter correctly, and only measured a couple tall components instead of the complete bounding box. This means that when we tried to put the USB hub and the step up converter inside the box, they bumped into each other and only one would fit.

3. All the posts fit pretty well, as we found from our post test, but some were slightly too loose. In the end, we used hot glue to keep some of the components stuck to the mount points. We also tested some snap mounts but found VeroWhite to be too brittle at this scale to smoothly deform. With more testing, it may be possible to create snap mounts for holes like the ones on the Raspberry Pi.

<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: