Thursday, November 5, 2015
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.
Monday, November 2, 2015
Atlas Stones Challenge - Day 3
![]() |
| Final robot design |
Atlas Stones Challenge - Day 2
![]() |
| Robot by the end of Day 2 |
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.
Tuesday, October 20, 2015
Transfer the Load with Winch Challenge - Day 5
Today was the final trial of the challenge. My partner and I had completed the initial requirements last class, so this time, we focused on gaining bonus points. Any team that lifted more than one mass would receive those points. Previously, our robot did not complete more than one cycle due to uneven weight distribution; the robot was top heavy.
Below is a video of our robot completing two cycles of the challenge. It lifted a total of 400g (200g per mass).
Final Thoughts
Performance: As previously mentioned, our robot completed all requirements in order to receive full credit. Throughout the building process, we directed our focus to weight distribution and stability. We added counterweights to various places, allowing the mass to be lifted steadily. If we were to do this challenge again, we would more closely focus on the string that lifted the mass; it kept on slipping, limiting our robot to completing only two cycles.
Improvement and Learning: Thanks to this challenge, I am proud to say that I now understand the concept of "torque", for it is something I never understood before. To put it as my partner did, we also learned a lot about patience; taking apart and rebuilding practically defined our Winch Challenge experience. Because this trial was more successful than the last, I hope that my robot-building skills continue to increase as I move onto the next challenge.
Saturday, October 10, 2015
Transfer the Load with Winch Challenge - Day 4
Last class we completed the challenge! My partner and I fixed the sliding string by adding a second axle where it could loop over. We added a metal Lego hook to the end of the string to allow the string to smoothly return down. We also used the rubber Lego wheels as weights and balances. We noticed that each time we ran the program, the top motor would lean extremely far forward. Originally there were three support axles where it connected to, but we were able to find a location to insert a fourth one, greatly improving its stability. In order to receive full credit for the challenge, we needed to lift one mass up to the table, have the robot change directions while holding the mass, deposit it on a wooden block, and return to the ground. Bonus points would be awarded if the robot could lift multiple masses. We were very close to completing another cycle, but unfortunately it lifted the mass just short of the necessary height. Next class we still have another trial. By that time, we will try to enforce the robot even more, and hopefully receive extra credit.
Friday, October 9, 2015
Transfer the Load with Winch Challenge - Day 3
![]() |
| Design by the end of class |
![]() |
| Final code |
Subscribe to:
Posts (Atom)



