Team Two/Final Paper
From Maslab 2011
- Leighton Barnes - Course 18, 2013
- Cathy Wu - Course 6, 2012
- Stanislav Nikolov - Course 6, 2011
- Dan Fourie - Course 2, 2012
Our robot was designed for robustness and reliability.
no slip wheels
Electrical Design and Sensors
NiCd and Lithium options reasons we used lead-acid
gyro (or lack thereof)
state machine with bump detection and timeouts
bump sensor coverage
pins falling out
single-conductor wire and broken connections
uORC sample rate
power for fourth motor
cathy & stan
- Form a team early and commit to doing MASLAB for all of IAP. We formed our team before the start of the school year.
- Have a well balanced team. It's important to cover all grounds with software, mechanical, and electrical. Our 2 software + 1 mechanical + 1 electrical combination balanced us very well.
- Work really really hard and stay motivated. We pulled endless all-nighters and never gave up. We continued to pester the staff mailing list with questions and even took a day to set up some legit practice fields in 26-100 before the seeding tournament.
- Start before IAP and aim to have most of everything done in the first 2 weeks of IAP. Because we did most of the design before IAP, We managed to have a functional robot (not the pegbot) by the first mock competition, which helped us out greatly. We also were able to spend the last week and a half making fixes for various edge cases and had time to just polish up things.
- Test often and relentlessly. You'll find something wrong with your robot every time.
|Error creating thumbnail: |
libgomp: Thread creation failed: Resource temporarily unavailable