Difference between revisions of "RoboCup Mechanical 2015"
Line 7: | Line 7: | ||
== Background == | == Background == | ||
− | <font size="2">The team has taken part in RoboCup every year since 2008*. Two different fleets of robots are used: a fleet designed in 2008, and a fleet designed in 2011. The 2008 fleet sports a solenoid powered kicker mechanism and a fixed dribbler. The 2011 fleet sports solenoid powered kicker AND chipper mechanisms, along with a fixed dribbler and encoders on the motors. However, due to an error in the manufacturing of the 2011 fleet, the drivetrain of these robots have suffered tremendously due to decayed performance of the motors. This renders mostly all 2011 robots functionally incapable | + | <font size="2">The team has taken part in RoboCup every year since 2008*. Two different fleets of robots are used: a fleet designed in 2008, and a fleet designed in 2011. The 2008 fleet sports a solenoid powered kicker mechanism and a fixed dribbler. The 2011 fleet sports solenoid powered kicker AND chipper mechanisms, along with a fixed dribbler and encoders on the motors. However, due to an error in the manufacturing of the 2011 fleet, the drivetrain of these robots have suffered tremendously due to decayed performance of the motors. This renders mostly all 2011 robots functionally incapable. Thus, the most reliable robots have been those designed in 2008. Without encoders, however, this presents significant challenges to our software team.</font> |
<font size="2">Due to these challenges, it has been determined that a complete rebuild of the robots is required to continue to be competitive in the RoboCup SSL.</font> | <font size="2">Due to these challenges, it has been determined that a complete rebuild of the robots is required to continue to be competitive in the RoboCup SSL.</font> | ||
Line 15: | Line 15: | ||
<span style="font-size: small; line-height: 20.7999992370605px;">The team for the 2015 competition year has meet several times to discuss the primary goals for a new fleet of robots. These requirements are outlined below, in order of highest priority to lowest priority.</span> | <span style="font-size: small; line-height: 20.7999992370605px;">The team for the 2015 competition year has meet several times to discuss the primary goals for a new fleet of robots. These requirements are outlined below, in order of highest priority to lowest priority.</span> | ||
− | + | ||
1) Encoders on the motors | 1) Encoders on the motors |
Revision as of 08:42, 18 December 2014
This page houses the 2015 RoboCup Mechanical efforts. Mechanical tasks for the 2015 competition year can be most easily summarized as a complete redesign of the SSL fleet.
Mechanical team meets Tuesday, 6-9pm Sunday, 1-5pm. More hours will be announced as deadlines approach.
http://wiki.robojackets.org/mediawiki/images/5/51/RC2008DevRender.jpg
Contents
Background
The team has taken part in RoboCup every year since 2008*. Two different fleets of robots are used: a fleet designed in 2008, and a fleet designed in 2011. The 2008 fleet sports a solenoid powered kicker mechanism and a fixed dribbler. The 2011 fleet sports solenoid powered kicker AND chipper mechanisms, along with a fixed dribbler and encoders on the motors. However, due to an error in the manufacturing of the 2011 fleet, the drivetrain of these robots have suffered tremendously due to decayed performance of the motors. This renders mostly all 2011 robots functionally incapable. Thus, the most reliable robots have been those designed in 2008. Without encoders, however, this presents significant challenges to our software team.
Due to these challenges, it has been determined that a complete rebuild of the robots is required to continue to be competitive in the RoboCup SSL.
Requirements
The team for the 2015 competition year has meet several times to discuss the primary goals for a new fleet of robots. These requirements are outlined below, in order of highest priority to lowest priority.
1) Encoders on the motors
2) Robust drivetrain mounts
3) Damped dribbler
4) Lower profile solenoids
5) Superior traction/grip for the wheels
6) Robust shell design
Systems
Drivetrain
- Omni Wheels<br/>
:Motors/Gearing
:Drive Module<br/>
Integration
Ball Control
Testing
- Test Rig
:Slope
:Impact Test
Schedule
- delivery of completed team of Robots 5/21/08
Specifications
- maximum robot weight - 1.8 kg
*ball speed after being kicked - 10 m/s
*dribbler bar speed - 8000 rpm
*compress time (time for dribbler to absorb ball's energy and compress) - .2 seconds
*no more than 20% of the ball's area (seen from top view) may be occupied by the robot - a critical Robocup SSL Rule
**see http://wiki.robojackets.org/mediawiki/images/c/c8/Ball_sketch.PNG
Meetings
Documentation
Testing
Quick Notes
- field area 5 meters x 3.5 meters
*max ball speed - 10 m/s
*ball diameter - 43 mm
*ball mass - 46 grams
*1 rpm = .105 rad/s
*ball material - DuPont Surlyn Ionomer Dupont's Surlyn Page
*coefficient of static friction of golf ball on felt carpet - .66
**last two points from Cornell 2003 Mechanical Documentation
Prototype Notes
- make drive module shaft out of stronger material to prevent bending
*ground clearance needs to be increased to prevent the robot from rubbing on the carpet
*4mm holes on the dribbler assembly need to changed to .177" - clearance hole for a 8-32 screw - ease of assembly, prevent burring of the dribbler shafts
*binding of the drive modules can be reduced by adjusting the position of the motor, using the tolerance of its mounting screws
*design plastic guide block so hole for chipper hinge is centered
*dribbler motor plate needs to be wider and flush to the motor
*M2x4mm screws need to be ordered for the dribbler motor
*consider increasing diameter of dribbler roller to add strength to the piece
Useful Links
- Cornell Documents (Look at 2003)
- [[Ftp:Eagle|ftp://ftp.itam.mx/pub/alfredo/PAPERS/SotoWeitzenfeld80LARS2006.pdf%7CEagle Knights Dribbler Testing]]
- MIT Design Handbook Index (VERY GOOD)
[[Category:RoboCup]]<br/>[[Category:Mechanical]]<br/>[[Category:Year: 2007-2008|Year:_2007-2008]]