Monday, December 6, 2010

Photos!

Simon's Merkurpult (week of 10/28)

 
Plan.
Our semi-functional other module. (Week of 11/4)

FORESHADOWING

SPRANGS. Couldn't get enough of the right kind to make this happen.

The bare bones of the radial tessellation I was working on. Sketches to come (I hope)


Better late than never- our team design! (Week of 10/21)

Sunday, December 5, 2010

Tuesday-Wednesday 10/26-7 (37-36 days left)

Group meetings were disorganized and lacked motivation. Discussion would last a few minutes but would fade to aimless chatter before anything of value was said.

When crunchtime came around, we were able to get something that worked. Most of our sensors (i.e. the ones we had the correct parts and data for) worked on their own, and we had a slight issue with actuating them in tandem, but we were able to make the solenoids work with the help of the external DC power supply and the LEDs with prompts from the Ultrasonic Range Finder. While we had working programs for the Pressure sensor and tilt ball sensors, neither made it into the demo; the voltage across the pressure resistor was too high and the device would just heat up and not produce an LED response upon being pressed, and the tilt ball sensors were inaccurate and therefore not worth demo-ing.

The form this ended up taking was as follows: a Merkur stand with LEDs lining the vertical piece of the structure and a rotating lever that accentuated the upward and downward motion of the solenoids. The solenoids, when actuated, would push down on one end of the lever, pushing the other end up to approximate our desire to have “pixels” in some pattern that when pushed or pulled would allow light to come from a light source behind the surface (we would likely mount it in front of a window). As the URF read in values of increasing proximity, the LEDs on the vertical Merkur piece lit up from bottom to top. This was as complicated as we were able to get, but we felt it adequately demonstrated our desire for the surface to react to multiple stimuli in various ways. Pictures will come!

Monday 10/25 (38 days left)

Continued working on the sensors today- had some trouble with the accelerometer. It seems I may need an ADC converter to make it work on the Arduino- it says on the parallax website that there’s an onboard one but all the schematics I can find are poorly labeled and seem to include one. Look out Chris, here comes an Arduino question!

Wednesday 10/20 (41 days left)

Doncha just love anachronism? Forgot to post this one:

We met at our earliest convenience (Wednesday, due to people's being away for fall break) to write our contract for the Team Design assignment. Here are the highlights:

Missions
- functional (duh)
- well-designed (sleek and elegant)
- uses element of surprise (for users as well as for us, i.e. we don't know how it will evolve)
- function informs form (i.e. we won't make the same mistake as with the visor- we don't want to constrain our design to too narrow a situation/problem)

Vision (of a team that is/will . . .)
- Efficient
- Maximize efforts and skill sets of all members
- Communicate well
- Allow for ideas to flow naturally

Values
- Democratic, consensus-based decision making
- Communication
- Maintained Inspiration
- Respect for other obligations: Studio, Senior Design, Exams

Goals
- Communicate well
- Substantial weekly improvements
- Component testing (NOTE: this was misunderstood in the final critique. "Component" here refers to smaller subsystems of our larger project, such as testing the motion sensors on a standard circuit. This does not refer to buying electrical components and playing around with them, which we did in a limited manner.
- Research precedents throroughly
- Learn new skills

And here's our SWOT analysis:

"We are a unified and dedicated group: we are cooperative and respond well to constructive criticism, and are resourceful with what materials are available to us. We brainstorm well, and as a result we often undertake imaginative projects with a high level of conceptual development and pursue these projects with a fearless attitude and a committed work ethic. We are able to self-motivate as a group; we respond well to the encouragements of other team members.

Our group’s most notable weaknesses all relate to timing. We often attempt to do more than is possible in the given amount of time, and if not we budget the time we do have poorly. Our process for assembly has been inefficient, as we put each entire model together at once, as opposed to testing before interfacing with other components. We are also occasionally prone to poor communication skills, as some team members are often uninformed of progress by the remainder of the team after having missed a meeting. Other issues we have had arise from lack of experience in Digital Project and biomimcry research.

Opportunities for our group consist mainly of as-yet untapped resources: we can take fuller advantage of our access to the metals studio and the tools therein, as well as relying even more on renderings, drawings, and other media of communicating our ideas and models to the class in critique. We also are fortunate to have a team member who works in the patent industry, should we invent a new mechanism or device.
External threats that could impact this team’s performance will consist mainly of scheduling constraints as other classes become more demanding and exams approach, so we will need to plan our time very efficiently. Acquisition of parts and components for the construction of our surface could also slow down our progress in making this project a success if they do not proceed in a timely manner, meaning that the sooner we can determine what we need the less likely the purchase and delivery of these items will impede the development of our finished surface."


We also agreed on a decentralized team structure that enabled everyone to work in different capacities and contribute to all portions of the project, knowing of course that some peoples' past experience and skills would to some extent determine the way in which we would choose to utilize them. For example, Chris would be in charge of Arduino-related aspects of the project, and Diana would be in charge of documenting the group's progress from day to day. This would leave the rest of us to take charge of mechanization and anything else that would need doing.

Sunday 10/24 (39 days left)


          Today we met in the Dude to start planning our final project. The general schedule we were given asked for a $200 budget and an operational prototype for Thursday, and per Karl’s morning email we started small (he said to stick to what works and design based on functionality). We laid out and listed all of our new toys that had come in the mail and used those as a jumping-off point for what our product could become. This was marginally successful, and we ended the meeting by assigning each member of the group who was capable two of our new sensors/components to wire and code: Simon had the force-sensitive resistors and the camera, Chris had the solenoids and the Temperature/Humidity sensors, Patrick had the Ultrasonic Range Finder and the microphones, and I had the accelerometers and data logger.
           Our brainstorming focused on the interactions we wanted users to have with our project based on what we could accomplish with our newly acquired sensors. Simon wanted something ambient- ideally the users would be unaware of the product’s presence until a response from the surface is provoked. We also talked about trying to incorporate our previous design (the triangles of project one) into this surface, or at the very least a folding/revealing mechanism.
I went to DL1 and assembled the data logger according to the instructions online. This took a while and I accidentally burned my finger but I was able to finish it before my ride had to leave. I didn’t get to code anything for it, but tomorrow I should be able to take care of both that and the accelerometer.  I feel optimistic that we can make a pretty cool (and functional) prototype this week, and look forward to finding out how this project evolves.

Thursday 10/21 (35 days left)


We were asked to order some toys to play with for next week- we all looked around on the Parallax, Sparkfun, Adafruit, and Jameco websites and compiled a list of sensors and components we wanted. Here's what we got:

3 solenoids
data logging shield for arduino
flex bend sensor
5 tilt ball switches
2 force-sensitive resistors
temperature/humidity sensor
2 electret microphones
arduino protoshield
CMOS camera
3 stepper h-bridges
CO2 gas sensor
ColorPAL color & light sensor

I was most excited about the data logger and the accelerometer. The data logger would allow us to track and analyze data and actuate based on trends as opposed to instantaneous data values should we want to. The accelerometer would allow us to track motion we actuate and further actuate the surface based on that.

Our field trip today was a journey to the botanical gardens. We were given a tour by David Michener that covered the majority of the indoor facility and which gave us largely formal inspiration- the two most intriguing plants we found were the “Swiss Cheese Plant”, so named for the characteristic holes in its leaves that allow light to reach the lower leaves, and the aspen plant, whose leaves are table to bend and twist towards light so as to increase absorption. Here are some pictures:  

Aspen? Mmmmmm, California.

Goes great with ham on rye.

HEY JOHN!

Get ready- this is the week I upload all the blog posts I've written but not posted, plus the ones I've neglected to write the past three weeks. If you hadn't already noticed I'm slightly verbose, so ready your reading glasses.