Atlas Stones Challenge - Day 8

Final robot design

Final Design/Thoughts: We were finally able to run a trial with our robot. It successfully completed the course, and we received full credit. The robot finished the course in 2 minutes and 3 seconds; it was not as fast as we would have liked, but at least it ran smoothly. The programming worked well - there were no delays nor did the robot get confused.

Throughout this challenge, we definitely came across setbacks, but they were minor in comparison to those we experienced in past challenges. Building the structure was almost second nature after being the third time around, and coding was not too difficult. However, something that we definitely learned was to use our resources wisely and efficiently. Many Lego pieces were not available due to misplacement and "hoarding"... We had to make do with the few pieces we had, which in the long run, was a blessing in disguise; our robot was simple and effective. Next time, both of us hope to do improve the speed of our robots.

Video link: https://drive.google.com/open?id=0B_EDAYZEobu0eHBEUHdDbHJWcVU

Atlas Stones Challenge - Day 6

Today we continued to program. A few classes ago, we identified that the cause of jerking movements was due to an abundance of friction. We were able to eliminate this problem by adding a small piece that acted as a spacer. Doing this almost doubled our speed along with smoothing out the ride. At a point, this caused the robot to move too fast. We ended up decreasing the power so it would still follow the line. Once our robot is able to successfully complete the course, we plan on gradually increasing the power until it reaches its maximum speed.

Atlas Stones Challenge - Day 5

Today was another day of programming. Because of time limits, my partner and I decided to divide tasks; one of us programmed while the other worked on what goes on Blogger. An issue we dealt with today was the slowness of the NXT programming software. Much of the programming contains a similar pattern, so copy/paste would have been the most efficient route. However, whenever we tried to do so, the program took five times as long to load. Not as much progress as we anticipated occurred today. Next class we will continue the same process.

Atlas Stones Challenge - Day 4

Last class was the first trial day. We finished the general construction portion of the challenge, so we continued to work on coding. By the end of that class, our robot was able to lift and bring back one mass (50 grams); one third of the programming was completed. However, towards the last twenty-minutes, while running the track, the robot would make small, quick, jerking motions during turns. We knew that the distance of the wheels from the NXT Brick may have been causing a large amount of friction, but we were unsure if it was the cause of the jerking as well. For next class, we may rethink wheel placement and swivel size. We will definitely continue working towards a completed, efficient coding.

Atlas Stones Challenge - Day 3

Final robot design

Here is a picture of the final robot. As previously mentioned, my partner coded as I built, so we were able to test the robot as soon as it was completed. Something different I tried in terms of the winch was having it stretch from opposite ends of the robot. This would balance the mass distribution. I also added a 200 gram mass on the side of the winch and motor to counter the weight of the masses it'd be lifting. Based on some test trials, the robot's systems are running well and strongly. For the next class, we plan on trying to complete the programming. Maybe we will even be able to run our first trial.

Atlas Stones Challenge - Day 2

Robot by the end of Day 2

By the time I returned to class, my partner and I decided we would divide the work necessary to complete the challenge. I would be in charge of the design and construction of the robot while my partner would be in charge of the coding and actions of the robot; the coding in this challenge was much more difficult than before. I was able to complete the entire base of the robot within one class period. We decided that the foundation would be low to the ground to prevent it from tipping as we added upwards. Next class I plan finishing the rest of the body, mainly the winch.

Atlas Stones Challenge - Day 1

For the first day of the Atlas Stones Challenge, I was ill and had to miss class. Typically before the actual construction, we are supposed to evaluate the situation/challenge and brainstorm potential design ideas based on the requirements. Below is a Google Document describing the functions, systems, and integration of our robot. This was completed by my partner George Gikas when I was absent.