It may be too late too figure out the hardest part, yet, it is a good time to explain the hardest part of the Rhino Glove. Because, after a long process of loving and hating programming Arduino sketch for this project, I understand writing a proper code to handle 6 inputs as data and retrieve information out of them is a frustrating part of such a project. In my project, three bend sensors, with three different range of output has been used to help program figures out what accelerometer outputs mean. For example, bending index finger, as a result bending sensor related to index finger, should be interpreted as a trigger for extruding object. In addition, bending middle finger sensor should trigger the rotation control. However, when user moves one finger other fingers move as well, and bend sensors send data to Arduino, writing proper code to find user desired action out of three different bend sensor outputs is a very hard job to be done. Same, when user moves his hand in an arbitrary direction, Arduino can read three different values of acceleration, each for one axis, figuring out the exact movement of hand using these three stream of data is a difficult task. In fact, I found it hardest part to build. Unfortunately, I faced this problem in last phase of my project, which was demonstration. I have not yet found out a way to overcome this problem. In future, I will focus on solving this problem more dedicated.
Archive for the 10. Build the Hardest Part Category
For long distant couples who suffer imbalanced conversation due to separation, soft drink · for two is a conversation display that encourages human-human interaction, unlike previous sound visualizers, which focus on individual pattern and human-computer interaction. Soft drink · for two engages couples to build a rich conversation together.
download detailed documentation: Soft drink for two_final report
The hardest part of my final project turned out to be a crazy amount of LED wiring for the interactive element of my Interactive Beer Pong Table. Figuring out how to wire 18 tri color RGB LEDs together was not a problem, and made putting it together sound and look very easy. However, this was not the case especially considering it was my first time soldering ever. First tip I learned of soldering…get a good iron. Second tip, set aside a lot of time, patience, and probably a beer or two to deal with the frustration of the tedious task. Once all the LED’s were finally soldered together adding the right transistor was a bit of an issue as I first tried a MOSFET instead of the simple TIP 120 I ended up using. The MOSFET would have worked however I got a 10V one instead of the required 5V (thank you radio shack).
Anywho, it worked out as you can see below (and above in the final project post). And now i cant WAIT to solder like crazy sometime soon, quite possibly for MayurSASA’s 2010 Booth.
At the very beginning i thought programming the accelerometer is the hardest part. However, after I took a look at this website:
the task became very easy. What actually turned to be the hardest part is mounting the electronics to the pillbox. Specifically, making the boxes covers act like switches especially that they have ting edges. So I tried:
1. Wires: did not work well because of tiny space and attaching them with a hot gun is just a pain.
2. Conductive paint: worked perfectly but after many trials, the paint start to take off from the box and that is absolutely not the desired result.
3. Finally, I have asked and done some research: CONDUCTIVE FABRIC solved my problems easily. they stick very hard to the box and stay after long number of trials of opening and closing the covers. Also, they are very flexible and can be easily mounted to the box. Moreover, you can shape them the way you want and their conductivity is high.
Hey everyone, so my project was the robotic spider controlled via the wiichuck and (for me) the hardest part about this assignment was how to actually build the spider. I did a lot of research as to what was the easiest and strongest build for it. Initially, I wanted to work off this design. However, when I prototyped a leg in this design with balsa wood, I found it difficult to attach a metal wire to the servo arm and get enough control and accuracy to operate the leg.
I did some more research and found the hexapod robot, it also appeared in many youtube videos. I ended up designing my robot largely off of this design… the only major change I incorporated was downsizing the legs from 3 servos to 2 servos on each (as the arduino only has 12 digital outputs). Although the hexapod robot is documented, there is no exact specification of what dimensions each part is since they were selling a kit. I didn’t want to buy the kit, partially because I couldn’t use 18 servos, but mostly because I thought it’d be fun to make it myself.
Because of this I did a lot of measurements and planning, and made a prototype out of wood. I drew up a design in Illustrator and had it laser cut on acrylic plastic. To my surprise, all of my laser cut pieces matched perfectly to what I wanted. If I had to do it again, I would make some slight changes in my shapes, but nothing too major.
For specific step by step instructions as to how to make the robot, look for my instructable that I will (hopefully) post shortly. Attached are some images of my robot and the process in making it.
I’ve managed to overcome the hardest part in my project, which was making an Arduino talk to my cell phone. In order to do that, I had to get an WiShield from Async Labs. Using their examples, I managed to create a Socket server that accepts phone events from the phone and actuates any sensor in the Arduino. On the phone, an event monitor was created, which listens for incoming calls. When an event that I’m interested occurs (in my case, ringing, missed call and new SMS), the phone application sends a message to the WiShield, which interprets what’s required and triggers the action on the Arduino board.
A question that got me thinking during my preparation for the demo was: “How do I get the Ambient Notifier to reset if I don’t want to call the person back?” Since there aren’t any switches, I resolved to capture the shaking movement on the phone, since it’s so popular for the undo and reset status on the iPhone.
Here you can find the source code for Arduino+WiShield side: Arduino Ambient Notifier
Here you can find the source code for Android side: Android Ambient Notifier
Here you can find my report: Ambient Notifier report
Here you can find my paper: Ambient Notifier paper
Here you can find a poster for my demo: Ambient Notifier poster
Here is a demo video of Ambient Notifier working: