View Single Post
  #3   Spotlight this post!  
Unread 10-04-2011, 02:22
nitneylion452's Avatar
nitneylion452 nitneylion452 is offline
Registered User
AKA: Joe Lee
FRC #3167 (Environmental Tectonics Crusaders)
Team Role: Mentor
 
Join Date: Jan 2010
Rookie Year: 2010
Location: Philadelphia, PA
Posts: 596
nitneylion452 has much to be proud ofnitneylion452 has much to be proud ofnitneylion452 has much to be proud ofnitneylion452 has much to be proud ofnitneylion452 has much to be proud ofnitneylion452 has much to be proud ofnitneylion452 has much to be proud ofnitneylion452 has much to be proud of
Re: Bad luck, or poor execution?

Quote:
Originally Posted by DonRotolo View Post
A team needs to consider what they are really capable of. If your second robot wasn't ready until several weeks after the first one was built, perhaps you "bit off more than you could chew". As a suggestion, consider a simpler robot next year, and focus on robust and 'done early'. That will set you up for future years of excellence.
The physical building of the practice robot was actually finished maybe 3 or 4 days after ship. We had wanted to add "just a few more sensors" to the robot. These included IR distance sensors and encoders. Our programmers worked frantically to get the code working, but so many things kept not working correctly that the process was dragged out over the course of a few weeks.

The entire process was made more difficult because our practice area was not in the same building as our workshop. We are located in the basement of a building behind our school and our practice area was on the school gym stage. Most of the programmers' tests needed the full size replica to be accurate, so in order for us to test the code, we had to bring the robot, tools, and various other items over to the practice area, which was about a half hour process.

I don't want to sound like I'm making excuses, I just want to provide some insight about our situation.

Thanks again for all of the feedback!
Reply With Quote