https://wiki.robojackets.org/api.php?action=feedcontributions&feedformat=atom&user=StefanRoboJackets Wiki - User contributions [en]2026-05-25T14:40:27ZUser contributionsMediaWiki 1.32.0https://wiki.robojackets.org/index.php?title=TE_Sessions&diff=9088TE Sessions2010-09-16T05:19:47Z<p>Stefan: /* Location */</p>
<hr />
<div>Technology Enrichment (TE) Sessions, started in 2002, is a yearly workshop program aimed at teaching both rookie and veteran high schools the required skills to succeed in the FIRST Robotics Competition (FRC). These sessions are conducted in the fall semester and the competition is held in the spring semester.<br />
On this page you can find info relating to past and current TE Sessions<br />
<br />
==Overview==<br />
The '''[[2010 TE Sessions]]''' will feature a single The basic sessions are aimed at first timers. At the conclusion of the sessions, the students participate in a capstone [[TE Competition | competition]] designed to test the skills learned during the course.<br />
<br />
==Resources==<br />
* [[2010 TE Session Outline]]<br />
* [[LabVIEW Resources]]<br />
* [https://lists.gatech.edu/sympa/info/robojackets-tesessions TE Sessions Teacher/Team /School Contact Mailing List]<br />
<br />
==Location==<br />
See the annotated [http://tinyurl.com/6dv8at google map]<br />
* Parking in Physics Visitor Lot (see [http://parking.gatech.edu/PublishingImages/Parking%20Map.pdf map])<br />
* Sessions: College of Computing 17 (building 50 on the [http://gtalumni.org/map/ map])<br />
* Room is on bottom floor<br />
<br />
==Time==<br />
The sessions will be held every Thursday from 4:35 to 5:55 PM.<br />
<br />
==Participating Schools==<br />
<br />
==TE Session Coordination==<br />
The TE Committee conducts planning meetings in the summer. A list of important contacts and other logistical info can be found on the [[TE Sessions Planning]] page.<br />
<br />
==Previous Sessions==<br />
* [[2009 TE Sessions]]<br />
* [[2008 TE Sessions]]<br />
* [[2007 TE Sessions]]<br />
* [[2006 TE Sessions]]<br />
* [[2005 TE Sessions]]<br />
<br />
[[Category: Technology Enrichment Sessions]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=TE_Sessions&diff=9087TE Sessions2010-09-16T05:19:00Z<p>Stefan: /* Time */</p>
<hr />
<div>Technology Enrichment (TE) Sessions, started in 2002, is a yearly workshop program aimed at teaching both rookie and veteran high schools the required skills to succeed in the FIRST Robotics Competition (FRC). These sessions are conducted in the fall semester and the competition is held in the spring semester.<br />
On this page you can find info relating to past and current TE Sessions<br />
<br />
==Overview==<br />
The '''[[2010 TE Sessions]]''' will feature a single The basic sessions are aimed at first timers. At the conclusion of the sessions, the students participate in a capstone [[TE Competition | competition]] designed to test the skills learned during the course.<br />
<br />
==Resources==<br />
* [[2010 TE Session Outline]]<br />
* [[LabVIEW Resources]]<br />
* [https://lists.gatech.edu/sympa/info/robojackets-tesessions TE Sessions Teacher/Team /School Contact Mailing List]<br />
<br />
==Location==<br />
See the annotated [http://tinyurl.com/6dv8at google map]<br />
* Parking in W21 (see [http://parking.gatech.edu/PublishingImages/Parking%20Map.pdf map])<br />
* Sessions: College of Computing 17 (building 50 on the [http://gtalumni.org/map/ map])<br />
* Room is on bottom floor<br />
<br />
==Time==<br />
The sessions will be held every Thursday from 4:35 to 5:55 PM.<br />
<br />
==Participating Schools==<br />
<br />
==TE Session Coordination==<br />
The TE Committee conducts planning meetings in the summer. A list of important contacts and other logistical info can be found on the [[TE Sessions Planning]] page.<br />
<br />
==Previous Sessions==<br />
* [[2009 TE Sessions]]<br />
* [[2008 TE Sessions]]<br />
* [[2007 TE Sessions]]<br />
* [[2006 TE Sessions]]<br />
* [[2005 TE Sessions]]<br />
<br />
[[Category: Technology Enrichment Sessions]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=TE_Sessions&diff=9086TE Sessions2010-09-16T05:18:44Z<p>Stefan: /* Overview */</p>
<hr />
<div>Technology Enrichment (TE) Sessions, started in 2002, is a yearly workshop program aimed at teaching both rookie and veteran high schools the required skills to succeed in the FIRST Robotics Competition (FRC). These sessions are conducted in the fall semester and the competition is held in the spring semester.<br />
On this page you can find info relating to past and current TE Sessions<br />
<br />
==Overview==<br />
The '''[[2010 TE Sessions]]''' will feature a single The basic sessions are aimed at first timers. At the conclusion of the sessions, the students participate in a capstone [[TE Competition | competition]] designed to test the skills learned during the course.<br />
<br />
==Resources==<br />
* [[2010 TE Session Outline]]<br />
* [[LabVIEW Resources]]<br />
* [https://lists.gatech.edu/sympa/info/robojackets-tesessions TE Sessions Teacher/Team /School Contact Mailing List]<br />
<br />
==Location==<br />
See the annotated [http://tinyurl.com/6dv8at google map]<br />
* Parking in W21 (see [http://parking.gatech.edu/PublishingImages/Parking%20Map.pdf map])<br />
* Sessions: College of Computing 17 (building 50 on the [http://gtalumni.org/map/ map])<br />
* Room is on bottom floor<br />
<br />
==Time==<br />
The sessions will be held every Thursday from 4:30 to 6:00 PM.<br />
<br />
==Participating Schools==<br />
<br />
==TE Session Coordination==<br />
The TE Committee conducts planning meetings in the summer. A list of important contacts and other logistical info can be found on the [[TE Sessions Planning]] page.<br />
<br />
==Previous Sessions==<br />
* [[2009 TE Sessions]]<br />
* [[2008 TE Sessions]]<br />
* [[2007 TE Sessions]]<br />
* [[2006 TE Sessions]]<br />
* [[2005 TE Sessions]]<br />
<br />
[[Category: Technology Enrichment Sessions]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=Proposals&diff=9076Proposals2010-09-05T04:18:07Z<p>Stefan: /* Overview */</p>
<hr />
<div>Proposals serves two purposes: To inform the officers and the club about the plans of each project and to help team leaders in their project planning. It is comprised of a description of the project objectives for the new year, a schedule, and a budget. Generally, the proposals are due to the officers by the beginning of the school year. Final budget amounts are then determined and announced in the subsequent weeks.<br />
<br />
==Preliminary Proposal==<br />
A preliminary proposal may be asked of the team leaders when the officers need information for planing purposes before the proposal deadline. These preliminary proposals are not binding and are strictly for pre-planning purposes.<br />
<br />
==Prior Results==<br />
A short description (one to two paragraphs) of what went right and what went wrong in the previous year. Serves as in introduction to the proposal.<br />
==Project Description==<br />
===Objectives===<br />
The project's objectives should be carefully considered as they will guide the planning of the project. Clear, concise objectives help keep a team focused without pulling the development in too many directions at once. Abstract, far reaching objectives are discouraged as they are hard to fully satisfy and give the team no clear direction. The best objectives focus in on each aspect of the project, and provide detail about what the expectations, such as performance and ease of use, will be for those aspects. Finally, the objectives shouldn't enumerate specific tasks. There should be at least 1 primary objective and 2 secondary objectives. Secondary objectives are defined as something that if not met will not prevent the project from failing to compete.<br />
<br />
====Bad Examples:====<br />
# "To be competitive relative to the current field" - Too broad and not clearly defined. There is no indication of what capabilities are considered competitive in the field and if a team needs to implement all of them.<br />
# "Fix the code for estimating position" - This sounds more like a bug fix or a to-do list than an objective.<br />
# "Design a manipulator for the science task" - While this is specific it really is just a re-hash of the competition objectives. <br />
<br />
====Good Examples:====<br />
# "Gain a competitive advantage by building a rotary based weapon" - Like the above objective the goal of being competitive is clearly conveyed and in addition details are given as to what ways the team will be competitive. Note that the objective is specific enough that the type of weapon is given but general enough that further details are omitted. Also note that the team already at this point has an idea of what type of robot is going to be built instead of starting from a clean slate. <br />
# "Train new members by having them fix some of Glados's simpler problems" - This objective is more general and it achieves a much bigger goal in terms of training. A team leader should be careful in choosing this goal though, as it indicates that they will need to allocate time and resources to training, time that could be spent on new systems for Glados.<br />
# This one can go two ways:<br />
##"Define the objectives for and build a manipulator for the science task" - Not the best objective but at least its this shows that there has been some thought on this objective.<br />
## "Design a manipulator that penetrate six inches of earth for the science task and has minimal size and power requirements" - Much better. Everything is spelled out and the objectives for the manipulator, though general are given. One can use this objective to really guide a design.<br />
<br />
===Milestones===<br />
The milestones are a means of demonstrating progress to the officers, the advisers, sponsors, and the campus as a whole. They also give members a clear sense of where the team is headed and provide motivation. They should be easily demonstrable and realistic without pushing back dates. A good milestone is one that members will prepare for with the same vigor as the actual competition deadline.<br />
<br />
The project description should clearly describe what each milestone is. Milestones can be an objective, parts of several objectives, or the completion of a set of small task such as repairing the robot. Milestones shouldn't be vague objectives such as 'working robots' or 'be ready for competition.' Like objectives some specifics should be given.<br />
<br />
At the very least the officers would like to see a milestone for a prototype/rev 1 sometime in the late fall, and a milestone for testing in the late spring. Beyond that milestones for sub-systems are a good place to start. Below is an example of a good set of milestones for a Mars Rover themed competition<br />
<br />
====Milestones Example====<br />
* Sept 15th 2009 - Fix the all the things broken at competition last year and demonstrate the old rover completing some of the task<br />
* After fall break - Demo at least 2 new prototype drive-trains<br />
* Week before dead week - Prototype - Demo new drive-train in tele-op driving, successfully acquire data from sensors, demo a new end-effector, <br />
* Feb 1st - Demo new manipulator using individual joint control<br />
* March 1st - Extended range driving<br />
* Spring Break - Demo some of the competition tasks using the manipulator<br />
* April 30th - Finalize travel plans, demo robot performing some competition objectives<br />
<br />
===Resources===<br />
Every team will need resources to complete their project and the proposal is where teams indicate what will be needed to successful complete the project. Resources are broken down into monetary, personnel and capital outlays/tooling.<br />
<br />
====Monetary====<br />
This is mainly covered in the budget but the proposal should contain a few words on why the team needs the items its requesting. This information will be helpful for the officers in budget defenses for the club and when dealing with potential sponsors.<br />
<br />
====Personnel====<br />
Team leaders should indicate the number of people they feel they will need to be successful and their skill sets. Since we are mostly undergrads, skill sets roughly means interest.<br />
<br />
====Capital Outlays/Tooling====<br />
While our shop and the Tin building provides an abundance of tools, team leaders may find that certain items are not available. There may also be large equipment purchases that the robots will need. In both cases those items should be listed here. Team leaders should also consider what resources that will be needed to manufacture parts and should list those resources here.<br />
<br />
====Travel/Registration====<br />
In the proposal teams should indicate what competition they are going to, what dates the competition is held (or at least a rough idea of when those dates are known), and expected cost for registration and travel. Per the internal travel policy, RoboJackets will only cover the following<br />
<br />
* Transportation - Gas at the SGA mileage rate, plane, train, or bus tickets, and rental vehicles.<br />
* Incidentals - Materials for competition, items for the robot, First Aid, anything that would be of use to every member of the team for the purposes of competition except, food, hotel, and entertainment. Example: Ponchos<br />
* Luggage for the robot<br />
* Shipping for the robot<br />
* Fees - Excess baggage, duties, <br />
<br />
In addition the proposal should state the anticipated cost for travel per member. This number should include hotel and possibly food, especially if you are going overseas. It should be based on a projected number of attendees.<br />
===Schedule===<br />
The schedule should detail what phases of the project the team will be working on throughout the year. These phases are derived from the objectives and the milestones and should be broken up by subsystem. A phase called design would not be a good choice as subsystem design times vary and can't all be lumped into one. <br />
<br />
There are no formatting rules for the schedule other than it be a separate page and look similar to a Gantt chart. Gnome Planner is preferred though.(You can get it here:http://live.gnome.org/Planner)<br />
===Budget===<br />
The budget contains details on the cost to build the robot and should provide sufficient detail. An example of sufficient detail are cost for metal for the frame. Its understood that teams may not know what their final design will look like (for example which motor they will go with). Careful study of the market and the competition though can go along way in determining what a maximum cost would be for an item. For RoboJackets, surpluses are okay, deficits are impossible since we can't operate in debt. For an example budget see the 2009-2010 SGA budget. Capital outlays (items that can reasonably get more than a year of use) should be listed on the teams budget as they require purchasing, but should by listed in a Capital Outlays Section.<br />
<br />
===Supplemental Documentation===<br />
Any documentation that the team leader feels is required in addition to the above<br />
<br />
==How funding works==<br />
==='''Important'''===<br />
=== Overview ===<br />
In the past project budgets were set at the beginning of the year with the entire budget for each team be allocated in one step. Since 2009 teams will have their budgets allocated in phases based on development the milestones they have specified. Not all milestones define a separate phase though but all phases will culminate with some milestone. It is '''required''' that teams at least have a '''design and and build phase''' with the milestone for the design phase being a successful design review. The design review shall be arranged by the team leader, the officers, and interested parties. Interested parties shall include all parties recognized by the officers and team leaders. Design reviews must happen at least once a month or at the initial design completion of a major project component (ie, drive system, main board, overall wiring plan, etc).<br />
<br />
===Milestones and Partial Completion===<br />
Milestones for projects are the milestones and the final travel deadline. Completion of a milestone will be defined by the milestone itself. Partial completion of milestones will be defined by the officers and other interested parties with the input of the team leader. The travel deadline is set as the date in the spring semester by which all travel plans are finalized including, who is going, deposits from members, any paperwork from Tech, and hotels and flights booked. Leniency is given for extenuating circumstances only. <br />
<br />
=== Penalities ===<br />
Failure to meet a milestone will result in the team losing out on additional funding until they have either completed the milestone or made satisfactory progress towards the milestone. Satisfactory progress will be defined by the officers and other parties in with input from the team leader and will take into account external factors such as vendor related issues.<br />
<br />
===Changes===<br />
Changes can be made to any deadline pending officer approval. The criteria for approval are:<br />
<br />
* Time till deadline in question<br />
* Progress made<br />
* External factors<br />
<br />
Changes should be made well before the deadline in question will be missed. Problems such as 11th hour vendor issues or broken hardware are better served by partial completion instead of change requests. <br />
<br />
=== Changes vs. Partial Completion ===<br />
It is understood that problems will arise along the way (Robotics is still very much a research field). As such team leaders have several options when their projects come into unexpected problems. Change request are best suited for bigger problems that can't be solved by simply moving the deadline back a few weeks. Examples include problems obtaining long lead (3+ weeks) items, inability to complete an objective, and changes to the competition. For problems that can be easily solved partial completion is better. The idea is that if a team has been worked hard to meet a deadline but hits a snafu no additional stress is placed on the members by having to continue to work to meet a new deadline.<br />
<br />
=== Authority ===<br />
The authority to approve funding rest solely with the officers. Team leaders, and interested parties can offer input but can not make decisions regarding funding. Funding decisions are approved with a unanimous vote by the officers. This authority is not dictated in the constitution but has been standard operating procedure.<br />
<br />
In general the officers can only ''enforce'' the milestones and objectives that the team leader defines. Even in the event of a change request the officers can only approve or dis-approve changes that the team leaders comes up with. Under normal circumstances officers cannot create objectives, milestones, or otherwise guide a team. Any officer on a team, on matters of team objectives and milestones, is subject to the decisions of the team leader. The only applicable events in which an officer can have any leadership of a team is:<br />
# if appointed by a team leader, <br />
# if there are no members to take lead of project, <br />
# or if a project has repeatedly missed deadlines and is sufficiently behind schedule to the point where competition appearance may be in question.<br />
<br />
==Procedure for Submission==<br />
The proposals are due at 11:59 on the 9/11. They should contain all the sections mention above be in 12pt font, double-spaced, and printed on one side only. The budget should be submitted electronically as a separate excel spreadsheet. It should also be attached to the hard copy. Once all the proposals are in the budget can be made up and then disbursed along with recommendations from the officers and the advisers.<br />
<br />
==Budget Template & Associated Files==<br />
[[File:RoboJackets-TEAM-Budget-Proposal.zip]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=Proposals&diff=9075Proposals2010-09-05T04:12:23Z<p>Stefan: /* Authority */</p>
<hr />
<div>Proposals serves two purposes: To inform the officers and the club about the plans of each project and to help team leaders in their project planning. It is comprised of a description of the project objectives for the new year, a schedule, and a budget. Generally, the proposals are due to the officers by the beginning of the school year. Final budget amounts are then determined and announced in the subsequent weeks.<br />
<br />
==Preliminary Proposal==<br />
A preliminary proposal may be asked of the team leaders when the officers need information for planing purposes before the proposal deadline. These preliminary proposals are not binding and are strictly for pre-planning purposes.<br />
<br />
==Prior Results==<br />
A short description (one to two paragraphs) of what went right and what went wrong in the previous year. Serves as in introduction to the proposal.<br />
==Project Description==<br />
===Objectives===<br />
The project's objectives should be carefully considered as they will guide the planning of the project. Clear, concise objectives help keep a team focused without pulling the development in too many directions at once. Abstract, far reaching objectives are discouraged as they are hard to fully satisfy and give the team no clear direction. The best objectives focus in on each aspect of the project, and provide detail about what the expectations, such as performance and ease of use, will be for those aspects. Finally, the objectives shouldn't enumerate specific tasks. There should be at least 1 primary objective and 2 secondary objectives. Secondary objectives are defined as something that if not met will not prevent the project from failing to compete.<br />
<br />
====Bad Examples:====<br />
# "To be competitive relative to the current field" - Too broad and not clearly defined. There is no indication of what capabilities are considered competitive in the field and if a team needs to implement all of them.<br />
# "Fix the code for estimating position" - This sounds more like a bug fix or a to-do list than an objective.<br />
# "Design a manipulator for the science task" - While this is specific it really is just a re-hash of the competition objectives. <br />
<br />
====Good Examples:====<br />
# "Gain a competitive advantage by building a rotary based weapon" - Like the above objective the goal of being competitive is clearly conveyed and in addition details are given as to what ways the team will be competitive. Note that the objective is specific enough that the type of weapon is given but general enough that further details are omitted. Also note that the team already at this point has an idea of what type of robot is going to be built instead of starting from a clean slate. <br />
# "Train new members by having them fix some of Glados's simpler problems" - This objective is more general and it achieves a much bigger goal in terms of training. A team leader should be careful in choosing this goal though, as it indicates that they will need to allocate time and resources to training, time that could be spent on new systems for Glados.<br />
# This one can go two ways:<br />
##"Define the objectives for and build a manipulator for the science task" - Not the best objective but at least its this shows that there has been some thought on this objective.<br />
## "Design a manipulator that penetrate six inches of earth for the science task and has minimal size and power requirements" - Much better. Everything is spelled out and the objectives for the manipulator, though general are given. One can use this objective to really guide a design.<br />
<br />
===Milestones===<br />
The milestones are a means of demonstrating progress to the officers, the advisers, sponsors, and the campus as a whole. They also give members a clear sense of where the team is headed and provide motivation. They should be easily demonstrable and realistic without pushing back dates. A good milestone is one that members will prepare for with the same vigor as the actual competition deadline.<br />
<br />
The project description should clearly describe what each milestone is. Milestones can be an objective, parts of several objectives, or the completion of a set of small task such as repairing the robot. Milestones shouldn't be vague objectives such as 'working robots' or 'be ready for competition.' Like objectives some specifics should be given.<br />
<br />
At the very least the officers would like to see a milestone for a prototype/rev 1 sometime in the late fall, and a milestone for testing in the late spring. Beyond that milestones for sub-systems are a good place to start. Below is an example of a good set of milestones for a Mars Rover themed competition<br />
<br />
====Milestones Example====<br />
* Sept 15th 2009 - Fix the all the things broken at competition last year and demonstrate the old rover completing some of the task<br />
* After fall break - Demo at least 2 new prototype drive-trains<br />
* Week before dead week - Prototype - Demo new drive-train in tele-op driving, successfully acquire data from sensors, demo a new end-effector, <br />
* Feb 1st - Demo new manipulator using individual joint control<br />
* March 1st - Extended range driving<br />
* Spring Break - Demo some of the competition tasks using the manipulator<br />
* April 30th - Finalize travel plans, demo robot performing some competition objectives<br />
<br />
===Resources===<br />
Every team will need resources to complete their project and the proposal is where teams indicate what will be needed to successful complete the project. Resources are broken down into monetary, personnel and capital outlays/tooling.<br />
<br />
====Monetary====<br />
This is mainly covered in the budget but the proposal should contain a few words on why the team needs the items its requesting. This information will be helpful for the officers in budget defenses for the club and when dealing with potential sponsors.<br />
<br />
====Personnel====<br />
Team leaders should indicate the number of people they feel they will need to be successful and their skill sets. Since we are mostly undergrads, skill sets roughly means interest.<br />
<br />
====Capital Outlays/Tooling====<br />
While our shop and the Tin building provides an abundance of tools, team leaders may find that certain items are not available. There may also be large equipment purchases that the robots will need. In both cases those items should be listed here. Team leaders should also consider what resources that will be needed to manufacture parts and should list those resources here.<br />
<br />
====Travel/Registration====<br />
In the proposal teams should indicate what competition they are going to, what dates the competition is held (or at least a rough idea of when those dates are known), and expected cost for registration and travel. Per the internal travel policy, RoboJackets will only cover the following<br />
<br />
* Transportation - Gas at the SGA mileage rate, plane, train, or bus tickets, and rental vehicles.<br />
* Incidentals - Materials for competition, items for the robot, First Aid, anything that would be of use to every member of the team for the purposes of competition except, food, hotel, and entertainment. Example: Ponchos<br />
* Luggage for the robot<br />
* Shipping for the robot<br />
* Fees - Excess baggage, duties, <br />
<br />
In addition the proposal should state the anticipated cost for travel per member. This number should include hotel and possibly food, especially if you are going overseas. It should be based on a projected number of attendees.<br />
===Schedule===<br />
The schedule should detail what phases of the project the team will be working on throughout the year. These phases are derived from the objectives and the milestones and should be broken up by subsystem. A phase called design would not be a good choice as subsystem design times vary and can't all be lumped into one. <br />
<br />
There are no formatting rules for the schedule other than it be a separate page and look similar to a Gantt chart. Gnome Planner is preferred though.(You can get it here:http://live.gnome.org/Planner)<br />
===Budget===<br />
The budget contains details on the cost to build the robot and should provide sufficient detail. An example of sufficient detail are cost for metal for the frame. Its understood that teams may not know what their final design will look like (for example which motor they will go with). Careful study of the market and the competition though can go along way in determining what a maximum cost would be for an item. For RoboJackets, surpluses are okay, deficits are impossible since we can't operate in debt. For an example budget see the 2009-2010 SGA budget. Capital outlays (items that can reasonably get more than a year of use) should be listed on the teams budget as they require purchasing, but should by listed in a Capital Outlays Section.<br />
<br />
===Supplemental Documentation===<br />
Any documentation that the team leader feels is required in addition to the above<br />
<br />
==How funding works==<br />
==='''Important'''===<br />
=== Overview ===<br />
In the past project budgets were set at the beginning of the year with the entire budget for each team be allocated in one step. This year teams will have their budgets allocated in phases based on development the milestones they have specified. Not all milestones define a separate phase though but all phases will culminate with some milestone. It is '''required''' that teams at least have a '''design and and build phase''' with the milestone for the design phase being a successful design review. The design review shall be arranged by the team leader, the officers, and interested parties. Interested parties shall include all parties recognized by the officers and team leaders. <br />
<br />
===Milestones and Partial Completion===<br />
Milestones for projects are the milestones and the final travel deadline. Completion of a milestone will be defined by the milestone itself. Partial completion of milestones will be defined by the officers and other interested parties with the input of the team leader. The travel deadline is set as the date in the spring semester by which all travel plans are finalized including, who is going, deposits from members, any paperwork from Tech, and hotels and flights booked. Leniency is given for extenuating circumstances only. <br />
<br />
=== Penalities ===<br />
Failure to meet a milestone will result in the team losing out on additional funding until they have either completed the milestone or made satisfactory progress towards the milestone. Satisfactory progress will be defined by the officers and other parties in with input from the team leader and will take into account external factors such as vendor related issues.<br />
<br />
===Changes===<br />
Changes can be made to any deadline pending officer approval. The criteria for approval are:<br />
<br />
* Time till deadline in question<br />
* Progress made<br />
* External factors<br />
<br />
Changes should be made well before the deadline in question will be missed. Problems such as 11th hour vendor issues or broken hardware are better served by partial completion instead of change requests. <br />
<br />
=== Changes vs. Partial Completion ===<br />
It is understood that problems will arise along the way (Robotics is still very much a research field). As such team leaders have several options when their projects come into unexpected problems. Change request are best suited for bigger problems that can't be solved by simply moving the deadline back a few weeks. Examples include problems obtaining long lead (3+ weeks) items, inability to complete an objective, and changes to the competition. For problems that can be easily solved partial completion is better. The idea is that if a team has been worked hard to meet a deadline but hits a snafu no additional stress is placed on the members by having to continue to work to meet a new deadline.<br />
<br />
=== Authority ===<br />
The authority to approve funding rest solely with the officers. Team leaders, and interested parties can offer input but can not make decisions regarding funding. Funding decisions are approved with a unanimous vote by the officers. This authority is not dictated in the constitution but has been standard operating procedure.<br />
<br />
In general the officers can only ''enforce'' the milestones and objectives that the team leader defines. Even in the event of a change request the officers can only approve or dis-approve changes that the team leaders comes up with. Under normal circumstances officers cannot create objectives, milestones, or otherwise guide a team. Any officer on a team, on matters of team objectives and milestones, is subject to the decisions of the team leader. The only applicable events in which an officer can have any leadership of a team is:<br />
# if appointed by a team leader, <br />
# if there are no members to take lead of project, <br />
# or if a project has repeatedly missed deadlines and is sufficiently behind schedule to the point where competition appearance may be in question.<br />
<br />
==Procedure for Submission==<br />
The proposals are due at 11:59 on the 9/11. They should contain all the sections mention above be in 12pt font, double-spaced, and printed on one side only. The budget should be submitted electronically as a separate excel spreadsheet. It should also be attached to the hard copy. Once all the proposals are in the budget can be made up and then disbursed along with recommendations from the officers and the advisers.<br />
<br />
==Budget Template & Associated Files==<br />
[[File:RoboJackets-TEAM-Budget-Proposal.zip]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=Proposals&diff=9074Proposals2010-09-05T03:55:02Z<p>Stefan: /* Procedure for Submission */</p>
<hr />
<div>Proposals serves two purposes: To inform the officers and the club about the plans of each project and to help team leaders in their project planning. It is comprised of a description of the project objectives for the new year, a schedule, and a budget. Generally, the proposals are due to the officers by the beginning of the school year. Final budget amounts are then determined and announced in the subsequent weeks.<br />
<br />
==Preliminary Proposal==<br />
A preliminary proposal may be asked of the team leaders when the officers need information for planing purposes before the proposal deadline. These preliminary proposals are not binding and are strictly for pre-planning purposes.<br />
<br />
==Prior Results==<br />
A short description (one to two paragraphs) of what went right and what went wrong in the previous year. Serves as in introduction to the proposal.<br />
==Project Description==<br />
===Objectives===<br />
The project's objectives should be carefully considered as they will guide the planning of the project. Clear, concise objectives help keep a team focused without pulling the development in too many directions at once. Abstract, far reaching objectives are discouraged as they are hard to fully satisfy and give the team no clear direction. The best objectives focus in on each aspect of the project, and provide detail about what the expectations, such as performance and ease of use, will be for those aspects. Finally, the objectives shouldn't enumerate specific tasks. There should be at least 1 primary objective and 2 secondary objectives. Secondary objectives are defined as something that if not met will not prevent the project from failing to compete.<br />
<br />
====Bad Examples:====<br />
# "To be competitive relative to the current field" - Too broad and not clearly defined. There is no indication of what capabilities are considered competitive in the field and if a team needs to implement all of them.<br />
# "Fix the code for estimating position" - This sounds more like a bug fix or a to-do list than an objective.<br />
# "Design a manipulator for the science task" - While this is specific it really is just a re-hash of the competition objectives. <br />
<br />
====Good Examples:====<br />
# "Gain a competitive advantage by building a rotary based weapon" - Like the above objective the goal of being competitive is clearly conveyed and in addition details are given as to what ways the team will be competitive. Note that the objective is specific enough that the type of weapon is given but general enough that further details are omitted. Also note that the team already at this point has an idea of what type of robot is going to be built instead of starting from a clean slate. <br />
# "Train new members by having them fix some of Glados's simpler problems" - This objective is more general and it achieves a much bigger goal in terms of training. A team leader should be careful in choosing this goal though, as it indicates that they will need to allocate time and resources to training, time that could be spent on new systems for Glados.<br />
# This one can go two ways:<br />
##"Define the objectives for and build a manipulator for the science task" - Not the best objective but at least its this shows that there has been some thought on this objective.<br />
## "Design a manipulator that penetrate six inches of earth for the science task and has minimal size and power requirements" - Much better. Everything is spelled out and the objectives for the manipulator, though general are given. One can use this objective to really guide a design.<br />
<br />
===Milestones===<br />
The milestones are a means of demonstrating progress to the officers, the advisers, sponsors, and the campus as a whole. They also give members a clear sense of where the team is headed and provide motivation. They should be easily demonstrable and realistic without pushing back dates. A good milestone is one that members will prepare for with the same vigor as the actual competition deadline.<br />
<br />
The project description should clearly describe what each milestone is. Milestones can be an objective, parts of several objectives, or the completion of a set of small task such as repairing the robot. Milestones shouldn't be vague objectives such as 'working robots' or 'be ready for competition.' Like objectives some specifics should be given.<br />
<br />
At the very least the officers would like to see a milestone for a prototype/rev 1 sometime in the late fall, and a milestone for testing in the late spring. Beyond that milestones for sub-systems are a good place to start. Below is an example of a good set of milestones for a Mars Rover themed competition<br />
<br />
====Milestones Example====<br />
* Sept 15th 2009 - Fix the all the things broken at competition last year and demonstrate the old rover completing some of the task<br />
* After fall break - Demo at least 2 new prototype drive-trains<br />
* Week before dead week - Prototype - Demo new drive-train in tele-op driving, successfully acquire data from sensors, demo a new end-effector, <br />
* Feb 1st - Demo new manipulator using individual joint control<br />
* March 1st - Extended range driving<br />
* Spring Break - Demo some of the competition tasks using the manipulator<br />
* April 30th - Finalize travel plans, demo robot performing some competition objectives<br />
<br />
===Resources===<br />
Every team will need resources to complete their project and the proposal is where teams indicate what will be needed to successful complete the project. Resources are broken down into monetary, personnel and capital outlays/tooling.<br />
<br />
====Monetary====<br />
This is mainly covered in the budget but the proposal should contain a few words on why the team needs the items its requesting. This information will be helpful for the officers in budget defenses for the club and when dealing with potential sponsors.<br />
<br />
====Personnel====<br />
Team leaders should indicate the number of people they feel they will need to be successful and their skill sets. Since we are mostly undergrads, skill sets roughly means interest.<br />
<br />
====Capital Outlays/Tooling====<br />
While our shop and the Tin building provides an abundance of tools, team leaders may find that certain items are not available. There may also be large equipment purchases that the robots will need. In both cases those items should be listed here. Team leaders should also consider what resources that will be needed to manufacture parts and should list those resources here.<br />
<br />
====Travel/Registration====<br />
In the proposal teams should indicate what competition they are going to, what dates the competition is held (or at least a rough idea of when those dates are known), and expected cost for registration and travel. Per the internal travel policy, RoboJackets will only cover the following<br />
<br />
* Transportation - Gas at the SGA mileage rate, plane, train, or bus tickets, and rental vehicles.<br />
* Incidentals - Materials for competition, items for the robot, First Aid, anything that would be of use to every member of the team for the purposes of competition except, food, hotel, and entertainment. Example: Ponchos<br />
* Luggage for the robot<br />
* Shipping for the robot<br />
* Fees - Excess baggage, duties, <br />
<br />
In addition the proposal should state the anticipated cost for travel per member. This number should include hotel and possibly food, especially if you are going overseas. It should be based on a projected number of attendees.<br />
===Schedule===<br />
The schedule should detail what phases of the project the team will be working on throughout the year. These phases are derived from the objectives and the milestones and should be broken up by subsystem. A phase called design would not be a good choice as subsystem design times vary and can't all be lumped into one. <br />
<br />
There are no formatting rules for the schedule other than it be a separate page and look similar to a Gantt chart. Gnome Planner is preferred though.(You can get it here:http://live.gnome.org/Planner)<br />
===Budget===<br />
The budget contains details on the cost to build the robot and should provide sufficient detail. An example of sufficient detail are cost for metal for the frame. Its understood that teams may not know what their final design will look like (for example which motor they will go with). Careful study of the market and the competition though can go along way in determining what a maximum cost would be for an item. For RoboJackets, surpluses are okay, deficits are impossible since we can't operate in debt. For an example budget see the 2009-2010 SGA budget. Capital outlays (items that can reasonably get more than a year of use) should be listed on the teams budget as they require purchasing, but should by listed in a Capital Outlays Section.<br />
<br />
===Supplemental Documentation===<br />
Any documentation that the team leader feels is required in addition to the above<br />
<br />
==How funding works==<br />
==='''Important'''===<br />
=== Overview ===<br />
In the past project budgets were set at the beginning of the year with the entire budget for each team be allocated in one step. This year teams will have their budgets allocated in phases based on development the milestones they have specified. Not all milestones define a separate phase though but all phases will culminate with some milestone. It is '''required''' that teams at least have a '''design and and build phase''' with the milestone for the design phase being a successful design review. The design review shall be arranged by the team leader, the officers, and interested parties. Interested parties shall include all parties recognized by the officers and team leaders. <br />
<br />
===Milestones and Partial Completion===<br />
Milestones for projects are the milestones and the final travel deadline. Completion of a milestone will be defined by the milestone itself. Partial completion of milestones will be defined by the officers and other interested parties with the input of the team leader. The travel deadline is set as the date in the spring semester by which all travel plans are finalized including, who is going, deposits from members, any paperwork from Tech, and hotels and flights booked. Leniency is given for extenuating circumstances only. <br />
<br />
=== Penalities ===<br />
Failure to meet a milestone will result in the team losing out on additional funding until they have either completed the milestone or made satisfactory progress towards the milestone. Satisfactory progress will be defined by the officers and other parties in with input from the team leader and will take into account external factors such as vendor related issues.<br />
<br />
===Changes===<br />
Changes can be made to any deadline pending officer approval. The criteria for approval are:<br />
<br />
* Time till deadline in question<br />
* Progress made<br />
* External factors<br />
<br />
Changes should be made well before the deadline in question will be missed. Problems such as 11th hour vendor issues or broken hardware are better served by partial completion instead of change requests. <br />
<br />
=== Changes vs. Partial Completion ===<br />
It is understood that problems will arise along the way (Robotics is still very much a research field). As such team leaders have several options when their projects come into unexpected problems. Change request are best suited for bigger problems that can't be solved by simply moving the deadline back a few weeks. Examples include problems obtaining long lead (3+ weeks) items, inability to complete an objective, and changes to the competition. For problems that can be easily solved partial completion is better. The idea is that if a team has been worked hard to meet a deadline but hits a snafu no additional stress is placed on the members by having to continue to work to meet a new deadline.<br />
<br />
=== Authority ===<br />
The authority to approve funding rest solely with the officers. Team leaders, and interested parties can offer input but can not make decisions regarding funding. Funding decisions are approved with a unanimous vote by the officers. This authority is not dictated in the constitution but has been standard operating procedure.<br />
<br />
In general the officers can only ''enforce'' the milestones and objectives that the team leader defines. Even in the event of a change request the officers can only approve or dis-approve changes that the team leaders comes up with. In no instance can an officer create objectives, milestones, or otherwise guide a team. Any officer on a team, on matters of team objectives and milestones, is subject to the decisions of the team leader. The only applicable event in which an officer can have any leadership of a team is if appointed by a team leader or if there are no members to take lead of project.<br />
<br />
==Procedure for Submission==<br />
The proposals are due at 11:59 on the 9/11. They should contain all the sections mention above be in 12pt font, double-spaced, and printed on one side only. The budget should be submitted electronically as a separate excel spreadsheet. It should also be attached to the hard copy. Once all the proposals are in the budget can be made up and then disbursed along with recommendations from the officers and the advisers.<br />
<br />
==Budget Template & Associated Files==<br />
[[File:RoboJackets-TEAM-Budget-Proposal.zip]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=Proposals&diff=9073Proposals2010-09-05T03:53:48Z<p>Stefan: /* Budget Template & Associated Files */</p>
<hr />
<div>Proposals serves two purposes: To inform the officers and the club about the plans of each project and to help team leaders in their project planning. It is comprised of a description of the project objectives for the new year, a schedule, and a budget. Generally, the proposals are due to the officers by the beginning of the school year. Final budget amounts are then determined and announced in the subsequent weeks.<br />
<br />
==Preliminary Proposal==<br />
A preliminary proposal may be asked of the team leaders when the officers need information for planing purposes before the proposal deadline. These preliminary proposals are not binding and are strictly for pre-planning purposes.<br />
<br />
==Prior Results==<br />
A short description (one to two paragraphs) of what went right and what went wrong in the previous year. Serves as in introduction to the proposal.<br />
==Project Description==<br />
===Objectives===<br />
The project's objectives should be carefully considered as they will guide the planning of the project. Clear, concise objectives help keep a team focused without pulling the development in too many directions at once. Abstract, far reaching objectives are discouraged as they are hard to fully satisfy and give the team no clear direction. The best objectives focus in on each aspect of the project, and provide detail about what the expectations, such as performance and ease of use, will be for those aspects. Finally, the objectives shouldn't enumerate specific tasks. There should be at least 1 primary objective and 2 secondary objectives. Secondary objectives are defined as something that if not met will not prevent the project from failing to compete.<br />
<br />
====Bad Examples:====<br />
# "To be competitive relative to the current field" - Too broad and not clearly defined. There is no indication of what capabilities are considered competitive in the field and if a team needs to implement all of them.<br />
# "Fix the code for estimating position" - This sounds more like a bug fix or a to-do list than an objective.<br />
# "Design a manipulator for the science task" - While this is specific it really is just a re-hash of the competition objectives. <br />
<br />
====Good Examples:====<br />
# "Gain a competitive advantage by building a rotary based weapon" - Like the above objective the goal of being competitive is clearly conveyed and in addition details are given as to what ways the team will be competitive. Note that the objective is specific enough that the type of weapon is given but general enough that further details are omitted. Also note that the team already at this point has an idea of what type of robot is going to be built instead of starting from a clean slate. <br />
# "Train new members by having them fix some of Glados's simpler problems" - This objective is more general and it achieves a much bigger goal in terms of training. A team leader should be careful in choosing this goal though, as it indicates that they will need to allocate time and resources to training, time that could be spent on new systems for Glados.<br />
# This one can go two ways:<br />
##"Define the objectives for and build a manipulator for the science task" - Not the best objective but at least its this shows that there has been some thought on this objective.<br />
## "Design a manipulator that penetrate six inches of earth for the science task and has minimal size and power requirements" - Much better. Everything is spelled out and the objectives for the manipulator, though general are given. One can use this objective to really guide a design.<br />
<br />
===Milestones===<br />
The milestones are a means of demonstrating progress to the officers, the advisers, sponsors, and the campus as a whole. They also give members a clear sense of where the team is headed and provide motivation. They should be easily demonstrable and realistic without pushing back dates. A good milestone is one that members will prepare for with the same vigor as the actual competition deadline.<br />
<br />
The project description should clearly describe what each milestone is. Milestones can be an objective, parts of several objectives, or the completion of a set of small task such as repairing the robot. Milestones shouldn't be vague objectives such as 'working robots' or 'be ready for competition.' Like objectives some specifics should be given.<br />
<br />
At the very least the officers would like to see a milestone for a prototype/rev 1 sometime in the late fall, and a milestone for testing in the late spring. Beyond that milestones for sub-systems are a good place to start. Below is an example of a good set of milestones for a Mars Rover themed competition<br />
<br />
====Milestones Example====<br />
* Sept 15th 2009 - Fix the all the things broken at competition last year and demonstrate the old rover completing some of the task<br />
* After fall break - Demo at least 2 new prototype drive-trains<br />
* Week before dead week - Prototype - Demo new drive-train in tele-op driving, successfully acquire data from sensors, demo a new end-effector, <br />
* Feb 1st - Demo new manipulator using individual joint control<br />
* March 1st - Extended range driving<br />
* Spring Break - Demo some of the competition tasks using the manipulator<br />
* April 30th - Finalize travel plans, demo robot performing some competition objectives<br />
<br />
===Resources===<br />
Every team will need resources to complete their project and the proposal is where teams indicate what will be needed to successful complete the project. Resources are broken down into monetary, personnel and capital outlays/tooling.<br />
<br />
====Monetary====<br />
This is mainly covered in the budget but the proposal should contain a few words on why the team needs the items its requesting. This information will be helpful for the officers in budget defenses for the club and when dealing with potential sponsors.<br />
<br />
====Personnel====<br />
Team leaders should indicate the number of people they feel they will need to be successful and their skill sets. Since we are mostly undergrads, skill sets roughly means interest.<br />
<br />
====Capital Outlays/Tooling====<br />
While our shop and the Tin building provides an abundance of tools, team leaders may find that certain items are not available. There may also be large equipment purchases that the robots will need. In both cases those items should be listed here. Team leaders should also consider what resources that will be needed to manufacture parts and should list those resources here.<br />
<br />
====Travel/Registration====<br />
In the proposal teams should indicate what competition they are going to, what dates the competition is held (or at least a rough idea of when those dates are known), and expected cost for registration and travel. Per the internal travel policy, RoboJackets will only cover the following<br />
<br />
* Transportation - Gas at the SGA mileage rate, plane, train, or bus tickets, and rental vehicles.<br />
* Incidentals - Materials for competition, items for the robot, First Aid, anything that would be of use to every member of the team for the purposes of competition except, food, hotel, and entertainment. Example: Ponchos<br />
* Luggage for the robot<br />
* Shipping for the robot<br />
* Fees - Excess baggage, duties, <br />
<br />
In addition the proposal should state the anticipated cost for travel per member. This number should include hotel and possibly food, especially if you are going overseas. It should be based on a projected number of attendees.<br />
===Schedule===<br />
The schedule should detail what phases of the project the team will be working on throughout the year. These phases are derived from the objectives and the milestones and should be broken up by subsystem. A phase called design would not be a good choice as subsystem design times vary and can't all be lumped into one. <br />
<br />
There are no formatting rules for the schedule other than it be a separate page and look similar to a Gantt chart. Gnome Planner is preferred though.(You can get it here:http://live.gnome.org/Planner)<br />
===Budget===<br />
The budget contains details on the cost to build the robot and should provide sufficient detail. An example of sufficient detail are cost for metal for the frame. Its understood that teams may not know what their final design will look like (for example which motor they will go with). Careful study of the market and the competition though can go along way in determining what a maximum cost would be for an item. For RoboJackets, surpluses are okay, deficits are impossible since we can't operate in debt. For an example budget see the 2009-2010 SGA budget. Capital outlays (items that can reasonably get more than a year of use) should be listed on the teams budget as they require purchasing, but should by listed in a Capital Outlays Section.<br />
<br />
===Supplemental Documentation===<br />
Any documentation that the team leader feels is required in addition to the above<br />
<br />
==How funding works==<br />
==='''Important'''===<br />
=== Overview ===<br />
In the past project budgets were set at the beginning of the year with the entire budget for each team be allocated in one step. This year teams will have their budgets allocated in phases based on development the milestones they have specified. Not all milestones define a separate phase though but all phases will culminate with some milestone. It is '''required''' that teams at least have a '''design and and build phase''' with the milestone for the design phase being a successful design review. The design review shall be arranged by the team leader, the officers, and interested parties. Interested parties shall include all parties recognized by the officers and team leaders. <br />
<br />
===Milestones and Partial Completion===<br />
Milestones for projects are the milestones and the final travel deadline. Completion of a milestone will be defined by the milestone itself. Partial completion of milestones will be defined by the officers and other interested parties with the input of the team leader. The travel deadline is set as the date in the spring semester by which all travel plans are finalized including, who is going, deposits from members, any paperwork from Tech, and hotels and flights booked. Leniency is given for extenuating circumstances only. <br />
<br />
=== Penalities ===<br />
Failure to meet a milestone will result in the team losing out on additional funding until they have either completed the milestone or made satisfactory progress towards the milestone. Satisfactory progress will be defined by the officers and other parties in with input from the team leader and will take into account external factors such as vendor related issues.<br />
<br />
===Changes===<br />
Changes can be made to any deadline pending officer approval. The criteria for approval are:<br />
<br />
* Time till deadline in question<br />
* Progress made<br />
* External factors<br />
<br />
Changes should be made well before the deadline in question will be missed. Problems such as 11th hour vendor issues or broken hardware are better served by partial completion instead of change requests. <br />
<br />
=== Changes vs. Partial Completion ===<br />
It is understood that problems will arise along the way (Robotics is still very much a research field). As such team leaders have several options when their projects come into unexpected problems. Change request are best suited for bigger problems that can't be solved by simply moving the deadline back a few weeks. Examples include problems obtaining long lead (3+ weeks) items, inability to complete an objective, and changes to the competition. For problems that can be easily solved partial completion is better. The idea is that if a team has been worked hard to meet a deadline but hits a snafu no additional stress is placed on the members by having to continue to work to meet a new deadline.<br />
<br />
=== Authority ===<br />
The authority to approve funding rest solely with the officers. Team leaders, and interested parties can offer input but can not make decisions regarding funding. Funding decisions are approved with a unanimous vote by the officers. This authority is not dictated in the constitution but has been standard operating procedure.<br />
<br />
In general the officers can only ''enforce'' the milestones and objectives that the team leader defines. Even in the event of a change request the officers can only approve or dis-approve changes that the team leaders comes up with. In no instance can an officer create objectives, milestones, or otherwise guide a team. Any officer on a team, on matters of team objectives and milestones, is subject to the decisions of the team leader. The only applicable event in which an officer can have any leadership of a team is if appointed by a team leader or if there are no members to take lead of project.<br />
<br />
==Procedure for Submission==<br />
The proposals are due at 11:59 on the 8/1. They should contain all the sections mention above be in 12pt font, double-spaced, and printed on one side only. The budget should be submitted electronically as a separate excel spreadsheet. It should also be attached to the hard copy. Once all the proposals are in the budget can be made up and then disbursed along with recommendations from the officers and the advisers.<br />
<br />
==Budget Template & Associated Files==<br />
[[File:RoboJackets-TEAM-Budget-Proposal.zip]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=Proposals&diff=9072Proposals2010-09-05T03:52:27Z<p>Stefan: /* Budget Template & Associated Files */</p>
<hr />
<div>Proposals serves two purposes: To inform the officers and the club about the plans of each project and to help team leaders in their project planning. It is comprised of a description of the project objectives for the new year, a schedule, and a budget. Generally, the proposals are due to the officers by the beginning of the school year. Final budget amounts are then determined and announced in the subsequent weeks.<br />
<br />
==Preliminary Proposal==<br />
A preliminary proposal may be asked of the team leaders when the officers need information for planing purposes before the proposal deadline. These preliminary proposals are not binding and are strictly for pre-planning purposes.<br />
<br />
==Prior Results==<br />
A short description (one to two paragraphs) of what went right and what went wrong in the previous year. Serves as in introduction to the proposal.<br />
==Project Description==<br />
===Objectives===<br />
The project's objectives should be carefully considered as they will guide the planning of the project. Clear, concise objectives help keep a team focused without pulling the development in too many directions at once. Abstract, far reaching objectives are discouraged as they are hard to fully satisfy and give the team no clear direction. The best objectives focus in on each aspect of the project, and provide detail about what the expectations, such as performance and ease of use, will be for those aspects. Finally, the objectives shouldn't enumerate specific tasks. There should be at least 1 primary objective and 2 secondary objectives. Secondary objectives are defined as something that if not met will not prevent the project from failing to compete.<br />
<br />
====Bad Examples:====<br />
# "To be competitive relative to the current field" - Too broad and not clearly defined. There is no indication of what capabilities are considered competitive in the field and if a team needs to implement all of them.<br />
# "Fix the code for estimating position" - This sounds more like a bug fix or a to-do list than an objective.<br />
# "Design a manipulator for the science task" - While this is specific it really is just a re-hash of the competition objectives. <br />
<br />
====Good Examples:====<br />
# "Gain a competitive advantage by building a rotary based weapon" - Like the above objective the goal of being competitive is clearly conveyed and in addition details are given as to what ways the team will be competitive. Note that the objective is specific enough that the type of weapon is given but general enough that further details are omitted. Also note that the team already at this point has an idea of what type of robot is going to be built instead of starting from a clean slate. <br />
# "Train new members by having them fix some of Glados's simpler problems" - This objective is more general and it achieves a much bigger goal in terms of training. A team leader should be careful in choosing this goal though, as it indicates that they will need to allocate time and resources to training, time that could be spent on new systems for Glados.<br />
# This one can go two ways:<br />
##"Define the objectives for and build a manipulator for the science task" - Not the best objective but at least its this shows that there has been some thought on this objective.<br />
## "Design a manipulator that penetrate six inches of earth for the science task and has minimal size and power requirements" - Much better. Everything is spelled out and the objectives for the manipulator, though general are given. One can use this objective to really guide a design.<br />
<br />
===Milestones===<br />
The milestones are a means of demonstrating progress to the officers, the advisers, sponsors, and the campus as a whole. They also give members a clear sense of where the team is headed and provide motivation. They should be easily demonstrable and realistic without pushing back dates. A good milestone is one that members will prepare for with the same vigor as the actual competition deadline.<br />
<br />
The project description should clearly describe what each milestone is. Milestones can be an objective, parts of several objectives, or the completion of a set of small task such as repairing the robot. Milestones shouldn't be vague objectives such as 'working robots' or 'be ready for competition.' Like objectives some specifics should be given.<br />
<br />
At the very least the officers would like to see a milestone for a prototype/rev 1 sometime in the late fall, and a milestone for testing in the late spring. Beyond that milestones for sub-systems are a good place to start. Below is an example of a good set of milestones for a Mars Rover themed competition<br />
<br />
====Milestones Example====<br />
* Sept 15th 2009 - Fix the all the things broken at competition last year and demonstrate the old rover completing some of the task<br />
* After fall break - Demo at least 2 new prototype drive-trains<br />
* Week before dead week - Prototype - Demo new drive-train in tele-op driving, successfully acquire data from sensors, demo a new end-effector, <br />
* Feb 1st - Demo new manipulator using individual joint control<br />
* March 1st - Extended range driving<br />
* Spring Break - Demo some of the competition tasks using the manipulator<br />
* April 30th - Finalize travel plans, demo robot performing some competition objectives<br />
<br />
===Resources===<br />
Every team will need resources to complete their project and the proposal is where teams indicate what will be needed to successful complete the project. Resources are broken down into monetary, personnel and capital outlays/tooling.<br />
<br />
====Monetary====<br />
This is mainly covered in the budget but the proposal should contain a few words on why the team needs the items its requesting. This information will be helpful for the officers in budget defenses for the club and when dealing with potential sponsors.<br />
<br />
====Personnel====<br />
Team leaders should indicate the number of people they feel they will need to be successful and their skill sets. Since we are mostly undergrads, skill sets roughly means interest.<br />
<br />
====Capital Outlays/Tooling====<br />
While our shop and the Tin building provides an abundance of tools, team leaders may find that certain items are not available. There may also be large equipment purchases that the robots will need. In both cases those items should be listed here. Team leaders should also consider what resources that will be needed to manufacture parts and should list those resources here.<br />
<br />
====Travel/Registration====<br />
In the proposal teams should indicate what competition they are going to, what dates the competition is held (or at least a rough idea of when those dates are known), and expected cost for registration and travel. Per the internal travel policy, RoboJackets will only cover the following<br />
<br />
* Transportation - Gas at the SGA mileage rate, plane, train, or bus tickets, and rental vehicles.<br />
* Incidentals - Materials for competition, items for the robot, First Aid, anything that would be of use to every member of the team for the purposes of competition except, food, hotel, and entertainment. Example: Ponchos<br />
* Luggage for the robot<br />
* Shipping for the robot<br />
* Fees - Excess baggage, duties, <br />
<br />
In addition the proposal should state the anticipated cost for travel per member. This number should include hotel and possibly food, especially if you are going overseas. It should be based on a projected number of attendees.<br />
===Schedule===<br />
The schedule should detail what phases of the project the team will be working on throughout the year. These phases are derived from the objectives and the milestones and should be broken up by subsystem. A phase called design would not be a good choice as subsystem design times vary and can't all be lumped into one. <br />
<br />
There are no formatting rules for the schedule other than it be a separate page and look similar to a Gantt chart. Gnome Planner is preferred though.(You can get it here:http://live.gnome.org/Planner)<br />
===Budget===<br />
The budget contains details on the cost to build the robot and should provide sufficient detail. An example of sufficient detail are cost for metal for the frame. Its understood that teams may not know what their final design will look like (for example which motor they will go with). Careful study of the market and the competition though can go along way in determining what a maximum cost would be for an item. For RoboJackets, surpluses are okay, deficits are impossible since we can't operate in debt. For an example budget see the 2009-2010 SGA budget. Capital outlays (items that can reasonably get more than a year of use) should be listed on the teams budget as they require purchasing, but should by listed in a Capital Outlays Section.<br />
<br />
===Supplemental Documentation===<br />
Any documentation that the team leader feels is required in addition to the above<br />
<br />
==How funding works==<br />
==='''Important'''===<br />
=== Overview ===<br />
In the past project budgets were set at the beginning of the year with the entire budget for each team be allocated in one step. This year teams will have their budgets allocated in phases based on development the milestones they have specified. Not all milestones define a separate phase though but all phases will culminate with some milestone. It is '''required''' that teams at least have a '''design and and build phase''' with the milestone for the design phase being a successful design review. The design review shall be arranged by the team leader, the officers, and interested parties. Interested parties shall include all parties recognized by the officers and team leaders. <br />
<br />
===Milestones and Partial Completion===<br />
Milestones for projects are the milestones and the final travel deadline. Completion of a milestone will be defined by the milestone itself. Partial completion of milestones will be defined by the officers and other interested parties with the input of the team leader. The travel deadline is set as the date in the spring semester by which all travel plans are finalized including, who is going, deposits from members, any paperwork from Tech, and hotels and flights booked. Leniency is given for extenuating circumstances only. <br />
<br />
=== Penalities ===<br />
Failure to meet a milestone will result in the team losing out on additional funding until they have either completed the milestone or made satisfactory progress towards the milestone. Satisfactory progress will be defined by the officers and other parties in with input from the team leader and will take into account external factors such as vendor related issues.<br />
<br />
===Changes===<br />
Changes can be made to any deadline pending officer approval. The criteria for approval are:<br />
<br />
* Time till deadline in question<br />
* Progress made<br />
* External factors<br />
<br />
Changes should be made well before the deadline in question will be missed. Problems such as 11th hour vendor issues or broken hardware are better served by partial completion instead of change requests. <br />
<br />
=== Changes vs. Partial Completion ===<br />
It is understood that problems will arise along the way (Robotics is still very much a research field). As such team leaders have several options when their projects come into unexpected problems. Change request are best suited for bigger problems that can't be solved by simply moving the deadline back a few weeks. Examples include problems obtaining long lead (3+ weeks) items, inability to complete an objective, and changes to the competition. For problems that can be easily solved partial completion is better. The idea is that if a team has been worked hard to meet a deadline but hits a snafu no additional stress is placed on the members by having to continue to work to meet a new deadline.<br />
<br />
=== Authority ===<br />
The authority to approve funding rest solely with the officers. Team leaders, and interested parties can offer input but can not make decisions regarding funding. Funding decisions are approved with a unanimous vote by the officers. This authority is not dictated in the constitution but has been standard operating procedure.<br />
<br />
In general the officers can only ''enforce'' the milestones and objectives that the team leader defines. Even in the event of a change request the officers can only approve or dis-approve changes that the team leaders comes up with. In no instance can an officer create objectives, milestones, or otherwise guide a team. Any officer on a team, on matters of team objectives and milestones, is subject to the decisions of the team leader. The only applicable event in which an officer can have any leadership of a team is if appointed by a team leader or if there are no members to take lead of project.<br />
<br />
==Procedure for Submission==<br />
The proposals are due at 11:59 on the 8/1. They should contain all the sections mention above be in 12pt font, double-spaced, and printed on one side only. The budget should be submitted electronically as a separate excel spreadsheet. It should also be attached to the hard copy. Once all the proposals are in the budget can be made up and then disbursed along with recommendations from the officers and the advisers.<br />
<br />
==Budget Template & Associated Files==<br />
[File:RoboJackets-TEAM-Budget-Proposal.zip]</div>Stefanhttps://wiki.robojackets.org/index.php?title=File:RoboJackets-TEAM-Budget-Proposal.zip&diff=9071File:RoboJackets-TEAM-Budget-Proposal.zip2010-09-05T03:51:56Z<p>Stefan: Files for team budgets</p>
<hr />
<div>Files for team budgets</div>Stefanhttps://wiki.robojackets.org/index.php?title=Proposals&diff=9070Proposals2010-09-05T03:31:21Z<p>Stefan: /* Monetary */</p>
<hr />
<div>Proposals serves two purposes: To inform the officers and the club about the plans of each project and to help team leaders in their project planning. It is comprised of a description of the project objectives for the new year, a schedule, and a budget. Generally, the proposals are due to the officers by the beginning of the school year. Final budget amounts are then determined and announced in the subsequent weeks.<br />
<br />
==Preliminary Proposal==<br />
A preliminary proposal may be asked of the team leaders when the officers need information for planing purposes before the proposal deadline. These preliminary proposals are not binding and are strictly for pre-planning purposes.<br />
<br />
==Prior Results==<br />
A short description (one to two paragraphs) of what went right and what went wrong in the previous year. Serves as in introduction to the proposal.<br />
==Project Description==<br />
===Objectives===<br />
The project's objectives should be carefully considered as they will guide the planning of the project. Clear, concise objectives help keep a team focused without pulling the development in too many directions at once. Abstract, far reaching objectives are discouraged as they are hard to fully satisfy and give the team no clear direction. The best objectives focus in on each aspect of the project, and provide detail about what the expectations, such as performance and ease of use, will be for those aspects. Finally, the objectives shouldn't enumerate specific tasks. There should be at least 1 primary objective and 2 secondary objectives. Secondary objectives are defined as something that if not met will not prevent the project from failing to compete.<br />
<br />
====Bad Examples:====<br />
# "To be competitive relative to the current field" - Too broad and not clearly defined. There is no indication of what capabilities are considered competitive in the field and if a team needs to implement all of them.<br />
# "Fix the code for estimating position" - This sounds more like a bug fix or a to-do list than an objective.<br />
# "Design a manipulator for the science task" - While this is specific it really is just a re-hash of the competition objectives. <br />
<br />
====Good Examples:====<br />
# "Gain a competitive advantage by building a rotary based weapon" - Like the above objective the goal of being competitive is clearly conveyed and in addition details are given as to what ways the team will be competitive. Note that the objective is specific enough that the type of weapon is given but general enough that further details are omitted. Also note that the team already at this point has an idea of what type of robot is going to be built instead of starting from a clean slate. <br />
# "Train new members by having them fix some of Glados's simpler problems" - This objective is more general and it achieves a much bigger goal in terms of training. A team leader should be careful in choosing this goal though, as it indicates that they will need to allocate time and resources to training, time that could be spent on new systems for Glados.<br />
# This one can go two ways:<br />
##"Define the objectives for and build a manipulator for the science task" - Not the best objective but at least its this shows that there has been some thought on this objective.<br />
## "Design a manipulator that penetrate six inches of earth for the science task and has minimal size and power requirements" - Much better. Everything is spelled out and the objectives for the manipulator, though general are given. One can use this objective to really guide a design.<br />
<br />
===Milestones===<br />
The milestones are a means of demonstrating progress to the officers, the advisers, sponsors, and the campus as a whole. They also give members a clear sense of where the team is headed and provide motivation. They should be easily demonstrable and realistic without pushing back dates. A good milestone is one that members will prepare for with the same vigor as the actual competition deadline.<br />
<br />
The project description should clearly describe what each milestone is. Milestones can be an objective, parts of several objectives, or the completion of a set of small task such as repairing the robot. Milestones shouldn't be vague objectives such as 'working robots' or 'be ready for competition.' Like objectives some specifics should be given.<br />
<br />
At the very least the officers would like to see a milestone for a prototype/rev 1 sometime in the late fall, and a milestone for testing in the late spring. Beyond that milestones for sub-systems are a good place to start. Below is an example of a good set of milestones for a Mars Rover themed competition<br />
<br />
====Milestones Example====<br />
* Sept 15th 2009 - Fix the all the things broken at competition last year and demonstrate the old rover completing some of the task<br />
* After fall break - Demo at least 2 new prototype drive-trains<br />
* Week before dead week - Prototype - Demo new drive-train in tele-op driving, successfully acquire data from sensors, demo a new end-effector, <br />
* Feb 1st - Demo new manipulator using individual joint control<br />
* March 1st - Extended range driving<br />
* Spring Break - Demo some of the competition tasks using the manipulator<br />
* April 30th - Finalize travel plans, demo robot performing some competition objectives<br />
<br />
===Resources===<br />
Every team will need resources to complete their project and the proposal is where teams indicate what will be needed to successful complete the project. Resources are broken down into monetary, personnel and capital outlays/tooling.<br />
<br />
====Monetary====<br />
This is mainly covered in the budget but the proposal should contain a few words on why the team needs the items its requesting. This information will be helpful for the officers in budget defenses for the club and when dealing with potential sponsors.<br />
<br />
====Personnel====<br />
Team leaders should indicate the number of people they feel they will need to be successful and their skill sets. Since we are mostly undergrads, skill sets roughly means interest.<br />
<br />
====Capital Outlays/Tooling====<br />
While our shop and the Tin building provides an abundance of tools, team leaders may find that certain items are not available. There may also be large equipment purchases that the robots will need. In both cases those items should be listed here. Team leaders should also consider what resources that will be needed to manufacture parts and should list those resources here.<br />
<br />
====Travel/Registration====<br />
In the proposal teams should indicate what competition they are going to, what dates the competition is held (or at least a rough idea of when those dates are known), and expected cost for registration and travel. Per the internal travel policy, RoboJackets will only cover the following<br />
<br />
* Transportation - Gas at the SGA mileage rate, plane, train, or bus tickets, and rental vehicles.<br />
* Incidentals - Materials for competition, items for the robot, First Aid, anything that would be of use to every member of the team for the purposes of competition except, food, hotel, and entertainment. Example: Ponchos<br />
* Luggage for the robot<br />
* Shipping for the robot<br />
* Fees - Excess baggage, duties, <br />
<br />
In addition the proposal should state the anticipated cost for travel per member. This number should include hotel and possibly food, especially if you are going overseas. It should be based on a projected number of attendees.<br />
===Schedule===<br />
The schedule should detail what phases of the project the team will be working on throughout the year. These phases are derived from the objectives and the milestones and should be broken up by subsystem. A phase called design would not be a good choice as subsystem design times vary and can't all be lumped into one. <br />
<br />
There are no formatting rules for the schedule other than it be a separate page and look similar to a Gantt chart. Gnome Planner is preferred though.(You can get it here:http://live.gnome.org/Planner)<br />
===Budget===<br />
The budget contains details on the cost to build the robot and should provide sufficient detail. An example of sufficient detail are cost for metal for the frame. Its understood that teams may not know what their final design will look like (for example which motor they will go with). Careful study of the market and the competition though can go along way in determining what a maximum cost would be for an item. For RoboJackets, surpluses are okay, deficits are impossible since we can't operate in debt. For an example budget see the 2009-2010 SGA budget. Capital outlays (items that can reasonably get more than a year of use) should be listed on the teams budget as they require purchasing, but should by listed in a Capital Outlays Section.<br />
<br />
===Supplemental Documentation===<br />
Any documentation that the team leader feels is required in addition to the above<br />
<br />
==How funding works==<br />
==='''Important'''===<br />
=== Overview ===<br />
In the past project budgets were set at the beginning of the year with the entire budget for each team be allocated in one step. This year teams will have their budgets allocated in phases based on development the milestones they have specified. Not all milestones define a separate phase though but all phases will culminate with some milestone. It is '''required''' that teams at least have a '''design and and build phase''' with the milestone for the design phase being a successful design review. The design review shall be arranged by the team leader, the officers, and interested parties. Interested parties shall include all parties recognized by the officers and team leaders. <br />
<br />
===Milestones and Partial Completion===<br />
Milestones for projects are the milestones and the final travel deadline. Completion of a milestone will be defined by the milestone itself. Partial completion of milestones will be defined by the officers and other interested parties with the input of the team leader. The travel deadline is set as the date in the spring semester by which all travel plans are finalized including, who is going, deposits from members, any paperwork from Tech, and hotels and flights booked. Leniency is given for extenuating circumstances only. <br />
<br />
=== Penalities ===<br />
Failure to meet a milestone will result in the team losing out on additional funding until they have either completed the milestone or made satisfactory progress towards the milestone. Satisfactory progress will be defined by the officers and other parties in with input from the team leader and will take into account external factors such as vendor related issues.<br />
<br />
===Changes===<br />
Changes can be made to any deadline pending officer approval. The criteria for approval are:<br />
<br />
* Time till deadline in question<br />
* Progress made<br />
* External factors<br />
<br />
Changes should be made well before the deadline in question will be missed. Problems such as 11th hour vendor issues or broken hardware are better served by partial completion instead of change requests. <br />
<br />
=== Changes vs. Partial Completion ===<br />
It is understood that problems will arise along the way (Robotics is still very much a research field). As such team leaders have several options when their projects come into unexpected problems. Change request are best suited for bigger problems that can't be solved by simply moving the deadline back a few weeks. Examples include problems obtaining long lead (3+ weeks) items, inability to complete an objective, and changes to the competition. For problems that can be easily solved partial completion is better. The idea is that if a team has been worked hard to meet a deadline but hits a snafu no additional stress is placed on the members by having to continue to work to meet a new deadline.<br />
<br />
=== Authority ===<br />
The authority to approve funding rest solely with the officers. Team leaders, and interested parties can offer input but can not make decisions regarding funding. Funding decisions are approved with a unanimous vote by the officers. This authority is not dictated in the constitution but has been standard operating procedure.<br />
<br />
In general the officers can only ''enforce'' the milestones and objectives that the team leader defines. Even in the event of a change request the officers can only approve or dis-approve changes that the team leaders comes up with. In no instance can an officer create objectives, milestones, or otherwise guide a team. Any officer on a team, on matters of team objectives and milestones, is subject to the decisions of the team leader. The only applicable event in which an officer can have any leadership of a team is if appointed by a team leader or if there are no members to take lead of project.<br />
<br />
==Procedure for Submission==<br />
The proposals are due at 11:59 on the 8/1. They should contain all the sections mention above be in 12pt font, double-spaced, and printed on one side only. The budget should be submitted electronically as a separate excel spreadsheet. It should also be attached to the hard copy. Once all the proposals are in the budget can be made up and then disbursed along with recommendations from the officers and the advisers.<br />
<br />
==Budget Template & Associated Files==</div>Stefanhttps://wiki.robojackets.org/index.php?title=Proposals&diff=9069Proposals2010-09-05T03:29:04Z<p>Stefan: /* Monetary */</p>
<hr />
<div>Proposals serves two purposes: To inform the officers and the club about the plans of each project and to help team leaders in their project planning. It is comprised of a description of the project objectives for the new year, a schedule, and a budget. Generally, the proposals are due to the officers by the beginning of the school year. Final budget amounts are then determined and announced in the subsequent weeks.<br />
<br />
==Preliminary Proposal==<br />
A preliminary proposal may be asked of the team leaders when the officers need information for planing purposes before the proposal deadline. These preliminary proposals are not binding and are strictly for pre-planning purposes.<br />
<br />
==Prior Results==<br />
A short description (one to two paragraphs) of what went right and what went wrong in the previous year. Serves as in introduction to the proposal.<br />
==Project Description==<br />
===Objectives===<br />
The project's objectives should be carefully considered as they will guide the planning of the project. Clear, concise objectives help keep a team focused without pulling the development in too many directions at once. Abstract, far reaching objectives are discouraged as they are hard to fully satisfy and give the team no clear direction. The best objectives focus in on each aspect of the project, and provide detail about what the expectations, such as performance and ease of use, will be for those aspects. Finally, the objectives shouldn't enumerate specific tasks. There should be at least 1 primary objective and 2 secondary objectives. Secondary objectives are defined as something that if not met will not prevent the project from failing to compete.<br />
<br />
====Bad Examples:====<br />
# "To be competitive relative to the current field" - Too broad and not clearly defined. There is no indication of what capabilities are considered competitive in the field and if a team needs to implement all of them.<br />
# "Fix the code for estimating position" - This sounds more like a bug fix or a to-do list than an objective.<br />
# "Design a manipulator for the science task" - While this is specific it really is just a re-hash of the competition objectives. <br />
<br />
====Good Examples:====<br />
# "Gain a competitive advantage by building a rotary based weapon" - Like the above objective the goal of being competitive is clearly conveyed and in addition details are given as to what ways the team will be competitive. Note that the objective is specific enough that the type of weapon is given but general enough that further details are omitted. Also note that the team already at this point has an idea of what type of robot is going to be built instead of starting from a clean slate. <br />
# "Train new members by having them fix some of Glados's simpler problems" - This objective is more general and it achieves a much bigger goal in terms of training. A team leader should be careful in choosing this goal though, as it indicates that they will need to allocate time and resources to training, time that could be spent on new systems for Glados.<br />
# This one can go two ways:<br />
##"Define the objectives for and build a manipulator for the science task" - Not the best objective but at least its this shows that there has been some thought on this objective.<br />
## "Design a manipulator that penetrate six inches of earth for the science task and has minimal size and power requirements" - Much better. Everything is spelled out and the objectives for the manipulator, though general are given. One can use this objective to really guide a design.<br />
<br />
===Milestones===<br />
The milestones are a means of demonstrating progress to the officers, the advisers, sponsors, and the campus as a whole. They also give members a clear sense of where the team is headed and provide motivation. They should be easily demonstrable and realistic without pushing back dates. A good milestone is one that members will prepare for with the same vigor as the actual competition deadline.<br />
<br />
The project description should clearly describe what each milestone is. Milestones can be an objective, parts of several objectives, or the completion of a set of small task such as repairing the robot. Milestones shouldn't be vague objectives such as 'working robots' or 'be ready for competition.' Like objectives some specifics should be given.<br />
<br />
At the very least the officers would like to see a milestone for a prototype/rev 1 sometime in the late fall, and a milestone for testing in the late spring. Beyond that milestones for sub-systems are a good place to start. Below is an example of a good set of milestones for a Mars Rover themed competition<br />
<br />
====Milestones Example====<br />
* Sept 15th 2009 - Fix the all the things broken at competition last year and demonstrate the old rover completing some of the task<br />
* After fall break - Demo at least 2 new prototype drive-trains<br />
* Week before dead week - Prototype - Demo new drive-train in tele-op driving, successfully acquire data from sensors, demo a new end-effector, <br />
* Feb 1st - Demo new manipulator using individual joint control<br />
* March 1st - Extended range driving<br />
* Spring Break - Demo some of the competition tasks using the manipulator<br />
* April 30th - Finalize travel plans, demo robot performing some competition objectives<br />
<br />
===Resources===<br />
Every team will need resources to complete their project and the proposal is where teams indicate what will be needed to successful complete the project. Resources are broken down into monetary, personnel and capital outlays/tooling.<br />
<br />
====Monetary====<br />
This is mainly covered in the budget but the proposal should contain a few words on why the team needs the items its requesting. This information will be helpful for the officers in budget defenses for the club and when dealing with potential sponsors. This would be a good place to state why larger ticket items are needed.<br />
<br />
====Personnel====<br />
Team leaders should indicate the number of people they feel they will need to be successful and their skill sets. Since we are mostly undergrads, skill sets roughly means interest.<br />
<br />
====Capital Outlays/Tooling====<br />
While our shop and the Tin building provides an abundance of tools, team leaders may find that certain items are not available. There may also be large equipment purchases that the robots will need. In both cases those items should be listed here. Team leaders should also consider what resources that will be needed to manufacture parts and should list those resources here.<br />
<br />
====Travel/Registration====<br />
In the proposal teams should indicate what competition they are going to, what dates the competition is held (or at least a rough idea of when those dates are known), and expected cost for registration and travel. Per the internal travel policy, RoboJackets will only cover the following<br />
<br />
* Transportation - Gas at the SGA mileage rate, plane, train, or bus tickets, and rental vehicles.<br />
* Incidentals - Materials for competition, items for the robot, First Aid, anything that would be of use to every member of the team for the purposes of competition except, food, hotel, and entertainment. Example: Ponchos<br />
* Luggage for the robot<br />
* Shipping for the robot<br />
* Fees - Excess baggage, duties, <br />
<br />
In addition the proposal should state the anticipated cost for travel per member. This number should include hotel and possibly food, especially if you are going overseas. It should be based on a projected number of attendees.<br />
===Schedule===<br />
The schedule should detail what phases of the project the team will be working on throughout the year. These phases are derived from the objectives and the milestones and should be broken up by subsystem. A phase called design would not be a good choice as subsystem design times vary and can't all be lumped into one. <br />
<br />
There are no formatting rules for the schedule other than it be a separate page and look similar to a Gantt chart. Gnome Planner is preferred though.(You can get it here:http://live.gnome.org/Planner)<br />
===Budget===<br />
The budget contains details on the cost to build the robot and should provide sufficient detail. An example of sufficient detail are cost for metal for the frame. Its understood that teams may not know what their final design will look like (for example which motor they will go with). Careful study of the market and the competition though can go along way in determining what a maximum cost would be for an item. For RoboJackets, surpluses are okay, deficits are impossible since we can't operate in debt. For an example budget see the 2009-2010 SGA budget. Capital outlays (items that can reasonably get more than a year of use) should be listed on the teams budget as they require purchasing, but should by listed in a Capital Outlays Section.<br />
<br />
===Supplemental Documentation===<br />
Any documentation that the team leader feels is required in addition to the above<br />
<br />
==How funding works==<br />
==='''Important'''===<br />
=== Overview ===<br />
In the past project budgets were set at the beginning of the year with the entire budget for each team be allocated in one step. This year teams will have their budgets allocated in phases based on development the milestones they have specified. Not all milestones define a separate phase though but all phases will culminate with some milestone. It is '''required''' that teams at least have a '''design and and build phase''' with the milestone for the design phase being a successful design review. The design review shall be arranged by the team leader, the officers, and interested parties. Interested parties shall include all parties recognized by the officers and team leaders. <br />
<br />
===Milestones and Partial Completion===<br />
Milestones for projects are the milestones and the final travel deadline. Completion of a milestone will be defined by the milestone itself. Partial completion of milestones will be defined by the officers and other interested parties with the input of the team leader. The travel deadline is set as the date in the spring semester by which all travel plans are finalized including, who is going, deposits from members, any paperwork from Tech, and hotels and flights booked. Leniency is given for extenuating circumstances only. <br />
<br />
=== Penalities ===<br />
Failure to meet a milestone will result in the team losing out on additional funding until they have either completed the milestone or made satisfactory progress towards the milestone. Satisfactory progress will be defined by the officers and other parties in with input from the team leader and will take into account external factors such as vendor related issues.<br />
<br />
===Changes===<br />
Changes can be made to any deadline pending officer approval. The criteria for approval are:<br />
<br />
* Time till deadline in question<br />
* Progress made<br />
* External factors<br />
<br />
Changes should be made well before the deadline in question will be missed. Problems such as 11th hour vendor issues or broken hardware are better served by partial completion instead of change requests. <br />
<br />
=== Changes vs. Partial Completion ===<br />
It is understood that problems will arise along the way (Robotics is still very much a research field). As such team leaders have several options when their projects come into unexpected problems. Change request are best suited for bigger problems that can't be solved by simply moving the deadline back a few weeks. Examples include problems obtaining long lead (3+ weeks) items, inability to complete an objective, and changes to the competition. For problems that can be easily solved partial completion is better. The idea is that if a team has been worked hard to meet a deadline but hits a snafu no additional stress is placed on the members by having to continue to work to meet a new deadline.<br />
<br />
=== Authority ===<br />
The authority to approve funding rest solely with the officers. Team leaders, and interested parties can offer input but can not make decisions regarding funding. Funding decisions are approved with a unanimous vote by the officers. This authority is not dictated in the constitution but has been standard operating procedure.<br />
<br />
In general the officers can only ''enforce'' the milestones and objectives that the team leader defines. Even in the event of a change request the officers can only approve or dis-approve changes that the team leaders comes up with. In no instance can an officer create objectives, milestones, or otherwise guide a team. Any officer on a team, on matters of team objectives and milestones, is subject to the decisions of the team leader. The only applicable event in which an officer can have any leadership of a team is if appointed by a team leader or if there are no members to take lead of project.<br />
<br />
==Procedure for Submission==<br />
The proposals are due at 11:59 on the 8/1. They should contain all the sections mention above be in 12pt font, double-spaced, and printed on one side only. The budget should be submitted electronically as a separate excel spreadsheet. It should also be attached to the hard copy. Once all the proposals are in the budget can be made up and then disbursed along with recommendations from the officers and the advisers.<br />
<br />
==Budget Template & Associated Files==</div>Stefanhttps://wiki.robojackets.org/index.php?title=Proposals&diff=9068Proposals2010-09-05T03:17:35Z<p>Stefan: </p>
<hr />
<div>Proposals serves two purposes: To inform the officers and the club about the plans of each project and to help team leaders in their project planning. It is comprised of a description of the project objectives for the new year, a schedule, and a budget. Generally, the proposals are due to the officers by the beginning of the school year. Final budget amounts are then determined and announced in the subsequent weeks.<br />
<br />
==Preliminary Proposal==<br />
A preliminary proposal may be asked of the team leaders when the officers need information for planing purposes before the proposal deadline. These preliminary proposals are not binding and are strictly for pre-planning purposes.<br />
<br />
==Prior Results==<br />
A short description (one to two paragraphs) of what went right and what went wrong in the previous year. Serves as in introduction to the proposal.<br />
==Project Description==<br />
===Objectives===<br />
The project's objectives should be carefully considered as they will guide the planning of the project. Clear, concise objectives help keep a team focused without pulling the development in too many directions at once. Abstract, far reaching objectives are discouraged as they are hard to fully satisfy and give the team no clear direction. The best objectives focus in on each aspect of the project, and provide detail about what the expectations, such as performance and ease of use, will be for those aspects. Finally, the objectives shouldn't enumerate specific tasks. There should be at least 1 primary objective and 2 secondary objectives. Secondary objectives are defined as something that if not met will not prevent the project from failing to compete.<br />
<br />
====Bad Examples:====<br />
# "To be competitive relative to the current field" - Too broad and not clearly defined. There is no indication of what capabilities are considered competitive in the field and if a team needs to implement all of them.<br />
# "Fix the code for estimating position" - This sounds more like a bug fix or a to-do list than an objective.<br />
# "Design a manipulator for the science task" - While this is specific it really is just a re-hash of the competition objectives. <br />
<br />
====Good Examples:====<br />
# "Gain a competitive advantage by building a rotary based weapon" - Like the above objective the goal of being competitive is clearly conveyed and in addition details are given as to what ways the team will be competitive. Note that the objective is specific enough that the type of weapon is given but general enough that further details are omitted. Also note that the team already at this point has an idea of what type of robot is going to be built instead of starting from a clean slate. <br />
# "Train new members by having them fix some of Glados's simpler problems" - This objective is more general and it achieves a much bigger goal in terms of training. A team leader should be careful in choosing this goal though, as it indicates that they will need to allocate time and resources to training, time that could be spent on new systems for Glados.<br />
# This one can go two ways:<br />
##"Define the objectives for and build a manipulator for the science task" - Not the best objective but at least its this shows that there has been some thought on this objective.<br />
## "Design a manipulator that penetrate six inches of earth for the science task and has minimal size and power requirements" - Much better. Everything is spelled out and the objectives for the manipulator, though general are given. One can use this objective to really guide a design.<br />
<br />
===Milestones===<br />
The milestones are a means of demonstrating progress to the officers, the advisers, sponsors, and the campus as a whole. They also give members a clear sense of where the team is headed and provide motivation. They should be easily demonstrable and realistic without pushing back dates. A good milestone is one that members will prepare for with the same vigor as the actual competition deadline.<br />
<br />
The project description should clearly describe what each milestone is. Milestones can be an objective, parts of several objectives, or the completion of a set of small task such as repairing the robot. Milestones shouldn't be vague objectives such as 'working robots' or 'be ready for competition.' Like objectives some specifics should be given.<br />
<br />
At the very least the officers would like to see a milestone for a prototype/rev 1 sometime in the late fall, and a milestone for testing in the late spring. Beyond that milestones for sub-systems are a good place to start. Below is an example of a good set of milestones for a Mars Rover themed competition<br />
<br />
====Milestones Example====<br />
* Sept 15th 2009 - Fix the all the things broken at competition last year and demonstrate the old rover completing some of the task<br />
* After fall break - Demo at least 2 new prototype drive-trains<br />
* Week before dead week - Prototype - Demo new drive-train in tele-op driving, successfully acquire data from sensors, demo a new end-effector, <br />
* Feb 1st - Demo new manipulator using individual joint control<br />
* March 1st - Extended range driving<br />
* Spring Break - Demo some of the competition tasks using the manipulator<br />
* April 30th - Finalize travel plans, demo robot performing some competition objectives<br />
<br />
===Resources===<br />
Every team will need resources to complete their project and the proposal is where teams indicate what will be needed to successful complete the project. Resources are broken down into monetary, personnel and capital outlays/tooling.<br />
<br />
====Monetary====<br />
This is mainly covered in the budget but the proposal should contain a few words on why the team needs the items its requesting. This information will be helpful for the officers in budget defenses for the club and when dealing with potential sponsors.<br />
<br />
====Personnel====<br />
Team leaders should indicate the number of people they feel they will need to be successful and their skill sets. Since we are mostly undergrads, skill sets roughly means interest.<br />
<br />
====Capital Outlays/Tooling====<br />
While our shop and the Tin building provides an abundance of tools, team leaders may find that certain items are not available. There may also be large equipment purchases that the robots will need. In both cases those items should be listed here. Team leaders should also consider what resources that will be needed to manufacture parts and should list those resources here.<br />
<br />
====Travel/Registration====<br />
In the proposal teams should indicate what competition they are going to, what dates the competition is held (or at least a rough idea of when those dates are known), and expected cost for registration and travel. Per the internal travel policy, RoboJackets will only cover the following<br />
<br />
* Transportation - Gas at the SGA mileage rate, plane, train, or bus tickets, and rental vehicles.<br />
* Incidentals - Materials for competition, items for the robot, First Aid, anything that would be of use to every member of the team for the purposes of competition except, food, hotel, and entertainment. Example: Ponchos<br />
* Luggage for the robot<br />
* Shipping for the robot<br />
* Fees - Excess baggage, duties, <br />
<br />
In addition the proposal should state the anticipated cost for travel per member. This number should include hotel and possibly food, especially if you are going overseas. It should be based on a projected number of attendees.<br />
===Schedule===<br />
The schedule should detail what phases of the project the team will be working on throughout the year. These phases are derived from the objectives and the milestones and should be broken up by subsystem. A phase called design would not be a good choice as subsystem design times vary and can't all be lumped into one. <br />
<br />
There are no formatting rules for the schedule other than it be a separate page and look similar to a Gantt chart. Gnome Planner is preferred though.(You can get it here:http://live.gnome.org/Planner)<br />
===Budget===<br />
The budget contains details on the cost to build the robot and should provide sufficient detail. An example of sufficient detail are cost for metal for the frame. Its understood that teams may not know what their final design will look like (for example which motor they will go with). Careful study of the market and the competition though can go along way in determining what a maximum cost would be for an item. For RoboJackets, surpluses are okay, deficits are impossible since we can't operate in debt. For an example budget see the 2009-2010 SGA budget. Capital outlays (items that can reasonably get more than a year of use) should be listed on the teams budget as they require purchasing, but should by listed in a Capital Outlays Section.<br />
<br />
===Supplemental Documentation===<br />
Any documentation that the team leader feels is required in addition to the above<br />
<br />
==How funding works==<br />
==='''Important'''===<br />
=== Overview ===<br />
In the past project budgets were set at the beginning of the year with the entire budget for each team be allocated in one step. This year teams will have their budgets allocated in phases based on development the milestones they have specified. Not all milestones define a separate phase though but all phases will culminate with some milestone. It is '''required''' that teams at least have a '''design and and build phase''' with the milestone for the design phase being a successful design review. The design review shall be arranged by the team leader, the officers, and interested parties. Interested parties shall include all parties recognized by the officers and team leaders. <br />
<br />
===Milestones and Partial Completion===<br />
Milestones for projects are the milestones and the final travel deadline. Completion of a milestone will be defined by the milestone itself. Partial completion of milestones will be defined by the officers and other interested parties with the input of the team leader. The travel deadline is set as the date in the spring semester by which all travel plans are finalized including, who is going, deposits from members, any paperwork from Tech, and hotels and flights booked. Leniency is given for extenuating circumstances only. <br />
<br />
=== Penalities ===<br />
Failure to meet a milestone will result in the team losing out on additional funding until they have either completed the milestone or made satisfactory progress towards the milestone. Satisfactory progress will be defined by the officers and other parties in with input from the team leader and will take into account external factors such as vendor related issues.<br />
<br />
===Changes===<br />
Changes can be made to any deadline pending officer approval. The criteria for approval are:<br />
<br />
* Time till deadline in question<br />
* Progress made<br />
* External factors<br />
<br />
Changes should be made well before the deadline in question will be missed. Problems such as 11th hour vendor issues or broken hardware are better served by partial completion instead of change requests. <br />
<br />
=== Changes vs. Partial Completion ===<br />
It is understood that problems will arise along the way (Robotics is still very much a research field). As such team leaders have several options when their projects come into unexpected problems. Change request are best suited for bigger problems that can't be solved by simply moving the deadline back a few weeks. Examples include problems obtaining long lead (3+ weeks) items, inability to complete an objective, and changes to the competition. For problems that can be easily solved partial completion is better. The idea is that if a team has been worked hard to meet a deadline but hits a snafu no additional stress is placed on the members by having to continue to work to meet a new deadline.<br />
<br />
=== Authority ===<br />
The authority to approve funding rest solely with the officers. Team leaders, and interested parties can offer input but can not make decisions regarding funding. Funding decisions are approved with a unanimous vote by the officers. This authority is not dictated in the constitution but has been standard operating procedure.<br />
<br />
In general the officers can only ''enforce'' the milestones and objectives that the team leader defines. Even in the event of a change request the officers can only approve or dis-approve changes that the team leaders comes up with. In no instance can an officer create objectives, milestones, or otherwise guide a team. Any officer on a team, on matters of team objectives and milestones, is subject to the decisions of the team leader. The only applicable event in which an officer can have any leadership of a team is if appointed by a team leader or if there are no members to take lead of project.<br />
<br />
==Procedure for Submission==<br />
The proposals are due at 11:59 on the 8/1. They should contain all the sections mention above be in 12pt font, double-spaced, and printed on one side only. The budget should be submitted electronically as a separate excel spreadsheet. It should also be attached to the hard copy. Once all the proposals are in the budget can be made up and then disbursed along with recommendations from the officers and the advisers.<br />
<br />
==Budget Template & Associated Files==</div>Stefanhttps://wiki.robojackets.org/index.php?title=Proposals&diff=9067Proposals2010-09-05T03:16:51Z<p>Stefan: /* Budget */</p>
<hr />
<div>Proposals serves two purposes: To inform the officers and the club about the plans of each project and to help team leaders in their project planning. It is comprised of a description of the project objectives for the new year, a schedule, and a budget. Generally, the proposals are due to the officers by the beginning of the school year. Final budget amounts are then determined and announced in the subsequent weeks.<br />
<br />
==Preliminary Proposal==<br />
A preliminary proposal may be asked of the team leaders when the officers need information for planing purposes before the proposal deadline. These preliminary proposals are not binding and are strictly for pre-planning purposes.<br />
<br />
==Prior Results==<br />
A short description (one to two paragraphs) of what went right and what went wrong in the previous year. Serves as in introduction to the proposal.<br />
==Project Description==<br />
===Objectives===<br />
The project's objectives should be carefully considered as they will guide the planning of the project. Clear, concise objectives help keep a team focused without pulling the development in too many directions at once. Abstract, far reaching objectives are discouraged as they are hard to fully satisfy and give the team no clear direction. The best objectives focus in on each aspect of the project, and provide detail about what the expectations, such as performance and ease of use, will be for those aspects. Finally, the objectives shouldn't enumerate specific tasks. There should be at least 1 primary objective and 2 secondary objectives. Secondary objectives are defined as something that if not met will not prevent the project from failing to compete.<br />
<br />
====Bad Examples:====<br />
# "To be competitive relative to the current field" - Too broad and not clearly defined. There is no indication of what capabilities are considered competitive in the field and if a team needs to implement all of them.<br />
# "Fix the code for estimating position" - This sounds more like a bug fix or a to-do list than an objective.<br />
# "Design a manipulator for the science task" - While this is specific it really is just a re-hash of the competition objectives. <br />
<br />
====Good Examples:====<br />
# "Gain a competitive advantage by building a rotary based weapon" - Like the above objective the goal of being competitive is clearly conveyed and in addition details are given as to what ways the team will be competitive. Note that the objective is specific enough that the type of weapon is given but general enough that further details are omitted. Also note that the team already at this point has an idea of what type of robot is going to be built instead of starting from a clean slate. <br />
# "Train new members by having them fix some of Glados's simpler problems" - This objective is more general and it achieves a much bigger goal in terms of training. A team leader should be careful in choosing this goal though, as it indicates that they will need to allocate time and resources to training, time that could be spent on new systems for Glados.<br />
# This one can go two ways:<br />
##"Define the objectives for and build a manipulator for the science task" - Not the best objective but at least its this shows that there has been some thought on this objective.<br />
## "Design a manipulator that penetrate six inches of earth for the science task and has minimal size and power requirements" - Much better. Everything is spelled out and the objectives for the manipulator, though general are given. One can use this objective to really guide a design.<br />
<br />
===Milestones===<br />
The milestones are a means of demonstrating progress to the officers, the advisers, sponsors, and the campus as a whole. They also give members a clear sense of where the team is headed and provide motivation. They should be easily demonstrable and realistic without pushing back dates. A good milestone is one that members will prepare for with the same vigor as the actual competition deadline.<br />
<br />
The project description should clearly describe what each milestone is. Milestones can be an objective, parts of several objectives, or the completion of a set of small task such as repairing the robot. Milestones shouldn't be vague objectives such as 'working robots' or 'be ready for competition.' Like objectives some specifics should be given.<br />
<br />
At the very least the officers would like to see a milestone for a prototype/rev 1 sometime in the late fall, and a milestone for testing in the late spring. Beyond that milestones for sub-systems are a good place to start. Below is an example of a good set of milestones for a Mars Rover themed competition<br />
<br />
====Milestones Example====<br />
* Sept 15th 2009 - Fix the all the things broken at competition last year and demonstrate the old rover completing some of the task<br />
* After fall break - Demo at least 2 new prototype drive-trains<br />
* Week before dead week - Prototype - Demo new drive-train in tele-op driving, successfully acquire data from sensors, demo a new end-effector, <br />
* Feb 1st - Demo new manipulator using individual joint control<br />
* March 1st - Extended range driving<br />
* Spring Break - Demo some of the competition tasks using the manipulator<br />
* April 30th - Finalize travel plans, demo robot performing some competition objectives<br />
<br />
===Resources===<br />
Every team will need resources to complete their project and the proposal is where teams indicate what will be needed to successful complete the project. Resources are broken down into monetary, personnel and capital outlays/tooling.<br />
<br />
====Monetary====<br />
This is mainly covered in the budget but the proposal should contain a few words on why the team needs the items its requesting. This information will be helpful for the officers in budget defenses for the club and when dealing with potential sponsors.<br />
<br />
====Personnel====<br />
Team leaders should indicate the number of people they feel they will need to be successful and their skill sets. Since we are mostly undergrads, skill sets roughly means interest.<br />
<br />
====Capital Outlays/Tooling====<br />
While our shop and the Tin building provides an abundance of tools, team leaders may find that certain items are not available. There may also be large equipment purchases that the robots will need. In both cases those items should be listed here. Team leaders should also consider what resources that will be needed to manufacture parts and should list those resources here.<br />
<br />
====Travel/Registration====<br />
In the proposal teams should indicate what competition they are going to, what dates the competition is held (or at least a rough idea of when those dates are known), and expected cost for registration and travel. Per the internal travel policy, RoboJackets will only cover the following<br />
<br />
* Transportation - Gas at the SGA mileage rate, plane, train, or bus tickets, and rental vehicles.<br />
* Incidentals - Materials for competition, items for the robot, First Aid, anything that would be of use to every member of the team for the purposes of competition except, food, hotel, and entertainment. Example: Ponchos<br />
* Luggage for the robot<br />
* Shipping for the robot<br />
* Fees - Excess baggage, duties, <br />
<br />
In addition the proposal should state the anticipated cost for travel per member. This number should include hotel and possibly food, especially if you are going overseas. It should be based on a projected number of attendees.<br />
===Schedule===<br />
The schedule should detail what phases of the project the team will be working on throughout the year. These phases are derived from the objectives and the milestones and should be broken up by subsystem. A phase called design would not be a good choice as subsystem design times vary and can't all be lumped into one. <br />
<br />
There are no formatting rules for the schedule other than it be a separate page and look similar to a Gantt chart. Gnome Planner is preferred though.(You can get it here:http://live.gnome.org/Planner)<br />
===Budget===<br />
The budget contains details on the cost to build the robot and should provide sufficient detail. An example of sufficient detail are cost for metal for the frame. Its understood that teams may not know what their final design will look like (for example which motor they will go with). Careful study of the market and the competition though can go along way in determining what a maximum cost would be for an item. For RoboJackets, surpluses are okay, deficits are impossible since we can't operate in debt. For an example budget see the 2009-2010 SGA budget. Capital outlays (items that can reasonably get more than a year of use) should be listed on the teams budget as they require purchasing, but should by listed in a Capital Outlays Section.<br />
<br />
===Supplemental Documentation===<br />
Any documentation that the team leader feels is required in addition to the above<br />
<br />
==How funding works==<br />
==='''Important'''===<br />
=== Overview ===<br />
In the past project budgets were set at the beginning of the year with the entire budget for each team be allocated in one step. This year teams will have their budgets allocated in phases based on development the milestones they have specified. Not all milestones define a separate phase though but all phases will culminate with some milestone. It is '''required''' that teams at least have a '''design and and build phase''' with the milestone for the design phase being a successful design review. The design review shall be arranged by the team leader, the officers, and interested parties. Interested parties shall include all parties recognized by the officers and team leaders. <br />
<br />
===Milestones and Partial Completion===<br />
Milestones for projects are the milestones and the final travel deadline. Completion of a milestone will be defined by the milestone itself. Partial completion of milestones will be defined by the officers and other interested parties with the input of the team leader. The travel deadline is set as the date in the spring semester by which all travel plans are finalized including, who is going, deposits from members, any paperwork from Tech, and hotels and flights booked. Leniency is given for extenuating circumstances only. <br />
<br />
=== Penalities ===<br />
Failure to meet a milestone will result in the team losing out on additional funding until they have either completed the milestone or made satisfactory progress towards the milestone. Satisfactory progress will be defined by the officers and other parties in with input from the team leader and will take into account external factors such as vendor related issues.<br />
<br />
===Changes===<br />
Changes can be made to any deadline pending officer approval. The criteria for approval are:<br />
<br />
* Time till deadline in question<br />
* Progress made<br />
* External factors<br />
<br />
Changes should be made well before the deadline in question will be missed. Problems such as 11th hour vendor issues or broken hardware are better served by partial completion instead of change requests. <br />
<br />
=== Changes vs. Partial Completion ===<br />
It is understood that problems will arise along the way (Robotics is still very much a research field). As such team leaders have several options when their projects come into unexpected problems. Change request are best suited for bigger problems that can't be solved by simply moving the deadline back a few weeks. Examples include problems obtaining long lead (3+ weeks) items, inability to complete an objective, and changes to the competition. For problems that can be easily solved partial completion is better. The idea is that if a team has been worked hard to meet a deadline but hits a snafu no additional stress is placed on the members by having to continue to work to meet a new deadline.<br />
<br />
=== Authority ===<br />
The authority to approve funding rest solely with the officers. Team leaders, and interested parties can offer input but can not make decisions regarding funding. Funding decisions are approved with a unanimous vote by the officers. This authority is not dictated in the constitution but has been standard operating procedure.<br />
<br />
In general the officers can only ''enforce'' the milestones and objectives that the team leader defines. Even in the event of a change request the officers can only approve or dis-approve changes that the team leaders comes up with. In no instance can an officer create objectives, milestones, or otherwise guide a team. Any officer on a team, on matters of team objectives and milestones, is subject to the decisions of the team leader. The only applicable event in which an officer can have any leadership of a team is if appointed by a team leader or if there are no members to take lead of project.<br />
<br />
==Procedure for Submission==<br />
The proposals are due at 11:59 on the 8/1. They should contain all the sections mention above be in 12pt font, double-spaced, and printed on one side only. The budget should be submitted electronically as a separate excel spreadsheet. It should also be attached to the hard copy. Once all the proposals are in the budget can be made up and then disbursed along with recommendations from the officers and the advisers.</div>Stefanhttps://wiki.robojackets.org/index.php?title=IGVC&diff=9003IGVC2010-07-29T01:35:13Z<p>Stefan: /* Important Items */</p>
<hr />
<div>[[Image:OfficiialPic.jpg|thumb|400px|right|[[Candi Robot Guide|Candi]], our robot for the 2007 IGVC competition.]]<br />
<br />
The [http://www.gatech.edu/ Georgia Tech] [http://www.robojackets.org/ RoboJackets] [http://www.igvc.org IGVC] team will compete for the fifth time in the intelligent ground vehicle competition. This year's competition will be held at Oakland University from June 5 - June 8, 2009. <br />
<br />
==Meeting Times==<br />
<br />
We meet in the Tin Building (Mechanical Engineering Research Building) and can be reached at 404-385-4067.<br />
<br />
* '''IGVC Planning Day''' - Wednesday 6:00 pm to 7:00 pm<br />
* '''IGVC Work Day''' - Saturday 2:00 pm to 6:00 pm<br />
<br />
==Announcements==<br />
''Please sign announcements with <tt><nowiki>-~~~~</nowiki></tt>.<br />
<br />
==Important Items==<br />
=====[[IGVC_Overview_2010|2010 Competition]]=====<br />
* Need a new robot page<br />
* [[IGVC 2010 Meeting Notes|Meeting Notes]]<br />
* [[IGVC 2010 Tasks|Tasks]]<br />
* [[IGVC 2010 Practice Field|Practice Field]]<br />
<br />
=====Reference=====<br />
* [https://lists.gatech.edu/sympa/info/robojackets-igvc IGVC Mailing List]<br />
* [http://www.igvc.org/ Official IGVC Website]<br />
* [[IGVC Rules]]<br />
* [[IGVC Design Guidelines|Design Guidelines]]<br />
* [[Resources for Learning]]<br />
* [[IGVC Parts Sampling List|Parts Sampling List]]<br />
* [[Past IGVC Competitions|Past Competitions]]<br />
<br />
[[Category: IGVC]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=File:RC2009ChipperKickerRender.jpg&diff=8972File:RC2009ChipperKickerRender.jpg2010-06-21T04:18:24Z<p>Stefan: uploaded a new version of "File:RC2009ChipperKickerRender.jpg"</p>
<hr />
<div></div>Stefanhttps://wiki.robojackets.org/index.php?title=File:RJShirtBack.jpg&diff=8895File:RJShirtBack.jpg2010-04-06T01:24:35Z<p>Stefan: uploaded a new version of "File:RJShirtBack.jpg": 2010 back</p>
<hr />
<div></div>Stefanhttps://wiki.robojackets.org/index.php?title=File:RJShirtFront.jpg&diff=8894File:RJShirtFront.jpg2010-04-06T01:23:22Z<p>Stefan: uploaded a new version of "File:RJShirtFront.jpg": 2010Shirt</p>
<hr />
<div></div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-KickerChipper&diff=8892RC09-KickerChipper2010-04-04T22:30:02Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], the kicker provides passing capabilities to the robots. It is part of the chipper / kicker assembly.<br />
[[Image:RC2009ChipperKickerRender.jpg|thumb|right|2009 RoboJackets RoboCup Kicker & Chipperl]]<br />
<br />
<br />
==Related Pages==<br />
* [[RC09KickerElectronics | Kicker Electronics]]<br />
<br />
==Parts & Components==<br />
Amounts are based on per robot. Materials are in sizes for prototyping not lowest cost per amount.<br />
<br />
===Stock===<br />
=====Brass Solenoid Core Tube=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8859K34<br />
:Cost - $11.34 / pack of 3<br />
:Description - Alloy 260 Miniature Brass Shapes Round Tube, 17/32" OD, 1' Length<br />
<br />
=====Inner Rod - Possible Candidate 1=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8909K761<br />
:Cost - $6.48<br />
:Description - Cast Gray Iron Rod 5/8" Diameter, 1' Length<br />
<br />
=====Inner Rod - Possible Candidate 2=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8909K761<br />
:Cost - $5.17<br />
:Description - O1 Tool Steel Rod 5/8" Diameter, 1' Length<br />
<br />
<br />
<br />
<br />
NOTE: 2.4in long by .247in tall by .302in deep<br />
7075 Grade, #8 32threads/in(8-32)<br />
<br />
==Action Log==<br />
# 10/12/2008 - Solenoid inner core diameter for prototype selected.<br />
# 03/04/2009 - Fabrication issues with quality control have been encountered in winding the solenoid.<br />
# 03/13/2009 - Decision has been made to purchase more of last years solenoids and attempt in house modifications.<br />
# 03/22/2009 - Initial concept completed.<br />
# 04/04/2009 - Resizing adjustments made.<br />
# 04/12/2009 - Kicker rev1 design completed.<br />
# 10/25/2009 - First fully machineable chipper design completed. (rev8)<br />
# 01/31/2010 - Prototype kicker and chipper OTS solenoids re selected and designs updated.<br />
# 01/31/2010 - Hardware testing of new electrical mockup shows estimated speeds of 12 m/s with 2008 solenoids.<br />
# 02/02/2010 - New solenoids ordered.<br />
# 02/07/2010 - Chipper & Kicker assemblies updated.<br />
# 03/25/2010 - Chipper variants assembled and tested. Variants non functional.<br />
# 03/26/2010 - Redesign completed, separate test rig designed, and fabrication started.<br />
# 03/27/2010 - Fabrication completed and device tested. Chipper working with a range of up to 13ft. Longer solenoid stroke need for better power transfer.<br />
# 04/04/2010 - Design refinements conducted.<br />
[[Category: RoboCup Mechanical]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-Chassis&diff=8891RC09-Chassis2010-04-04T22:24:24Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], the chassis holds the various system together and is primarily composed of a top and bottom plate.<br />
[[Image:RC2009RobotRender.jpg|thumb|right|2009 RoboJackets RoboCup Robot]]<br />
<br />
==Drawings==<br />
<br />
==Materials==<br />
<br />
==Assembly Structure==<br />
====Parts List====<br />
<br />
<br />
====Instructions====<br />
<br />
==Non-Mechanical Components==<br />
====Antenna Board====<br />
====Kicker Board====<br />
====Li-Po Battery====<br />
<br />
==Parts & Components==<br />
Amounts are based on per robot. Materials are in sizes for prototyping not lowest cost per robot volume pricing if available is in parenthesis.<br />
<br />
===Stock===<br />
=====Plate - Bottom=====<br />
:Vendor - <br />
:Part No. - <br />
:Cost - <br />
:Description -<br />
<br />
<br />
<br />
===Fasteners===<br />
<br />
====6-32 Low Head Socket Cap Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92220A141<br />
:Cost - $7.42 (Packs of 25)<br />
:Description - Alloy Steel Low Head Socket Cap Screw 6-32 Thread, 1/4" Length<br />
<br />
==== 1/8" Locating Pins====<br />
:Vendor - MSC Industrial Supply<br />
:Part No. - 88231469<br />
:Cost - $26.46 (pk 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/8 Overall Length: 3/16 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
===Other===<br />
<br />
<br />
<br />
<br />
==Cost Estimates==<br />
<br />
==Action Log==<br />
# 02/08/2008 - Initial base with 4 modules designed.<br />
# 02/18/2009 - Preliminary solenoid added.<br />
# 03/17/2009 - Batteries and Caps now fit.<br />
# 03/19/2009 - Everything all assemblies now fit with out clipping.<br />
# 03/20/2009 - Fillets added to base plate to keep it with in dimensions.<br />
# 03/22/2009 - Updated chipper & kicker assembly added.<br />
# 04/12/2009 - Base plate modified to allow attachment of chipper & kicker assembly.<br />
# 07/18/2009 - Bottom plate CAM'd.<br />
# 12/28/2009 - Bottom plate machined.<br />
# 01/31/2010 - Electrical board standoffs and new caps are selected. Designs updated. <br />
# 03/19/2010 - Top plate water jetted.<br />
# 03/20/2010 - Drive train test completed with weights producing a gross robot weight of 5 lbs. Robot is faster and more responsive than 2008. <br />
<br />
[[Category: RoboCup Mechanical]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-DriveMotorFab&diff=8890RC09-DriveMotorFab2010-04-04T22:20:50Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]] Drive Modules we were required to modify the drive motors to accommodate our custom pinion shaft. This page holds information on that process and the jigs and fixtures we made to complete that.<br />
<br />
[[Image:RC2009DriveMotorFabRender.jpg|thumb|right|A development rendering of the 2009 Drive Motor Assembly Procedure]]<br />
<br />
==Parts & Components==<br />
===Parts to be assembled===<br />
====Drive Motor====<br />
<br />
====Custom Pinion Shaft====<br />
<br />
===Stock===<br />
====Al Plate 1"====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8975K313<br />
:Cost - $21.56<br />
:Description - Multipurpose Aluminum (Alloy 6061) 1" Thick X 3" Width X 1' Length<br />
<br />
====Al Plate 1/8"====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 89015K18<br />
:Cost - $26.06<br />
:Description - Multipurpose Aluminum (Alloy 6061) .125" Thick, 12" X 12"<br />
<br />
====Steel Rod 1/2" Dia====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 5227T26<br />
:Cost - $18.05<br />
:Description - 12L14 Carbon Steel Tight-Tolerance Rod 1/2" Diameter, 6' Length<br />
<br />
====Al Plate 0.020"====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8973K82<br />
:Cost - $3.86<br />
:Description - Improved-Strength Basic Aluminum (Alloy 3003) .020" Thick, 12" X 12"<br />
<br />
===Fasteners===<br />
====M3 x 6 Metric Flat Head Socket Cap Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 91294A126<br />
:Cost - $6.76 (pk 100)<br />
:Description - Metric Flat Head Socket Cap Screw Class 10.9 Stl, M3 Size, 6mm Length, .50mm Pitch (Needs 90 deg countersink)<br />
<br />
==Process==<br />
====Disassembly====<br />
<br />
====Assembly====<br />
<br />
==Action Log==<br />
# 04/01/2009 - A spare drive motor from 2008 fleet was successfully disassembled and reassembled.<br />
# 04/02/2009 - Design of fixture for reassembling drive motors completed.<br />
# 04/05/2009 - Shafts upgraded. Material list added to wiki.<br />
# 11/05/2009 - Material trimmed and device made to fit on small press. Allows for possible reassembly at competition.<br />
# 01/19/2010 - All parts fabricated.<br />
# 01/26/2010 - Block remade and interference fit still not correct. Situation corrected with gasket sealer.<br />
# 01/29/2010 - Gasket sealer fix verified.<br />
# 03/20/2010 - Design verified with the successful assembly of motors for prototype.</div>Stefanhttps://wiki.robojackets.org/index.php?title=RoboCupMechanical&diff=8889RoboCupMechanical2010-04-04T22:19:18Z<p>Stefan: /* Ball Control */</p>
<hr />
<div>This page houses the current [[RoboCup]] Mechanical efforts. The 2008 efforts can be found [[RoboCupMechanical2008 | here]]. All development work will be done in Autodesk Inventor 2009. How to use Inventor and get it can be found on the [[How to Guide Inventor | Inventor How to Guide]]. Inventor is also available on our CAD Machines in Tin and in the ECS Lab in the French building.<br />
<br />
[[Image:RC2009RobotRender.jpg|thumb|right|A development rendering of a 2009 RoboCup robot]]<br />
<br />
==Meetings & Development Time Line==<br />
===Current Work Schedule===<br />
:Sundays, 2pm - 6pm<br />
<br />
===Development Schedule & Tasks===<br />
This is just a list of our most pressing objectives. For a full listing see [[RoboCupMechanicalDev|RoboCup Mechanical Dev]].<br />
# Review Drive base and Chipper / Kicker Assembly.<br />
# Machine<br />
#: Omni Bodies<br />
#: Drive Plates<br />
#: Base Plates<br />
#: Dribbler Plates<br />
# Solenoid development<br />
<br />
==Systems==<br />
===Overall===<br />
: [[RC09-Components|System Components and Bill of Materials]]<br />
===Drivetrain===<br />
: [[RC09-Omni|Omni Wheels]]<br />
: [[RC09-DriveModule|Drive Module]]<br />
: [[RC09-DriveMotor|Drive Motor]]<br />
: ''Personnel''<br />
:# [[User:Stefan|Stefan]] (Drive Modules & Omni Wheels, Mechanical Lead)<br />
<br />
===Integration===<br />
: [[RC09-Shell|Shell]]<br />
: [[RC09-Chassis|Chassis]]<br />
<br />
===Ball Control===<br />
: [[RC09-Dribbler|Dribbler]]<br />
: [[RC09-KickerChipper|Kicker & Chipper]]<br />
: ''Personnel''<br />
:# [[User:StoianB|Stu]] (Kicker & Chipper)<br />
:# [[User:Stefan|Stefan]] (Dribbler)<br />
<br />
===Testing===<br />
: [[RC09-METestRig|Test Rig]]<br />
: [[RC09-Slope|Slope]]<br />
: [[RC09-Impact Test|Impact Test]]<br />
: [[RC09-Carpet|Carpet]]<br />
<br />
===Fabrication===<br />
: [[RC09-DriveMotorFab|Drive Motor Fixture]]<br />
<br />
==Competition Specifications==<br />
* Field<br />
*: Area 6.6m x 4.7m<br />
*: Material - Locally available carpet<br />
* Robot<br />
*: Maximum Diameter - 180mm<br />
*: Maximum Height - 150mm (measured from solid surface)<br />
*: Maximum Weight - 1.8 kg<br />
* Golf Ball<br />
*: Max Speed - 10 m/s<br />
*: Diameter - 43 mm<br />
*: Mass - 46 grams<br />
*: Material - DuPont Surlyn Ionomer [http://www2.dupont.com/Surlyn/en_US/ Dupont's Surlyn Page]<br />
*: No more than 20% of the ball's area may be occupied by / within the robot. See [[:Image:Ball_sketch.PNG|this illustration]].<br />
* More info found in rules [http://small-size.informatik.uni-bremen.de/ RoboCup SSL Website]<br />
<br />
==Testing==<br />
[[RoboCup Testing | RoboCup Testing]]<br />
<br />
==Useful Links==<br />
*[http://www.cis.cornell.edu/boom/2005/ProjectArchive/robocup/ Cornell Documents] (Look at 2003)<br />
*[ftp://ftp.itam.mx/pub/alfredo/PAPERS/SotoWeitzenfeld80LARS2006.pdf Eagle Knights Dribbler Testing]<br />
*[http://www.sdp-si.com/D220/D220cat.htm#T35 Mechanical Engineering Tips]<br />
*[http://www.linuxcnc.org/handbook/gcode/g-code.html G-Code Tutorial]<br />
*[http://robojackets.org/~circuitben/ Overhead camera footage from Robocup 2007 Championship Match]<br />
*[http://www.drgears.com/gearterms/GearTermIndex.htm Dr. Gear - Gear Encyclopedia]<br />
*[http://shtylman.com/robocup_resource/mechanical/CornellRoboCupMechanicalDocumentation2004.doc Cornell 2004 Mechanical Documentation]<br />
*[http://pergatory.mit.edu/2.007/Resources/index.html#manufacturing MIT Design Handbook Index] (VERY GOOD)<br />
*[http://thomasnet.com Global supplier and CAD drawing database]<br />
<br />
[[Category: RoboCup]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RoboCupMechanical&diff=8888RoboCupMechanical2010-04-04T22:18:49Z<p>Stefan: /* Drivetrain */</p>
<hr />
<div>This page houses the current [[RoboCup]] Mechanical efforts. The 2008 efforts can be found [[RoboCupMechanical2008 | here]]. All development work will be done in Autodesk Inventor 2009. How to use Inventor and get it can be found on the [[How to Guide Inventor | Inventor How to Guide]]. Inventor is also available on our CAD Machines in Tin and in the ECS Lab in the French building.<br />
<br />
[[Image:RC2009RobotRender.jpg|thumb|right|A development rendering of a 2009 RoboCup robot]]<br />
<br />
==Meetings & Development Time Line==<br />
===Current Work Schedule===<br />
:Sundays, 2pm - 6pm<br />
<br />
===Development Schedule & Tasks===<br />
This is just a list of our most pressing objectives. For a full listing see [[RoboCupMechanicalDev|RoboCup Mechanical Dev]].<br />
# Review Drive base and Chipper / Kicker Assembly.<br />
# Machine<br />
#: Omni Bodies<br />
#: Drive Plates<br />
#: Base Plates<br />
#: Dribbler Plates<br />
# Solenoid development<br />
<br />
==Systems==<br />
===Overall===<br />
: [[RC09-Components|System Components and Bill of Materials]]<br />
===Drivetrain===<br />
: [[RC09-Omni|Omni Wheels]]<br />
: [[RC09-DriveModule|Drive Module]]<br />
: [[RC09-DriveMotor|Drive Motor]]<br />
: ''Personnel''<br />
:# [[User:Stefan|Stefan]] (Drive Modules & Omni Wheels, Mechanical Lead)<br />
<br />
===Integration===<br />
: [[RC09-Shell|Shell]]<br />
: [[RC09-Chassis|Chassis]]<br />
<br />
===Ball Control===<br />
: [[RC09-Dribbler|Dribbler]]<br />
: [[RC09-KickerChipper|Kicker & Chipper]]<br />
: ''Personnel''<br />
:# [[User:StoianB|Stu]] (Kicker & Chipper)<br />
:# [[User:ArjunM|Arjun]] (Dribbler)<br />
<br />
===Testing===<br />
: [[RC09-METestRig|Test Rig]]<br />
: [[RC09-Slope|Slope]]<br />
: [[RC09-Impact Test|Impact Test]]<br />
: [[RC09-Carpet|Carpet]]<br />
<br />
===Fabrication===<br />
: [[RC09-DriveMotorFab|Drive Motor Fixture]]<br />
<br />
==Competition Specifications==<br />
* Field<br />
*: Area 6.6m x 4.7m<br />
*: Material - Locally available carpet<br />
* Robot<br />
*: Maximum Diameter - 180mm<br />
*: Maximum Height - 150mm (measured from solid surface)<br />
*: Maximum Weight - 1.8 kg<br />
* Golf Ball<br />
*: Max Speed - 10 m/s<br />
*: Diameter - 43 mm<br />
*: Mass - 46 grams<br />
*: Material - DuPont Surlyn Ionomer [http://www2.dupont.com/Surlyn/en_US/ Dupont's Surlyn Page]<br />
*: No more than 20% of the ball's area may be occupied by / within the robot. See [[:Image:Ball_sketch.PNG|this illustration]].<br />
* More info found in rules [http://small-size.informatik.uni-bremen.de/ RoboCup SSL Website]<br />
<br />
==Testing==<br />
[[RoboCup Testing | RoboCup Testing]]<br />
<br />
==Useful Links==<br />
*[http://www.cis.cornell.edu/boom/2005/ProjectArchive/robocup/ Cornell Documents] (Look at 2003)<br />
*[ftp://ftp.itam.mx/pub/alfredo/PAPERS/SotoWeitzenfeld80LARS2006.pdf Eagle Knights Dribbler Testing]<br />
*[http://www.sdp-si.com/D220/D220cat.htm#T35 Mechanical Engineering Tips]<br />
*[http://www.linuxcnc.org/handbook/gcode/g-code.html G-Code Tutorial]<br />
*[http://robojackets.org/~circuitben/ Overhead camera footage from Robocup 2007 Championship Match]<br />
*[http://www.drgears.com/gearterms/GearTermIndex.htm Dr. Gear - Gear Encyclopedia]<br />
*[http://shtylman.com/robocup_resource/mechanical/CornellRoboCupMechanicalDocumentation2004.doc Cornell 2004 Mechanical Documentation]<br />
*[http://pergatory.mit.edu/2.007/Resources/index.html#manufacturing MIT Design Handbook Index] (VERY GOOD)<br />
*[http://thomasnet.com Global supplier and CAD drawing database]<br />
<br />
[[Category: RoboCup]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-Omni&diff=8887RC09-Omni2010-04-04T22:17:48Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], the Omni Wheels allow the robots to move in any direction at anytime.<br />
[[Image:RC2009OmniWheelRender.jpg|thumb|right|2009 RoboJackets RoboCup Omni Wheel]]<br />
<br />
==Drawings==<br />
<br />
==Materials==<br />
<br />
==Assembly Structure==<br />
====Parts List====<br />
<br />
====Instructions====<br />
<br />
==Parts & Components==<br />
Amounts are based on per robot. Materials are in sizes for prototyping not lowest cost per robot volume pricing if available is in parenthesis.<br />
<br />
===Stock===<br />
=====Plate - Wheel Plate=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8885K13<br />
:Cost - $21.63<br />
:Description - Alloy 7075 Aluminum Sheet .063" Thick, 12" X 12"<br />
<br />
=====Plate - Wheel Body=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 9246K23<br />
:Cost - $28.51<br />
:Description - Multipurpose Aluminum (Alloy 6061) 3/8" Thick, 12" X 12"<br />
<br />
=====Shaft - Rollers=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 9063K243<br />
:Cost - $17.48<br />
:Description - Alloy 7075 Aluminum Precision Ground Rod 1/8" Diameter, 3' Length<br />
:''Note: Usually ships within 2 weeks.''<br />
<br />
===Fasteners===<br />
=====6-32 Low Head Socket Cap Screw=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92220A141<br />
:Cost - $7.42 (packs of 25)<br />
:Description - Alloy Steel Low Head Socket Cap Screw 6-32 Thread, 1/4" Length<br />
<br />
=====3/16" Dowel Pin=====<br />
:Vendor - MSC<br />
:Part No. - 88231758<br />
:Cost - $43.08 (per 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 3/16 Overall Length: 1/4 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
=====1/16" Dowel Pin=====<br />
:Vendor - MSC<br />
:Part No. - 88231196<br />
:Cost - $19.83 (per 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/16 Overall Length: 1/4 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
===Other===<br />
=====O-Ring=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 94115K012<br />
:Cost - $2.87 (Pks of 100)<br />
:Quantity -<br />
:Description - Neoprene O-Ring AS568A Dash Number 012<br />
<br />
==Fabrication==<br />
=====Omni Plates=====<br />
: Can be done in house on Haas for prototype.<br />
: Fleet should be water jetted.<br />
<br />
=====Omni Bodies=====<br />
: In House on Haas VF-2<br />
<br />
=====Omni Rollers=====<br />
: MFG.com - CNC Lathe Required<br />
<br />
==Cost Estimates==<br />
<br />
==Action Log==<br />
# 10/19/2008 - Initial revised roller design completed.<br />
# 11/02/2008 - Added new groove style for new rollers.<br />
# 11/09/2008 - Refined roller design.<br />
# 12/30/2008 - Resized to match internal gear dimensions.<br />
# 01/13/2009 - Added fillets.<br />
# 02/01/2009 - Drawing for rollers produced and ready to be posted for quote.<br />
# 02/22/2009 - Design for prototype completed. <br />
# 03/15/2009 - Rollers posted to mfg.com for quote.<br />
# 03/17/2009 - Design revised. Internal gear added to omni body.<br />
# 03/25/2009 - Supplier for rollers selected.<br />
# 04/08/2009 - All 400 Rollers arrive for omni wheels.<br />
# 05/05/2009 - 1/2 of rollers are assembled.<br />
# 07/18/2009 - Omni bodies CAM'd.<br />
# 01/26/2010 - Omni plates for prototype water jetted.<br />
# 02/03/2010 - Tooling required to make omni bodies arrives.<br />
# 02/13/2010 - First omni body completed. Problems encountered with automated tapping of 6-32s.<br />
# 03/20/2010 - Last omni body for prototype made.<br />
# 03/23/2010 - Revisions made to omni design to allow for better draining of retaining compound, symmetrical plate positioning, and new bearings. <br />
# 04/03/2010 - First fleet omni body made. Process is down to 2hrs.<br />
<br />
[[Category: RoboCup Mechanical]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-DriveModule&diff=8886RC09-DriveModule2010-04-04T22:11:57Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], Drive Modules integrate the motor, gearbox and omniwheel in to one modular assembly.<br />
[[Image:RC2009DriveModuleRender.jpg|thumb|right|2009 RoboJackets RoboCup Drive Module]]<br />
<br />
<br />
==Assembly Structure==<br />
====Parts Structure====<br />
# Inner Drive Plate<br />
# Omni Wheel<br />
# Output Axel<br />
# Spindle<br />
## Internal Gear<br />
## Bearing Plate<br />
## Wheel Attachment Plate<br />
## Hex Shaft<br />
<br />
<br />
====Parts List====<br />
# 1 - Omni Wheel (RC-2009-02-00)<br />
# 1 - Maxon Brushless Drive Motor (RC-2009-03-01)<br />
# 1 - Drive Module Plate (RC-2009-03-02)<br />
# 1 - Shaft (RC-2009-03-03)<br />
# 1 - Internal Gear (RC-2009-03-04)<br />
# 3 - 5/8" Long Hex Standoffs (RC-2009- -)<br />
# 2 - 1/4" Ball Bearings (RC-2009-03-05) (RC-2008-03-08)<br />
<br />
====Instructions====<br />
<br />
==Parts & Components==<br />
===Motors and Encoders===<br />
====Brushless Motors====<br />
:Vendor - Maxon<br />
:Part No. - 200142<br />
:Cost - $50.53(EUR)<br />
:Description - EC 45 flat Ø45 mm, brushless, 30 Watt<br />
<br />
====Encoders====<br />
:Vendor - US Digital<br />
:Part No. - E4P-360-157-D-D-T-B<br />
:Cost - $26.39 ($20.75)<br />
:Description - E4P OEM Miniature Optical Kit Encoder [http://usdigital.com/assets/drawings/471.pdf Spec]<br />
:Note - Vendor supplied 3-48 x 1/4" screws are not long enough for 0.05" plate. We have switched to transfer adhesive.<br />
<br />
===Gears & Bearings===<br />
====Motor Output Gear====<br />
:Vendor - SDP/SI<br />
:Part No. - S1VS05M016F0704<br />
:Cost - $22.06 ($18.16)<br />
:Description - Module 0.5, 16 Teeth, 20° Pressure Angle, 303 Stainless Steel Gear<br />
<br />
====Internal Gear (Standard)(Supplier A)====<br />
:Vendor - SDP/SI<br />
:Part No. - S1E62Z-072S110<br />
:Cost - $47.16 ($44.51)<br />
:Description - 72 DP, 110T, AGMA Q10, 303 STAINLESS STEEL INTERNAL GEAR<br />
<br />
====Internal Gear (Standard)(Supplier B)====<br />
:Vendor - WM BERG<br />
:Part No. - N72S2-110 <br />
:Cost - $46.25<br />
:Description - 72 DP, 110T, AGMA Q10, 303 STAINLESS STEEL INTERNAL GEAR<br />
<br />
====Internal Gear (Metric)(Supplier A)====<br />
:Vendor - SDP/SI <br />
:Part No. - S1E05ZM05S072 <br />
:Cost - $31.10 ($28.48) <br />
:Description - Module 0.5, 72 TEETH, 20° Pressure Angle, 303 Stainless Steel, INTERNAL GEAR<br />
<br />
====Internal Gear (Metric)(Supplier B)====<br />
:Vendor - <br />
:Part No. - <br />
:Cost - <br />
:Description - <br />
<br />
====Bearing (1/4" Shaft)====<br />
:Vendor - Grainger<br />
:Part No. - 1ZEJ7<br />
:Cost - $5.59 Each<br />
:Description - Miniature Ball Bearing, Open, Flanged, Bore Dia 0.2500 In, Outside Dia 0.5000 In, Width 0.1250 In, Flange Dia 0.5470 In, Flange Thickness 0.0230 In, ABEC Level 3<br />
:Info - [http://www.grainger.com/Grainger/wwg/productIndex.shtml?operator=keywordSearch&search_type=keyword&QueryString=1ZEJ7&submit.x=6&submit.y=6 Web Link]<br />
<br />
===Stock===<br />
====Al Plate 1/8"====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 89015K18<br />
:Cost - $26.06<br />
:Description - Alloy 6061 Aluminum Sheet .125" Thick, 12" X 12"<br />
<br />
====Al Plate 0.05"====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8885K18 <br />
:Cost - $35.62 Each <br />
:Description - Alloy 7075 Aluminum Sheet .050" Thick, 12" X 24"<br />
:Note - 7075 b/c we have left over from last year other wise 6061.<br />
<br />
===Fasteners===<br />
====0-80 x 1/4" Button Head====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92949A054<br />
:Cost - $9.30 (Packs of 50)<br />
:Description - 18-8 SS Button Head Socket Cap Screw 0-80 Thread, 1/4" Length<br />
<br />
====6-32 Low Head Socket Cap Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92220A141<br />
:Cost - $7.42 (Packs of 25)<br />
:Description - Alloy Steel Low Head Socket Cap Screw 6-32 Thread, 1/4" Length<br />
<br />
====6-32 Socket Cap Counter Sunk Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 91253A144<br />
:Cost - $9.91 (Packs of 100)<br />
:Description - Alloy Steel Flat Head Socket Cap Screw 6-32 Thread, 1/4" Length, Black Oxide<br />
<br />
====6-32 Button Head====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92949A143<br />
:Cost - $7.88 (Packs of 100)<br />
:Description - 18-8 SS Button Head Socket Cap Screw 6-32 Thread, 3/16" Length<br />
<br />
====6-32 3/4" Standoffs====<br />
:Vendor - Digi-Key<br />
:Part No. - 2211K-ND<br />
:Cost - $6.14 (pk 10) $55.83 (pk 100) <br />
:Description - STANDOFF HEX 6-32THR ALUM .750"<br />
<br />
====10-32 Shoulder Bolt====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 94035A531<br />
:Cost - $2.08 (each)<br />
:Description - 18-8 SS Precision Hex Socket Shoulder Screw 1/4" Shoulder Dia, 1/8" L Shoulder, 10-32 Thread<br />
<br />
====M3 x 6 Metric Flat Head Socket Cap Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 91294A126<br />
:Cost - $6.76 (pk 100)<br />
:Description - Metric Flat Head Socket Cap Screw Class 10.9 Stl, M3 Size, 6mm Length, .50mm Pitch (Needs 90 deg countersink)<br />
<br />
==== 1/16" Locating Pins====<br />
:Vendor - MSC Industrial Supply<br />
:Part No. - 88231196<br />
:Cost - $19.83 (pk 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/16 Overall Length: 1/4 Material: Stainless Steel - 416 SS Finish/Coating: Bright <br />
<br />
==== 1/8" Locating Pins====<br />
:Vendor - MSC Industrial Supply<br />
:Part No. - 88231469<br />
:Cost - $26.46 (pk 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/8 Overall Length: 3/16 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
==Fabrication==<br />
<br />
==Action Log==<br />
# 12/29/2008 - Internal gears selected.<br />
# 12/30/2008 - Initial design of gear box completed.<br />
# 01/11/2009 - Removed mass and moved to 1/8" plate for motor mounting.<br />
# 01/12/2009 - Dropped 8-32 screws to 6-32, and made treading full on hex..<br />
# 01/13/2009 - Confirmed that Maxon does offer custom shafts for motors and added current materials to wiki.<br />
# 01/25/2009 - Preliminary encoder selected.<br />
# 01/26/2009 - Initial design with a encoder completed.<br />
# 02/02/2009 - Design revised. Attachment to bottom plate enhanced and encoder fully compensated for.<br />
# 02/22/2009 - Design for prototype completed.<br />
# 03/07/2009 - Design revised. Drive modules reshaped to accommodate capacitors.<br />
# 03/16/2009 - Gear posted to mfg.com for quote.<br />
# 03/17/2009 - Design revised. Spindle removed and internal gear placed on omni body.<br />
# 03/19/2009 - Plates reshaped to allow room for dribbler components.<br />
# 03/17/2009 - RFQ for internal gears posted on mfg.com.<br />
# 03/25/2009 - Supplier for initial run of internal gears selected.<br />
# 03/26/2009 - Have moved to reversing engineering and modifying drive motors in house.<br />
# 04/01/2009 - A spare drive motor from 2008 fleet was successfully disassembled and reassembled.<br />
# 04/02/2009 - Design of fixture for reassembling drive motors completed. Info can be found on the [[RC09-DriveMotorFab | Drive Motor Fixture]] page.<br />
# 07/18/2009 - Drive plates have been CAM'd.<br />
# 07/28/2009 - Motor shaft modified to allow for better assembly.<br />
# 10/18/2009 - Encoder plate CAM'd up in waterjet software.<br />
# 11/01/2009 - Output shaft standoffs fabricated.<br />
# 12/23/2009 - Drive plates machined.<br />
# 01/26/2010 - Encoder plates water jetted.<br />
# 02/16/2010 - Drive module assembled and wheel wobble discovered.<br />
# 03/19/2010 - Output shafts modified and remade.<br />
# 03/20/2010 - All drive modules assembled and tested wheel wobble still persists.<br />
# 03/25/2010 - New shielded bearings arrive and installed. Wheel wobble has been mitigated.<br />
# 03/27/2010 - Drive modules now ready fleet.<br />
[[Category: RoboCup Mechanical]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8874Elections Procedure2010-03-25T00:41:43Z<p>Stefan: </p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings. In the past we have had people not running for some positions due to time commitments. Terms for elected positions last for one year. That cannot happen this year as many people are graduating and cannot go empty. See below as these are noted.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down. Note it is not advisable for a officer to also be a project manager.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed as well as a few responsibilities.<br />
<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President (Graduating)===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
* Works with PR Chair to plan outreach events.<br />
<br />
===Treasurer (Graduating)===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This position will at some point mean driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
* Gets our name out.<br />
<br />
===Secretary (Vacant)===<br />
* Manages club records.<br />
* Works with PR Chair on external image.<br />
* Helps keep site current.<br />
* Adds to filtering communications.<br />
* Maintains email list.<br />
<br />
==Project Mangers==<br />
These are responsible getting the job done, having robots at competitions, and managing a workshop series. Replacements are nominated by the current leader and then voted on by the specific team.<br />
* '''FIRST'''<br />
* '''BattleBots'''<br />
* IGVC<br />
* RoboCup<br />
* '''TE Sessions'''<br />
<br />
Bold denotes vacancies that must be filled.<br />
<br />
==Non-Elected Positions==<br />
===IT Coordinator (Graduating)===<br />
This person manages our server and computers. They need to be skilled in linux CLI and windows implementation. Any one interested will need to talk with the current IT coordinator and officers.</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8873Elections Procedure2010-03-25T00:40:59Z<p>Stefan: /* IT Coordinator */</p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings. In the past we have had people not running for some positions due to time commitments. That cannot happen this year as many people are graduating and cannot go empty. See below as these are noted.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down. Note it is not advisable for a officer to also be a project manager.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed as well as a few responsibilities.<br />
<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President (Graduating)===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
* Works with PR Chair to plan outreach events.<br />
<br />
===Treasurer (Graduating)===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This position will at some point mean driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
* Gets our name out.<br />
<br />
===Secretary (Vacant)===<br />
* Manages club records.<br />
* Works with PR Chair on external image.<br />
* Helps keep site current.<br />
* Adds to filtering communications.<br />
* Maintains email list.<br />
<br />
==Project Mangers==<br />
These are responsible getting the job done, having robots at competitions, and managing a workshop series. Replacements are nominated by the current leader and then voted on by the specific team.<br />
* '''FIRST'''<br />
* '''BattleBots'''<br />
* IGVC<br />
* RoboCup<br />
* '''TE Sessions'''<br />
<br />
Bold denotes vacancies that must be filled.<br />
<br />
==Non-Elected Positions==<br />
===IT Coordinator (Graduating)===<br />
This person manages our server and computers. They need to be skilled in linux CLI and windows implementation. Any one interested will need to talk with the current IT coordinator and officers.</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8872Elections Procedure2010-03-25T00:38:10Z<p>Stefan: </p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings. In the past we have had people not running for some positions due to time commitments. That cannot happen this year as many people are graduating and cannot go empty. See below as these are noted.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down. Note it is not advisable for a officer to also be a project manager.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed as well as a few responsibilities.<br />
<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President (Graduating)===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
* Works with PR Chair to plan outreach events.<br />
<br />
===Treasurer (Graduating)===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This position will at some point mean driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
* Gets our name out.<br />
<br />
===Secretary (Vacant)===<br />
* Manages club records.<br />
* Works with PR Chair on external image.<br />
* Helps keep site current.<br />
* Adds to filtering communications.<br />
* Maintains email list.<br />
<br />
==Project Mangers==<br />
These are responsible getting the job done, having robots at competitions, and managing a workshop series. Replacements are nominated by the current leader and then voted on by the specific team.<br />
* '''FIRST'''<br />
* '''BattleBots'''<br />
* IGVC<br />
* RoboCup<br />
* '''TE Sessions'''<br />
<br />
Bold denotes vacancies that must be filled.<br />
<br />
==Non-Elected Positions==<br />
===IT Coordinator===<br />
This person manages our server and computers. They need to be skilled in linux CLI and windows implementation. Any one interested will need to talk with the current IT coordinator and officers.</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8871Elections Procedure2010-03-25T00:29:26Z<p>Stefan: /* Nominations */</p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down. Note it is not advisable for a officer to also be a project manager.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed as well as a few responsibilities.<br />
<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President (Graduating)===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
* Works with PR Chair to plan outreach events.<br />
<br />
===Treasurer (Graduating)===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This position will at some point mean driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
* Gets our name out.<br />
<br />
===Secretary (Vacant)===<br />
* Manages club records.<br />
* Works with PR Chair on external image.<br />
* Helps keep site current.<br />
* Adds to filtering communications.<br />
* Maintains email list.<br />
<br />
==Project Mangers==<br />
These are responsible getting the job done, having robots at competitions, and managing a workshop series. Replacements are nominated by the current leader and then voted on by the specific team.<br />
* '''FIRST'''<br />
* '''BattleBots'''<br />
* IGVC<br />
* RoboCup<br />
* '''TE Sessions'''<br />
<br />
Bold denotes vacancies that must be filled.<br />
<br />
==Non-Elected Positions==<br />
===IT Coordinator===<br />
This person manages our server and computers. They need to be skilled in linux CLI and windows implementation. Any one interested will need to talk with the current IT coordinator and officers.</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8870Elections Procedure2010-03-25T00:29:10Z<p>Stefan: /* Nominations */</p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down. Note it is not adviseable for a team leader to also be a project manager.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed as well as a few responsibilities.<br />
<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President (Graduating)===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
* Works with PR Chair to plan outreach events.<br />
<br />
===Treasurer (Graduating)===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This position will at some point mean driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
* Gets our name out.<br />
<br />
===Secretary (Vacant)===<br />
* Manages club records.<br />
* Works with PR Chair on external image.<br />
* Helps keep site current.<br />
* Adds to filtering communications.<br />
* Maintains email list.<br />
<br />
==Project Mangers==<br />
These are responsible getting the job done, having robots at competitions, and managing a workshop series. Replacements are nominated by the current leader and then voted on by the specific team.<br />
* '''FIRST'''<br />
* '''BattleBots'''<br />
* IGVC<br />
* RoboCup<br />
* '''TE Sessions'''<br />
<br />
Bold denotes vacancies that must be filled.<br />
<br />
==Non-Elected Positions==<br />
===IT Coordinator===<br />
This person manages our server and computers. They need to be skilled in linux CLI and windows implementation. Any one interested will need to talk with the current IT coordinator and officers.</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8869Elections Procedure2010-03-25T00:28:06Z<p>Stefan: /* Vice-President */</p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed as well as a few responsibilities.<br />
<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President (Graduating)===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
* Works with PR Chair to plan outreach events.<br />
<br />
===Treasurer (Graduating)===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This position will at some point mean driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
* Gets our name out.<br />
<br />
===Secretary (Vacant)===<br />
* Manages club records.<br />
* Works with PR Chair on external image.<br />
* Helps keep site current.<br />
* Adds to filtering communications.<br />
* Maintains email list.<br />
<br />
==Project Mangers==<br />
These are responsible getting the job done, having robots at competitions, and managing a workshop series. Replacements are nominated by the current leader and then voted on by the specific team.<br />
* '''FIRST'''<br />
* '''BattleBots'''<br />
* IGVC<br />
* RoboCup<br />
* '''TE Sessions'''<br />
<br />
Bold denotes vacancies that must be filled.<br />
<br />
==Non-Elected Positions==<br />
===IT Coordinator===<br />
This person manages our server and computers. They need to be skilled in linux CLI and windows implementation. Any one interested will need to talk with the current IT coordinator and officers.</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8868Elections Procedure2010-03-25T00:27:54Z<p>Stefan: /* Treasurer */</p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed as well as a few responsibilities.<br />
<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
* Works with PR Chair to plan outreach events.<br />
<br />
===Treasurer (Graduating)===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This position will at some point mean driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
* Gets our name out.<br />
<br />
===Secretary (Vacant)===<br />
* Manages club records.<br />
* Works with PR Chair on external image.<br />
* Helps keep site current.<br />
* Adds to filtering communications.<br />
* Maintains email list.<br />
<br />
==Project Mangers==<br />
These are responsible getting the job done, having robots at competitions, and managing a workshop series. Replacements are nominated by the current leader and then voted on by the specific team.<br />
* '''FIRST'''<br />
* '''BattleBots'''<br />
* IGVC<br />
* RoboCup<br />
* '''TE Sessions'''<br />
<br />
Bold denotes vacancies that must be filled.<br />
<br />
==Non-Elected Positions==<br />
===IT Coordinator===<br />
This person manages our server and computers. They need to be skilled in linux CLI and windows implementation. Any one interested will need to talk with the current IT coordinator and officers.</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8867Elections Procedure2010-03-25T00:27:42Z<p>Stefan: /* Secretary */</p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed as well as a few responsibilities.<br />
<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
* Works with PR Chair to plan outreach events.<br />
<br />
===Treasurer===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This position will at some point mean driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
* Gets our name out.<br />
<br />
===Secretary (Vacant)===<br />
* Manages club records.<br />
* Works with PR Chair on external image.<br />
* Helps keep site current.<br />
* Adds to filtering communications.<br />
* Maintains email list.<br />
<br />
==Project Mangers==<br />
These are responsible getting the job done, having robots at competitions, and managing a workshop series. Replacements are nominated by the current leader and then voted on by the specific team.<br />
* '''FIRST'''<br />
* '''BattleBots'''<br />
* IGVC<br />
* RoboCup<br />
* '''TE Sessions'''<br />
<br />
Bold denotes vacancies that must be filled.<br />
<br />
==Non-Elected Positions==<br />
===IT Coordinator===<br />
This person manages our server and computers. They need to be skilled in linux CLI and windows implementation. Any one interested will need to talk with the current IT coordinator and officers.</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8866Elections Procedure2010-03-25T00:27:13Z<p>Stefan: /* Project Mangers */</p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed as well as a few responsibilities.<br />
<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
* Works with PR Chair to plan outreach events.<br />
<br />
===Treasurer===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This position will at some point mean driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
* Gets our name out.<br />
<br />
===Secretary===<br />
* Manages club records.<br />
* Works with PR Chair on external image.<br />
* Helps keep site current.<br />
* Adds to filtering communications.<br />
* Maintains email list.<br />
<br />
==Project Mangers==<br />
These are responsible getting the job done, having robots at competitions, and managing a workshop series. Replacements are nominated by the current leader and then voted on by the specific team.<br />
* '''FIRST'''<br />
* '''BattleBots'''<br />
* IGVC<br />
* RoboCup<br />
* '''TE Sessions'''<br />
<br />
Bold denotes vacancies that must be filled.<br />
<br />
==Non-Elected Positions==<br />
===IT Coordinator===<br />
This person manages our server and computers. They need to be skilled in linux CLI and windows implementation. Any one interested will need to talk with the current IT coordinator and officers.</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8865Elections Procedure2010-03-25T00:25:30Z<p>Stefan: </p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed as well as a few responsibilities.<br />
<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
* Works with PR Chair to plan outreach events.<br />
<br />
===Treasurer===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This position will at some point mean driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
* Gets our name out.<br />
<br />
===Secretary===<br />
* Manages club records.<br />
* Works with PR Chair on external image.<br />
* Helps keep site current.<br />
* Adds to filtering communications.<br />
* Maintains email list.<br />
<br />
==Project Mangers==<br />
These are responsible getting the job done, having robots at competitions, and managing a workshop series.<br />
* FIRST<br />
* BattleBots<br />
* IGVC<br />
* RoboCup<br />
* ''TE Sessions''<br />
<br />
==Non-Elected Positions==<br />
===IT Coordinator===<br />
This person manages our server and computers. They need to be skilled in linux CLI and windows implementation. Any one interested will need to talk with the current IT coordinator and officers.</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8864Elections Procedure2010-03-25T00:16:10Z<p>Stefan: </p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed as well as a few responsibilities.<br />
<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
* Works with PR Chair to plan outreach events.<br />
<br />
===Treasurer===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This position will at some point mean driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
* Gets our name out.<br />
<br />
===Secretary===<br />
* Manages club records.<br />
* Works with PR Chair on external image.<br />
* Helps keep site current.<br />
* Adds to filtering communications.<br />
* Maintains email list.<br />
<br />
==Non-Elected Positions==<br />
===IT Coordinator===<br />
This person manages our server and computers. They need to be skilled in linux CLI and windows implementation. Any one interested will need to talk with the current IT coordinator and officers.</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8863Elections Procedure2010-03-25T00:11:39Z<p>Stefan: /* Officers */</p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed as well as a few responsibilities.<br />
<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
<br />
===Treasurer===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This position will at some point mean driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
* Gets our name out.<br />
<br />
===Secretary===<br />
* Manages club records.<br />
* Works with PR Chair on external image.<br />
* Helps keep site current.<br />
* Adds to filtering communications.</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8862Elections Procedure2010-03-25T00:08:00Z<p>Stefan: /* Officers */</p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed.<br />
===President===<br />
* Keeps teams on track and monitors progress.<br />
* Works with staff and faculty from ME, ECE and CoC to coordinate on campus support.<br />
* Works with sponsors and handles proposals.<br />
* Picks up the slack as needed.<br />
* Works with other SCC teams on issues.<br />
<br />
===Vice-President===<br />
* Works with president to get support.<br />
* Takes care of the shop.<br />
* Improve & implement member training. <br />
<br />
===Treasurer===<br />
Has to get things bought on time and moved to the shop. Also monitors the accounts and keeps track of expenses. Keeps spending inline and works with president and project managers on purchase planning. This will mean skipping class and driving down to McMaster-Carr, MSC, or another supplier to pick up items.<br />
<br />
===Public Relations Chair===<br />
* Responsible for keeping promotional materials current and keeping them stocked.<br />
* Manages and works with the president for sponsor relations.<br />
* Posts to the website about events and finds ways to publicize them on campus.<br />
* Member recruitment.<br />
* Helps to organize events.<br />
<br />
===Secretary===<br />
*</div>Stefanhttps://wiki.robojackets.org/index.php?title=Elections_Procedure&diff=8861Elections Procedure2010-03-24T23:52:33Z<p>Stefan: Created page with 'Each year elections are held for officers. This takes place late spring. This takes two meetings. ==Nominations== To be eligible for a position a person must be nominated, secon...'</p>
<hr />
<div>Each year elections are held for officers. This takes place late spring. This takes two meetings.<br />
<br />
==Nominations==<br />
To be eligible for a position a person must be nominated, seconded, and then accept their nomination. Positions do not drop down.<br />
<br />
==Elections==<br />
These will take place at an additional meeting. Only student members can vote and to be a member you must have paid dues for the semester.<br />
<br />
==Officers==<br />
These positions are elected each year. Below the roles of each are listed.<br />
===President===<br />
===Vice-President===<br />
===Treasurer===<br />
===Public Relations Chair===<br />
Responsible for keeping promotional materials current and keeping them stocked. <br />
===Secretary===</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-Dribbler&diff=8726RC09-Dribbler2010-02-09T05:47:31Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], the dribbler provides back spin on the golf ball and allows the robot to steal the ball from opponents and move with it. This unit also hold the ball sensor LED's.<br />
<br />
[[Image:RC2009DribblerRender.jpg|thumb|right|2009 RoboJackets RoboCup Dribbler]]<br />
<br />
==Testing==<br />
===Dribbler Bar Type===<br />
The current plan for the 2009 Dribbler is to have it be segmented. Segmenting creates two sections of dribbler with a gap in between. Theoretically, this allows for more ball control. The Mexican team used this set up in 2008 ([http://www.robojackets.org/gallery/v/archive/RoboCup/2008/world/P1090014.JPG.html see here]). The gap in between is going to be between a quarter to a third of the length of the dribbler.<br />
===Performance Assessment===<br />
To measure last years performance and game play. This will be determined by receiving a kick and grabbing a stationary ball all under computer control. These results will be used as a benchmark to our new Dribbler model.<br />
===Pouring===<br />
We might want to look into pouring a mold of silicon rubber for the Dribbler assembly. This will be easier to put the rubber on the shaft. We don't know how well this will work, but we should do tests to see its effectiveness.<br />
====Candidates====<br />
# 75115A65 McMaster-Carr ($17.89)<br />
====Obstacles====<br />
# Make an outer mold.<br />
# Make inner mold/shaft.<br />
# Develop out gassing technique for pour.<br />
<br />
==Parts & Components==<br />
===Motors===<br />
====Dribbler Motor====<br />
:Vendor - Maxon<br />
:Part No. - 266521 (with attached gear head 118184 5.4 gear reduction)<br />
:Cost - $146.20 each<br />
:Notes <br />
:: [http://test.maxonmotor.com/docsx/Download/catalog_2007/Pdf/07_154_e.pdf Motor Data Sheet]<br />
:: [http://test.maxonmotor.com/docsx/Download/catalog_2007/Pdf/07_215_e.pdf Gearhead Data Sheet]<br />
<br />
===Gears & Bearings===<br />
====Motor Gear (Supplier A)====<br />
:Vendor - WM Berg<br />
:Part No. - PFS80-46<br />
:Description - Module 0.5, 34 Teeth, 20° Pressure Angle, Stainless Steel Gear with hub set screw, 3mm bore, 23mm PD<br />
:Cost - $20.41<br />
:Drawing - [http://www.wmberg.com/catalog/catpage.aspx?url=pdf/M05B082.pdf Motor Gear Spec Sheet]<br />
<br />
====Motor Gear (Supplier B)====<br />
:Vendor - SDP/SI<br />
:Part No. - S10T05M046S0303<br />
:Description - Module 0.5, 34 Teeth, 20° Pressure Angle, Stainless Steel Gear with hub set screw, 3mm bore, 23mm PD<br />
:Cost - $13.96<br />
<br />
====Output Gear (Supplier A)====<br />
:Vendor - WM Berg<br />
:Part No. - PFS80-26<br />
:Description - Module 0.5, 20 Teeth, 20° Pressure Angle, Stainless Steel Gear with set screw, 3mm bore, 13mm PD<br />
:Cost - $17.42<br />
:Drawing - [http://www.wmberg.com/catalog/catpage.aspx?url=pdf/M05B082.pdf Dribbler Gear Spec Sheet]<br />
<br />
====Output Gear (Supplier B)====<br />
:Vendor - SDP/SI<br />
:Part No. - S10T05M026S0303<br />
:Description - Module 0.5, 20 Teeth, 20° Pressure Angle, Stainless Steel Gear with set screw, 3mm bore, 13mm PD<br />
:Cost - $11.52<br />
<br />
====Bearing (1/8" Shaft)====<br />
:Vendor - Grainger<br />
:Part No. - 1ZEH7<br />
:Cost - $7.16 Each<br />
:Description - Miniature Ball Bearing, Open, Flanged, Bore Dia 0.1250 In, Outside Dia 0.2500 In, Width 0.0937 In, Flange Dia 0.2960 In, Flange Thickness 0.0230 In, ABEC Level 3<br />
:Info - [http://www.grainger.com/Grainger/items/1ZEH7 Web Link]<br />
<br />
===Stock===<br />
====RTV====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 75115A65<br />
:Description - Loctite Gray Silicone Gasket Maker Number 18718, 2.36 Ounce Tube<br />
:Cost - $17.89<br />
<br />
====Shaft====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8974K25<br />
:Description - Multipurpose Aluminum (Alloy 6061) 7/16" Diameter X 6' Length<br />
:Cost - $13.51<br />
<br />
===Fasteners===<br />
====1st Stand off====<br />
:Vendor - Digi-Key<br />
:Part No. - 4856K-ND<br />
:Description - STANDOFF HEX 6-32THR ALUM 2"<br />
:Cost - $0.6775 each (must buy in packs of 100)<br />
<br />
====1/4" Hex Stand off====<br />
:Vendor - Digi-Key<br />
:Part No. - 2214K-ND<br />
:Description - STANDOFF HEX 6-32THR ALUM 2"<br />
:Cost - $1.225 each (must buy in packs of 10)<br />
<br />
====6-32 x 5/8 Low Head Socket Cap Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92220A144<br />
:Description - Alloy Steel Low Head Socket Cap Screw 6-32 Thread, 5/8" Length<br />
:Cost - $9.63 (pkg 25)<br />
<br />
==Action Log==<br />
# 10/12/2008 - Segmented dribbler prototype design completed.<br />
# 10/16/2008 - Acquisition of silicone gasket sealer to test in mold.<br />
# 11/02/2008 - The spare dribbler from 08 was modified to be a segmented.<br />
#: Note - The rubber as damaged some while on the lathe. Patched was tested with gasket sealer.<br />
# 11/09/2008 - Impact tester was modified to allow for testing of receiving a pass.<br />
# 03/17/2009 - Housing preliminary sizing completed.<br />
# 03/18/2009 - Gearing Reselected.<br />
# 03/19/2009 - Preliminary design completed.<br />
# 03/20/2009 - Full initial design completed and fits with out interference.<br />
# 03/22/2009 - Fabrication touch ups added.<br />
# 04/05/2009 - More fabrication fixes added. (mounting hole placement)<br />
# 04/13/2009 - Dribbler roller suppler found on mfg.com.<br />
# 05/15/2009 - Dribbler rollers arrive.<br />
# 07/18/2009 - Dribbler side plates CAM'd.<br />
# 12/29/2009 - Dribbler machined and assembled.<br />
# 02/07/2010 - All parts of dribbler assembled and tested. Performance is acceptable will retest with chipper.<br />
<br />
[[Category: RoboCup Mechanical]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-KickerChipper&diff=8725RC09-KickerChipper2010-02-09T05:45:52Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], the kicker provides passing capabilities to the robots. It is part of the chipper / kicker assembly.<br />
[[Image:RC2009ChipperKickerRender.jpg|thumb|right|2009 RoboJackets RoboCup Kicker & Chipperl]]<br />
<br />
<br />
==Related Pages==<br />
* [[RC09KickerElectronics | Kicker Electronics]]<br />
<br />
==Parts & Components==<br />
Amounts are based on per robot. Materials are in sizes for prototyping not lowest cost per amount.<br />
<br />
===Stock===<br />
=====Brass Solenoid Core Tube=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8859K34<br />
:Cost - $11.34 / pack of 3<br />
:Description - Alloy 260 Miniature Brass Shapes Round Tube, 17/32" OD, 1' Length<br />
<br />
=====Inner Rod - Possible Candidate 1=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8909K761<br />
:Cost - $6.48<br />
:Description - Cast Gray Iron Rod 5/8" Diameter, 1' Length<br />
<br />
=====Inner Rod - Possible Candidate 2=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8909K761<br />
:Cost - $5.17<br />
:Description - O1 Tool Steel Rod 5/8" Diameter, 1' Length<br />
<br />
<br />
<br />
<br />
NOTE: 2.4in long by .247in tall by .302in deep<br />
7075 Grade, #8 32threads/in(8-32)<br />
<br />
==Action Log==<br />
# 10/12/2008 - Solenoid inner core diameter for prototype selected.<br />
# 03/04/2009 - Fabrication issues with quality control have been encountered in winding the solenoid.<br />
# 03/13/2009 - Decision has been made to purchase more of last years solenoids and attempt in house modifications.<br />
# 03/22/2009 - Initial concept completed.<br />
# 04/04/2009 - Resizing adjustments made.<br />
# 04/12/2009 - Kicker rev1 design completed.<br />
# 10/25/2009 - First fully machineable chipper design completed. (rev8)<br />
# 01/31/2010 - Prototype kicker and chipper OTS solenoids re selected and designs updated.<br />
# 01/31/2010 - Hardware testing of new electrical mockup shows estimated speeds of 12 m/s with 2008 solenoids.<br />
# 02/02/2010 - New solenoids ordered.<br />
# 02/07/2010 - Chipper & Kicker assemblies updated.<br />
<br />
[[Category: RoboCup Mechanical]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-DriveMotorFab&diff=8718RC09-DriveMotorFab2010-02-04T23:46:33Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]] Drive Modules we were required to modify the drive motors to accommodate our custom pinion shaft. This page holds information on that process and the jigs and fixtures we made to complete that.<br />
<br />
[[Image:RC2009DriveMotorFabRender.jpg|thumb|right|A development rendering of the 2009 Drive Motor Assembly Procedure]]<br />
<br />
==Parts & Components==<br />
===Parts to be assembled===<br />
====Drive Motor====<br />
<br />
====Custom Pinion Shaft====<br />
<br />
===Stock===<br />
====Al Plate 1"====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8975K313<br />
:Cost - $21.56<br />
:Description - Multipurpose Aluminum (Alloy 6061) 1" Thick X 3" Width X 1' Length<br />
<br />
====Al Plate 1/8"====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 89015K18<br />
:Cost - $26.06<br />
:Description - Multipurpose Aluminum (Alloy 6061) .125" Thick, 12" X 12"<br />
<br />
====Steel Rod 1/2" Dia====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 5227T26<br />
:Cost - $18.05<br />
:Description - 12L14 Carbon Steel Tight-Tolerance Rod 1/2" Diameter, 6' Length<br />
<br />
====Al Plate 0.020"====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8973K82<br />
:Cost - $3.86<br />
:Description - Improved-Strength Basic Aluminum (Alloy 3003) .020" Thick, 12" X 12"<br />
<br />
===Fasteners===<br />
====M3 x 6 Metric Flat Head Socket Cap Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 91294A126<br />
:Cost - $6.76 (pk 100)<br />
:Description - Metric Flat Head Socket Cap Screw Class 10.9 Stl, M3 Size, 6mm Length, .50mm Pitch (Needs 90 deg countersink)<br />
<br />
==Process==<br />
====Disassembly====<br />
<br />
====Assembly====<br />
<br />
==Action Log==<br />
# 04/01/2009 - A spare drive motor from 2008 fleet was successfully disassembled and reassembled.<br />
# 04/02/2009 - Design of fixture for reassembling drive motors completed.<br />
# 04/05/2009 - Shafts upgraded. Material list added to wiki.<br />
# 11/05/2009 - Material trimmed and device made to fit on small press. Allows for possible reassembly at competition.<br />
# 01/19/2010 - All parts fabricated.<br />
# 01/26/2010 - Block remade and interference fit still not correct. Situation corrected with gasket sealer.<br />
# 01/29/2010 - Gasket sealer fix verified.</div>Stefanhttps://wiki.robojackets.org/index.php?title=RoboCupMechanical&diff=8716RoboCupMechanical2010-02-04T23:29:07Z<p>Stefan: /* Drivetrain */</p>
<hr />
<div>This page houses the current [[RoboCup]] Mechanical efforts. The 2008 efforts can be found [[RoboCupMechanical2008 | here]]. All development work will be done in Autodesk Inventor 2009. How to use Inventor and get it can be found on the [[How to Guide Inventor | Inventor How to Guide]]. Inventor is also available on our CAD Machines in Tin and in the ECS Lab in the French building.<br />
<br />
[[Image:RC2009RobotRender.jpg|thumb|right|A development rendering of a 2009 RoboCup robot]]<br />
<br />
==Meetings & Development Time Line==<br />
===Current Work Schedule===<br />
:Sundays, 2pm - 6pm<br />
<br />
===Development Schedule & Tasks===<br />
This is just a list of our most pressing objectives. For a full listing see [[RoboCupMechanicalDev|RoboCup Mechanical Dev]].<br />
# Review Drive base and Chipper / Kicker Assembly.<br />
# Machine<br />
#: Omni Bodies<br />
#: Drive Plates<br />
#: Base Plates<br />
#: Dribbler Plates<br />
# Solenoid development<br />
<br />
==Systems==<br />
===Overall===<br />
: [[RC09-Components|System Components and Bill of Materials]]<br />
===Drivetrain===<br />
: [[RC09-Omni|Omni Wheels]]<br />
: [[RC09-DriveModule|Drive Module]]<br />
: [[RC09-DriveMotor|Drive Motor]]<br />
: ''Personnel''<br />
:# [[User:Stefan|Stefan]] (Drive Modules, Mechanical Lead)<br />
:# [[User:ArjunM|Arjun]] (Omni Wheels)<br />
<br />
===Integration===<br />
: [[RC09-Shell|Shell]]<br />
: [[RC09-Chassis|Chassis]]<br />
<br />
===Ball Control===<br />
: [[RC09-Dribbler|Dribbler]]<br />
: [[RC09-KickerChipper|Kicker & Chipper]]<br />
: ''Personnel''<br />
:# [[User:StoianB|Stu]] (Kicker & Chipper)<br />
:# [[User:ArjunM|Arjun]] (Dribbler)<br />
<br />
===Testing===<br />
: [[RC09-METestRig|Test Rig]]<br />
: [[RC09-Slope|Slope]]<br />
: [[RC09-Impact Test|Impact Test]]<br />
: [[RC09-Carpet|Carpet]]<br />
<br />
===Fabrication===<br />
: [[RC09-DriveMotorFab|Drive Motor Fixture]]<br />
<br />
==Competition Specifications==<br />
* Field<br />
*: Area 6.6m x 4.7m<br />
*: Material - Locally available carpet<br />
* Robot<br />
*: Maximum Diameter - 180mm<br />
*: Maximum Height - 150mm (measured from solid surface)<br />
*: Maximum Weight - 1.8 kg<br />
* Golf Ball<br />
*: Max Speed - 10 m/s<br />
*: Diameter - 43 mm<br />
*: Mass - 46 grams<br />
*: Material - DuPont Surlyn Ionomer [http://www2.dupont.com/Surlyn/en_US/ Dupont's Surlyn Page]<br />
*: No more than 20% of the ball's area may be occupied by / within the robot. See [[:Image:Ball_sketch.PNG|this illustration]].<br />
* More info found in rules [http://small-size.informatik.uni-bremen.de/ RoboCup SSL Website]<br />
<br />
==Testing==<br />
[[RoboCup Testing | RoboCup Testing]]<br />
<br />
==Useful Links==<br />
*[http://www.cis.cornell.edu/boom/2005/ProjectArchive/robocup/ Cornell Documents] (Look at 2003)<br />
*[ftp://ftp.itam.mx/pub/alfredo/PAPERS/SotoWeitzenfeld80LARS2006.pdf Eagle Knights Dribbler Testing]<br />
*[http://www.sdp-si.com/D220/D220cat.htm#T35 Mechanical Engineering Tips]<br />
*[http://www.linuxcnc.org/handbook/gcode/g-code.html G-Code Tutorial]<br />
*[http://robojackets.org/~circuitben/ Overhead camera footage from Robocup 2007 Championship Match]<br />
*[http://www.drgears.com/gearterms/GearTermIndex.htm Dr. Gear - Gear Encyclopedia]<br />
*[http://shtylman.com/robocup_resource/mechanical/CornellRoboCupMechanicalDocumentation2004.doc Cornell 2004 Mechanical Documentation]<br />
*[http://pergatory.mit.edu/2.007/Resources/index.html#manufacturing MIT Design Handbook Index] (VERY GOOD)<br />
*[http://thomasnet.com Global supplier and CAD drawing database]<br />
<br />
[[Category: RoboCup]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-KickerChipper&diff=8715RC09-KickerChipper2010-02-04T23:27:53Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], the kicker provides passing capabilities to the robots. It is part of the chipper / kicker assembly.<br />
[[Image:RC2009ChipperKickerRender.jpg|thumb|right|2009 RoboJackets RoboCup Kicker & Chipperl]]<br />
<br />
<br />
==Related Pages==<br />
* [[RC09KickerElectronics | Kicker Electronics]]<br />
<br />
==Parts & Components==<br />
Amounts are based on per robot. Materials are in sizes for prototyping not lowest cost per amount.<br />
<br />
===Stock===<br />
=====Brass Solenoid Core Tube=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8859K34<br />
:Cost - $11.34 / pack of 3<br />
:Description - Alloy 260 Miniature Brass Shapes Round Tube, 17/32" OD, 1' Length<br />
<br />
=====Inner Rod - Possible Candidate 1=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8909K761<br />
:Cost - $6.48<br />
:Description - Cast Gray Iron Rod 5/8" Diameter, 1' Length<br />
<br />
=====Inner Rod - Possible Candidate 2=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8909K761<br />
:Cost - $5.17<br />
:Description - O1 Tool Steel Rod 5/8" Diameter, 1' Length<br />
<br />
<br />
<br />
<br />
NOTE: 2.4in long by .247in tall by .302in deep<br />
7075 Grade, #8 32threads/in(8-32)<br />
<br />
==Action Log==<br />
# 10/12/2008 - Solenoid inner core diameter for prototype selected.<br />
# 03/04/2009 - Fabrication issues with quality control have been encountered in winding the solenoid.<br />
# 03/13/2009 - Decision has been made to purchase more of last years solenoids and attempt in house modifications.<br />
# 03/22/2009 - Initial concept completed.<br />
# 04/04/2009 - Resizing adjustments made.<br />
# 04/12/2009 - Kicker rev1 design completed.<br />
# 10/25/2009 - First fully machineable chipper design completed. (rev8)<br />
# 01/31/2010 - Prototype kicker and chipper OTS solenoids re selected and designs updated.<br />
# 01/31/2010 - Hardware testing of new electrical mockup shows estimated speeds of 12 m/s with 2008 solenoids.<br />
<br />
[[Category: RoboCup Mechanical]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-Omni&diff=8714RC09-Omni2010-02-04T23:25:51Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], the Omni Wheels allow the robots to move in any direction at anytime.<br />
[[Image:RC2009OmniWheelRender.jpg|thumb|right|2009 RoboJackets RoboCup Omni Wheel]]<br />
<br />
==Drawings==<br />
<br />
==Materials==<br />
<br />
==Assembly Structure==<br />
====Parts List====<br />
<br />
====Instructions====<br />
<br />
==Parts & Components==<br />
Amounts are based on per robot. Materials are in sizes for prototyping not lowest cost per robot volume pricing if available is in parenthesis.<br />
<br />
===Stock===<br />
=====Plate - Wheel Plate=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8885K13<br />
:Cost - $21.63<br />
:Description - Alloy 7075 Aluminum Sheet .063" Thick, 12" X 12"<br />
<br />
=====Plate - Wheel Body=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 9246K23<br />
:Cost - $28.51<br />
:Description - Multipurpose Aluminum (Alloy 6061) 3/8" Thick, 12" X 12"<br />
<br />
=====Shaft - Rollers=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 9063K243<br />
:Cost - $17.48<br />
:Description - Alloy 7075 Aluminum Precision Ground Rod 1/8" Diameter, 3' Length<br />
:''Note: Usually ships within 2 weeks.''<br />
<br />
===Fasteners===<br />
=====6-32 Low Head Socket Cap Screw=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92220A141<br />
:Cost - $7.42 (packs of 25)<br />
:Description - Alloy Steel Low Head Socket Cap Screw 6-32 Thread, 1/4" Length<br />
<br />
=====3/16" Dowel Pin=====<br />
:Vendor - MSC<br />
:Part No. - 88231758<br />
:Cost - $43.08 (per 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 3/16 Overall Length: 1/4 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
=====1/16" Dowel Pin=====<br />
:Vendor - MSC<br />
:Part No. - 88231196<br />
:Cost - $19.83 (per 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/16 Overall Length: 1/4 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
===Other===<br />
=====O-Ring=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 94115K012<br />
:Cost - $2.87 (Pks of 100)<br />
:Quantity -<br />
:Description - Neoprene O-Ring AS568A Dash Number 012<br />
<br />
==Fabrication==<br />
=====Omni Plates=====<br />
: Can be done in house on Haas for prototype.<br />
: Fleet should be water jetted.<br />
<br />
=====Omni Bodies=====<br />
: In House on Haas VF-2<br />
<br />
=====Omni Rollers=====<br />
: MFG.com - CNC Lathe Required<br />
<br />
==Cost Estimates==<br />
<br />
==Action Log==<br />
# 10/19/2008 - Initial revised roller design completed.<br />
# 11/02/2008 - Added new groove style for new rollers.<br />
# 11/09/2008 - Refined roller design.<br />
# 12/30/2008 - Resized to match internal gear dimensions.<br />
# 01/13/2009 - Added fillets.<br />
# 02/01/2009 - Drawing for rollers produced and ready to be posted for quote.<br />
# 02/22/2009 - Design for prototype completed. <br />
# 03/15/2009 - Rollers posted to mfg.com for quote.<br />
# 03/17/2009 - Design revised. Internal gear added to omni body.<br />
# 03/25/2009 - Supplier for rollers selected.<br />
# 04/08/2009 - All 400 Rollers arrive for omni wheels.<br />
# 05/05/2009 - 1/2 of rollers are assembled.<br />
# 07/18/2009 - Omni bodies CAM'd.<br />
# 01/26/2010 - Omni plates for prototype water jetted.<br />
# 02/03/2010 - Tooling required to make omni bodies arrives.<br />
<br />
[[Category: RoboCup Mechanical]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-Omni&diff=8713RC09-Omni2010-02-04T23:25:06Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], the Omni Wheels allow the robots to move in any direction at anytime.<br />
[[Image:RC2009OmniWheelRender.jpg|thumb|right|2009 RoboJackets RoboCup Omni Wheel]]<br />
<br />
==Drawings==<br />
<br />
==Materials==<br />
<br />
==Assembly Structure==<br />
====Parts List====<br />
<br />
====Instructions====<br />
<br />
==Parts & Components==<br />
Amounts are based on per robot. Materials are in sizes for prototyping not lowest cost per robot volume pricing if available is in parenthesis.<br />
<br />
===Stock===<br />
=====Plate - Wheel Plate=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8885K13<br />
:Cost - $21.63<br />
:Description - Alloy 7075 Aluminum Sheet .063" Thick, 12" X 12"<br />
<br />
=====Plate - Wheel Body=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 9246K23<br />
:Cost - $28.51<br />
:Description - Multipurpose Aluminum (Alloy 6061) 3/8" Thick, 12" X 12"<br />
<br />
=====Shaft - Rollers=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 9063K243<br />
:Cost - $17.48<br />
:Description - Alloy 7075 Aluminum Precision Ground Rod 1/8" Diameter, 3' Length<br />
:''Note: Usually ships within 2 weeks.''<br />
<br />
===Fasteners===<br />
=====6-32 Low Head Socket Cap Screw=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92220A141<br />
:Cost - $7.42 (packs of 25)<br />
:Description - Alloy Steel Low Head Socket Cap Screw 6-32 Thread, 1/4" Length<br />
<br />
=====3/16" Dowel Pin=====<br />
:Vendor - MSC<br />
:Part No. - 88231758<br />
:Cost - $43.08 (per 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 3/16 Overall Length: 1/4 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
=====1/16" Dowel Pin=====<br />
:Vendor - MSC<br />
:Part No. - 88231196<br />
:Cost - $19.83 (per 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/16 Overall Length: 1/4 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
===Other===<br />
=====O-Ring=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 94115K012<br />
:Cost - $2.87 (Pks of 100)<br />
:Quantity -<br />
:Description - Neoprene O-Ring AS568A Dash Number 012<br />
<br />
==Fabrication==<br />
=====Omni Plates=====<br />
: Can be done in house on Haas for prototype.<br />
: Fleet should be water jetted.<br />
<br />
=====Omni Bodies=====<br />
: In House on Haas VF-2<br />
<br />
=====Omni Rollers=====<br />
: MFG.com - CNC Lathe Required<br />
<br />
==Cost Estimates==<br />
<br />
==Action Log==<br />
# 10/19/2008 - Initial revised roller design completed.<br />
# 11/02/2008 - Added new groove style for new rollers.<br />
# 11/09/2008 - Refined roller design.<br />
# 12/30/2008 - Resized to match internal gear dimensions.<br />
# 01/13/2009 - Added fillets.<br />
# 02/01/2009 - Drawing for rollers produced and ready to be posted for quote.<br />
# 02/22/2009 - Design for prototype completed. <br />
# 03/15/2009 - Rollers posted to mfg.com for quote.<br />
# 03/17/2009 - Design revised. Internal gear added to omni body.<br />
# 03/25/2009 - Supplier for rollers selected.<br />
# 04/08/2009 - All 400 Rollers arrive for omni wheels.<br />
# 05/05/2009 - 1/2 of rollers are assembled.<br />
# 07/18/2009 - Omni bodies CAM'd.<br />
# 01/26/2010 - Omni plates for prototype water jetted.<br />
<br />
[[Category: RoboCup Mechanical]] [[Category: 2008]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-Omni&diff=8712RC09-Omni2010-02-04T23:24:00Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], the Omni Wheels allow the robots to move in any direction at anytime.<br />
[[Image:RC2009OmniWheelRender.jpg|thumb|right|2009 RoboJackets RoboCup Omni Wheel]]<br />
<br />
==Drawings==<br />
<br />
==Materials==<br />
<br />
==Assembly Structure==<br />
====Parts List====<br />
<br />
====Instructions====<br />
<br />
==Parts & Components==<br />
Amounts are based on per robot. Materials are in sizes for prototyping not lowest cost per robot volume pricing if available is in parenthesis.<br />
<br />
===Stock===<br />
=====Plate - Wheel Plate=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8885K13<br />
:Cost - $21.63<br />
:Description - Alloy 7075 Aluminum Sheet .063" Thick, 12" X 12"<br />
<br />
=====Plate - Wheel Body=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 9246K23<br />
:Cost - $28.51<br />
:Description - Multipurpose Aluminum (Alloy 6061) 3/8" Thick, 12" X 12"<br />
<br />
=====Shaft - Rollers=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 9063K243<br />
:Cost - $17.48<br />
:Description - Alloy 7075 Aluminum Precision Ground Rod 1/8" Diameter, 3' Length<br />
:''Note: Usually ships within 2 weeks.''<br />
<br />
===Fasteners===<br />
=====6-32 Low Head Socket Cap Screw=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92220A141<br />
:Cost - $7.42 (packs of 25)<br />
:Description - Alloy Steel Low Head Socket Cap Screw 6-32 Thread, 1/4" Length<br />
<br />
=====3/16" Dowel Pin=====<br />
:Vendor - MSC<br />
:Part No. - 88231758<br />
:Cost - $43.08 (per 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 3/16 Overall Length: 1/4 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
=====1/16" Dowel Pin=====<br />
:Vendor - MSC<br />
:Part No. - 88231196<br />
:Cost - $19.83 (per 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/16 Overall Length: 1/4 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
===Other===<br />
=====O-Ring=====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 94115K012<br />
:Cost - $2.87 (Pks of 100)<br />
:Quantity -<br />
:Description - Neoprene O-Ring AS568A Dash Number 012<br />
<br />
==Fabrication==<br />
=====Omni Plates=====<br />
: Can be done in house on Haas for prototype.<br />
: Fleet should be water jetted.<br />
<br />
=====Omni Bodies=====<br />
: In House on Haas VF-2<br />
<br />
=====Omni Rollers=====<br />
: MFG.com - CNC Lathe Required<br />
<br />
==Cost Estimates==<br />
<br />
==Action Log==<br />
# 10/19/2008 - Initial revised roller design completed.<br />
# 11/02/2008 - Added new groove style for new rollers.<br />
# 11/09/2008 - Refined roller design.<br />
# 12/30/2008 - Resized to match internal gear dimensions.<br />
# 01/13/2009 - Added fillets.<br />
# 02/01/2009 - Drawing for rollers produced and ready to be posted for quote.<br />
# 02/22/2009 - Design for prototype completed. <br />
# 03/15/2009 - Rollers posted to mfg.com for quote.<br />
# 03/17/2009 - Design revised. Internal gear added to omni body.<br />
# 03/25/2009 - Supplier for rollers selected.<br />
# 04/08/2009 - All 400 Rollers arrive for omni wheels.<br />
# 05/05/2009 - 1/2 of rollers are assembled.<br />
# 07/18/2009 - Omni bodies CAM'd.<br />
# 01/26/2010 - Omni plates water jetted.<br />
<br />
[[Category: RoboCup Mechanical]] [[Category: 2008]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-DriveModule&diff=8711RC09-DriveModule2010-02-04T23:23:06Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], Drive Modules integrate the motor, gearbox and omniwheel in to one modular assembly.<br />
[[Image:RC2009DriveModuleRender.jpg|thumb|right|2009 RoboJackets RoboCup Drive Module]]<br />
<br />
<br />
==Assembly Structure==<br />
====Parts Structure====<br />
# Inner Drive Plate<br />
# Omni Wheel<br />
# Output Axel<br />
# Spindle<br />
## Internal Gear<br />
## Bearing Plate<br />
## Wheel Attachment Plate<br />
## Hex Shaft<br />
<br />
<br />
====Parts List====<br />
# 1 - Omni Wheel (RC-2009-02-00)<br />
# 1 - Maxon Brushless Drive Motor (RC-2009-03-01)<br />
# 1 - Drive Module Plate (RC-2009-03-02)<br />
# 1 - Shaft (RC-2009-03-03)<br />
# 1 - Internal Gear (RC-2009-03-04)<br />
# 3 - 5/8" Long Hex Standoffs (RC-2009- -)<br />
# 2 - 1/4" Ball Bearings (RC-2009-03-05) (RC-2008-03-08)<br />
<br />
====Instructions====<br />
<br />
==Parts & Components==<br />
===Motors and Encoders===<br />
====Brushless Motors====<br />
:Vendor - Maxon<br />
:Part No. - 200142<br />
:Cost - $50.53(EUR)<br />
:Description - EC 45 flat Ø45 mm, brushless, 30 Watt<br />
<br />
====Encoders====<br />
:Vendor - US Digital<br />
:Part No. - E4P-360-157-D-D-T-B<br />
:Cost - $26.39 ($20.75)<br />
:Description - E4P OEM Miniature Optical Kit Encoder [http://usdigital.com/assets/drawings/471.pdf Spec]<br />
:Note - Vendor supplied 3-48 x 1/4" screws are not long enough for 0.05" plate. We have switched to transfer adhesive.<br />
<br />
===Gears & Bearings===<br />
====Motor Output Gear====<br />
:Vendor - SDP/SI<br />
:Part No. - S1VS05M016F0704<br />
:Cost - $22.06 ($18.16)<br />
:Description - Module 0.5, 16 Teeth, 20° Pressure Angle, 303 Stainless Steel Gear<br />
<br />
====Internal Gear (Standard)(Supplier A)====<br />
:Vendor - SDP/SI<br />
:Part No. - S1E62Z-072S110<br />
:Cost - $47.16 ($44.51)<br />
:Description - 72 DP, 110T, AGMA Q10, 303 STAINLESS STEEL INTERNAL GEAR<br />
<br />
====Internal Gear (Standard)(Supplier B)====<br />
:Vendor - WM BERG<br />
:Part No. - N72S2-110 <br />
:Cost - $46.25<br />
:Description - 72 DP, 110T, AGMA Q10, 303 STAINLESS STEEL INTERNAL GEAR<br />
<br />
====Internal Gear (Metric)(Supplier A)====<br />
:Vendor - SDP/SI <br />
:Part No. - S1E05ZM05S072 <br />
:Cost - $31.10 ($28.48) <br />
:Description - Module 0.5, 72 TEETH, 20° Pressure Angle, 303 Stainless Steel, INTERNAL GEAR<br />
<br />
====Internal Gear (Metric)(Supplier B)====<br />
:Vendor - <br />
:Part No. - <br />
:Cost - <br />
:Description - <br />
<br />
====Bearing (1/4" Shaft)====<br />
:Vendor - Grainger<br />
:Part No. - 1ZEJ7<br />
:Cost - $5.59 Each<br />
:Description - Miniature Ball Bearing, Open, Flanged, Bore Dia 0.2500 In, Outside Dia 0.5000 In, Width 0.1250 In, Flange Dia 0.5470 In, Flange Thickness 0.0230 In, ABEC Level 3<br />
:Info - [http://www.grainger.com/Grainger/wwg/productIndex.shtml?operator=keywordSearch&search_type=keyword&QueryString=1ZEJ7&submit.x=6&submit.y=6 Web Link]<br />
<br />
===Stock===<br />
====Al Plate 1/8"====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 89015K18<br />
:Cost - $26.06<br />
:Description - Alloy 6061 Aluminum Sheet .125" Thick, 12" X 12"<br />
<br />
====Al Plate 0.05"====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8885K18 <br />
:Cost - $35.62 Each <br />
:Description - Alloy 7075 Aluminum Sheet .050" Thick, 12" X 24"<br />
:Note - 7075 b/c we have left over from last year other wise 6061.<br />
<br />
===Fasteners===<br />
====0-80 x 1/4" Button Head====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92949A054<br />
:Cost - $9.30 (Packs of 50)<br />
:Description - 18-8 SS Button Head Socket Cap Screw 0-80 Thread, 1/4" Length<br />
<br />
====6-32 Low Head Socket Cap Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92220A141<br />
:Cost - $7.42 (Packs of 25)<br />
:Description - Alloy Steel Low Head Socket Cap Screw 6-32 Thread, 1/4" Length<br />
<br />
====6-32 Socket Cap Counter Sunk Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 91253A144<br />
:Cost - $9.91 (Packs of 100)<br />
:Description - Alloy Steel Flat Head Socket Cap Screw 6-32 Thread, 1/4" Length, Black Oxide<br />
<br />
====6-32 Button Head====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92949A143<br />
:Cost - $7.88 (Packs of 100)<br />
:Description - 18-8 SS Button Head Socket Cap Screw 6-32 Thread, 3/16" Length<br />
<br />
====6-32 3/4" Standoffs====<br />
:Vendor - Digi-Key<br />
:Part No. - 2211K-ND<br />
:Cost - $6.14 (pk 10) $55.83 (pk 100) <br />
:Description - STANDOFF HEX 6-32THR ALUM .750"<br />
<br />
====10-32 Shoulder Bolt====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 94035A531<br />
:Cost - $2.08 (each)<br />
:Description - 18-8 SS Precision Hex Socket Shoulder Screw 1/4" Shoulder Dia, 1/8" L Shoulder, 10-32 Thread<br />
<br />
====M3 x 6 Metric Flat Head Socket Cap Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 91294A126<br />
:Cost - $6.76 (pk 100)<br />
:Description - Metric Flat Head Socket Cap Screw Class 10.9 Stl, M3 Size, 6mm Length, .50mm Pitch (Needs 90 deg countersink)<br />
<br />
==== 1/16" Locating Pins====<br />
:Vendor - MSC Industrial Supply<br />
:Part No. - 88231196<br />
:Cost - $19.83 (pk 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/16 Overall Length: 1/4 Material: Stainless Steel - 416 SS Finish/Coating: Bright <br />
<br />
==== 1/8" Locating Pins====<br />
:Vendor - MSC Industrial Supply<br />
:Part No. - 88231469<br />
:Cost - $26.46 (pk 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/8 Overall Length: 3/16 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
==Fabrication==<br />
<br />
==Action Log==<br />
# 12/29/2008 - Internal gears selected.<br />
# 12/30/2008 - Initial design of gear box completed.<br />
# 01/11/2009 - Removed mass and moved to 1/8" plate for motor mounting.<br />
# 01/12/2009 - Dropped 8-32 screws to 6-32, and made treading full on hex..<br />
# 01/13/2009 - Confirmed that Maxon does offer custom shafts for motors and added current materials to wiki.<br />
# 01/25/2009 - Preliminary encoder selected.<br />
# 01/26/2009 - Initial design with a encoder completed.<br />
# 02/02/2009 - Design revised. Attachment to bottom plate enhanced and encoder fully compensated for.<br />
# 02/22/2009 - Design for prototype completed.<br />
# 03/07/2009 - Design revised. Drive modules reshaped to accommodate capacitors.<br />
# 03/16/2009 - Gear posted to mfg.com for quote.<br />
# 03/17/2009 - Design revised. Spindle removed and internal gear placed on omni body.<br />
# 03/19/2009 - Plates reshaped to allow room for dribbler components.<br />
# 03/17/2009 - RFQ for internal gears posted on mfg.com.<br />
# 03/25/2009 - Supplier for initial run of internal gears selected.<br />
# 03/26/2009 - Have moved to reversing engineering and modifying drive motors in house.<br />
# 04/01/2009 - A spare drive motor from 2008 fleet was successfully disassembled and reassembled.<br />
# 04/02/2009 - Design of fixture for reassembling drive motors completed. Info can be found on the [[RC09-DriveMotorFab | Drive Motor Fixture]] page.<br />
# 07/18/2009 - Drive plates have been CAM'd.<br />
# 07/28/2009 - Motor shaft modified to allow for better assembly.<br />
# 10/18/2009 - Encoder plate CAM'd up in waterjet software.<br />
# 11/01/2009 - Output shaft standoffs fabricated.<br />
# 12/23/2009 - Drive plates machined.<br />
# 01/26/2010 - Encoder plates water jetted.<br />
[[Category: RoboCup Mechanical]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-DriveModule&diff=8710RC09-DriveModule2010-02-04T23:22:10Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], Drive Modules integrate the motor, gearbox and omniwheel in to one modular assembly.<br />
[[Image:RC2009DriveModuleRender.jpg|thumb|right|2009 RoboJackets RoboCup Drive Module]]<br />
<br />
<br />
==Assembly Structure==<br />
====Parts Structure====<br />
# Inner Drive Plate<br />
# Omni Wheel<br />
# Output Axel<br />
# Spindle<br />
## Internal Gear<br />
## Bearing Plate<br />
## Wheel Attachment Plate<br />
## Hex Shaft<br />
<br />
<br />
====Parts List====<br />
# 1 - Omni Wheel (RC-2009-02-00)<br />
# 1 - Maxon Brushless Drive Motor (RC-2009-03-01)<br />
# 1 - Drive Module Plate (RC-2009-03-02)<br />
# 1 - Shaft (RC-2009-03-03)<br />
# 1 - Internal Gear (RC-2009-03-04)<br />
# 3 - 5/8" Long Hex Standoffs (RC-2009- -)<br />
# 2 - 1/4" Ball Bearings (RC-2009-03-05) (RC-2008-03-08)<br />
<br />
====Instructions====<br />
<br />
==Parts & Components==<br />
===Motors and Encoders===<br />
====Brushless Motors====<br />
:Vendor - Maxon<br />
:Part No. - 200142<br />
:Cost - $50.53(EUR)<br />
:Description - EC 45 flat Ø45 mm, brushless, 30 Watt<br />
<br />
====Encoders====<br />
:Vendor - US Digital<br />
:Part No. - E4P-360-157-D-D-T-B<br />
:Cost - $26.39 ($20.75)<br />
:Description - E4P OEM Miniature Optical Kit Encoder [http://usdigital.com/assets/drawings/471.pdf Spec]<br />
:Note - Vendor supplied 3-48 x 1/4" screws are not long enough for 0.05" plate. We have switched to transfer adhesive.<br />
<br />
===Gears & Bearings===<br />
====Motor Output Gear====<br />
:Vendor - SDP/SI<br />
:Part No. - S1VS05M016F0704<br />
:Cost - $22.06 ($18.16)<br />
:Description - Module 0.5, 16 Teeth, 20° Pressure Angle, 303 Stainless Steel Gear<br />
<br />
====Internal Gear (Standard)(Supplier A)====<br />
:Vendor - SDP/SI<br />
:Part No. - S1E62Z-072S110<br />
:Cost - $47.16 ($44.51)<br />
:Description - 72 DP, 110T, AGMA Q10, 303 STAINLESS STEEL INTERNAL GEAR<br />
<br />
====Internal Gear (Standard)(Supplier B)====<br />
:Vendor - WM BERG<br />
:Part No. - N72S2-110 <br />
:Cost - $46.25<br />
:Description - 72 DP, 110T, AGMA Q10, 303 STAINLESS STEEL INTERNAL GEAR<br />
<br />
====Internal Gear (Metric)(Supplier A)====<br />
:Vendor - SDP/SI <br />
:Part No. - S1E05ZM05S072 <br />
:Cost - $31.10 ($28.48) <br />
:Description - Module 0.5, 72 TEETH, 20° Pressure Angle, 303 Stainless Steel, INTERNAL GEAR<br />
<br />
====Internal Gear (Metric)(Supplier B)====<br />
:Vendor - <br />
:Part No. - <br />
:Cost - <br />
:Description - <br />
<br />
====Bearing (1/4" Shaft)====<br />
:Vendor - Grainger<br />
:Part No. - 1ZEJ7<br />
:Cost - $5.59 Each<br />
:Description - Miniature Ball Bearing, Open, Flanged, Bore Dia 0.2500 In, Outside Dia 0.5000 In, Width 0.1250 In, Flange Dia 0.5470 In, Flange Thickness 0.0230 In, ABEC Level 3<br />
:Info - [http://www.grainger.com/Grainger/wwg/productIndex.shtml?operator=keywordSearch&search_type=keyword&QueryString=1ZEJ7&submit.x=6&submit.y=6 Web Link]<br />
<br />
===Stock===<br />
====Al Plate 1/8"====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 89015K18<br />
:Cost - $26.06<br />
:Description - Alloy 6061 Aluminum Sheet .125" Thick, 12" X 12"<br />
<br />
====Al Plate 0.05"====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 8885K18 <br />
:Cost - $35.62 Each <br />
:Description - Alloy 7075 Aluminum Sheet .050" Thick, 12" X 24"<br />
:Note - 7075 b/c we have left over from last year other wise 6061.<br />
<br />
===Fasteners===<br />
====0-80 x 1/4" Button Head====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92949A054<br />
:Cost - $9.30 (Packs of 50)<br />
:Description - 18-8 SS Button Head Socket Cap Screw 0-80 Thread, 1/4" Length<br />
<br />
====6-32 Low Head Socket Cap Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92220A141<br />
:Cost - $7.42 (Packs of 25)<br />
:Description - Alloy Steel Low Head Socket Cap Screw 6-32 Thread, 1/4" Length<br />
<br />
====6-32 Socket Cap Counter Sunk Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 91253A144<br />
:Cost - $9.91 (Packs of 100)<br />
:Description - Alloy Steel Flat Head Socket Cap Screw 6-32 Thread, 1/4" Length, Black Oxide<br />
<br />
====6-32 Button Head====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92949A143<br />
:Cost - $7.88 (Packs of 100)<br />
:Description - 18-8 SS Button Head Socket Cap Screw 6-32 Thread, 3/16" Length<br />
<br />
====6-32 3/4" Standoffs====<br />
:Vendor - Digi-Key<br />
:Part No. - 2211K-ND<br />
:Cost - $6.14 (pk 10) $55.83 (pk 100) <br />
:Description - STANDOFF HEX 6-32THR ALUM .750"<br />
<br />
====10-32 Shoulder Bolt====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 94035A531<br />
:Cost - $2.08 (each)<br />
:Description - 18-8 SS Precision Hex Socket Shoulder Screw 1/4" Shoulder Dia, 1/8" L Shoulder, 10-32 Thread<br />
<br />
====M3 x 6 Metric Flat Head Socket Cap Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 91294A126<br />
:Cost - $6.76 (pk 100)<br />
:Description - Metric Flat Head Socket Cap Screw Class 10.9 Stl, M3 Size, 6mm Length, .50mm Pitch (Needs 90 deg countersink)<br />
<br />
==== 1/16" Locating Pins====<br />
:Vendor - MSC Industrial Supply<br />
:Part No. - 88231196<br />
:Cost - $19.83 (pk 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/16 Overall Length: 1/4 Material: Stainless Steel - 416 SS Finish/Coating: Bright <br />
<br />
==== 1/8" Locating Pins====<br />
:Vendor - MSC Industrial Supply<br />
:Part No. - 88231469<br />
:Cost - $26.46 (pk 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/8 Overall Length: 3/16 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
==Fabrication==<br />
<br />
==Action Log==<br />
# 12/29/2008 - Internal gears selected.<br />
# 12/30/2008 - Initial design of gear box completed.<br />
# 01/11/2009 - Removed mass and moved to 1/8" plate for motor mounting.<br />
# 01/12/2009 - Dropped 8-32 screws to 6-32, and made treading full on hex..<br />
# 01/13/2009 - Confirmed that Maxon does offer custom shafts for motors and added current materials to wiki.<br />
# 01/25/2009 - Preliminary encoder selected.<br />
# 01/26/2009 - Initial design with a encoder completed.<br />
# 02/02/2009 - Design revised. Attachment to bottom plate enhanced and encoder fully compensated for.<br />
# 02/22/2009 - Design for prototype completed.<br />
# 03/07/2009 - Design revised. Drive modules reshaped to accommodate capacitors.<br />
# 03/16/2009 - Gear posted to mfg.com for quote.<br />
# 03/17/2009 - Design revised. Spindle removed and internal gear placed on omni body.<br />
# 03/19/2009 - Plates reshaped to allow room for dribbler components.<br />
# 03/17/2009 - RFQ for internal gears posted on mfg.com.<br />
# 03/25/2009 - Supplier for initial run of internal gears selected.<br />
# 03/26/2009 - Have moved to reversing engineering and modifying drive motors in house.<br />
# 04/01/2009 - A spare drive motor from 2008 fleet was successfully disassembled and reassembled.<br />
# 04/02/2009 - Design of fixture for reassembling drive motors completed. Info can be found on the [[RC09-DriveMotorFab | Drive Motor Fixture]] page.<br />
# 07/18/2009 - Drive plates have been CAM'd.<br />
# 07/28/2009 - Motor shaft modified to allow for better assembly.<br />
# 10/18/2009 - Encoder plate CAM'd up in waterjet software.<br />
# 11/01/2009 - Output shaft standoffs fabricated.<br />
# 12/23/2009 - Drive plates machined.<br />
<br />
[[Category: RoboCup Mechanical]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-Chassis&diff=8709RC09-Chassis2010-02-04T23:20:54Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], the chassis holds the various system together and is primarily composed of a top and bottom plate.<br />
[[Image:RC2009RobotRender.jpg|thumb|right|2009 RoboJackets RoboCup Robot]]<br />
<br />
==Drawings==<br />
<br />
==Materials==<br />
<br />
==Assembly Structure==<br />
====Parts List====<br />
<br />
<br />
====Instructions====<br />
<br />
==Non-Mechanical Components==<br />
====Antenna Board====<br />
====Kicker Board====<br />
====Li-Po Battery====<br />
<br />
==Parts & Components==<br />
Amounts are based on per robot. Materials are in sizes for prototyping not lowest cost per robot volume pricing if available is in parenthesis.<br />
<br />
===Stock===<br />
=====Plate - Bottom=====<br />
:Vendor - <br />
:Part No. - <br />
:Cost - <br />
:Description -<br />
<br />
<br />
<br />
===Fasteners===<br />
<br />
====6-32 Low Head Socket Cap Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92220A141<br />
:Cost - $7.42 (Packs of 25)<br />
:Description - Alloy Steel Low Head Socket Cap Screw 6-32 Thread, 1/4" Length<br />
<br />
==== 1/8" Locating Pins====<br />
:Vendor - MSC Industrial Supply<br />
:Part No. - 88231469<br />
:Cost - $26.46 (pk 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/8 Overall Length: 3/16 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
===Other===<br />
<br />
<br />
<br />
<br />
==Cost Estimates==<br />
<br />
==Action Log==<br />
# 02/08/2008 - Initial base with 4 modules designed.<br />
# 02/18/2009 - Preliminary solenoid added.<br />
# 03/17/2009 - Batteries and Caps now fit.<br />
# 03/19/2009 - Everything all assemblies now fit with out clipping.<br />
# 03/20/2009 - Fillets added to base plate to keep it with in dimensions.<br />
# 03/22/2009 - Updated chipper & kicker assembly added.<br />
# 04/12/2009 - Base plate modified to allow attachment of chipper & kicker assembly.<br />
# 07/18/2009 - Bottom plate CAM'd.<br />
# 12/28/2009 - Bottom plate machined.<br />
# 01/31/2010 - Electrical board standoffs and new caps are selected. Designs updated. <br />
<br />
[[Category: RoboCup Mechanical]] [[Category: 2009]]</div>Stefanhttps://wiki.robojackets.org/index.php?title=RC09-Chassis&diff=8708RC09-Chassis2010-02-04T23:19:50Z<p>Stefan: /* Action Log */</p>
<hr />
<div>As part of the [[RoboCupMechanical|RoboCup 2009 Mechanical]], the chassis holds the various system together and is primarily composed of a top and bottom plate.<br />
[[Image:RC2009RobotRender.jpg|thumb|right|2009 RoboJackets RoboCup Robot]]<br />
<br />
==Drawings==<br />
<br />
==Materials==<br />
<br />
==Assembly Structure==<br />
====Parts List====<br />
<br />
<br />
====Instructions====<br />
<br />
==Non-Mechanical Components==<br />
====Antenna Board====<br />
====Kicker Board====<br />
====Li-Po Battery====<br />
<br />
==Parts & Components==<br />
Amounts are based on per robot. Materials are in sizes for prototyping not lowest cost per robot volume pricing if available is in parenthesis.<br />
<br />
===Stock===<br />
=====Plate - Bottom=====<br />
:Vendor - <br />
:Part No. - <br />
:Cost - <br />
:Description -<br />
<br />
<br />
<br />
===Fasteners===<br />
<br />
====6-32 Low Head Socket Cap Screw====<br />
:Vendor - McMaster-Carr<br />
:Part No. - 92220A141<br />
:Cost - $7.42 (Packs of 25)<br />
:Description - Alloy Steel Low Head Socket Cap Screw 6-32 Thread, 1/4" Length<br />
<br />
==== 1/8" Locating Pins====<br />
:Vendor - MSC Industrial Supply<br />
:Part No. - 88231469<br />
:Cost - $26.46 (pk 100)<br />
:Description - Precision Ground Dowel Pins - Stainless Steel Type: Dowel Pin Diameter: 1/8 Overall Length: 3/16 Material: Stainless Steel - 416 SS Finish/Coating: Bright<br />
<br />
===Other===<br />
<br />
<br />
<br />
<br />
==Cost Estimates==<br />
<br />
==Action Log==<br />
# 02/08/2008 - Initial base with 4 modules designed.<br />
# 02/18/2009 - Preliminary solenoid added.<br />
# 03/17/2009 - Batteries and Caps now fit.<br />
# 03/19/2009 - Everything all assemblies now fit with out clipping.<br />
# 03/20/2009 - Fillets added to base plate to keep it with in dimensions.<br />
# 03/22/2009 - Updated chipper & kicker assembly added.<br />
# 04/12/2009 - Base plate modified to allow attachment of chipper & kicker assembly.<br />
# 07/18/2009 - Bottom plate CAM'd.<br />
# 01/31/2010 - Electrical board standoffs and new caps are selected. Designs updated. <br />
<br />
[[Category: RoboCup Mechanical]] [[Category: 2009]]</div>Stefan