
The 2006 LEGO Mountaineers
U.S. FIRST Jr. Robotics team #3344
Pine Mountain Club, California
www.icarobotics.com/lego

Search
Recent Entries
- Using wind turbines for alternativ
- HELP! Can you help me with RoboLab
- In Leaps and Bounds
- Wind as an alternative energy sour
- Moving Forward in our Research
- This year’s FIRST research p
- Mayan Adventures with the NXT
- Back for One More Round
- The Challenge is Released!
- The 2007 FIRST Challenge is Releas
- Triumph and Success
- We won the Director’s award!
- Competition Time
- We finally figured out a way to do
- The Clock is Ticking!
- We’re Making Progress!
- Frustration and Triumph
- Long Jump Mission ideas
- Great Job Flying Geeks!!!
- Clovis - The State Competition
Recent Comments
Photo Album
Archives
- October 2007 (7)
- September 2007 (3)
- May 2007 (1)
- April 2007 (6)
- March 2007 (2)
- December 2006 (6)
- November 2006 (20)
- October 2006 (39)
- September 2006 (6)
- August 2006 (12)
- March 2005 (2)
- November 2004 (34)
- October 2004 (11)
- September 2004 (20)
- August 2004 (8)
- December 2003 (1)
- September 2003 (3)
- August 2003 (2)
- July 2003 (1)
- June 2003 (1)
- December 2002 (4)
- November 2002 (15)
- October 2002 (8)
- September 2002 (3)
- August 2002 (2)
- July 2002 (2)
Highlights
- HELP! Can you help me with RoboLab
- We won the robot design award!!!
- Patience and hard work made all th
- A mother’s perspective on te
- You’ve helped us more than y
- The competition is getting close!
- One Little, Two Little, Three Litt
- We’re on a roll!
- How to Write Great Programs
- I just built and programmed my fir
- The Competition Playing Field Has
- Frequent failure, the key to succe
- 2006 U.S. First Robotics season be
- We won the Director’s award,
- Lessons we learned at the event
Corporate Sponsors
Partners
Links of Interest
Video Gallery
(Windows Media Player Required)
Recent Googles
Frustration and Triumph
Last night, after repeatedly having trouble with the line following part of the competition, we all went home frustrated and discouraged. The robot didn't seem to work properly and we were having trouble understanding why. Today, we worked hard with Kevin and Derek to make some progress.
This meeting consisted of two parts: a three hour meeting without mentors, and another meeting with. During the first half, we mainly focused on learning RoboLab. I was able to share with the others how to flowchart, (A tool I have found invaluable in programming) and give them a brief once over of this software. After much discussion, we finally decided to use this program as the official team software.
Toward the end of the second meeting, we were able to solve the line following mission. Our team found that because of the sharp lines that our robot was required to follow, moving in a slow arch instead of a point turn caused the robot to respond sluggishly with varying results. (We made this turn by braking one motor and having the other drive forward) After a lot of problem solving we came up with a solution that seemed to work consistently. Using a point turn, we sped up its forward motion and slowed down its backward pull. This way, the robot turned accurately, yet still made it to base in a reasonable amount of time.
We also were able to adjust our light sensor so that it relied completely on its own light and not on its surroundings. This will be very helpful because at each competition, the lighting can change.
I think the neatest thing that I saw during this meeting was that the others learned so much in such a short period of time, and actually enjoyed it! Even though I have had the privilege of working with RoboLab for three years I still haven't come close to learning what it can do. It seems that each time I sit down to work with it I learn something new.
We all learned a lot this meeting and we are excited about solving our next mission.
This meeting consisted of two parts: a three hour meeting without mentors, and another meeting with. During the first half, we mainly focused on learning RoboLab. I was able to share with the others how to flowchart, (A tool I have found invaluable in programming) and give them a brief once over of this software. After much discussion, we finally decided to use this program as the official team software.
Toward the end of the second meeting, we were able to solve the line following mission. Our team found that because of the sharp lines that our robot was required to follow, moving in a slow arch instead of a point turn caused the robot to respond sluggishly with varying results. (We made this turn by braking one motor and having the other drive forward) After a lot of problem solving we came up with a solution that seemed to work consistently. Using a point turn, we sped up its forward motion and slowed down its backward pull. This way, the robot turned accurately, yet still made it to base in a reasonable amount of time.
We also were able to adjust our light sensor so that it relied completely on its own light and not on its surroundings. This will be very helpful because at each competition, the lighting can change.
I think the neatest thing that I saw during this meeting was that the others learned so much in such a short period of time, and actually enjoyed it! Even though I have had the privilege of working with RoboLab for three years I still haven't come close to learning what it can do. It seems that each time I sit down to work with it I learn something new.
We all learned a lot this meeting and we are excited about solving our next mission.
0 Comment(s)
No Comments Found
Discussion for this entry is now closed.