View Single Post
  #5   Spotlight this post!  
Unread 23-02-2007, 15:59
Lil' Lavery Lil' Lavery is offline
TSIMFD
AKA: Sean Lavery
FRC #1712 (DAWGMA)
Team Role: Mentor
 
Join Date: Nov 2003
Rookie Year: 2003
Location: Philadelphia, PA
Posts: 6,634
Lil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond reputeLil' Lavery has a reputation beyond repute
Send a message via AIM to Lil' Lavery
Re: Drive Systems... ...The FIRST Arms Race?

Danny, I couldn't disagree with you more. Sensors will be vital during all phases of the game this year. Especially when trying to acquire and place tubes on the far side of the rack, sensor aided systems are going to be a huge advantage. 116 is using more sensors on our robot, particularly our maniuplator, than we ever have (at least to my knowledge). A total of 10 sensors may see use during our matches this year, and most will still be used during teleoperated mode. At one point we may even have automatic alignment software fully functional, so that we can align directly with a spider foot on the far side of the rack.
Sensor integration and navigation software are aspects that can be worked with over the summer to a certain degree, but not nearly to the extent as drivetrains. Because we don't know if we're going to have the camera, or an IR beacon, or any other kind of "target" next year, certain sensor specifics are really a risk to spend a lot of time developing during the off-season. Same with certain navigation frameworks (this year having a field element that changes placement between matches made navigation software harder).
__________________
Being correct doesn't mean you don't have to explain yourself.
Reply With Quote