Reverse Engineered Object: Selection


For this project, we had to find three objects that we could reverse engineer: in other words, take apart to make a 3D model of.

I choose all of my objects because they are some of the only things around my dorm that I can take apart without consequences. The hand model has moving parts with the fingers, but I'm not entirely sure I could put it back together perfectly. On the other hand, the nail clippers I have taken apart and put back together countless times. I don't tend to own a lot of mechanical items that allow for me to take apart and put back together that is small enough to measure with the caliper, so these were the items that made up my choices.

The object I'm most likely to pick is the Wii remote. I also ordered a screwdriver to open the inside with too, so it would give me a challenge to recreate the inner breadboards and such. The other two are moveable but not as nice to take apart. Not to mention, while they have some complex curves I think that they may be too easy for a three week time period.




Comments

Post a Comment

Popular posts from this blog

Algorithmic Surface Modelling + Animation

Image
Tile design: Test Shapes: To experiment with tiling, I initially tried using a cylinder and a shape similar to the class demo to make sure my algorithm works. For my animation, I tried to tesselate my design to a series of lofted polygons, but I found that when I tried to input the loft into the surface morph, it gave me an error saying "1 value inherited from 1 source... Null". It didn't matter whether or not the loft was connected to the rotate axis (between polygon and loft) and I couldn't manage to make it work even when using mesh brep or the brep parameter. Even baking this surface did not help.  I found that using this shape gave me two main errors: 1. Divide Domain: Data Conversion failed from Brep to Domain²  2. Surface morph: Data Conversion failed from Brep to Surface Putting mesh brep between brep and divide domain² helped, but it still had errors regarding the V domain values being 0. Oddly enough, this exact same algorithm worked when I replaced polygon
Read more

Parametric Structure & Animation

Image
In class tutorial animation: My own spin: I found that it was a really straightforward process, especially since I've had experience already with making short animated gifs. What I found to be really nice was that instead of a choppy gif made up of 3 or 4 screenshots, I was able to create something really smooth. I also found that rhino's naming structure for saving the .png files made it so I didn't need to worry about organizing 180 or so individual images. The hardest part was thinking up a new object to create and when I did, I found that I had to make individual brep's and play around with positioning a lot.
Read more

Algorithmic Surface Model for SLA Printing

Image
Revised Design in bounding box: Some feedback I got from the class was to consider the direction that my design is going towards. In particular, which way the "arrow" part of my design faced. I decided that I liked it with the box shape facing up. One critique was to improve the support for the corners, specifically the way some intersections hang with little support. Because I'm using a lattice structure, Bryan mentioned that I could deal with delicate parts by increasing the thickness of the print or else I could use an underlying form as a support structure. Since we will be using clear resin, I plan to use this feedback to create a low relief design for final print using an underlying form. Along with the feedback regarding structure, it was mentioned that the way I set up my piece made it so that new iterations would be fast without changing the surface design. This came with the idea to explore more forms. Overall, I made 14 shapes using the revolve tool in rhino, b
Read more