Difference between revisions of "DEWBOT VI IRI Post-Mortem"

From DEW Robotics
Jump to: navigation, search
(Action Plan)
(What went wrong)
Line 22: Line 22:
 
:* The robot appeared to kick by itself in teleop.  Kicking was mis-timed and ineffective.  This may be a control issue, but more likely a user interface problem.
 
:* The robot appeared to kick by itself in teleop.  Kicking was mis-timed and ineffective.  This may be a control issue, but more likely a user interface problem.
 
:* The user interface is complex and not understood by the drive team (esp. the driver).
 
:* The user interface is complex and not understood by the drive team (esp. the driver).
 +
:* The battery box broke (again).  The field fix is quite effective.
  
 
==Action Plan==
 
==Action Plan==

Revision as of 00:30, 23 July 2010

Summary

  • The team & robot did very well
  • 5 wins - 3 losses
  • Finished qualification matches 31st out of 78 teams
  • We were not selected for a play-off alliance
  • DEWBOT VI played phenonimal defense, virtually shutting down scoring 1-on-2 during two matches
  • DEWBOT VI also scored very well in the near field

What went right

  • The drive team brought their Mojo
  • Siri coached 6 of the 8 matches for 4 wins and 2 losses. Great job!
  • The crazy wheel problem did not occur. Replacing steering Jaguars with Victors seems to have done the trick.
  • No fatal field failures. We played every scheduled match; through the match.

What went wrong

  • Communications - we had a communications problem between the Classmate and robot when tethered. No significant field failures. Most times, tethering through the router worked. Most times, tethering directly from the Classmate did not. We know we have a problem with the ethernet port on the Classmate, but this problem appears different.
  • Our possessor eats balls. It will not eat the team's practice balls, so there appears to be a significant difference between the two. We will correct this.
  • Possessor actuation failed. We destroyed two cylinders on the left side. Issue is poor alignment. We'll fix.
  • Possessor grip became less grippy. Need to explore this & resolve.
  • The mirror sagged. We removed (to avoid penalty). Need to fix.
  • Autonomous kicking often failed. When it worked, it was too late & missed the goal. We need to make kicking reliable and set angles empirically (calculated angles are a starting point, but the assumption for calculated angles is that the robot kicks at the original ball position. this is not the case. If we know speed & delay, we can refine the model)
  • The robot appeared to kick by itself in teleop. Kicking was mis-timed and ineffective. This may be a control issue, but more likely a user interface problem.
  • The user interface is complex and not understood by the drive team (esp. the driver).
  • The battery box broke (again). The field fix is quite effective.

Action Plan

  • Resolve comm issues. Purchase back-up Classmate if advisable.
  • Purchase accurate game piece. Develop / rebuild possessor
  • Autonomous testing and setting of Auto angles to score
  • Resolve user interface issues between drive & programming teams
  • Remount mirror securely
  • Design / procure / build a battery charging caddy

Other pages about the DEWBOT VI Indiana Robotics Invitational

DEWBOT VI IRI Photo Gallery
DEWBOT VI IRI Scouting
DEWBOT VI IRI Matches
DEWBOT VI IRI Problems Encountered
DEWBOT VI IRI Trip Reports
DEWBOT VI IRI Post-Mortem