RoboJackets Wiki - User contributions [en]

User:Rosawa3

2020-05-09T00:38:15Z

Rosawa3: profile update

'''Name:''' Ryo Osawa

'''E-mail:''' [mailto:rosawa@gatech.edu rosawa@gatech.edu]

'''Major:''' Electrical Engineering / Information and Intelligent Systems

'''Position:''' Alumni (RoboCup Electrical)

== Involvement ==

*[[RoboCup]]

*Tohoku University JYPE 2013-2014
**[https://www.ecei.tohoku.ac.jp/eipe/ Department of Information and Intelligent Systems (now Department of Electrical, Information and Physics Engineering)]
***[http://www.riec.tohoku.ac.jp/introduction/organization/division/ultra-broad/ Ultra-Broadband Signal Processing]

User:Rosawa3

2018-04-30T01:11:08Z

Rosawa3: phone change

[[File:Kokkuri.png|right|kokkuri.png]]

'''Name:''' Ryo Osawa

'''E-mail:''' [mailto:rosawa@gatech.edu rosawa@gatech.edu]

'''Phone:''' +1-470-268-3529

'''Major:''' Electrical Engineering / Information and Intelligent Systems

'''Position:''' Alumni (RoboCup Electrical)

== Involvement ==

*[[RoboCup]]
**[[RoboCup Electrical 2012]]
**[[RoboCup Electrical 2013]]
**[[RoboCup Electrical 2014]]
**[[RoboCup Electrical 2015]]
**RoboCup Electrical 2016
**RoboCup Electrical 2017

*Tohoku University JYPE 2013-2014
**[http://www.eng.tohoku.ac.jp/english/academics/studies/bachelor/iis.html Department of Information and Intelligent Systems (now Department of Electrical, Information and Physics Engineering)]
***[http://www.riec.tohoku.ac.jp/introduction/organization/division/ultra-broad/ Ultra-Broadband Signal Processing]

Main Page

2017-11-12T23:52:16Z

Rosawa3: added shop management link

__NOTOC__
{|
|-

! colspan="3" valign="bottom" |
'''''RoboJackets Wiki'''''

|-

| colspan="3" style="text-align: center;" | Welcome to the '''[http://www.gatech.edu/ Georgia Tech]''' '''[https://robojackets.org/ RoboJackets]''' wiki! We are currently looking for both volunteers and sponsors. More info can be found on the [[How you can help]] page.
|-

| rowspan = "2" style="vertical-align: middle; width: 200px;" | '''<big>Teams</big>'''
<ul style="line-height: 20.7999992370605px;">
<li>[[Outreach]]</li>
<li>[[IGVC]]</li>
<li>[[RoboRacing]]</li>
<li>[[RoboCup]]</li>
<li>[[BattleBots]]</li>
<li>[[Team-Template]]</li>
</ul>

! style="vertical-align: middle; width: 300px;" colspan="1" rowspan = "2"| [[File:Robobuzz.svg]]
'''The Georgia Tech RoboJackets''' '''https://robojackets.org/'''

| style="vertical-align: middle; width: 150px; | '''<big>Resources</big>'''
<ul style="line-height: 20.7999992370605px;">
<li>[[How to Guides]]</li>
<li>[[Vendor_List|Vendor and Supplier List]]</li>
<li>[https://gtvault.sharepoint.com/sites/gww/scc/SitePages/Home.aspx SCC Sharepoint]
</li>
</ul>

|-
| style="vertical-align: middle; width: 200px;" | '''<big>Info</big>'''
<ul style="line-height: 20.7999992370605px;">
<li>[[Policies and Best Practices]]</li>
<li>[[Shop Management]]</li>
<li>[[Public Relations]]</li>
<li>[[Info|RoboJackets Information]]</li>
</ul>
!
|}

MediaWiki:Sidebar

2017-10-20T02:28:27Z

Rosawa3: adding homecoming car link

MediaWiki:Sidebar

2017-08-22T17:03:49Z

Rosawa3: Changed IARRC to RoboRacing

MediaWiki:Sidebar

2017-08-22T15:10:40Z

Rosawa3: Changed FIRST to Outreach

Planning a Trip

2017-05-31T15:23:32Z

Rosawa3:

A core component of RoboJackets is travel to events and competitions. This article is targeted at Project Managers to assist them in understanding the steps and policies around planning a trip.

=Before you Book=
==Budgeting for Travel==
All trips, including an accurate account of all expected expenses, shall be included on the project budget in each [[Proposals|annual proposal]]. This budget might include, but is not necessarily limited to, line items for the following expenses:
* Competition Registration
* Primary Transportation (E.g. A flight or long drive)
* Secondary Transportation (E.g. Rental car or train after a flight)
* Gas
* Baggage Fees for bags containing RoboJackets property (If flying)
* Customs / Duty Fees (E.g. An ATA Carnet)
* Lodging
* Trip contribution from members (represent as a negative amount)

See [[Budgeting for Travel]] for more information.

You should not budget for any of the following:
* Meals or Snacks
* Baggage fees for personal luggage (Unless personal luggage allowances were displaced by RoboJackets bags)
* Anything else listed under the [[Travel Policy#Prohibited Allocations|prohibited allocations]]

==Gathering Interest==
As early as feasible, PMs should solicit interest in attending competition from members. The form should contain critical information on the trip (including dates) and at least the following questions:
# Are you interested in attending competition?
#* Yes, Maybe, no
# Are you available to attend competition?
#* Definitely, Probably, Probably not, No

It is frequently wise to ask additional questions to help select attendees. Examples of additional questions include:
* What subteam are you on?
* How many years have you been in RoboJackets?
* How long have you been at GT?
* How many times have you been to competition before?

==Picking Who Will Attend==
The final decision as to who will attend a competition is left to the Project Manager. The final number attending competition should be based on the expected attendance from the proposal, adjusted in response to any significant changes in prices.

When selecting a group, it is important to bring as diverse a group as possible. Ideally, it will include members from all disciplines (Software, Electrical, Mechanical) and it will include members from all age groups, including 1st year members. Competition is regularly cited by older members as the moment when RoboJackets became their passion, so it can be a good way to prepare new members. Finally, all team members must be eligible per the [[Travel Policy#Travel Eligibility| RoboJackets Travel policy]]

Additionally, priority should be given to current and future team leadership (if known).

Once the list is chosen, personally invite each member. Avoid sending out a list or reading names at a meeting. Be prepared to contact alternates as necessary.

At this point, collect all necessary information from the travelers. Depending on the nature of the trip, the information may vary. Additionally, depending on your mode of transportation or competition registration system, it may not be possible to change the travelers after the date of commitment. Provide information on the cost of a given trip prior to this point in the process.

==Common Questions==
* '''How do I know if we should fly or drive?'''
** First, you can look to previous year for precedent. Second, consider if the cargo can all be carried on an airplane (Consider size and chemical composition). Finally, if Flying and Driving Remain an option, drive for trips under 650 miles and fly for trips over 650 miles. This is a loose guideline, and depending on flight and fuel costs, you can decide to justify either decision.
* '''When do we book a rental car vs using a personal vehicle?'''
** For out of state trips, it is preferable to use rental cars to reduce risk or burden on an individual member. For in-state trips, generally advisable to use personal vehicles to reduce the workload of leadership.

=Making Reservations=

==Institute Vehicles==
The School of Mechanical Engineering maintains a fleet of vehicles available for checkout by RoboJackets members who have completed the online safe driving course.

The primary vehicle RoboJackets uses is the SCC F350 in order to tow the trailer. See [[Reserving the F350|reserving the F350]] for instructions on how to reserve it. Reservations should be made as soon as competition dates are known.

Additionally, the School of Mechanical Engineering has an F150 and two minivans available for checkout. These vehicles are not permitted to leave Georgia, but exceptions have been made under extenuating circumstances. Contact the RoboJackets secretary at least 2 months in advance for assistance booking these vehicles.

==Rental Cars==
Rental cars are typically used when traveling long distance out of state where you are not flying, or after reaching your destination during a long flight if the destination does not have suitable public transit. To use a rental car during a competition trip, the following steps must be taken:
# Determine the exact dates and times you will be needing the rental car and how many cars you will need. Remember to account for when you need to pick up the cars, often the day before the trip, and when you need to return them, often the day after. For trips involving more than 7 people, more than one rental car will be needed as the most common available van size is 7 total people. Some vans have seating for 8, but it depends on the rental car agency.
# Look over the team roster and confirm there is at least one individual going on the trip who has a credit card and is at least 21 years of age. No one under 21 is allowed to rent a car. The individual will be reimbursed by RoboJackets for the expense, but RoboJackets does not have a credit card to use for the rental. It is preferable to have two drivers per vehicle and both must be at least 21. If there is not an individual going that is 21, then another method of transit must be selected or the team roster altered.
# Once the drivers and the number of vehicles are confirmed, the following information should be sent to the administrative assistant assigned to RoboJackets. She will make the reservation in the drivers name. This allows the rental to be associated with Georgia Tech and receive any potential discounts.
#* Renter’s Name
#* Phone Number
#* Credit Card Type
#* Credit Card Holder Age
#* Email Address (to send you a confirmation)
#* Type of Vehicle (Compact, Intermediate, Standard or Full-size)
# Upon confirmation of the rental, the final step is to pick up the car from the selected agency location at the date and time in the confirmation. When completing the rental agreement, you should decline the fuel prepay option and accept the collision and liability insurance coverage.
# At the end of the rental period, return it based on the instructions given by the rental car agency by the assigned date and time with a full tank of gas.
Financial Note: RoboJackets, after reimbursing the individual for the rental, will then submit reimbursement requests based on the allocated travel line items in the SGA bill/budget for the particular competition.

==Flights==
TODO: Will Stuckey

===Ground Transportation===
Upon arrival in your destination airport, there are several options for ground transportation. The specific option chosen is dependent on the location and number of travelers. Before considering the options below, please look to see if the event or hotel has any sponsored transportation options. In the past, competitions have run shuttle buses to the airport and/or to the venue or offered free/discounted fares on public transportation. Using on demand ride services (Taxi, Uber, Lyft, etc) should be avoided when practical.

====Rental Cars====
Rental cars are most appropriate for trips to areas lacking public transport or on trips with a high baggage to member ratio, where carrying bags would represent a significant logistical challenge. See [[Planning a Trip#Rental Cars|rental cars]] for more information.

====Long Distance Trains====
In the event that the host city does not have an airport reachable from Atlanta for a reasonable cost, it may be appropriate to take a long distance train. This is typically an option for Europe or Asia. Depending on the trip finances, it may be appropriate for either RoboJackets to buy the tickets or for each member to buy them individually. It is also worth investigating if a railpass is more cost effective than individual tickets. Railpasses are preferred as they offer great flexibility with regards to timing, so flight delays do not result in missing the train. Additionally, if vacation days are being taken at the end of the trip, team members may elect to purchase additional days on their railpass at their own expense.

====Subway/Bus====
If the event is in a large city, subway or bus is usually cheapest and most convenient method to get to competition. RoboJackets typically does not cover the cost for subway/bus fares. Do your diligence to identify whether it is cheaper to buy day/week passes over individual tickets. Note that sometimes free or discounted fares will be available to competitors. Check with event organizers for details.

==Lodging==
RoboJackets uses all available resources to find the most ideal housing situation for members. In the past, teams have stayed in hotels, hostels, and AirBnBs. Hotel reservations should be made as early as feasible, which is typically as soon as it is known how many people will attend the trip.

===Hotels===
RoboJackets typically seeks mid-grade hotels that feature breakfast. A typical room will have two queen beds and will hold four members. Additionally, consider booking suites if they allow getting a lower price/person ratio. It is not advisable to put more than 2 people per bed per room.

Examples of mid-grade hotels include, but are not limited to, La Quinta, Hampton Inn, and Holiday inn. Cost can vary widely based on location, so review financial records from previous years to estimate cost.

While the use of third party booking tools, such as Expedia and Booking.com may assist in finding properties, there are significant risks to using these services. At a minimum, they rarely guarantee room type (king vs 2 queen). Since you do not have a contract directly with the property, dispute resolution is very difficult. Therefore, using these services should be avoided when feasible.

===Hostels===
When traveling abroad, it may be most cost effective to stay in a hostel. For larger groups (8+ people), it is usually worthwhile to email the hostel to negotiate a group rate. If at a small hostel and traveling with a larger group, you may be able to negotiate renting the entire hostel for additional privacy. Be aware that some hostels may require wiring money for a deposit. This is something we can do, but use extreme caution. Also be aware that many hostels cannot accept credit cards.

If the hostel does not feature breakfast, but does have a communal kitchen, save money by going to a grocery store and making breakfast. Typically RoboJackets will pay for the food initially and then get reimbursed from travelers upon return.

===AirBnB===
AirBnBs are rapidly becoming the easiest way to house a medium number of people on a trip and can be more comfortable than a hotel or hostel. Since AirBnB accounts must be tied to an individual person, it is not possible for RoboJackets to book an a central account. Any member attending the trip may use a personal account to make the reservation, to be paid via RoboJackets card or reimbursement. RoboJackets claims no responsibility for damage to a member's AirBnB reputation, though this has not been an issue in the past.

In the event that robots or equipment will be stored in the AirBnB that is a shared home, there should be facilities to secure RoboJackets property.

=International Travel=
International travel adds additional steps and risks to a trip that must be addressed to ensure a safe and successful journey.

==GT Travel Authority Request Form==
When traveling internationally, GT requires all travelers complete a Travel Authority Request form (TAR) and complete the International Questionnaire contained within that document. The TAR form can be obtained from ME Finances or our designated administrative assistant. This form will need to be signed by each traveler, so it is important to start this process before purchasing plane tickets and the end of the school year (for summer trips).

==Passports & Visas==
For all international trips, each traveler is required to have a valid passport. Many countries require 6 months of validity beyond the planned return date, so be sure to check the policies of the destination countries, including those you are only transiting.

If a country requires a visa for entry, it may be necessary to present an invitation letter from competition. Contact the competition organizers if you have questions. Additionally, since GT is an international community, be sure to check the requirements for the countries of the passports held by each member. It is unlikely that all travelers will have a U.S. passport.

==Import/Export==
Due to the high value of the robots and equipment taken to competition, it may be necessary to declare their value. Check the regulations of your destination country for details. When determining the value being imported, limits are typically by person, so if the pelican cases are each below the individual limit, then declaration is not necessary.

For many countries, it is necessary to declare the goods with an ATA Carnet, also known as a "passport for goods". The ATA Carnet is a packet of documents that will be completed by customs officials whenever you enter or leave a country. This paperwork demonstrates to customs officials that you re-exported the goods that you imported and as such are not subject to import duties.

==Transiting a Country==
Depending on the flight itinerary, it may be necessary to transit a country. Transiting a country is defined as disembarking an aircraft, spending time in the "transit area" of the airport (The area "behind" customs) and leaving the country without clearing customs at the country you visited. For example, taking a flight from Atlanta to Tokyo via Toronto would result in transiting in Toronto. Since it is not necessary to clear customs in Toronto, it isn't necessary to complete any customs forms or pay any duties.

However, some airports, such as Mexico City, do not have a transit area and will require travelers to clear customs prior to connecting. In these instances, it is necessary to review the customs regulations of the connecting country. If travelling with an ATA Carnet, it will be necessary to request additional foils to clear customs.

When planning travel, effort should be taken to avoid connecting via airports without a transit area. Each time a traveler clears customs (and then goes through security again) provides risk that some of our items, such as Li-Po Batteries, will be confiscated.

==Currency Conversion==
Sometimes competitions or accommodations require RoboJackets to pay in cash of a foreign currency. In the event this is necessary, RoboJackets should use a foreign ATM to withdraw money at the best possible conversion rate. It is inadvisable to convert the money prior to departing, due to the bad exchange rates in the U.S. and the risks of carrying large quantities of cash.

In the event that RoboJackets receives cash in a foreign currency (Such as prize money), all efforts to sell the currency to RoboJackets members on the trip at market rates should be made. If RoboJackets is planning to visit that country again within ~14 months, it is acceptable to retain the foreign cash currency.

Planning a Trip

2017-05-31T15:21:05Z

Rosawa3:

A core component of RoboJackets is travel to events and competitions. This article is targeted at Project Managers to assist them in understanding the steps and policies around planning a trip.

==Before you Book==
===Budgeting for Travel===
All trips, including an accurate account of all expected expenses, shall be included on the project budget in each [[Proposals|annual proposal]]. This budget might include, but is not necessarily limited to, line items for the following expenses:
* Competition Registration
* Primary Transportation (E.g. A flight or long drive)
* Secondary Transportation (E.g. Rental car or train after a flight)
* Gas
* Baggage Fees for bags containing RoboJackets property (If flying)
* Customs / Duty Fees (E.g. An ATA Carnet)
* Lodging
* Trip contribution from members (represent as a negative amount)

See [[Budgeting for Travel]] for more information.

You should not budget for any of the following:
* Meals or Snacks
* Baggage fees for personal luggage (Unless personal luggage allowances were displaced by RoboJackets bags)
* Anything else listed under the [[Travel Policy#Prohibited Allocations|prohibited allocations]]

===Gathering Interest===
As early as feasible, PMs should solicit interest in attending competition from members. The form should contain critical information on the trip (including dates) and at least the following questions:
# Are you interested in attending competition?
#* Yes, Maybe, no
# Are you available to attend competition?
#* Definitely, Probably, Probably not, No

It is frequently wise to ask additional questions to help select attendees. Examples of additional questions include:
* What subteam are you on?
* How many years have you been in RoboJackets?
* How long have you been at GT?
* How many times have you been to competition before?

===Picking Who Will Attend===
The final decision as to who will attend a competition is left to the Project Manager. The final number attending competition should be based on the expected attendance from the proposal, adjusted in response to any significant changes in prices.

When selecting a group, it is important to bring as diverse a group as possible. Ideally, it will include members from all disciplines (Software, Electrical, Mechanical) and it will include members from all age groups, including 1st year members. Competition is regularly cited by older members as the moment when RoboJackets became their passion, so it can be a good way to prepare new members. Finally, all team members must be eligible per the [[Travel Policy#Travel Eligibility| RoboJackets Travel policy]]

Additionally, priority should be given to current and future team leadership (if known).

Once the list is chosen, personally invite each member. Avoid sending out a list or reading names at a meeting. Be prepared to contact alternates as necessary.

At this point, collect all necessary information from the travelers. Depending on the nature of the trip, the information may vary. Additionally, depending on your mode of transportation or competition registration system, it may not be possible to change the travelers after the date of commitment. Provide information on the cost of a given trip prior to this point in the process.

===Common Questions===
* '''How do I know if we should fly or drive?'''
** First, you can look to previous year for precedent. Second, consider if the cargo can all be carried on an airplane (Consider size and chemical composition). Finally, if Flying and Driving Remain an option, drive for trips under 650 miles and fly for trips over 650 miles. This is a loose guideline, and depending on flight and fuel costs, you can decide to justify either decision.
* '''When do we book a rental car vs using a personal vehicle?'''
** For out of state trips, it is preferable to use rental cars to reduce risk or burden on an individual member. For in-state trips, generally advisable to use personal vehicles to reduce the workload of leadership.

==Making Reservations==

===Institute Vehicles===
The School of Mechanical Engineering maintains a fleet of vehicles available for checkout by RoboJackets members who have completed the online safe driving course.

The primary vehicle RoboJackets uses is the SCC F350 in order to tow the trailer. See [[Reserving the F350|reserving the F350]] for instructions on how to reserve it. Reservations should be made as soon as competition dates are known.

Additionally, the School of Mechanical Engineering has an F150 and two minivans available for checkout. These vehicles are not permitted to leave Georgia, but exceptions have been made under extenuating circumstances. Contact the RoboJackets secretary at least 2 months in advance for assistance booking these vehicles.

===Rental Cars===
Rental cars are typically used when traveling long distance out of state where you are not flying, or after reaching your destination during a long flight if the destination does not have suitable public transit. To use a rental car during a competition trip, the following steps must be taken:
# Determine the exact dates and times you will be needing the rental car and how many cars you will need. Remember to account for when you need to pick up the cars, often the day before the trip, and when you need to return them, often the day after. For trips involving more than 7 people, more than one rental car will be needed as the most common available van size is 7 total people. Some vans have seating for 8, but it depends on the rental car agency.
# Look over the team roster and confirm there is at least one individual going on the trip who has a credit card and is at least 21 years of age. No one under 21 is allowed to rent a car. The individual will be reimbursed by RoboJackets for the expense, but RoboJackets does not have a credit card to use for the rental. It is preferable to have two drivers per vehicle and both must be at least 21. If there is not an individual going that is 21, then another method of transit must be selected or the team roster altered.
# Once the drivers and the number of vehicles are confirmed, the following information should be sent to the administrative assistant assigned to RoboJackets. She will make the reservation in the drivers name. This allows the rental to be associated with Georgia Tech and receive any potential discounts.
#* Renter’s Name
#* Phone Number
#* Credit Card Type
#* Credit Card Holder Age
#* Email Address (to send you a confirmation)
#* Type of Vehicle (Compact, Intermediate, Standard or Full-size)
# Upon confirmation of the rental, the final step is to pick up the car from the selected agency location at the date and time in the confirmation. When completing the rental agreement, you should decline the fuel prepay option and accept the collision and liability insurance coverage.
# At the end of the rental period, return it based on the instructions given by the rental car agency by the assigned date and time with a full tank of gas.
Financial Note: RoboJackets, after reimbursing the individual for the rental, will then submit reimbursement requests based on the allocated travel line items in the SGA bill/budget for the particular competition.

===Flights===
TODO: Will Stuckey

====Ground Transportation====
Upon arrival in your destination airport, there are several options for ground transportation. The specific option chosen is dependent on the location and number of travelers. Before considering the options below, please look to see if the event or hotel has any sponsored transportation options. In the past, competitions have run shuttle buses to the airport and/or to the venue or offered free/discounted fares on public transportation. Using on demand ride services (Taxi, Uber, Lyft, etc) should be avoided when practical.

=====Rental Cars=====
Rental cars are most appropriate for trips to areas lacking public transport or on trips with a high baggage to member ratio, where carrying bags would represent a significant logistical challenge. See [[Planning a Trip#Rental Cars|rental cars]] for more information.

=====Long Distance Trains=====
In the event that the host city does not have an airport reachable from Atlanta for a reasonable cost, it may be appropriate to take a long distance train. This is typically an option for Europe or Asia. Depending on the trip finances, it may be appropriate for either RoboJackets to buy the tickets or for each member to buy them individually. It is also worth investigating if a railpass is more cost effective than individual tickets. Railpasses are preferred as they offer great flexibility with regards to timing, so flight delays do not result in missing the train. Additionally, if vacation days are being taken at the end of the trip, team members may elect to purchase additional days on their railpass at their own expense.

=====Subway/Bus=====
If the event is in a large city, subway or bus is usually cheapest and most convenient method to get to competition. RoboJackets typically does not cover the cost for subway/bus fares. Do your diligence to identify whether it is cheaper to buy day/week passes over individual tickets. Note that sometimes free or discounted fares will be available to competitors. Check with event organizers for details.

===Lodging===
RoboJackets uses all available resources to find the most ideal housing situation for members. In the past, teams have stayed in hotels, hostels, and AirBnBs. Hotel reservations should be made as early as feasible, which is typically as soon as it is known how many people will attend the trip.

====Hotels====
RoboJackets typically seeks mid-grade hotels that feature breakfast. A typical room will have two queen beds and will hold four members. Additionally, consider booking suites if they allow getting a lower price/person ratio. It is not advisable to put more than 2 people per bed per room.

Examples of mid-grade hotels include, but are not limited to, La Quinta, Hampton Inn, and Holiday inn. Cost can vary widely based on location, so review financial records from previous years to estimate cost.

While the use of third party booking tools, such as Expedia and Booking.com may assist in finding properties, there are significant risks to using these services. At a minimum, they rarely guarantee room type (king vs 2 queen). Since you do not have a contract directly with the property, dispute resolution is very difficult. Therefore, using these services should be avoided when feasible.

====Hostels====
When traveling abroad, it may be most cost effective to stay in a hostel. For larger groups (8+ people), it is usually worthwhile to email the hostel to negotiate a group rate. If at a small hostel and traveling with a larger group, you may be able to negotiate renting the entire hostel for additional privacy. Be aware that some hostels may require wiring money for a deposit. This is something we can do, but use extreme caution. Also be aware that many hostels cannot accept credit cards.

If the hostel does not feature breakfast, but does have a communal kitchen, save money by going to a grocery store and making breakfast. Typically RoboJackets will pay for the food initially and then get reimbursed from travelers upon return.

====AirBnB====
AirBnBs are rapidly becoming the easiest way to house a medium number of people on a trip and can be more comfortable than a hotel or hostel. Since AirBnB accounts must be tied to an individual person, it is not possible for RoboJackets to book an a central account. Any member attending the trip may use a personal account to make the reservation, to be paid via RoboJackets card or reimbursement. RoboJackets claims no responsibility for damage to a member's AirBnB reputation, though this has not been an issue in the past.

In the event that robots or equipment will be stored in the AirBnB that is a shared home, there should be facilities to secure RoboJackets property.

==International Travel==
International travel adds additional steps and risks to a trip that must be addressed to ensure a safe and successful journey.

===GT Travel Authority Request Form===
When traveling internationally, GT requires all travelers complete a Travel Authority Request form (TAR) and complete the International Questionnaire contained within that document. The TAR form can be obtained from ME Finances or our designated administrative assistant. This form will need to be signed by each traveler, so it is important to start this process before purchasing plane tickets and the end of the school year (for summer trips).

===Passports & Visas===
For all international trips, each traveler is required to have a valid passport. Many countries require 6 months of validity beyond the planned return date, so be sure to check the policies of the destination countries, including those you are only transiting.

If a country requires a visa for entry, it may be necessary to present an invitation letter from competition. Contact the competition organizers if you have questions. Additionally, since GT is an international community, be sure to check the requirements for the countries of the passports held by each member. It is unlikely that all travelers will have a U.S. passport.

===Import/Export===
Due to the high value of the robots and equipment taken to competition, it may be necessary to declare their value. Check the regulations of your destination country for details. When determining the value being imported, limits are typically by person, so if the pelican cases are each below the individual limit, then declaration is not necessary.

For many countries, it is necessary to declare the goods with an ATA Carnet, also known as a "passport for goods". The ATA Carnet is a packet of documents that will be completed by customs officials whenever you enter or leave a country. This paperwork demonstrates to customs officials that you re-exported the goods that you imported and as such are not subject to import duties.

===Transiting a Country===
Depending on the flight itinerary, it may be necessary to transit a country. Transiting a country is defined as disembarking an aircraft, spending time in the "transit area" of the airport (The area "behind" customs) and leaving the country without clearing customs at the country you visited. For example, taking a flight from Atlanta to Tokyo via Toronto would result in transiting in Toronto. Since it is not necessary to clear customs in Toronto, it isn't necessary to complete any customs forms or pay any duties.

However, some airports, such as Mexico City, do not have a transit area and will require travelers to clear customs prior to connecting. In these instances, it is necessary to review the customs regulations of the connecting country. If travelling with an ATA Carnet, it will be necessary to request additional foils to clear customs.

When planning travel, effort should be taken to avoid connecting via airports without a transit area. Each time a traveler clears customs (and then goes through security again) provides risk that some of our items, such as Li-Po Batteries, will be confiscated.

===Currency Conversion===
Sometimes competitions or accommodations require RoboJackets to pay in cash of a foreign currency. In the event this is necessary, RoboJackets should use a foreign ATM to withdraw money at the best possible conversion rate. It is inadvisable to convert the money prior to departing, due to the bad exchange rates in the U.S. and the risks of carrying large quantities of cash.

In the event that RoboJackets receives cash in a foreign currency (Such as prize money), all efforts to sell the currency to RoboJackets members on the trip at market rates should be made. If RoboJackets is planning to visit that country again within ~14 months, it is acceptable to retain the foreign cash currency.

Planning a Trip

2017-05-31T15:20:41Z

Rosawa3:

A core component of RoboJackets is travel to events and competitions. This article targeted at Project Managers to assist them in understanding the steps and policy around planning a trip.

==Before you Book==
===Budgeting for Travel===
All trips, including an accurate account of all expected expenses, shall be included on the project budget in each [[Proposals|annual proposal]]. This budget might include, but is not necessarily limited to, line items for the following expenses:
* Competition Registration
* Primary Transportation (E.g. A flight or long drive)
* Secondary Transportation (E.g. Rental car or train after a flight)
* Gas
* Baggage Fees for bags containing RoboJackets property (If flying)
* Customs / Duty Fees (E.g. An ATA Carnet)
* Lodging
* Trip contribution from members (represent as a negative amount)

See [[Budgeting for Travel]] for more information.

You should not budget for any of the following:
* Meals or Snacks
* Baggage fees for personal luggage (Unless personal luggage allowances were displaced by RoboJackets bags)
* Anything else listed under the [[Travel Policy#Prohibited Allocations|prohibited allocations]]

===Gathering Interest===
As early as feasible, PMs should solicit interest in attending competition from members. The form should contain critical information on the trip (including dates) and at least the following questions:
# Are you interested in attending competition?
#* Yes, Maybe, no
# Are you available to attend competition?
#* Definitely, Probably, Probably not, No

It is frequently wise to ask additional questions to help select attendees. Examples of additional questions include:
* What subteam are you on?
* How many years have you been in RoboJackets?
* How long have you been at GT?
* How many times have you been to competition before?

===Picking Who Will Attend===
The final decision as to who will attend a competition is left to the Project Manager. The final number attending competition should be based on the expected attendance from the proposal, adjusted in response to any significant changes in prices.

When selecting a group, it is important to bring as diverse a group as possible. Ideally, it will include members from all disciplines (Software, Electrical, Mechanical) and it will include members from all age groups, including 1st year members. Competition is regularly cited by older members as the moment when RoboJackets became their passion, so it can be a good way to prepare new members. Finally, all team members must be eligible per the [[Travel Policy#Travel Eligibility| RoboJackets Travel policy]]

Additionally, priority should be given to current and future team leadership (if known).

Once the list is chosen, personally invite each member. Avoid sending out a list or reading names at a meeting. Be prepared to contact alternates as necessary.

At this point, collect all necessary information from the travelers. Depending on the nature of the trip, the information may vary. Additionally, depending on your mode of transportation or competition registration system, it may not be possible to change the travelers after the date of commitment. Provide information on the cost of a given trip prior to this point in the process.

===Common Questions===
* '''How do I know if we should fly or drive?'''
** First, you can look to previous year for precedent. Second, consider if the cargo can all be carried on an airplane (Consider size and chemical composition). Finally, if Flying and Driving Remain an option, drive for trips under 650 miles and fly for trips over 650 miles. This is a loose guideline, and depending on flight and fuel costs, you can decide to justify either decision.
* '''When do we book a rental car vs using a personal vehicle?'''
** For out of state trips, it is preferable to use rental cars to reduce risk or burden on an individual member. For in-state trips, generally advisable to use personal vehicles to reduce the workload of leadership.

==Making Reservations==

===Institute Vehicles===
The School of Mechanical Engineering maintains a fleet of vehicles available for checkout by RoboJackets members who have completed the online safe driving course.

The primary vehicle RoboJackets uses is the SCC F350 in order to tow the trailer. See [[Reserving the F350|reserving the F350]] for instructions on how to reserve it. Reservations should be made as soon as competition dates are known.

Additionally, the School of Mechanical Engineering has an F150 and two minivans available for checkout. These vehicles are not permitted to leave Georgia, but exceptions have been made under extenuating circumstances. Contact the RoboJackets secretary at least 2 months in advance for assistance booking these vehicles.

===Rental Cars===
Rental cars are typically used when traveling long distance out of state where you are not flying, or after reaching your destination during a long flight if the destination does not have suitable public transit. To use a rental car during a competition trip, the following steps must be taken:
# Determine the exact dates and times you will be needing the rental car and how many cars you will need. Remember to account for when you need to pick up the cars, often the day before the trip, and when you need to return them, often the day after. For trips involving more than 7 people, more than one rental car will be needed as the most common available van size is 7 total people. Some vans have seating for 8, but it depends on the rental car agency.
# Look over the team roster and confirm there is at least one individual going on the trip who has a credit card and is at least 21 years of age. No one under 21 is allowed to rent a car. The individual will be reimbursed by RoboJackets for the expense, but RoboJackets does not have a credit card to use for the rental. It is preferable to have two drivers per vehicle and both must be at least 21. If there is not an individual going that is 21, then another method of transit must be selected or the team roster altered.
# Once the drivers and the number of vehicles are confirmed, the following information should be sent to the administrative assistant assigned to RoboJackets. She will make the reservation in the drivers name. This allows the rental to be associated with Georgia Tech and receive any potential discounts.
#* Renter’s Name
#* Phone Number
#* Credit Card Type
#* Credit Card Holder Age
#* Email Address (to send you a confirmation)
#* Type of Vehicle (Compact, Intermediate, Standard or Full-size)
# Upon confirmation of the rental, the final step is to pick up the car from the selected agency location at the date and time in the confirmation. When completing the rental agreement, you should decline the fuel prepay option and accept the collision and liability insurance coverage.
# At the end of the rental period, return it based on the instructions given by the rental car agency by the assigned date and time with a full tank of gas.
Financial Note: RoboJackets, after reimbursing the individual for the rental, will then submit reimbursement requests based on the allocated travel line items in the SGA bill/budget for the particular competition.

===Flights===
TODO: Will Stuckey

====Ground Transportation====
Upon arrival in your destination airport, there are several options for ground transportation. The specific option chosen is dependent on the location and number of travelers. Before considering the options below, please look to see if the event or hotel has any sponsored transportation options. In the past, competitions have run shuttle buses to the airport and/or to the venue or offered free/discounted fares on public transportation. Using on demand ride services (Taxi, Uber, Lyft, etc) should be avoided when practical.

=====Rental Cars=====
Rental cars are most appropriate for trips to areas lacking public transport or on trips with a high baggage to member ratio, where carrying bags would represent a significant logistical challenge. See [[Planning a Trip#Rental Cars|rental cars]] for more information.

=====Long Distance Trains=====
In the event that the host city does not have an airport reachable from Atlanta for a reasonable cost, it may be appropriate to take a long distance train. This is typically an option for Europe or Asia. Depending on the trip finances, it may be appropriate for either RoboJackets to buy the tickets or for each member to buy them individually. It is also worth investigating if a railpass is more cost effective than individual tickets. Railpasses are preferred as they offer great flexibility with regards to timing, so flight delays do not result in missing the train. Additionally, if vacation days are being taken at the end of the trip, team members may elect to purchase additional days on their railpass at their own expense.

=====Subway/Bus=====
If the event is in a large city, subway or bus is usually cheapest and most convenient method to get to competition. RoboJackets typically does not cover the cost for subway/bus fares. Do your diligence to identify whether it is cheaper to buy day/week passes over individual tickets. Note that sometimes free or discounted fares will be available to competitors. Check with event organizers for details.

===Lodging===
RoboJackets uses all available resources to find the most ideal housing situation for members. In the past, teams have stayed in hotels, hostels, and AirBnBs. Hotel reservations should be made as early as feasible, which is typically as soon as it is known how many people will attend the trip.

====Hotels====
RoboJackets typically seeks mid-grade hotels that feature breakfast. A typical room will have two queen beds and will hold four members. Additionally, consider booking suites if they allow getting a lower price/person ratio. It is not advisable to put more than 2 people per bed per room.

Examples of mid-grade hotels include, but are not limited to, La Quinta, Hampton Inn, and Holiday inn. Cost can vary widely based on location, so review financial records from previous years to estimate cost.

While the use of third party booking tools, such as Expedia and Booking.com may assist in finding properties, there are significant risks to using these services. At a minimum, they rarely guarantee room type (king vs 2 queen). Since you do not have a contract directly with the property, dispute resolution is very difficult. Therefore, using these services should be avoided when feasible.

====Hostels====
When traveling abroad, it may be most cost effective to stay in a hostel. For larger groups (8+ people), it is usually worthwhile to email the hostel to negotiate a group rate. If at a small hostel and traveling with a larger group, you may be able to negotiate renting the entire hostel for additional privacy. Be aware that some hostels may require wiring money for a deposit. This is something we can do, but use extreme caution. Also be aware that many hostels cannot accept credit cards.

If the hostel does not feature breakfast, but does have a communal kitchen, save money by going to a grocery store and making breakfast. Typically RoboJackets will pay for the food initially and then get reimbursed from travelers upon return.

====AirBnB====
AirBnBs are rapidly becoming the easiest way to house a medium number of people on a trip and can be more comfortable than a hotel or hostel. Since AirBnB accounts must be tied to an individual person, it is not possible for RoboJackets to book an a central account. Any member attending the trip may use a personal account to make the reservation, to be paid via RoboJackets card or reimbursement. RoboJackets claims no responsibility for damage to a member's AirBnB reputation, though this has not been an issue in the past.

In the event that robots or equipment will be stored in the AirBnB that is a shared home, there should be facilities to secure RoboJackets property.

==International Travel==
International travel adds additional steps and risks to a trip that must be addressed to ensure a safe and successful journey.

===GT Travel Authority Request Form===
When traveling internationally, GT requires all travelers complete a Travel Authority Request form (TAR) and complete the International Questionnaire contained within that document. The TAR form can be obtained from ME Finances or our designated administrative assistant. This form will need to be signed by each traveler, so it is important to start this process before purchasing plane tickets and the end of the school year (for summer trips).

===Passports & Visas===
For all international trips, each traveler is required to have a valid passport. Many countries require 6 months of validity beyond the planned return date, so be sure to check the policies of the destination countries, including those you are only transiting.

If a country requires a visa for entry, it may be necessary to present an invitation letter from competition. Contact the competition organizers if you have questions. Additionally, since GT is an international community, be sure to check the requirements for the countries of the passports held by each member. It is unlikely that all travelers will have a U.S. passport.

===Import/Export===
Due to the high value of the robots and equipment taken to competition, it may be necessary to declare their value. Check the regulations of your destination country for details. When determining the value being imported, limits are typically by person, so if the pelican cases are each below the individual limit, then declaration is not necessary.

For many countries, it is necessary to declare the goods with an ATA Carnet, also known as a "passport for goods". The ATA Carnet is a packet of documents that will be completed by customs officials whenever you enter or leave a country. This paperwork demonstrates to customs officials that you re-exported the goods that you imported and as such are not subject to import duties.

===Transiting a Country===
Depending on the flight itinerary, it may be necessary to transit a country. Transiting a country is defined as disembarking an aircraft, spending time in the "transit area" of the airport (The area "behind" customs) and leaving the country without clearing customs at the country you visited. For example, taking a flight from Atlanta to Tokyo via Toronto would result in transiting in Toronto. Since it is not necessary to clear customs in Toronto, it isn't necessary to complete any customs forms or pay any duties.

However, some airports, such as Mexico City, do not have a transit area and will require travelers to clear customs prior to connecting. In these instances, it is necessary to review the customs regulations of the connecting country. If travelling with an ATA Carnet, it will be necessary to request additional foils to clear customs.

When planning travel, effort should be taken to avoid connecting via airports without a transit area. Each time a traveler clears customs (and then goes through security again) provides risk that some of our items, such as Li-Po Batteries, will be confiscated.

===Currency Conversion===
Sometimes competitions or accommodations require RoboJackets to pay in cash of a foreign currency. In the event this is necessary, RoboJackets should use a foreign ATM to withdraw money at the best possible conversion rate. It is inadvisable to convert the money prior to departing, due to the bad exchange rates in the U.S. and the risks of carrying large quantities of cash.

In the event that RoboJackets receives cash in a foreign currency (Such as prize money), all efforts to sell the currency to RoboJackets members on the trip at market rates should be made. If RoboJackets is planning to visit that country again within ~14 months, it is acceptable to retain the foreign cash currency.

RoboCupMechanical2007

2017-05-18T02:49:42Z

Rosawa3: /* Index */

==Mechanical System==
This page breaks down the mechanical system of the Robots. The problem has been broken down into five phases as follows:

==The Wall==
[http://www.cis.cornell.edu/boom/2005/ProjectArchive/robocup/documentation/robocup/2003/2003ME.pdf Cornell Resource] -Ryan

* Have ya'll checked out [http://robocup.mae.cornell.edu/documentation/robocup/2002/2002ME.doc these] [http://robocup.mae.cornell.edu/documentation/robocup/2003/2003ME.pdf papers] [http://robocup.mae.cornell.edu/documentation/robocup/2004open/CornellRoboCupMechanicalDocumentation2004.doc yet?] They are definately worth looking at. --[[User:AndyB|Andy]] 23:47, 26 September 2006 (EDT)

==Announcements==

'''01-29-07'''

Due to our inability to machine and drill into 1/8" block the idea brought up now is to make 2 seperate motor housings into one solid hdpe block, 1/4" thick. I have this cadded as well the updated base plate. Also, the kicker will have to be restructured to allow space for the dribller.

I'll have the new models with me, and once it's all done I will release Rev-0 (final) drawings and parts onto the wiki

- Jason

'''01-28-07'''
Solid edge parts are updated along with the mechanical parts list.

-John

'''01-23-07'''
I'm changing a few parts and updating the CAD - there is a lot to do...I'll be in the TIN today, and tomorrow...please stop by

'''01-18-07'''
Checking out plates holding axle - will also design support for motors. With the transfer from inventor no dimensions were put in SE - probably will also make it impossible to do the drawings. So I'm going to just remodel all parts in SE and send out a revised copy...Email me at gth722p@mail.gatech.edu with any questions.

-Jason

'''01-18-07'''
Drivetrain has been uploaded as Solid Edge .par files. The zip file can be found here: [[Image:solid_edge.zip]]

-John

'''10-30-06'''
I will be late to the meeting.

To do list:
1)Create single document with all needed parts and part #'s for ordering.

2)Drive Train: Encoders we found, will not work. Electrical team is looking for another encoder. Work on CAD model, put in bearings for axles, and mounting plates. Cantilever wheels are ok.

3)Manipulator: Select components to populate order sheet (see above). Begin modeling in CAD.

-Ryan

'''Update 10-12-06'''

I edited the Dribbler page with some useful info.

-Pat

Found bevel gears, but we will still need a coupler or custom shaft. Bevel Gears (sdp-si) part #:
A 1B 3MYK05040 - same gears, 1 to 1 ratio.

-Brian

==Roadmap==
*Phase 1
**Simple prototype with holonomic drive train made from the Vex Robotics kit (Complete)
*Phase 2
**Build a second fully functioning prototype
**Kiwi drive system
**Dribbler and shooter
**Built to competition dimensions and requirements
*Phase 3
**Detail design of entire mechancial system
**Five robots
**Design Presentation to ME department
**Technical Drawings (AutoCAD or Inventor)
*Phase 4
**Purchase parts and assemble robot fleet
*Phase 5
**Test system and update designs

==Index==
*[[Parts List]]
*[[Design]]
*[[Motors]]
*[[Drive Train]]
*[[Dribbler]]
*[[Kicker]]
*[http://www.robotobjects.com/scripts/prodView.asp?idproduct=290 Wheels]
*[http://www.omniwheel.com/transwheel/transwheel-2000.htm Transwheels]
*[[Robot Weight]]
*[[Drivetrain drawings]]
*[[Dribbler/Kicker Rough Sketch]]

[[Category: RoboCup]]
[[Category: Mechanical]]
[[Category: Year: 2006-2007]]

Dribbler

2017-05-18T02:49:16Z

Rosawa3:

'''Motor'''

Here is the motor!!! http://www.maxonmotorusa.com/files/catalog/2005/pdf/05_076_e.pdf
part #: 118729

Accompanying Gearhead: http://www.maxonmotorusa.com/files/catalog/2005/pdf/05_205_e.pdf
part #: 110321

----

This is apparently the motor they were using

"The motor that matched our needs best was the Maxon 6V motor # 11827 (we are planning
to overdrive it to 12V) with either a 4.4:1 or 5.4:1 gear head ratio."

-Aaron

That model number doesn't seem to exist, I cant even find it on the maxon site.

-Shaun

'''Possible Solenoid'''

Model S-20-100-H:

http://www.solenoidcity.com/solenoid/tubular/s-20-100hp2.htm

http://www.solenoidcity.com/solenoid/tubular/s-20-100hp1.htm

http://www.electromechanicsonline.com/products/SOTUH025051.asp

'''70 Durometer Sorbothane Statistics (10-26-06)'''

http://www.matweb.com/search/SpecificMaterial.asp?bassnum=PSORB2

-Pat

'''Update'''

Apparently, angled dribblers have been BANNED (as of 2003)

-Pat

'''Dribbler Rules:''' (from: [http://agents.sci.brooklyn.cuny.edu/dev/rcj/rcj2006/soccer-rules2006.pdf])

5.6. Ball Movement.

5.6.1. A robot cannot "hold" a ball.
Hint: Holding a ball means taking a full control of the ball by removing all of its degrees of freedom. For example, this would mean fixing a
ball to the robot's body, surrounding a ball using the robot's body to prevent access by others, encircling the ball or somehow trapping the
ball with any part of the robot's body. If a ball stops rolling while a robot is moving ,or a ball does not rebound when rolled into a robot, it is a good indication that the ball is trapped.

5.6.2. The ball cannot be held underneath a robot.

5.6.3. The ball must be visible at all times.

5.6.4. Other players must be able to access the ball.

5.6.5 The only exception to rule 5.6.1 is the use of a rotating drum that imparts dynamic back spin on the ball to keep the ball on its
surface. This is called a "dribbler".

5.6.6. A dribbler must comply with Rule 2.7 Ball Capturing Zones; i.e., the ball cannot penetrate under the dribbler for more than 2cm. The
2cm is measured from the contact point of the dribbler on the ball.

'''Good Dribbler Reference Pages:'''

1) [http://robocup.mae.cornell.edu/documentation/robocup/2004open/CornellRoboCupMechanicalDocumentation2004.doc#_Toc72784621]

Detailed design of Cornell's 2003 Bots. Dribbler and Kicker stuff on pg 35-76.

2) [http://www.cs.cmu.edu/afs/cs/academic/class/16741-s06/www/Projects/stancliff_16741.pdf]

Summary of the dribbler mechanisms. It's short.

3) [http://pclabsai1.dei.unipd.it/proceedings/Robocup-2005/TDP/SocSSL/CornellTDP.pdf]

Description of Cornell's 2005 bot. Brief mention of dribbler on pg 2-3.

By: Pat (10-12-06)

[[Category: RoboCup]]
[[Category: Mechanical]]
[[Category: Year: 2006-2007]]

RoboCupMechanical2007

2017-05-18T02:49:04Z

Rosawa3: /* Index */

==Mechanical System==
This page breaks down the mechanical system of the Robots. The problem has been broken down into five phases as follows:

==The Wall==
[http://www.cis.cornell.edu/boom/2005/ProjectArchive/robocup/documentation/robocup/2003/2003ME.pdf Cornell Resource] -Ryan

* Have ya'll checked out [http://robocup.mae.cornell.edu/documentation/robocup/2002/2002ME.doc these] [http://robocup.mae.cornell.edu/documentation/robocup/2003/2003ME.pdf papers] [http://robocup.mae.cornell.edu/documentation/robocup/2004open/CornellRoboCupMechanicalDocumentation2004.doc yet?] They are definately worth looking at. --[[User:AndyB|Andy]] 23:47, 26 September 2006 (EDT)

==Announcements==

'''01-29-07'''

Due to our inability to machine and drill into 1/8" block the idea brought up now is to make 2 seperate motor housings into one solid hdpe block, 1/4" thick. I have this cadded as well the updated base plate. Also, the kicker will have to be restructured to allow space for the dribller.

I'll have the new models with me, and once it's all done I will release Rev-0 (final) drawings and parts onto the wiki

- Jason

'''01-28-07'''
Solid edge parts are updated along with the mechanical parts list.

-John

'''01-23-07'''
I'm changing a few parts and updating the CAD - there is a lot to do...I'll be in the TIN today, and tomorrow...please stop by

'''01-18-07'''
Checking out plates holding axle - will also design support for motors. With the transfer from inventor no dimensions were put in SE - probably will also make it impossible to do the drawings. So I'm going to just remodel all parts in SE and send out a revised copy...Email me at gth722p@mail.gatech.edu with any questions.

-Jason

'''01-18-07'''
Drivetrain has been uploaded as Solid Edge .par files. The zip file can be found here: [[Image:solid_edge.zip]]

-John

'''10-30-06'''
I will be late to the meeting.

To do list:
1)Create single document with all needed parts and part #'s for ordering.

2)Drive Train: Encoders we found, will not work. Electrical team is looking for another encoder. Work on CAD model, put in bearings for axles, and mounting plates. Cantilever wheels are ok.

3)Manipulator: Select components to populate order sheet (see above). Begin modeling in CAD.

-Ryan

'''Update 10-12-06'''

I edited the Dribbler page with some useful info.

-Pat

Found bevel gears, but we will still need a coupler or custom shaft. Bevel Gears (sdp-si) part #:
A 1B 3MYK05040 - same gears, 1 to 1 ratio.

-Brian

==Roadmap==
*Phase 1
**Simple prototype with holonomic drive train made from the Vex Robotics kit (Complete)
*Phase 2
**Build a second fully functioning prototype
**Kiwi drive system
**Dribbler and shooter
**Built to competition dimensions and requirements
*Phase 3
**Detail design of entire mechancial system
**Five robots
**Design Presentation to ME department
**Technical Drawings (AutoCAD or Inventor)
*Phase 4
**Purchase parts and assemble robot fleet
*Phase 5
**Test system and update designs

==Index==
*[[Parts List]]
*[[Design]]
*[[Motors]]
*[[Drive Train]]
*[[Dribbler]]
**[[Dribbler_Kicker_Rough_Sketch|Rough Sketch]]
*[[Kicker]]
*[http://www.robotobjects.com/scripts/prodView.asp?idproduct=290 Wheels]
*[http://www.omniwheel.com/transwheel/transwheel-2000.htm Transwheels]
*[[Robot Weight]]
*[[Drivetrain drawings]]
*[[Dribbler/Kicker Rough Sketch]]

[[Category: RoboCup]]
[[Category: Mechanical]]
[[Category: Year: 2006-2007]]

RoboCup System Archive

2017-05-18T02:46:21Z

Rosawa3: /* 2013 */

== System Archive ==
==== 2014 ====
* [[RoboCup 2014 System Outline]]

Subteams
:* [[RoboCup_Electrical_2014|Electrical System]]
:* [[RoboCup_Software_2014|Software System]]
:* [[RoboCup_Mechanical_2014|Mechanical System]]

==== 2013 ====
* [[RoboCup 2013 System Outline]]

Subteams
:* [[RoboCup_Electrical_2013|Electrical System]]
:* [[Robocup_Software_Tasks_2013|Software System]]
:* [[RoboCup_Mechanical_2013|Mechanical System]]

==== 2012 ====
* [[RoboCup 2012 System Outline]]
* [http://wiki.robojackets.org/images/2/2d/RJRC_2012_TDP.pdf 2012 TDP]
Subteams
:* [[RoboCup_Electrical_2012|Electrical System]]
:* [[RoboCup_Software_2012|Software System]]
:* [[RoboCupMechanical|Mechanical System]]

==== 2011 ====
* [[RoboCup 2011 System Outline]]
* [http://wiki.robojackets.org/images/4/4e/RJRC_2011_TDP.pdf 2011 TDP]
Qualification Video
:* [http://www.robojackets.org/RC/robojackets-robocup2011qual.mkv RoboJackets Server (MKV format)]
:* [http://www.robojackets.org/RC/robojackets-robocup2011qual.wmv RoboJackets Server (WMV format)]
:* [http://www.youtube.com/watch?v=nnZMUu3QT6Y Youtube]
Subteams
:* [[RoboCup_Electrical_2011|Electrical System]]
:* [[Robocup_Software_2011_Plan|Software System]]
:* [[RoboCupMechanical|Mechanical System]]

==== 2010 ====
* [[RoboCup_Overview_2010 | RoboCup 2010 System Outline]]
* [http://wiki.robojackets.org/images/a/af/RJRC_2010_TDP.pdf 2010 TDP]
* [[RoboCupTravel2010 | Travel]]
* [[2010 US Open]]
Subteams
:* [[RoboCup_Electrical_2010|Electrical System]]
:* [[RoboCup_Software_2010|Software System]]
:* [[RoboCupMechanical|Mechanical System]]

==== 2009 ====
* [[RCMeetingMinutes | RoboCup 2009 System Outline]]
* [[RoboCup Meeting Minutes | Meeting Minutes]]
Subteams
* [[RoboCup_Electrical_2009|Electrical System]]
** [[RoboCup_Radio_2009|Radio Communication]]
* [[RoboCup_Software_2009|Software System]]
* [[RoboCupMechanical|Mechanical System]]
**[[RoboCupMechanicalDev2009|Mechanical Prototype Development]]

==== 2008 ====
*[[RoboCup 2008 System Outline]]
*[http://wiki.robojackets.org/images/1/14/RJRC_2008_TDP.pdf 2008 TDP]
*[[RC08Travel|Personal Travel Costs and Info]]
*[[RC08TravelLog|Team Travel Logistics and Costs]]
Subteams
:*[[RoboCup_Electrical_2008|Electrical System]]
:*[[RoboCupMechanical2008|Mechanical System]]
:*[[RoboCupSoftware|Software System]]
::*[[RC08SWRoadMap|Short Term Software Roadmap]]
::*[[Development Tools]]
::*[[RoboCup Coding Style|Coding Style]]
::*[[Code Examples]]

==== 2007 ====
*[http://wiki.robojackets.org/images/c/c1/RJRC_2007_TDP.pdf 2007 TDP]
Subteams
:* [[RoboCupElectrical2007|Electrical System Information]]
::* [[RCpartsSample|How to Sample Parts for RoboCup]]
:* [[RoboCupSoftware2007|Software System Information]]
:* [[RoboCupMechanical2007|Mechanical System Information]]
:* [[RobocupVision|Vision System Information]]
::* [[RCVisSoftware|Robocup Image Processing]]
::* [[RCCamera|Robocup Image Acquisition]]

[[Category: RoboCup]]

RoboCup System Archive

2017-05-18T02:45:22Z

Rosawa3: /* 2011 */

== System Archive ==
==== 2014 ====
* [[RoboCup 2014 System Outline]]

Subteams
:* [[RoboCup_Electrical_2014|Electrical System]]
:* [[RoboCup_Software_2014|Software System]]
:* [[RoboCup_Mechanical_2014|Mechanical System]]

==== 2013 ====
* [[RoboCup 2013 System Outline]]

Subteams
:* [[RoboCup_Electrical_2013|Electrical System]]
:* [[RoboCup_Software_2013|Software System]]
:* [[RoboCup_Mechanical_2013|Mechanical System]]

==== 2012 ====
* [[RoboCup 2012 System Outline]]
* [http://wiki.robojackets.org/images/2/2d/RJRC_2012_TDP.pdf 2012 TDP]
Subteams
:* [[RoboCup_Electrical_2012|Electrical System]]
:* [[RoboCup_Software_2012|Software System]]
:* [[RoboCupMechanical|Mechanical System]]

==== 2011 ====
* [[RoboCup 2011 System Outline]]
* [http://wiki.robojackets.org/images/4/4e/RJRC_2011_TDP.pdf 2011 TDP]
Qualification Video
:* [http://www.robojackets.org/RC/robojackets-robocup2011qual.mkv RoboJackets Server (MKV format)]
:* [http://www.robojackets.org/RC/robojackets-robocup2011qual.wmv RoboJackets Server (WMV format)]
:* [http://www.youtube.com/watch?v=nnZMUu3QT6Y Youtube]
Subteams
:* [[RoboCup_Electrical_2011|Electrical System]]
:* [[Robocup_Software_2011_Plan|Software System]]
:* [[RoboCupMechanical|Mechanical System]]

==== 2010 ====
* [[RoboCup_Overview_2010 | RoboCup 2010 System Outline]]
* [http://wiki.robojackets.org/images/a/af/RJRC_2010_TDP.pdf 2010 TDP]
* [[RoboCupTravel2010 | Travel]]
* [[2010 US Open]]
Subteams
:* [[RoboCup_Electrical_2010|Electrical System]]
:* [[RoboCup_Software_2010|Software System]]
:* [[RoboCupMechanical|Mechanical System]]

==== 2009 ====
* [[RCMeetingMinutes | RoboCup 2009 System Outline]]
* [[RoboCup Meeting Minutes | Meeting Minutes]]
Subteams
* [[RoboCup_Electrical_2009|Electrical System]]
** [[RoboCup_Radio_2009|Radio Communication]]
* [[RoboCup_Software_2009|Software System]]
* [[RoboCupMechanical|Mechanical System]]
**[[RoboCupMechanicalDev2009|Mechanical Prototype Development]]

==== 2008 ====
*[[RoboCup 2008 System Outline]]
*[http://wiki.robojackets.org/images/1/14/RJRC_2008_TDP.pdf 2008 TDP]
*[[RC08Travel|Personal Travel Costs and Info]]
*[[RC08TravelLog|Team Travel Logistics and Costs]]
Subteams
:*[[RoboCup_Electrical_2008|Electrical System]]
:*[[RoboCupMechanical2008|Mechanical System]]
:*[[RoboCupSoftware|Software System]]
::*[[RC08SWRoadMap|Short Term Software Roadmap]]
::*[[Development Tools]]
::*[[RoboCup Coding Style|Coding Style]]
::*[[Code Examples]]

==== 2007 ====
*[http://wiki.robojackets.org/images/c/c1/RJRC_2007_TDP.pdf 2007 TDP]
Subteams
:* [[RoboCupElectrical2007|Electrical System Information]]
::* [[RCpartsSample|How to Sample Parts for RoboCup]]
:* [[RoboCupSoftware2007|Software System Information]]
:* [[RoboCupMechanical2007|Mechanical System Information]]
:* [[RobocupVision|Vision System Information]]
::* [[RCVisSoftware|Robocup Image Processing]]
::* [[RCCamera|Robocup Image Acquisition]]

[[Category: RoboCup]]

RoboCup Electrical 2013

2017-05-18T02:43:30Z

Rosawa3: /* Kicker */

==The Electrical System==
The electrical system is all the electrical hardware and firmware used to operate the 2013 RoboCup team. It includes the host hardware, the wireless link, and the electronics for each robot.

==Current Activities==
* [[RC_Electrical_Kicker2013 | Kicker Design 2013]]
* [[RC13HighStrengthEncoderWires | High Strength Encoder Wire (Prototype)]]

==Systems==
=== On-Board Control ===

* [[RC13Microcontroller | Microcontroller]]
* [[RC13FPGA | FPGA]]
* [[RCFirmware | Firmware]]

=== Kicker ===
* [[RoboCup:_Kicker_Board_2013 | Kicker Electronics]]

=== Base Station ===
* [[RoboCup_Base_Station | Base Station]]
=== Sensors ===
* [[RC13BallSense|IR Break-Beam Ball Sensor]]
* [[RC13IMU|Inertial Measuring Unit (IMU)]]
=== Power ===
* [[RC13Power | Power Supplies and Batteries]]

==Some Ideas==
*[http://www.electro-tech-online.com/electronic-projects-design-ideas-reviews/33205-laser-beam-break-detector.html Ball sensor upgrade]
*Upgrade IGBTs, since we seem to be running more current through them than they are rated for...
** [http://www.digikey.com/product-detail/en/IXGX400N30A3/IXGX400N30A3-ND/1652310 IXGX400N30A3 (No stack)]
**>> [http://www.digikey.com/product-detail/en/IXGK400N30A3/IXGK400N30A3-ND/2117089 IXGK400N30A3 (No Stack)]
**[http://www.digikey.com/product-detail/en/IXGQ200N30PB/IXGQ200N30PB-ND/2117137 IXGQ200N30PB (No stack)]
**[http://www.digikey.com/product-detail/en/IXGQ240N30PB/IXGQ240N30PB-ND/2117139 IXGQ240N30PB (Dual-stack)]
*Using analog hall effect sensors to eliminate optical encoders
*All on-board processing
*Move back to a kicker board design similar to the 2008 design (except with chipping, efficiency, and durability upgrades)
*Make stuff easier to be transported safely (e.g. to competitions)...

==Links==
[[Category: RoboCup]]
[[Category: Electrical]]
[[Category: Year: 2012-2013]]

RoboCup: Kicker Board 2013

2017-05-18T02:42:49Z

Rosawa3: /* Parts list */

== Overview ==

This is an overview of all the features and concepts on the 2013 kicker board made for the RoboCup competition by the electrical team of Georgia Institute of Technology's RoboCup team. This board's purpose is to drive a high voltage, high peak current solenoid to kick the ball. This page is to be used to farmiliarize new members of RoboCup with how the kicker board works.

== Safety and Handling ==

This board uses high voltage. Be extremely careful around high voltage. It can cause considerable damage. Until you know that the capacitors are discharged, assume that they are still charged up to 250V. Check if there is a red LED lit on the back of the the kicker board. This is the death light. It is powered directly by the capacitors. If this light is on, you should not touch the board.

== Kicker Charger ==

[[File:Kicker charger.PNG|thumb|center|1200px]]

This is the kicker board's charging circutry. This allows the board to charge large capacitors up to a very high voltage. This part of the board consists of two main components: the bank capacitors and the flyback regulator. The bank capacitor is charged up to a high voltage and allows a high peak power delivery. The flyback controller is used to convert a low voltage, high current input to a high voltage, low current output.

=== Flyback Controller ===

The flyback controller that is on the board is a LT3757. This chip modulates the duty cycle of the priamry side switch based ont he feedback voltage to regulate the output voltage.

=== LT3757/Converter controller ===

The converter controller that is on the board is a LT3757. This chip manages the switching of our Buck-boost converter. When the supply loop has reached full capacity it will lock the supply loop. When the potential is transferred to the capacitors the supply loop is again unlocked. The LT3757 is an integrated circuit that uses inputs to determine precisely when to switch in order maximize power transfer. We can not do this manually or with our FPGA and CPU because of the asymptotic nature of capacitors and inductors. Unfortunately the LT3757 was designed for a resistive load, and while it can handle capacitive loads quite well there may be other chips that do it even better. We are looking at other possibilities and may improve on this component in the future.

=== Other converter methods ===

It has been suggested that other converter types may be able to charge the capacitors faster. A boost converter may allow us to create a higher voltage potential. This would allow a faster transfer from the inductor to the capacitor. The other converter that has been looked at is the cuk converter. A cuk converter might be able to allow the capacitors to be charged while other inductors are charging which would increase the rate of power transfer without raising the voltage across the capacitor. The electrical team is looking at these and other possibilities to improve on these systems in the future.

== Voltage Monitor ==

This component is covered in detail on the control board page.

[http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker]

== Kicker Trigger ==

[[File:Kicker trigger.PNG|thumb|left|600px]]

This section of the board allows the control board to release the energy stored in the capacitors into the kicker or chipper. This is done by using the TC4427 to control two high current, high voltage power transitors. These transistors will allow all of the energy stored in the capacitors to be released over the solenoid. There is a very value resistor and a diode pointing from the ground side of the solenoid to the power side in case the there is voltage overflow from the solenoid.

== Auto-Discharge ==

The other way for the capacitors to discharge is the auto-discharger. This section is controled by either the control board, when it needs less voltage to kick with or the by the LT3757 when it has reached the maximum voltage allowed by the circutry. This discharger has much lower current transitors and large resistors that limit the discharge current. This is never used for discharging the capacitors fully as it will take longer than kicking and will release a lot of heat if the full capacitors were discharged over this section.

== 2008 Model of the 2013 Board ==

The 2013 kicker boards have redplaced out the previous models of the 2008 and 2011 boards. The 2013 board is based on the 2011 version with the addition of some updated parts and adding a voltage monitor for the capacitors. However, the 2008 board was very different. While the 2011 and 2013 kicker boards have a chip port, the 2008 boards and robots could not chip the ball. We have removed the chipping components from certain boards to avoid confusion with ports and plugs. Additionally, some of the 2008 model 2013 boards do not have voltage monitoring components because the control boards are unable to read the voltage monitor in 2008 mode

== Parts list ==

Disclaimer: Some of the parts are not used in the final kicker board, but are printed on the mini board that is removed to make room for the capacitors. [[RC13KickerElectronics|Here]] is a list of major parts.

== References ==
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li>[http://en.wikipedia.org/wiki/Transformer http://en.wikipedia.org/wiki/Transformer]</li>
<li>[http://en.wikipedia.org/wiki/Inductor#Stored_energy http://en.wikipedia.org/wiki/Inductor]</li>
<li>[http://en.wikipedia.org/wiki/Flyback_converter http://en.wikipedia.org/wiki/Flyback_converter]</li>
<li>[http://cds.linear.com/docs/en/datasheet/3757Afd.pdf http://cds.linear.com/docs/en/datasheet/3757Afd.pdf]</li>
<li>[http://en.wikipedia.org/wiki/Field-programmable_gate_array http://en.wikipedia.org/wiki/Field-programmable_gate_array]</li>
<li>[http://en.wikipedia.org/wiki/Microprocessor http://en.wikipedia.org/wiki/Microprocessor]</li>
<li>[http://en.wikipedia.org/wiki/Boost_converter http://en.wikipedia.org/wiki/Boost_converter]</li>
<li>[http://en.wikipedia.org/wiki/%C4%86uk_converter http://en.wikipedia.org/wiki/%C4%86uk_converter]</li>
</ol>

[[Category:RoboCup]] [[Category:Electrical]] [[Category:Year: 2013-2014]]

RoboCup: Kicker Board 2013

2017-05-18T02:39:53Z

Rosawa3:

== Overview ==

This is an overview of all the features and concepts on the 2013 kicker board made for the RoboCup competition by the electrical team of Georgia Institute of Technology's RoboCup team. This board's purpose is to drive a high voltage, high peak current solenoid to kick the ball. This page is to be used to farmiliarize new members of RoboCup with how the kicker board works.

== Safety and Handling ==

This board uses high voltage. Be extremely careful around high voltage. It can cause considerable damage. Until you know that the capacitors are discharged, assume that they are still charged up to 250V. Check if there is a red LED lit on the back of the the kicker board. This is the death light. It is powered directly by the capacitors. If this light is on, you should not touch the board.

== Kicker Charger ==

[[File:Kicker charger.PNG|thumb|center|1200px]]

This is the kicker board's charging circutry. This allows the board to charge large capacitors up to a very high voltage. This part of the board consists of two main components: the bank capacitors and the flyback regulator. The bank capacitor is charged up to a high voltage and allows a high peak power delivery. The flyback controller is used to convert a low voltage, high current input to a high voltage, low current output.

=== Flyback Controller ===

The flyback controller that is on the board is a LT3757. This chip modulates the duty cycle of the priamry side switch based ont he feedback voltage to regulate the output voltage.

=== LT3757/Converter controller ===

The converter controller that is on the board is a LT3757. This chip manages the switching of our Buck-boost converter. When the supply loop has reached full capacity it will lock the supply loop. When the potential is transferred to the capacitors the supply loop is again unlocked. The LT3757 is an integrated circuit that uses inputs to determine precisely when to switch in order maximize power transfer. We can not do this manually or with our FPGA and CPU because of the asymptotic nature of capacitors and inductors. Unfortunately the LT3757 was designed for a resistive load, and while it can handle capacitive loads quite well there may be other chips that do it even better. We are looking at other possibilities and may improve on this component in the future.

=== Other converter methods ===

It has been suggested that other converter types may be able to charge the capacitors faster. A boost converter may allow us to create a higher voltage potential. This would allow a faster transfer from the inductor to the capacitor. The other converter that has been looked at is the cuk converter. A cuk converter might be able to allow the capacitors to be charged while other inductors are charging which would increase the rate of power transfer without raising the voltage across the capacitor. The electrical team is looking at these and other possibilities to improve on these systems in the future.

== Voltage Monitor ==

This component is covered in detail on the control board page.

[http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker]

== Kicker Trigger ==

[[File:Kicker trigger.PNG|thumb|left|600px]]

This section of the board allows the control board to release the energy stored in the capacitors into the kicker or chipper. This is done by using the TC4427 to control two high current, high voltage power transitors. These transistors will allow all of the energy stored in the capacitors to be released over the solenoid. There is a very value resistor and a diode pointing from the ground side of the solenoid to the power side in case the there is voltage overflow from the solenoid.

== Auto-Discharge ==

The other way for the capacitors to discharge is the auto-discharger. This section is controled by either the control board, when it needs less voltage to kick with or the by the LT3757 when it has reached the maximum voltage allowed by the circutry. This discharger has much lower current transitors and large resistors that limit the discharge current. This is never used for discharging the capacitors fully as it will take longer than kicking and will release a lot of heat if the full capacitors were discharged over this section.

== 2008 Model of the 2013 Board ==

The 2013 kicker boards have redplaced out the previous models of the 2008 and 2011 boards. The 2013 board is based on the 2011 version with the addition of some updated parts and adding a voltage monitor for the capacitors. However, the 2008 board was very different. While the 2011 and 2013 kicker boards have a chip port, the 2008 boards and robots could not chip the ball. We have removed the chipping components from certain boards to avoid confusion with ports and plugs. Additionally, some of the 2008 model 2013 boards do not have voltage monitoring components because the control boards are unable to read the voltage monitor in 2008 mode

== Parts list ==

Disclaimer: Some of the parts are not used in the final kicker board, but are printed on the mini board that is removed to make room for the capacitors. The parts list can be downloaded [http://wiki.robojackets.org/mediawiki/Media%3AKicker%20parts.pdf here].

== References ==
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li>[http://en.wikipedia.org/wiki/Transformer http://en.wikipedia.org/wiki/Transformer]</li>
<li>[http://en.wikipedia.org/wiki/Inductor#Stored_energy http://en.wikipedia.org/wiki/Inductor]</li>
<li>[http://en.wikipedia.org/wiki/Flyback_converter http://en.wikipedia.org/wiki/Flyback_converter]</li>
<li>[http://cds.linear.com/docs/en/datasheet/3757Afd.pdf http://cds.linear.com/docs/en/datasheet/3757Afd.pdf]</li>
<li>[http://en.wikipedia.org/wiki/Field-programmable_gate_array http://en.wikipedia.org/wiki/Field-programmable_gate_array]</li>
<li>[http://en.wikipedia.org/wiki/Microprocessor http://en.wikipedia.org/wiki/Microprocessor]</li>
<li>[http://en.wikipedia.org/wiki/Boost_converter http://en.wikipedia.org/wiki/Boost_converter]</li>
<li>[http://en.wikipedia.org/wiki/%C4%86uk_converter http://en.wikipedia.org/wiki/%C4%86uk_converter]</li>
</ol>

[[Category:RoboCup]] [[Category:Electrical]] [[Category:Year: 2013-2014]]

RoboCup: Kicker Board 2013

2017-05-18T02:39:17Z

Rosawa3:

== Overview ==

This is an overview of all the features and concepts on the 2013 kicker board made for the RoboCup competition by the electrical team of Georgia Institute of Technology's RoboCup team. This board's purpose is to drive a high voltage, high peak current solenoid to kick the ball. This page is to be used to farmiliarize new members of RoboCup with how the kicker board works.

== Safety and Handling ==

This board uses high voltage. Be extremely careful around high voltage. It can cause considerable damage. Until you know that the capacitors are discharged, assume that they are still charged up to 250V. Check if there is a red LED lit on the back of the the kicker board. This is the death light. It is powered directly by the capacitors. If this light is on, you should not touch the board.

== Kicker Charger ==

[[File:Kicker charger.PNG|thumb|center|1200px]]

This is the kicker board's charging circutry. This allows the board to charge large capacitors up to a very high voltage. This part of the board consists of two main components: the bank capacitors and the flyback regulator. The bank capacitor is charged up to a high voltage and allows a high peak power delivery. The flyback controller is used to convert a low voltage, high current input to a high voltage, low current output.

=== Flyback Controller ===

The flyback controller that is on the board is a LT3757. This chip modulates the duty cycle of the priamry side switch based ont he feedback voltage to regulate the output voltage.

=== LT3757/Converter controller ===

The converter controller that is on the board is a LT3757. This chip manages the switching of our Buck-boost converter. When the supply loop has reached full capacity it will lock the supply loop. When the potential is transferred to the capacitors the supply loop is again unlocked. The LT3757 is an integrated circuit that uses inputs to determine precisely when to switch in order maximize power transfer. We can not do this manually or with our FPGA and CPU because of the asymptotic nature of capacitors and inductors. Unfortunately the LT3757 was designed for a resistive load, and while it can handle capacitive loads quite well there may be other chips that do it even better. We are looking at other possibilities and may improve on this component in the future.

=== Other converter methods ===

It has been suggested that other converter types may be able to charge the capacitors faster. A boost converter may allow us to create a higher voltage potential. This would allow a faster transfer from the inductor to the capacitor. The other converter that has been looked at is the cuk converter. A cuk converter might be able to allow the capacitors to be charged while other inductors are charging which would increase the rate of power transfer without raising the voltage across the capacitor. The electrical team is looking at these and other possibilities to improve on these systems in the future.

== Voltage Monitor ==

This component is covered in detail on the control board page.

[http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker]

== Kicker Trigger ==

[[File:Kicker trigger.PNG|thumb|left|600px]]

This section of the board allows the control board to release the energy stored in the capacitors into the kicker or chipper. This is done by using the TC4427 to control two high current, high voltage power transitors. These transistors will allow all of the energy stored in the capacitors to be released over the solenoid. There is a very value resistor and a diode pointing from the ground side of the solenoid to the power side in case the there is voltage overflow from the solenoid.

== Auto-Discharge ==

The other way for the capacitors to discharge is the auto-discharger. This section is controled by either the control board, when it needs less voltage to kick with or the by the LT3757 when it has reached the maximum voltage allowed by the circutry. This discharger has much lower current transitors and large resistors that limit the discharge current. This is never used for discharging the capacitors fully as it will take longer than kicking and will release a lot of heat if the full capacitors were discharged over this section.

== 2008 Model of the 2013 Board ==

The 2013 kicker boards have redplaced out the previous models of the 2008 and 2011 boards. The 2013 board is based on the 2011 version with the addition of some updated parts and adding a voltage monitor for the capacitors. However, the 2008 board was very different. While the 2011 and 2013 kicker boards have a chip port, the 2008 boards and robots could not chip the ball. We have removed the chipping components from certain boards to avoid confusion with ports and plugs. Additionally, some of the 2008 model 2013 boards do not have voltage monitoring components because the control boards are unable to read the voltage monitor in 2008 mode

== Parts list ==

Disclaimer: Some of the parts are not used in the final kicker board, but are printed on the mini board that is removed to make room for the capacitors. The parts list can be downloaded [http://wiki.robojackets.org/mediawiki/Media%3AKicker%20parts.pdf here].

== References ==
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li>[http://en.wikipedia.org/wiki/Transformer http://en.wikipedia.org/wiki/Transformer]</li>
<li>[http://en.wikipedia.org/wiki/Inductor#Stored_energy http://en.wikipedia.org/wiki/Inductor]</li>
<li>[http://en.wikipedia.org/wiki/Flyback_converter http://en.wikipedia.org/wiki/Flyback_converter]</li>
<li>[http://cds.linear.com/docs/en/datasheet/3757Afd.pdf http://cds.linear.com/docs/en/datasheet/3757Afd.pdf]</li>
<li>[http://en.wikipedia.org/wiki/Field-programmable_gate_array http://en.wikipedia.org/wiki/Field-programmable_gate_array]</li>
<li>[http://en.wikipedia.org/wiki/Microprocessor http://en.wikipedia.org/wiki/Microprocessor]</li>
<li>[http://en.wikipedia.org/wiki/Boost_converter http://en.wikipedia.org/wiki/Boost_converter]</li>
<li>[http://en.wikipedia.org/wiki/%C4%86uk_converter http://en.wikipedia.org/wiki/%C4%86uk_converter]</li>
</ol>

[[Category:RoboCup]] [[Category:Electrical]] [[Category:Year: 2014-2015]]

RoboCup: Kicker Board 2013

2017-05-18T02:33:55Z

Rosawa3:

== Overview ==

This is an overview of all the features and concepts on the 2013 kicker board made for the RoboCup competition by the electrical team of Georgia Institute of Technology's RoboCup team. This board's purpose is to drive a high voltage, high peak current solenoid to kick the ball. This page is to be used to farmiliarize new members of RoboCup with how the kicker board works.

== Safety and Handling ==

This board uses high voltage. Be extremely careful around high voltage. It can cause considerable damage. Until you know that the capacitors are discharged, assume that they are still charged up to 250V. Check if there is a red LED lit on the back of the the kicker board. This is the death light. It is powered directly by the capacitors. If this light is on, you should not touch the board.

== Kicker Charger ==

[[File:Kicker charger.PNG|thumb|center|1200px]]

This is the kicker board's charging circutry. This allows the board to charge large capacitors up to a very high voltage. This part of the board consists of two main components: the bank capacitors and the flyback regulator. The bank capacitor is charged up to a high voltage and allows a high peak power delivery. The flyback controller is used to convert a low voltage, high current input to a high voltage, low current output.

=== Flyback Controller ===

The flyback controller that is on the board is a LT3757. This chip modulates the duty cycle of the priamry side switch based ont he feedback voltage to regulate the output voltage.

=== LT3757/Converter controller ===

The converter controller that is on the board is a LT3757. This chip manages the switching of our Buck-boost converter. When the supply loop has reached full capacity it will lock the supply loop. When the potential is transferred to the capacitors the supply loop is again unlocked. The LT3757 is an integrated circuit that uses inputs to determine precisely when to switch in order maximize power transfer. We can not do this manually or with our FPGA and CPU because of the asymptotic nature of capacitors and inductors. Unfortunately the LT3757 was designed for a resistive load, and while it can handle capacitive loads quite well there may be other chips that do it even better. We are looking at other possibilities and may improve on this component in the future.

=== Other converter methods ===

It has been suggested that other converter types may be able to charge the capacitors faster. A boost converter may allow us to create a higher voltage potential. This would allow a faster transfer from the inductor to the capacitor. The other converter that has been looked at is the cuk converter. A cuk converter might be able to allow the capacitors to be charged while other inductors are charging which would increase the rate of power transfer without raising the voltage across the capacitor. The electrical team is looking at these and other possibilities to improve on these systems in the future.

== Voltage Monitor ==

This component is covered in detail on the control board page.

[http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker]

== Kicker Trigger ==

[[File:Kicker trigger.PNG|thumb|left|600px]]

This section of the board allows the control board to release the energy stored in the capacitors into the kicker or chipper. This is done by using the TC4427 to control two high current, high voltage power transitors. These transistors will allow all of the energy stored in the capacitors to be released over the solenoid. There is a very value resistor and a diode pointing from the ground side of the solenoid to the power side in case the there is voltage overflow from the solenoid.

== Auto-Discharge ==

The other way for the capacitors to discharge is the auto-discharger. This section is controled by either the control board, when it needs less voltage to kick with or the by the LT3757 when it has reached the maximum voltage allowed by the circutry. This discharger has much lower current transitors and large resistors that limit the discharge current. This is never used for discharging the capacitors fully as it will take longer than kicking and will release a lot of heat if the full capacitors were discharged over this section.

== 2008 Model of the 2013 Board ==

The 2013 kicker boards have redplaced out the previous models of the 2008 and 2011 boards. The 2013 board is based on the 2011 version with the addition of some updated parts and adding a voltage monitor for the capacitors. However, the 2008 board was very different. While the 2011 and 2013 kicker boards have a chip port, the 2008 boards and robots could not chip the ball. We have removed the chipping components from certain boards to avoid confusion with ports and plugs. Additionally, some of the 2008 model 2013 boards do not have voltage monitoring components because the control boards are unable to read the voltage monitor in 2008 mode

== Parts list ==

Disclaimer: Some of the parts are not used in the final kicker board, but are printed on the mini board that is removed to make room for the capacitors. The parts list can be downloaded [http://wiki.robojackets.org/mediawiki/Media%3AKicker%20parts.pdf here].

== References ==
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li>[http://en.wikipedia.org/wiki/Transformer http://en.wikipedia.org/wiki/Transformer]</li>
<li>[http://en.wikipedia.org/wiki/Inductor#Stored_energy http://en.wikipedia.org/wiki/Inductor]</li>
<li>[http://en.wikipedia.org/wiki/Flyback_converter http://en.wikipedia.org/wiki/Flyback_converter]</li>
<li>[http://cds.linear.com/docs/en/datasheet/3757Afd.pdf http://cds.linear.com/docs/en/datasheet/3757Afd.pdf]</li>
<li>[http://en.wikipedia.org/wiki/Field-programmable_gate_array http://en.wikipedia.org/wiki/Field-programmable_gate_array]</li>
<li>[http://en.wikipedia.org/wiki/Microprocessor http://en.wikipedia.org/wiki/Microprocessor]</li>
<li>[http://en.wikipedia.org/wiki/Boost_converter http://en.wikipedia.org/wiki/Boost_converter]</li>
<li>[http://en.wikipedia.org/wiki/%C4%86uk_converter http://en.wikipedia.org/wiki/%C4%86uk_converter]</li>
</ol>

RCResources

2017-05-18T02:28:47Z

Rosawa3: /* General */

==Papers==
===Vision===
*http://shtylman.com/robocup_resource/vision/03icra-jim.pdf
*http://shtylman.com/robocup_resource/vision/ICRA06Lu.pdf
*http://shtylman.com/robocup_resource/vision/Vision.pdf
*http://shtylman.com/robocup_resource/vision/acra2004_visionsystem.pdf
*http://shtylman.com/robocup_resource/vision/calibration.pdf
*http://shtylman.com/robocup_resource/vision/pers-wwk2002.pdf
*http://shtylman.com/robocup_resource/vision/undistort.pdf
*http://shtylman.com/robocup_resource/vision/vass_gg_2003_lo.pdf
*[http://ieeexplore.ieee.org.www.library.gatech.edu:2048/search/selected.jsp?qry=%28a+simple+and+analytical+procedure+for+calibrating+extrinsic+camera+parameters%3Cin%3Emetadata%29&srch=1&resset=1643271&imageField.x=56&imageField.y=13&imageField=View+Selected+Items&chklist=1266651%40ieeejrns| A Simple and Analytical Procedure for Calibrating Extrinsic Camera Parameters]
:- You will need a gatech account to view this paper

===Mechanical===
*http://shtylman.com/robocup_resource/mechanical/2003ME.pdf
*http://shtylman.com/robocup_resource/mechanical/CornellRoboCupMechanicalDocumentation2004.doc
*http://shtylman.com/robocup_resource/mechanical/SotoWeitzenfeld80LARS2006.pdf
===Electrical===
*http://shtylman.com/robocup_resource/electrical/2004EEfinaldocumentation.doc
===Software===
===Control===
* [http://www.ri.cmu.edu/pub_files/pub4/koes_mary_2006_3/koes_mary_2006_3.pdf Article on robot team planning]
*http://shtylman.com/robocup_resource/control/omnidrive.pdf
*http://shtylman.com/robocup_resource/control/omnidrive player for robocup.pdf
*http://shtylman.com/robocup_resource/control/robotheal.pdf
===General===
*http://shtylman.com/robocup_resource/general/B-Smart_TDP2007.pdf
*http://shtylman.com/robocup_resource/general/EKRBTDP2007.pdf
*http://shtylman.com/robocup_resource/general/RoboCup99-03.pdf
*http://shtylman.com/robocup_resource/general/p83_yly003.pdf
*[[USOpen_notes|US Open Notes]]

==Links==
* [http://small-size.informatik.uni-bremen.de/start Small-Size League Website]
* [http://www.cs.cmu.edu/~brettb/robocup/#movies Small size resource page] - link dump, very good!!!
* [http://robocup.mae.cornell.edu/ Cornell Big Red] very good technical documentation!! Check out the ME writeups!
* [http://www.cs.cmu.edu/~robosoccer/small CMU webpage - great resource]

===General Links===
* [http://www.aaai.org/Library/Magazine/magazine-library.php The AAAI digital Library]
* [http://www.cadsoft.de/freeware.htm Eagle Cad Freeware version.]
* [http://oersted.dtu.dk/personal/mho/eagle/eagle_tut.pdf Eagle Tutorial]
* [http://oersted.dtu.dk/personal/mho/eagle/ Library of Supply pieces]
* [http://www.protoexpress.com Sierra Proto Express]
* [http://www.mae.cornell.edu/lipson/application.htm (Phill pasted this link to store so he can view it later at home)]
* [http://ccsl.mae.cornell.edu/research/selfmodels/ Research on self modeling robots]
* [http://ccsl.mae.cornell.edu/papers/DETC04_Lipson.pdf More on self-modeling robots]

[[Category: RoboCup]]
[[Category: Electrical]]
[[Category: Mechanical]]
[[Category: Software]]

RoboCup Software

2017-05-18T02:26:04Z

Rosawa3: /* Main Programs */

= Overview =

RoboCup Software encompasses all parts of the system that run on a host machine (not the robots). The entire software system is composed both of the components we play soccer and compete with as well as a sort of SDK that allows new components to be written quickly for idea and system testing.

We currently host our software project on github, so check it out: [https://github.com/RoboJackets/robocup-software https://github.com/RoboJackets/robocup-software].

= Main Programs =

;[[RoboCup Soccer|soccer]] 
:Everything after [[RoboCup_Vision|vision]] and before radio happens here.
;[[RoboCup Simulator|simulator]] 
:Simulates a game environment, including vision and radio
;[[RoboCup_Referee|sslrefbox]] 
:The standard SSL referee box for issuing referee commands to all teams
;radio 
:Radio communication with on-field robots

= Logging Utilities =

;log_viewer 
:Playback of logged data
;simple_logger 
:Records vision and referee data just like soccer does, but with no processing.
;convert_tcpdump 
:Reads vision and referee packets from a tcpdump file and generates a log file. Use with util/log_vision.

= Development =

;[[RoboCup Tips&Tricks]] 
:Some pointers on how to begin writing and debugging code.
;[[RoboCup GIT HOWTO]] 
:We currently use Git as our code management system, and this will explain how to acquire and update the code base.
;[[RoboCup Simulator Execution]] 
:How to start and configure the simulator and connect to one or two soccer playing modules, as well as the Referee Module
;[[RoboCup Live Robot Execution]] 
:How to start and run the soccer with actual robots, connect to shared vision, and receive commands from the Referee Module

= Conventions =

There are a variety of conventions used throughout the code, both to represent soccer-playing, and to maintain consistency in code development.

;[[RoboCup Field Structure]] 
:The coordinate systems and their relationship to the field
;[[RC FieldCamera|Field and Camera Information]] 
:Specifications on our cameras
[[Category:RoboCup]] [[Category:Software]] [[Category:Year: 2013-2014|Year:_2013-2014]]

RoboCup Software

2017-05-18T02:12:46Z

Rosawa3: /* Main Programs */

= Overview =

RoboCup Software encompasses all parts of the system that run on a host machine (not the robots). The entire software system is composed both of the components we play soccer and compete with as well as a sort of SDK that allows new components to be written quickly for idea and system testing.

We currently host our software project on github, so check it out: [https://github.com/RoboJackets/robocup-software https://github.com/RoboJackets/robocup-software].

= Main Programs =

;[[RoboCup Soccer|soccer]] 
:Everything after vision and before radio happens here.
;[[RoboCup Simulator|simulator]] 
:Simulates a game environment, including vision and radio
;[[RoboCup_Referee|sslrefbox]] 
:The standard SSL referee box for issuing referee commands to all teams
;radio 
:Radio communication with on-field robots

= Logging Utilities =

;log_viewer 
:Playback of logged data
;simple_logger 
:Records vision and referee data just like soccer does, but with no processing.
;convert_tcpdump 
:Reads vision and referee packets from a tcpdump file and generates a log file. Use with util/log_vision.

= Development =

;[[RoboCup Tips&Tricks]] 
:Some pointers on how to begin writing and debugging code.
;[[RoboCup GIT HOWTO]] 
:We currently use Git as our code management system, and this will explain how to acquire and update the code base.
;[[RoboCup Simulator Execution]] 
:How to start and configure the simulator and connect to one or two soccer playing modules, as well as the Referee Module
;[[RoboCup Live Robot Execution]] 
:How to start and run the soccer with actual robots, connect to shared vision, and receive commands from the Referee Module

= Conventions =

There are a variety of conventions used throughout the code, both to represent soccer-playing, and to maintain consistency in code development.

;[[RoboCup Field Structure]] 
:The coordinate systems and their relationship to the field
;[[RC FieldCamera|Field and Camera Information]] 
:Specifications on our cameras
[[Category:RoboCup]] [[Category:Software]] [[Category:Year: 2013-2014|Year:_2013-2014]]

RoboCup Software

2017-05-18T02:11:02Z

Rosawa3: /* Conventions */

= Overview =

RoboCup Software encompasses all parts of the system that run on a host machine (not the robots). The entire software system is composed both of the components we play soccer and compete with as well as a sort of SDK that allows new components to be written quickly for idea and system testing.

We currently host our software project on github, so check it out: [https://github.com/RoboJackets/robocup-software https://github.com/RoboJackets/robocup-software].

= Main Programs =

;[[RoboCup Soccer|soccer]] 
:Everything after vision and before radio happens here.
;[[RoboCup Simulator|simulator]] 
:Simulates a game environment, including vision and radio
;sslrefbox 
:The standard SSL referee box for issuing referee commands to all teams
;radio 
:Radio communication with on-field robots

= Logging Utilities =

;log_viewer 
:Playback of logged data
;simple_logger 
:Records vision and referee data just like soccer does, but with no processing.
;convert_tcpdump 
:Reads vision and referee packets from a tcpdump file and generates a log file. Use with util/log_vision.

= Development =

;[[RoboCup Tips&Tricks]] 
:Some pointers on how to begin writing and debugging code.
;[[RoboCup GIT HOWTO]] 
:We currently use Git as our code management system, and this will explain how to acquire and update the code base.
;[[RoboCup Simulator Execution]] 
:How to start and configure the simulator and connect to one or two soccer playing modules, as well as the Referee Module
;[[RoboCup Live Robot Execution]] 
:How to start and run the soccer with actual robots, connect to shared vision, and receive commands from the Referee Module

= Conventions =

There are a variety of conventions used throughout the code, both to represent soccer-playing, and to maintain consistency in code development.

;[[RoboCup Field Structure]] 
:The coordinate systems and their relationship to the field
;[[RC FieldCamera|Field and Camera Information]] 
:Specifications on our cameras
[[Category:RoboCup]] [[Category:Software]] [[Category:Year: 2013-2014|Year:_2013-2014]]

RoboCup Software

2017-05-18T02:10:32Z

Rosawa3: /* Development */

= Overview =

RoboCup Software encompasses all parts of the system that run on a host machine (not the robots). The entire software system is composed both of the components we play soccer and compete with as well as a sort of SDK that allows new components to be written quickly for idea and system testing.

We currently host our software project on github, so check it out: [https://github.com/RoboJackets/robocup-software https://github.com/RoboJackets/robocup-software].

= Main Programs =

;[[RoboCup Soccer|soccer]] 
:Everything after vision and before radio happens here.
;[[RoboCup Simulator|simulator]] 
:Simulates a game environment, including vision and radio
;sslrefbox 
:The standard SSL referee box for issuing referee commands to all teams
;radio 
:Radio communication with on-field robots

= Logging Utilities =

;log_viewer 
:Playback of logged data
;simple_logger 
:Records vision and referee data just like soccer does, but with no processing.
;convert_tcpdump 
:Reads vision and referee packets from a tcpdump file and generates a log file. Use with util/log_vision.

= Development =

;[[RoboCup Tips&Tricks]] 
:Some pointers on how to begin writing and debugging code.
;[[RoboCup GIT HOWTO]] 
:We currently use Git as our code management system, and this will explain how to acquire and update the code base.
;[[RoboCup Simulator Execution]] 
:How to start and configure the simulator and connect to one or two soccer playing modules, as well as the Referee Module
;[[RoboCup Live Robot Execution]] 
:How to start and run the soccer with actual robots, connect to shared vision, and receive commands from the Referee Module

= Conventions =

There are a variety of conventions used throughout the code, both to represent soccer-playing, and to maintain consistency in code development.

;[[RoboCup Robot Identification]] 
:The means by which specific robots and field entities can be identified
;[[RoboCup Field Structure]] 
:The coordinate systems and their relationship to the field
;[[RC FieldCamera|Field and Camera Information]] 
:Specifications on our cameras
[[Category:RoboCup]] [[Category:Software]] [[Category:Year: 2013-2014|Year:_2013-2014]]

RoboCup System Archive

2017-05-18T02:09:06Z

Rosawa3: /* System Archive */

== System Archive ==
==== 2014 ====
* [[RoboCup 2014 System Outline]]

Subteams
:* [[RoboCup_Electrical_2014|Electrical System]]
:* [[RoboCup_Software_2014|Software System]]
:* [[RoboCup_Mechanical_2014|Mechanical System]]

==== 2013 ====
* [[RoboCup 2013 System Outline]]

Subteams
:* [[RoboCup_Electrical_2013|Electrical System]]
:* [[RoboCup_Software_2013|Software System]]
:* [[RoboCup_Mechanical_2013|Mechanical System]]

==== 2012 ====
* [[RoboCup 2012 System Outline]]
* [http://wiki.robojackets.org/images/2/2d/RJRC_2012_TDP.pdf 2012 TDP]
Subteams
:* [[RoboCup_Electrical_2012|Electrical System]]
:* [[RoboCup_Software_2012|Software System]]
:* [[RoboCupMechanical|Mechanical System]]

==== 2011 ====
* [[RoboCup 2011 System Outline]]
* [http://wiki.robojackets.org/images/4/4e/RJRC_2011_TDP.pdf 2011 TDP]
Qualification Video
:* [http://www.robojackets.org/RC/robojackets-robocup2011qual.mkv RoboJackets Server (MKV format)]
:* [http://www.robojackets.org/RC/robojackets-robocup2011qual.wmv RoboJackets Server (WMV format)]
:* [http://www.youtube.com/watch?v=nnZMUu3QT6Y Youtube]
Subteams
:* [[RoboCup_Electrical_2011|Electrical System]]
:* [[RoboCup_Software_2011|Software System]]
:* [[RoboCupMechanical|Mechanical System]]

==== 2010 ====
* [[RoboCup_Overview_2010 | RoboCup 2010 System Outline]]
* [http://wiki.robojackets.org/images/a/af/RJRC_2010_TDP.pdf 2010 TDP]
* [[RoboCupTravel2010 | Travel]]
* [[2010 US Open]]
Subteams
:* [[RoboCup_Electrical_2010|Electrical System]]
:* [[RoboCup_Software_2010|Software System]]
:* [[RoboCupMechanical|Mechanical System]]

==== 2009 ====
* [[RCMeetingMinutes | RoboCup 2009 System Outline]]
* [[RoboCup Meeting Minutes | Meeting Minutes]]
Subteams
* [[RoboCup_Electrical_2009|Electrical System]]
** [[RoboCup_Radio_2009|Radio Communication]]
* [[RoboCup_Software_2009|Software System]]
* [[RoboCupMechanical|Mechanical System]]
**[[RoboCupMechanicalDev2009|Mechanical Prototype Development]]

==== 2008 ====
*[[RoboCup 2008 System Outline]]
*[http://wiki.robojackets.org/images/1/14/RJRC_2008_TDP.pdf 2008 TDP]
*[[RC08Travel|Personal Travel Costs and Info]]
*[[RC08TravelLog|Team Travel Logistics and Costs]]
Subteams
:*[[RoboCup_Electrical_2008|Electrical System]]
:*[[RoboCupMechanical2008|Mechanical System]]
:*[[RoboCupSoftware|Software System]]
::*[[RC08SWRoadMap|Short Term Software Roadmap]]
::*[[Development Tools]]
::*[[RoboCup Coding Style|Coding Style]]
::*[[Code Examples]]

==== 2007 ====
*[http://wiki.robojackets.org/images/c/c1/RJRC_2007_TDP.pdf 2007 TDP]
Subteams
:* [[RoboCupElectrical2007|Electrical System Information]]
::* [[RCpartsSample|How to Sample Parts for RoboCup]]
:* [[RoboCupSoftware2007|Software System Information]]
:* [[RoboCupMechanical2007|Mechanical System Information]]
:* [[RobocupVision|Vision System Information]]
::* [[RCVisSoftware|Robocup Image Processing]]
::* [[RCCamera|Robocup Image Acquisition]]

[[Category: RoboCup]]

RoboCup System Archive

2017-05-18T02:08:01Z

Rosawa3: /* 2008 */

== System Archive ==
==== 2013 ====
* [[RoboCup 2013 System Outline]]

Subteams
:* [[RoboCup_Electrical_2013|Electrical System]]
:* [[RoboCup_Software_2013|Software System]]
:* [[RoboCup_Mechanical_2013|Mechanical System]]

==== 2012 ====
* [[RoboCup 2012 System Outline]]
* [http://wiki.robojackets.org/images/2/2d/RJRC_2012_TDP.pdf 2012 TDP]
Subteams
:* [[RoboCup_Electrical_2012|Electrical System]]
:* [[RoboCup_Software_2012|Software System]]
:* [[RoboCupMechanical|Mechanical System]]

==== 2011 ====
* [[RoboCup 2011 System Outline]]
* [http://wiki.robojackets.org/images/4/4e/RJRC_2011_TDP.pdf 2011 TDP]
Qualification Video
:* [http://www.robojackets.org/RC/robojackets-robocup2011qual.mkv RoboJackets Server (MKV format)]
:* [http://www.robojackets.org/RC/robojackets-robocup2011qual.wmv RoboJackets Server (WMV format)]
:* [http://www.youtube.com/watch?v=nnZMUu3QT6Y Youtube]
Subteams
:* [[RoboCup_Electrical_2011|Electrical System]]
:* [[RoboCup_Software_2011|Software System]]
:* [[RoboCupMechanical|Mechanical System]]

==== 2010 ====
* [[RoboCup_Overview_2010 | RoboCup 2010 System Outline]]
* [http://wiki.robojackets.org/images/a/af/RJRC_2010_TDP.pdf 2010 TDP]
* [[RoboCupTravel2010 | Travel]]
* [[2010 US Open]]
Subteams
:* [[RoboCup_Electrical_2010|Electrical System]]
:* [[RoboCup_Software_2010|Software System]]
:* [[RoboCupMechanical|Mechanical System]]

==== 2009 ====
* [[RCMeetingMinutes | RoboCup 2009 System Outline]]
* [[RoboCup Meeting Minutes | Meeting Minutes]]
Subteams
* [[RoboCup_Electrical_2009|Electrical System]]
** [[RoboCup_Radio_2009|Radio Communication]]
* [[RoboCup_Software_2009|Software System]]
* [[RoboCupMechanical|Mechanical System]]
**[[RoboCupMechanicalDev2009|Mechanical Prototype Development]]

==== 2008 ====
*[[RoboCup 2008 System Outline]]
*[http://wiki.robojackets.org/images/1/14/RJRC_2008_TDP.pdf 2008 TDP]
*[[RC08Travel|Personal Travel Costs and Info]]
*[[RC08TravelLog|Team Travel Logistics and Costs]]
Subteams
:*[[RoboCup_Electrical_2008|Electrical System]]
:*[[RoboCupMechanical2008|Mechanical System]]
:*[[RoboCupSoftware|Software System]]
::*[[RC08SWRoadMap|Short Term Software Roadmap]]
::*[[Development Tools]]
::*[[RoboCup Coding Style|Coding Style]]
::*[[Code Examples]]

==== 2007 ====
*[http://wiki.robojackets.org/images/c/c1/RJRC_2007_TDP.pdf 2007 TDP]
Subteams
:* [[RoboCupElectrical2007|Electrical System Information]]
::* [[RCpartsSample|How to Sample Parts for RoboCup]]
:* [[RoboCupSoftware2007|Software System Information]]
:* [[RoboCupMechanical2007|Mechanical System Information]]
:* [[RobocupVision|Vision System Information]]
::* [[RCVisSoftware|Robocup Image Processing]]
::* [[RCCamera|Robocup Image Acquisition]]

[[Category: RoboCup]]

People with Keys

2017-03-15T01:36:48Z

Rosawa3: key transfer

'''These people have keys to the RoboJackets shop area. ''' See [[Shop_Keys|Shop Keys]] for details on key assignments.

{| class="wikitable sortable"
|-
! Key Number
! Assigned To
|-
| 3SB6: 1
| [[User:Rmartin|Ryan Martin]]
|-
| 3SB6: 4
| Kelvin Chong
|-
| 3SB6: 5
| [[User:Petersonev|Evan Peterson]]
|-
| 3SB6: 7
| Jonathan Spalten
|-
| 3SB6: 8
| [[User:Sastorer3|Sarah Storer]]
|-
| 3SB6: 9
| [[User:Biachonkov3|Boris Iachonkov]]
|-
| 3SB6:12
| [[User:Radebayo|Ransomed Adebayo]]
|-
| 3SB6:14
| Sameer Naeem
|-
| 3SB6:15
| [[User:S|Sean Csukas]]
|-
| 3SB6:18
| [[User:Kberzinch|Kristaps Berzinch]]
|-
| 3SB6:19
| Daniil Budanov
|-
| 3SB6:20
| Satoshi Yuki
|-
| 3SB6:21
| [[User:Jkamat|Jay Kamat]]
|-
| 3SB6:22
| Noah Daugherty
|-
| 3SB6:23
| [[User:Dchoi|Daniel Choi]]
|-
| 3SB6:24
| [[User:Rstrat|Ryan Strat]]
|-
| 3SB6:29
| [[User:Mbarulic|Matthew Barulic]]
|-
| 3SB6:31
|[[User:Stewathia3|Sanjana Tewathia]]
|}

RoboCup: Competition 2014

2017-03-04T01:18:59Z

Rosawa3: /* SSL Robot Gallery */ ThunderBots whereever fixable

[[File:RoboCup-Competition-2014 Venue001.jpg|thumb|right|420px|The RoboCup competition's venue area in João Pessoa, Brazil.]]

This page is a compilation of the documentation, images, and other forms of information obtained at the RoboCup 2014 SSL competition in [http://en.wikipedia.org/wiki/Jo%C3%A3o_Pessoa,_Para%C3%ADba João Pessoa], Brazil.

__TOC__

== SSL Robot Gallery ==

The gallery below shows various teams that competed in the 2014 RoboCup SSL league.

<gallery align="center">
File:RoboCup-Competition-2014 ACES001.jpg | ACES
File:RoboCup-Competition-2014 ACES002.jpg | ACES
File:RoboCup-Competition-2014 ACES003.jpg | ACES
File:RoboCup-Competition-2014 ACES004.jpg | ACES
File:RoboCup-Competition-2014 ACES005.jpg | ACES
File:RoboCup-Competition-2014 ACES006.jpg | ACES
File:RoboCup-Competition-2014 CMDragons001.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons002.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons003.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons004.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons005.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons006.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons007.jpg | CMDragons
File:RoboCup-Competition-2014 ER-Force002.jpg | ER-Force
File:RoboCup-Competition-2014 ER-Force001.jpg | ER-Force
File:RoboCup-Competition-2014 Immortals001.jpg | Immortals
File:RoboCup-Competition-2014 Immortals002.jpg | Immortals
File:RoboCup-Competition-2014 Immortals003.jpg | Immortals
File:RoboCup-Competition-2014 Immortals004.jpg | Immortals
File:RoboCup-Competition-2014 KIKS001.jpg | KIKS
File:RoboCup-Competition-2014 KIKS002.jpg | KIKS
File:RoboCup-Competition-2014 KIKS003.jpg | KIKS
<-- File:RoboCup-Competition-2014 KIKS004.jpg | KIKS (This file number was skipped by accident when uploading)!-->
File:RoboCup-Competition-2014 KIKS005.jpg | KIKS
File:RoboCup-Competition-2014 KIKS006.jpg | KIKS
File:RoboCup-Competition-2014 KIKS007.jpg | KIKS
File:RoboCup-Competition-2014 KIKS008.jpg | KIKS
File:RoboCup-Competition-2014 KIKS009.jpg | KIKS
File:RoboCup-Competition-2014 KIKS010.jpg | KIKS
File:RoboCup-Competition-2014 KIKS011.jpg | KIKS
File:RoboCup-Competition-2014 KIKS012.jpg | KIKS
File:RoboCup-Competition-2014 KIKS013.jpg | KIKS
File:RoboCup-Competition-2014 KIKS014.jpg | KIKS
File:RoboCup-Competition-2014 KIKS015.jpg | KIKS
File:RoboCup-Competition-2014 KIKS016.jpg | KIKS
File:RoboCup-Competition-2014 KIKS017.jpg | KIKS
File:RoboCup-Competition-2014 KIKS018.jpg | KIKS
File:RoboCup-Competition-2014 KIKS019.jpg | KIKS
File:FileRoboCup-Competition-2014 MRL020.jpg | MRL
File:FileRoboCup-Competition-2014 MRL019.jpg | MRL
File:FileRoboCup-Competition-2014 MRL018.jpg | MRL
File:FileRoboCup-Competition-2014 MRL017.jpg | MRL
File:FileRoboCup-Competition-2014 MRL016.jpg | MRL
File:FileRoboCup-Competition-2014 MRL015.jpg | MRL
File:FileRoboCup-Competition-2014 MRL014.jpg | MRL
File:FileRoboCup-Competition-2014 MRL013.jpg | MRL
File:FileRoboCup-Competition-2014 MRL012.jpg | MRL
File:FileRoboCup-Competition-2014_MRL011.jpg | MRL
File:RoboCup-Competition-2014 MRL010.jpg | MRL
File:RoboCup-Competition-2014 MRL009.jpg | MRL
File:RoboCup-Competition-2014 MRL008.jpg | MRL
File:RoboCup-Competition-2014 MRL007.jpg | MRL
File:RoboCup-Competition-2014 MRL006.jpg | MRL
File:RoboCup-Competition-2014 MRL005.jpg | MRL
File:RoboCup-Competition-2014 MRL004.jpg | MRL
File:RoboCup-Competition-2014 MRL003.jpg | MRL
File:RoboCup-Competition-2014 MRL002.jpg | MRL
File:RoboCup-Competition-2014 MRL001.jpg | MRL
File:RoboCup-Competition-2014 RoboDragons001.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons002.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons003.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons004.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons005.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons006.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons007.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons008.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons009.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons010.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons011.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons012.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons013.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons014.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons015.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons016.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons017.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons018.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons019.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons020.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons021.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons022.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons023.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons024.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons025.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons026.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons027.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboIME001.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME002.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME003.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME004.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME005.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME006.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME007.jpg | RoboIME
File:RoboCup-Competition-2014 RoboJackets001.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets002.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets003.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets004.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets005.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets006.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets007.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets008.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets009.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets010.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets011.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets012.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets013.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets014.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets015.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets016.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets017.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets018.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets019.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets020.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets021.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets022.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets023.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets024.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets025.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets026.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets027.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets028.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets029.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets030.jpg | RoboJackets
File:RoboCup-Competition-2014 STOxs001.jpg | STOx's
File:RoboCup-Competition-2014 STOxs002.jpg | STOx's
File:RoboCup-Competition-2014 STOxs003.jpg | STOx's
File:RoboCup-Competition-2014 STOxs004.jpg | STOx's
File:RoboCup-Competition-2014 STOxs005.jpg | STOx's
File:RoboCup-Competition-2014 STOxs006.jpg | STOx's
File:RoboCup-Competition-2014 STOxs007.jpg | STOx's
File:RoboCup-Competition-2014 STOxs008.jpg | STOx's
File:RoboCup-Competition-2014 STOxs009.jpg | STOx's
File:RoboCup-Competition-2014 STOxs010.jpg | STOx's
File:RoboCup-Competition-2014 STOxs011.jpg | STOx's
File:RoboCup-Competition-2014 STOxs012.jpg | STOx's
File:RoboCup-Competition-2014 STOxs013.jpg | STOx's
File:RoboCup-Competition-2014 STOxs014.jpg | STOx's
File:RoboCup-Competition-2014 Thunderbolts001.jpg | Thunderbots
File:RoboCup-Competition-2014 Thunderbolts002.jpg | Thunderbots
File:RoboCup-Competition-2014 Thunderbolts003.jpg | Thunderbots
File:RoboCup-Competition-2014 Thunderbolts004.jpg | Thunderbots
File:RoboCup-Competition-2014 Thunderbolts005.jpg | Thunderbots
File:RoboCup-Competition-2014 Thunderbolts006.jpg | Thunderbots
File:RoboCup-Competition-2014 Thunderbolts007.jpg | Thunderbots
File:RoboCup-Competition-2014 Thunderbolts008.jpg | Thunderbots
File:RoboCup-Competition-2014 Thunderbolts009.jpg | Thunderbots
File:RoboCup-Competition-2014 Thunderbolts010.jpg | Thunderbots
File:RoboCup-Competition-2014 Thunderbolts011.jpg | Thunderbots
File:RoboCup-Competition-2014 TigersMannheim012.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim011.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim010.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim009.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim008.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim007.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim006.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim005.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim004.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim003.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim002.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim001.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 WarthogRobotics001.jpg | Warthog Robotics
</gallery>

== SSL Team Notes ==

The following table of information was documented at the competition's venue.

Much of the information is incomplete because of the limited time at competition. The cells that contain only "--" indicate that no information was documented for that team's category. Blank cells indicate 1) an error occurred from transferring this information to the wiki or 2) the information was lost from a wiki edit.

{| class="wikitable"
|- style="height:20px;"
! id="0R0" style="height: 32px; white-space: nowrap; vertical-align: middle;" class="row-headers-background" |
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RoboDragons'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Warthog Robotics'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Thunderbolts'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Tigers Mannheim'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''NEUislanders'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''MRL'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RoboFEI'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Immortals'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''KIKS'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''ZJUNlict'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''ER-Force'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RoboIME'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''UaiSoccer'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''CMDragons'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Parsian'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''ACES'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''STOx's'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''BRocks'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Cyrus'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Eagle Knights'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''EMEnents'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''FURGbot'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''MCT Susanoo Logics'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''IRSS Deluxe'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RFC Cambridge'''</big>
! class="s2" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''KN2C'''</big>
|- style="height:25px;"
! id="0R0" style="height: 32px;" class="row-headers-background" |
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Japan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Canada''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Germany''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Cyprus''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Japan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''China''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Germany''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''United States''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Pakistan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Colombia''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Turkey''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Mexico''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Pakistan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Japan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Chile''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''United States''</var>
! class="s4" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
|- style="height:25px;"
| class="s5" dir="ltr" | '''Board Types/Qty'''
| class="s6" dir="ltr" | 1 board - outsourced
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | see Misc. Notes
| class="s6" dir="ltr" | custom boards
| class="s6" dir="ltr" | 1 main board; 1 small daughter board for ball sense
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | custom (3 total: control, kicker, power)
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Motor Capacitor(s)'''
| class="s8" dir="ltr" | none
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 1 large electrolytic capacitor
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | yes
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Antenna'''
| class="s6" dir="ltr" | see reference pictures
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | radio is from Microchip; they moved away from XBee
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | XBee
| class="s6" dir="ltr" | NRF
| class="s6" dir="ltr" | NRF
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s9" dir="ltr" | --
| class="s6" dir="ltr" | 2.5GHz
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | NRF 2401
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | NRF
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Microcotroller/FPGA'''
| class="s8" dir="ltr" | 4-5 chips; definitely had MCU and FPGA on board
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | STM32F4; ARM Cortex
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Atmel 312
| class="s8" dir="ltr" | Cyclone I FPGA, NXP Microcontroller (PN: LPC2378FBD144)
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Power Capacitor(s)'''
| class="s6" dir="ltr" | 2 x (250V, 2200μF)
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | total of 4000μF; voltage unknown
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | 2 large capacitors
| class="s6" dir="ltr" | 2 x (200V, 2700μF)
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | 4x 1200μF @ 200V
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Motor Power'''
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | 50W; removed standard plug and soldered wires directly
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | DC gearmotors
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Motor Gear Ratio (approx.)'''
| class="s6" dir="ltr" | ~1:2
| class="s6" dir="ltr" | 1:6
| class="s6" dir="ltr" | ~1:2
| class="s6" dir="ltr" | ~1:2
| class="s6" dir="ltr" | ~1:3
| class="s6" dir="ltr" | 1:3.6
| class="s6" dir="ltr" | dampened
| class="s6" dir="ltr" | ~1/3
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | 1:4
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~1:3
| class="s6" dir="ltr" | ~1:3
| class="s6" dir="ltr" | ~1/2.5?
| class="s6" dir="ltr" | 1:3.6
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Dribbler'''
| class="s8" dir="ltr" | dampened lower pivot; spring back via rubber; +5/8" OD; motor PN: 433326
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | diagonal sliding rail, clear polyurethane dribbler; ~5/8"; 3/2 ratio
| class="s8" dir="ltr" | ~1/2" OD; two separate rubber pieces to center ball; 2/1 ratio
| class="s8" dir="ltr" | undampened; 1/2" squishy foam/rubber; Also have concave dribbler but said it was untested
| class="s8" dir="ltr" | heavily dampened; lower pivot; 5/8" OD
| class="s8" dir="ltr" | 5/8" OD; 1:3 ratio; belt drive; dampened upper pivot
| class="s8" dir="ltr" | ~5/8" OD, damped, lower pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 1/2", damped, ~3/2 ratio
| class="s8" dir="ltr" | rubber; 5/8" OD; ~3/2 ratio; dampened lower pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 5/8" OD; squishy ruber; dampened top pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 5/8" OD, dampened lower pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Mouth Width'''
| class="s6" dir="ltr" | ~3.125"
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~2.4"
| class="s6" dir="ltr" | not blocked; open design; ~2.75" chipper plate
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~3.125"
| class="s6" dir="ltr" | ~2.5"
| class="s6" dir="ltr" | --
|
| class="s6" dir="ltr" | ~3.125
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~3.25"
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Kicker Solenoid'''
| class="s8" dir="ltr" | Flat
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | small cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Cylindrical
| class="s8" dir="ltr" | cylindrical; 7/8" OD
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Flat
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Chipper Solenoid'''
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Flat; pulls diagonally downward
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | cylindrical
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Cylindrical
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Shell'''
| class="s8" dir="ltr" | carbon fiber exterior; plastic top with stick on dots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | plastic sheet, colors taped on top; screws sticking up for alignment
| class="s8" dir="ltr" | plastic sheet for old ones; separate top section; screws sticking up for alignment
| class="s8" dir="ltr" | plastic top only
| class="s8" dir="ltr" | milled from single block of plastic; Significant amount of material is milled away
| class="s8" dir="ltr" | carbon fiber; 3 layers; flexible & rugged; possible radio interference; also uses a standard plastic sheet
| class="s8" dir="ltr" | Plastic wrapped with a separate top piece glued onto it
| class="s8" dir="ltr" | Looked to be casted in a plastic-type resin/epoxy (their shell had small bubbles in it that are usually seen n casted objects)
| class="s8" dir="ltr" | Plastic shell with paper top piece
| class="s8" dir="ltr" | magnetic top piece; wrapped plastic sheet for sides
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | plastic top
| class="s8" dir="ltr" | fiberglass; stick on dots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Plastic sheet wrapped around, separate paper top section for dots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Motor Driver/Configuration'''
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | similar to our 2014 proto
| class="s6" dir="ltr" | off the shelf
| class="s6" dir="ltr" | 3 drivers, 3 fets, and mystery chip on every motor; 100K between gate and source; see pictures for exact details
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | L6240 chip
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:86px;"
| class="s10" dir="ltr" | '''Misc. Notes'''
| class="s8" dir="ltr" | no hardware team; electronics outsourced to SMATS; robots are $10K each; they have 12 robots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | all electronics are open source
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | they said they never replace parts during competition; they print boards every year. Email for contacting electrical lead: hosseinikia.adel@gmail.com
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | uses magnetic encoders (PN: AS4050) that have 10-bit resolution
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | the team said that the best electrical team were the tigers
| class="s8" dir="ltr" | contact: awaisazhar84@yahoo.com (M. Awais Azhar); their university was founded by several GT graduates
| class="s8" dir="ltr" | their electrical boards are printed locally in Colombia. Ball sensors are held on by screwed in U-blocks
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|}

[[Category:RoboCup]]
[[Category:Electrical]]
[[Category:Mechanical]]
[[Category:Year: 2013-2014]]

RoboCup: Competition 2014

2017-03-03T22:33:38Z

Rosawa3: /* SSL Team Notes */ content fix

[[File:RoboCup-Competition-2014 Venue001.jpg|thumb|right|420px|The RoboCup competition's venue area in João Pessoa, Brazil.]]

This page is a compilation of the documentation, images, and other forms of information obtained at the RoboCup 2014 SSL competition in [http://en.wikipedia.org/wiki/Jo%C3%A3o_Pessoa,_Para%C3%ADba João Pessoa], Brazil.

__TOC__

== SSL Robot Gallery ==

The gallery below shows various teams that competed in the 2014 RoboCup SSL league.

<gallery align="center">
File:RoboCup-Competition-2014 ACES001.jpg | ACES
File:RoboCup-Competition-2014 ACES002.jpg | ACES
File:RoboCup-Competition-2014 ACES003.jpg | ACES
File:RoboCup-Competition-2014 ACES004.jpg | ACES
File:RoboCup-Competition-2014 ACES005.jpg | ACES
File:RoboCup-Competition-2014 ACES006.jpg | ACES
File:RoboCup-Competition-2014 CMDragons001.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons002.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons003.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons004.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons005.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons006.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons007.jpg | CMDragons
File:RoboCup-Competition-2014 ER-Force002.jpg | ER-Force
File:RoboCup-Competition-2014 ER-Force001.jpg | ER-Force
File:RoboCup-Competition-2014 Immortals001.jpg | Immortals
File:RoboCup-Competition-2014 Immortals002.jpg | Immortals
File:RoboCup-Competition-2014 Immortals003.jpg | Immortals
File:RoboCup-Competition-2014 Immortals004.jpg | Immortals
File:RoboCup-Competition-2014 KIKS001.jpg | KIKS
File:RoboCup-Competition-2014 KIKS002.jpg | KIKS
File:RoboCup-Competition-2014 KIKS003.jpg | KIKS
<-- File:RoboCup-Competition-2014 KIKS004.jpg | KIKS (This file number was skipped by accident when uploading)!-->
File:RoboCup-Competition-2014 KIKS005.jpg | KIKS
File:RoboCup-Competition-2014 KIKS006.jpg | KIKS
File:RoboCup-Competition-2014 KIKS007.jpg | KIKS
File:RoboCup-Competition-2014 KIKS008.jpg | KIKS
File:RoboCup-Competition-2014 KIKS009.jpg | KIKS
File:RoboCup-Competition-2014 KIKS010.jpg | KIKS
File:RoboCup-Competition-2014 KIKS011.jpg | KIKS
File:RoboCup-Competition-2014 KIKS012.jpg | KIKS
File:RoboCup-Competition-2014 KIKS013.jpg | KIKS
File:RoboCup-Competition-2014 KIKS014.jpg | KIKS
File:RoboCup-Competition-2014 KIKS015.jpg | KIKS
File:RoboCup-Competition-2014 KIKS016.jpg | KIKS
File:RoboCup-Competition-2014 KIKS017.jpg | KIKS
File:RoboCup-Competition-2014 KIKS018.jpg | KIKS
File:RoboCup-Competition-2014 KIKS019.jpg | KIKS
File:FileRoboCup-Competition-2014 MRL020.jpg | MRL
File:FileRoboCup-Competition-2014 MRL019.jpg | MRL
File:FileRoboCup-Competition-2014 MRL018.jpg | MRL
File:FileRoboCup-Competition-2014 MRL017.jpg | MRL
File:FileRoboCup-Competition-2014 MRL016.jpg | MRL
File:FileRoboCup-Competition-2014 MRL015.jpg | MRL
File:FileRoboCup-Competition-2014 MRL014.jpg | MRL
File:FileRoboCup-Competition-2014 MRL013.jpg | MRL
File:FileRoboCup-Competition-2014 MRL012.jpg | MRL
File:FileRoboCup-Competition-2014_MRL011.jpg | MRL
File:RoboCup-Competition-2014 MRL010.jpg | MRL
File:RoboCup-Competition-2014 MRL009.jpg | MRL
File:RoboCup-Competition-2014 MRL008.jpg | MRL
File:RoboCup-Competition-2014 MRL007.jpg | MRL
File:RoboCup-Competition-2014 MRL006.jpg | MRL
File:RoboCup-Competition-2014 MRL005.jpg | MRL
File:RoboCup-Competition-2014 MRL004.jpg | MRL
File:RoboCup-Competition-2014 MRL003.jpg | MRL
File:RoboCup-Competition-2014 MRL002.jpg | MRL
File:RoboCup-Competition-2014 MRL001.jpg | MRL
File:RoboCup-Competition-2014 RoboDragons001.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons002.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons003.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons004.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons005.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons006.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons007.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons008.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons009.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons010.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons011.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons012.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons013.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons014.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons015.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons016.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons017.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons018.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons019.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons020.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons021.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons022.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons023.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons024.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons025.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons026.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons027.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboIME001.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME002.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME003.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME004.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME005.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME006.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME007.jpg | RoboIME
File:RoboCup-Competition-2014 RoboJackets001.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets002.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets003.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets004.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets005.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets006.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets007.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets008.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets009.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets010.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets011.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets012.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets013.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets014.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets015.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets016.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets017.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets018.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets019.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets020.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets021.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets022.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets023.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets024.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets025.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets026.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets027.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets028.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets029.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets030.jpg | RoboJackets
File:RoboCup-Competition-2014 STOxs001.jpg | STOx's
File:RoboCup-Competition-2014 STOxs002.jpg | STOx's
File:RoboCup-Competition-2014 STOxs003.jpg | STOx's
File:RoboCup-Competition-2014 STOxs004.jpg | STOx's
File:RoboCup-Competition-2014 STOxs005.jpg | STOx's
File:RoboCup-Competition-2014 STOxs006.jpg | STOx's
File:RoboCup-Competition-2014 STOxs007.jpg | STOx's
File:RoboCup-Competition-2014 STOxs008.jpg | STOx's
File:RoboCup-Competition-2014 STOxs009.jpg | STOx's
File:RoboCup-Competition-2014 STOxs010.jpg | STOx's
File:RoboCup-Competition-2014 STOxs011.jpg | STOx's
File:RoboCup-Competition-2014 STOxs012.jpg | STOx's
File:RoboCup-Competition-2014 STOxs013.jpg | STOx's
File:RoboCup-Competition-2014 STOxs014.jpg | STOx's
File:RoboCup-Competition-2014 Thunderbolts001.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts002.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts003.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts004.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts005.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts006.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts007.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts008.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts009.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts010.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts011.jpg | Thunderbolts
File:RoboCup-Competition-2014 TigersMannheim012.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim011.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim010.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim009.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim008.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim007.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim006.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim005.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim004.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim003.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim002.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim001.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 WarthogRobotics001.jpg | Warthog Robotics
</gallery>

== SSL Team Notes ==

The following table of information was documented at the competition's venue.

Much of the information is incomplete because of the limited time at competition. The cells that contain only "--" indicate that no information was documented for that team's category. Blank cells indicate 1) an error occurred from transferring this information to the wiki or 2) the information was lost from a wiki edit.

{| class="wikitable"
|- style="height:20px;"
! id="0R0" style="height: 32px; white-space: nowrap; vertical-align: middle;" class="row-headers-background" |
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RoboDragons'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Warthog Robotics'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Thunderbolts'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Tigers Mannheim'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''NEUislanders'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''MRL'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RoboFEI'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Immortals'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''KIKS'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''ZJUNlict'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''ER-Force'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RoboIME'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''UaiSoccer'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''CMDragons'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Parsian'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''ACES'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''STOx's'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''BRocks'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Cyrus'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Eagle Knights'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''EMEnents'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''FURGbot'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''MCT Susanoo Logics'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''IRSS Deluxe'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RFC Cambridge'''</big>
! class="s2" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''KN2C'''</big>
|- style="height:25px;"
! id="0R0" style="height: 32px;" class="row-headers-background" |
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Japan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Canada''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Germany''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Cyprus''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Japan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''China''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Germany''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''United States''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Pakistan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Colombia''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Turkey''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Mexico''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Pakistan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Japan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Chile''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''United States''</var>
! class="s4" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
|- style="height:25px;"
| class="s5" dir="ltr" | '''Board Types/Qty'''
| class="s6" dir="ltr" | 1 board - outsourced
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | see Misc. Notes
| class="s6" dir="ltr" | custom boards
| class="s6" dir="ltr" | 1 main board; 1 small daughter board for ball sense
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | custom (3 total: control, kicker, power)
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Motor Capacitor(s)'''
| class="s8" dir="ltr" | none
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 1 large electrolytic capacitor
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | yes
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Antenna'''
| class="s6" dir="ltr" | see reference pictures
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | radio is from Microchip; they moved away from XBee
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | XBee
| class="s6" dir="ltr" | NRF
| class="s6" dir="ltr" | NRF
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s9" dir="ltr" | --
| class="s6" dir="ltr" | 2.5GHz
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | NRF 2401
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | NRF
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Microcotroller/FPGA'''
| class="s8" dir="ltr" | 4-5 chips; definitely had MCU and FPGA on board
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | STM32F4; ARM Cortex
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Atmel 312
| class="s8" dir="ltr" | Cyclone I FPGA, NXP Microcontroller (PN: LPC2378FBD144)
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Power Capacitor(s)'''
| class="s6" dir="ltr" | 2 x (250V, 2200μF)
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | total of 4000μF; voltage unknown
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | 2 large capacitors
| class="s6" dir="ltr" | 2 x (200V, 2700μF)
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | 4x 1200μF @ 200V
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Motor Power'''
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | 50W; removed standard plug and soldered wires directly
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | DC gearmotors
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Motor Gear Ratio (approx.)'''
| class="s6" dir="ltr" | ~1:2
| class="s6" dir="ltr" | 1:6
| class="s6" dir="ltr" | ~1:2
| class="s6" dir="ltr" | ~1:2
| class="s6" dir="ltr" | ~1:3
| class="s6" dir="ltr" | 1:3.6
| class="s6" dir="ltr" | dampened
| class="s6" dir="ltr" | ~1/3
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | 1:4
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~1:3
| class="s6" dir="ltr" | ~1:3
| class="s6" dir="ltr" | ~1/2.5?
| class="s6" dir="ltr" | 1:3.6
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Dribbler'''
| class="s8" dir="ltr" | dampened lower pivot; spring back via rubber; +5/8" OD; motor PN: 433326
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | diagonal sliding rail, clear polyurethane dribbler; ~5/8"; 3/2 ratio
| class="s8" dir="ltr" | ~1/2" OD; two separate rubber pieces to center ball; 2/1 ratio
| class="s8" dir="ltr" | undampened; 1/2" squishy foam/rubber; Also have concave dribbler but said it was untested
| class="s8" dir="ltr" | heavily dampened; lower pivot; 5/8" OD
| class="s8" dir="ltr" | 5/8" OD; 1:3 ratio; belt drive; dampened upper pivot
| class="s8" dir="ltr" | ~5/8" OD, damped, lower pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 1/2", damped, ~3/2 ratio
| class="s8" dir="ltr" | rubber; 5/8" OD; ~3/2 ratio; dampened lower pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 5/8" OD; squishy ruber; dampened top pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 5/8" OD, dampened lower pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Mouth Width'''
| class="s6" dir="ltr" | ~3.125"
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~2.4"
| class="s6" dir="ltr" | not blocked; open design; ~2.75" chipper plate
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~3.125"
| class="s6" dir="ltr" | ~2.5"
| class="s6" dir="ltr" | --
|
| class="s6" dir="ltr" | ~3.125
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~3.25"
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Kicker Solenoid'''
| class="s8" dir="ltr" | Flat
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | small cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Cylindrical
| class="s8" dir="ltr" | cylindrical; 7/8" OD
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Flat
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Chipper Solenoid'''
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Flat; pulls diagonally downward
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | cylindrical
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Cylindrical
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Shell'''
| class="s8" dir="ltr" | carbon fiber exterior; plastic top with stick on dots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | plastic sheet, colors taped on top; screws sticking up for alignment
| class="s8" dir="ltr" | plastic sheet for old ones; separate top section; screws sticking up for alignment
| class="s8" dir="ltr" | plastic top only
| class="s8" dir="ltr" | milled from single block of plastic; Significant amount of material is milled away
| class="s8" dir="ltr" | carbon fiber; 3 layers; flexible & rugged; possible radio interference; also uses a standard plastic sheet
| class="s8" dir="ltr" | Plastic wrapped with a separate top piece glued onto it
| class="s8" dir="ltr" | Looked to be casted in a plastic-type resin/epoxy (their shell had small bubbles in it that are usually seen n casted objects)
| class="s8" dir="ltr" | Plastic shell with paper top piece
| class="s8" dir="ltr" | magnetic top piece; wrapped plastic sheet for sides
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | plastic top
| class="s8" dir="ltr" | fiberglass; stick on dots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Plastic sheet wrapped around, separate paper top section for dots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Motor Driver/Configuration'''
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | similar to our 2014 proto
| class="s6" dir="ltr" | off the shelf
| class="s6" dir="ltr" | 3 drivers, 3 fets, and mystery chip on every motor; 100K between gate and source; see pictures for exact details
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | L6240 chip
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:86px;"
| class="s10" dir="ltr" | '''Misc. Notes'''
| class="s8" dir="ltr" | no hardware team; electronics outsourced to SMATS; robots are $10K each; they have 12 robots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | all electronics are open source
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | they said they never replace parts during competition; they print boards every year. Email for contacting electrical lead: hosseinikia.adel@gmail.com
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | uses magnetic encoders (PN: AS4050) that have 10-bit resolution
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | the team said that the best electrical team were the tigers
| class="s8" dir="ltr" | contact: awaisazhar84@yahoo.com (M. Awais Azhar); their university was founded by several GT graduates
| class="s8" dir="ltr" | their electrical boards are printed locally in Colombia. Ball sensors are held on by screwed in U-blocks
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|}

[[Category:RoboCup]]
[[Category:Electrical]]
[[Category:Mechanical]]
[[Category:Year: 2013-2014]]

RoboCup: Kicker Board 2013

2017-03-03T19:32:29Z

Rosawa3: /* Flyback Converter */ removed inaccurate content

== Overview ==

This is an overview of all the features and concepts on the 2013 kicker board made for the RoboCup competition by the electrical team of Georgia Institute of Technology's RoboCup team. This board's purpose is to drive a high voltage, high peak current solenoid to kick the ball. This page is to be used to farmiliarize new members of RoboCup with how the kicker board works.

== Safety and Handling ==

This board uses high voltage. Be extremely careful around high voltage. It can cause considerable damage. Until you know that the capacitors are discharged, assume that they are still charged up to 250V. Check if there is a red LED lit on the back of the the kicker board. This is the death light. It is powered directly by the capacitors. If this light is on, you should not touch the board.

== Kicker Charger ==

[[File:Kicker charger.PNG|thumb|center|1200px]]

This is the kicker board's charging circutry. This allows the board to charge large capacitors up to a very high voltage. This part of the board consists of two main components: the bank capacitors and the flyback regulator. The bank capacitor is charged up to a high voltage and allows a high peak power delivery. The flyback controller is used to convert a low voltage, high current input to a high voltage, low current output.

=== Flyback Controller ===

The flyback controller that is on the board is a LT3757 [4]. This chip modulates the duty cycle of the priamry side switch based ont he feedback voltage to regulate the output voltage.

=== LT3757/Converter controller ===

The converter controller that is on the board is a LT3757 [4]. This chip manages the switching of our Buck-boost converter. When the supply loop has reached full capacity it will lock the supply loop. When the potential is transferred to the capacitors the supply loop is again unlocked. The LT3757 is an integrated circuit that uses inputs to determine precisely when to switch in order maximize power transfer. We can not do this manually or with our FPGA [5] and CPU [6] because of the asymptotic nature of capacitors and inductors. Unfortunately the LT3757 was designed for a resistive load, and while it can handle capacitive loads quite well there may be other chips that do it even better. We are looking at other possibilities and may improve on this component in the future.

=== Other converter methods ===

It has been suggested that other converter types may be able to charge the capacitors faster. A boost converter [7] may allow us to create a higher voltage potential. This would allow a faster transfer from the inductor to the capacitor. The other converter that has been looked at is the cuk converter [8]. A cuk converter might be able to allow the capacitors to be charged while other inductors are charging which would increase the rate of power transfer without raising the voltage across the capacitor. The electrical team is looking at these and other possibilities to improve on these systems in the future.

== Voltage Monitor ==

This component is covered in detail on the control board page.

[http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker]

== Kicker Trigger ==

[[File:Kicker trigger.PNG|thumb|left|600px]]

This section of the board allows the control board to release the energy stored in the capacitors into the kicker or chipper. This is done by using the TC4427 to control two high current, high voltage power transitors. These transistors will allow all of the energy stored in the capacitors to be released over the solenoid. There is a very value resistor and a diode pointing from the ground side of the solenoid to the power side in case the there is voltage overflow from the solenoid.

== Auto-Discharge ==

The other way for the capacitors to discharge is the auto-discharger. This section is controled by either the control board, when it needs less voltage to kick with or the by the LT3757 when it has reached the maximum voltage allowed by the circutry. This discharger has much lower current transitors and large resistors that limit the discharge current. This is never used for discharging the capacitors fully as it will take longer than kicking and will release a lot of heat if the full capacitors were discharged over this section.

== 2008 Model of the 2013 Board ==

The 2013 kicker boards have redplaced out the previous models of the 2008 and 2011 boards. The 2013 board is based on the 2011 version with the addition of some updated parts and adding a voltage monitor for the capacitors. However, the 2008 board was very different. While the 2011 and 2013 kicker boards have a chip port, the 2008 boards and robots could not chip the ball. We have removed the chipping components from certain boards to avoid confusion with ports and plugs. Additionally, some of the 2008 model 2013 boards do not have voltage monitoring components because the control boards are unable to read the voltage monitor in 2008 mode

== Parts list ==

Disclaimer: Some of the parts are not used in the final kicker board, but are printed on the mini board that is removed to make room for the capacitors. The parts list can be downloaded [http://wiki.robojackets.org/mediawiki/Media%3AKicker%20parts.pdf here].

== References ==
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li>[http://en.wikipedia.org/wiki/Transformer http://en.wikipedia.org/wiki/Transformer]</li>
<li>[http://en.wikipedia.org/wiki/Inductor#Stored_energy http://en.wikipedia.org/wiki/Inductor]</li>
<li>[http://en.wikipedia.org/wiki/Flyback_converter http://en.wikipedia.org/wiki/Flyback_converter]</li>
<li>[http://cds.linear.com/docs/en/datasheet/3757Afd.pdf http://cds.linear.com/docs/en/datasheet/3757Afd.pdf]</li>
<li>[http://en.wikipedia.org/wiki/Field-programmable_gate_array http://en.wikipedia.org/wiki/Field-programmable_gate_array]</li>
<li>[http://en.wikipedia.org/wiki/Microprocessor http://en.wikipedia.org/wiki/Microprocessor]</li>
<li>[http://en.wikipedia.org/wiki/Boost_converter http://en.wikipedia.org/wiki/Boost_converter]</li>
<li>[http://en.wikipedia.org/wiki/%C4%86uk_converter http://en.wikipedia.org/wiki/%C4%86uk_converter]</li>
</ol>

RoboCup: Kicker Board 2013

2017-03-03T16:42:19Z

Rosawa3: /* Flyback Converter */ correcting information

== Overview ==

This is an overview of all the features and concepts on the 2013 kicker board made for the RoboCup competition by the electrical team of Georgia Institute of Technology's RoboCup team. This board's purpose is to drive a high voltage, high peak current solenoid to kick the ball. This page is to be used to farmiliarize new members of RoboCup with how the kicker board works.

== Safety and Handling ==

This board uses high voltage. Be extremely careful around high voltage. It can cause considerable damage. Until you know that the capacitors are discharged, assume that they are still charged up to 250V. Check if there is a red LED lit on the back of the the kicker board. This is the death light. It is powered directly by the capacitors. If this light is on, you should not touch the board.

== Kicker Charger ==

[[File:Kicker charger.PNG|thumb|center|1200px]]

This is the kicker board's charging circutry. This allows the board to charge large capacitors up to a very high voltage. This part of the board consists of two main components: the bank capacitors and the flyback regulator. The bank capacitor is charged up to a high voltage and allows a high peak power delivery. The flyback controller is used to convert a low voltage, high current input to a high voltage, low current output.

=== Flyback Converter ===
The board currently uses a flyback [3] converter to create a very high voltage which we can store in the capacitors. The flyback converter allows the output voltage to increase above what can be supplied by the input. This is done through a process of transferring potential energy.

First, the supply voltage charges the primary side of the flyback transformer to some potential energy. The primary side circuit is then opened. This causes the magnetic field to collapse. Since the primary side is opened, this collapse induces a current in the secondary winding. This induced current charges the bank capacitors. The diode rectifies the current such that the bank capacitors will not backdrive the system. This process is repeated until the feedback voltage from the capacitors reaches the target value.

=== LT3757/Converter controller ===

The converter controller that is on the board is a LT3757 [4]. This chip manages the switching of our Buck-boost converter. When the supply loop has reached full capacity it will lock the supply loop. When the potential is transferred to the capacitors the supply loop is again unlocked. The LT3757 is an integrated circuit that uses inputs to determine precisely when to switch in order maximize power transfer. We can not do this manually or with our FPGA [5] and CPU [6] because of the asymptotic nature of capacitors and inductors. Unfortunately the LT3757 was designed for a resistive load, and while it can handle capacitive loads quite well there may be other chips that do it even better. We are looking at other possibilities and may improve on this component in the future.

=== Other converter methods ===

It has been suggested that other converter types may be able to charge the capacitors faster. A boost converter [7] may allow us to create a higher voltage potential. This would allow a faster transfer from the inductor to the capacitor. The other converter that has been looked at is the cuk converter [8]. A cuk converter might be able to allow the capacitors to be charged while other inductors are charging which would increase the rate of power transfer without raising the voltage across the capacitor. The electrical team is looking at these and other possibilities to improve on these systems in the future.

== Voltage Monitor ==

This component is covered in detail on the control board page.

[http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker]

== Kicker Trigger ==

[[File:Kicker trigger.PNG|thumb|left|600px]]

This section of the board allows the control board to release the energy stored in the capacitors into the kicker or chipper. This is done by using the TC4427 to control two high current, high voltage power transitors. These transistors will allow all of the energy stored in the capacitors to be released over the solenoid. There is a very value resistor and a diode pointing from the ground side of the solenoid to the power side in case the there is voltage overflow from the solenoid.

== Auto-Discharge ==

The other way for the capacitors to discharge is the auto-discharger. This section is controled by either the control board, when it needs less voltage to kick with or the by the LT3757 when it has reached the maximum voltage allowed by the circutry. This discharger has much lower current transitors and large resistors that limit the discharge current. This is never used for discharging the capacitors fully as it will take longer than kicking and will release a lot of heat if the full capacitors were discharged over this section.

== 2008 Model of the 2013 Board ==

The 2013 kicker boards have redplaced out the previous models of the 2008 and 2011 boards. The 2013 board is based on the 2011 version with the addition of some updated parts and adding a voltage monitor for the capacitors. However, the 2008 board was very different. While the 2011 and 2013 kicker boards have a chip port, the 2008 boards and robots could not chip the ball. We have removed the chipping components from certain boards to avoid confusion with ports and plugs. Additionally, some of the 2008 model 2013 boards do not have voltage monitoring components because the control boards are unable to read the voltage monitor in 2008 mode

== Parts list ==

Disclaimer: Some of the parts are not used in the final kicker board, but are printed on the mini board that is removed to make room for the capacitors. The parts list can be downloaded [http://wiki.robojackets.org/mediawiki/Media%3AKicker%20parts.pdf here].

== References ==
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li>[http://en.wikipedia.org/wiki/Transformer http://en.wikipedia.org/wiki/Transformer]</li>
<li>[http://en.wikipedia.org/wiki/Inductor#Stored_energy http://en.wikipedia.org/wiki/Inductor]</li>
<li>[http://en.wikipedia.org/wiki/Flyback_converter http://en.wikipedia.org/wiki/Flyback_converter]</li>
<li>[http://cds.linear.com/docs/en/datasheet/3757Afd.pdf http://cds.linear.com/docs/en/datasheet/3757Afd.pdf]</li>
<li>[http://en.wikipedia.org/wiki/Field-programmable_gate_array http://en.wikipedia.org/wiki/Field-programmable_gate_array]</li>
<li>[http://en.wikipedia.org/wiki/Microprocessor http://en.wikipedia.org/wiki/Microprocessor]</li>
<li>[http://en.wikipedia.org/wiki/Boost_converter http://en.wikipedia.org/wiki/Boost_converter]</li>
<li>[http://en.wikipedia.org/wiki/%C4%86uk_converter http://en.wikipedia.org/wiki/%C4%86uk_converter]</li>
</ol>

RoboCup: Kicker Board 2013

2017-03-03T16:34:57Z

Rosawa3: /* Kicker Charger */ removed mention of discharge controller

== Overview ==

This is an overview of all the features and concepts on the 2013 kicker board made for the RoboCup competition by the electrical team of Georgia Institute of Technology's RoboCup team. This board's purpose is to drive a high voltage, high peak current solenoid to kick the ball. This page is to be used to farmiliarize new members of RoboCup with how the kicker board works.

== Safety and Handling ==

This board uses high voltage. Be extremely careful around high voltage. It can cause considerable damage. Until you know that the capacitors are discharged, assume that they are still charged up to 250V. Check if there is a red LED lit on the back of the the kicker board. This is the death light. It is powered directly by the capacitors. If this light is on, you should not touch the board.

== Kicker Charger ==

[[File:Kicker charger.PNG|thumb|center|1200px]]

This is the kicker board's charging circutry. This allows the board to charge large capacitors up to a very high voltage. This part of the board consists of two main components: the bank capacitors and the flyback regulator. The bank capacitor is charged up to a high voltage and allows a high peak power delivery. The flyback controller is used to convert a low voltage, high current input to a high voltage, low current output.

=== Flyback Converter ===
The board currently uses a flyback [3] or buck-boost converter along with a transformer to create a very high voltage which we can store in the capacitors. A boost converter allows the output voltage to increase above what can be supplied as input. A very high voltage potential must be reached as soon as possible. This is done through a process of transferring potential energy.

First the supply voltage charges the transformer to some potential energy specified by the LT3757. The load loop is effectively locked in place by the potential of our capacitive load and a diode which prevents current from being discharged over the capacitors. The supply loop is then locked with a transistor by the LT3757. This forces all of the potential gathered in the transistor into the load loop. Not all of potential energy is transferred because there is already potential energy on the capacitors from the last round of charging. Once enough energy has been transferred to the capacitors the LT3757 will open up the supply loop. This restarts our process recharging the supply loop.

=== LT3757/Converter controller ===

The converter controller that is on the board is a LT3757 [4]. This chip manages the switching of our Buck-boost converter. When the supply loop has reached full capacity it will lock the supply loop. When the potential is transferred to the capacitors the supply loop is again unlocked. The LT3757 is an integrated circuit that uses inputs to determine precisely when to switch in order maximize power transfer. We can not do this manually or with our FPGA [5] and CPU [6] because of the asymptotic nature of capacitors and inductors. Unfortunately the LT3757 was designed for a resistive load, and while it can handle capacitive loads quite well there may be other chips that do it even better. We are looking at other possibilities and may improve on this component in the future.

=== Other converter methods ===

It has been suggested that other converter types may be able to charge the capacitors faster. A boost converter [7] may allow us to create a higher voltage potential. This would allow a faster transfer from the inductor to the capacitor. The other converter that has been looked at is the cuk converter [8]. A cuk converter might be able to allow the capacitors to be charged while other inductors are charging which would increase the rate of power transfer without raising the voltage across the capacitor. The electrical team is looking at these and other possibilities to improve on these systems in the future.

== Voltage Monitor ==

This component is covered in detail on the control board page.

[http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker]

== Kicker Trigger ==

[[File:Kicker trigger.PNG|thumb|left|600px]]

This section of the board allows the control board to release the energy stored in the capacitors into the kicker or chipper. This is done by using the TC4427 to control two high current, high voltage power transitors. These transistors will allow all of the energy stored in the capacitors to be released over the solenoid. There is a very value resistor and a diode pointing from the ground side of the solenoid to the power side in case the there is voltage overflow from the solenoid.

== Auto-Discharge ==

The other way for the capacitors to discharge is the auto-discharger. This section is controled by either the control board, when it needs less voltage to kick with or the by the LT3757 when it has reached the maximum voltage allowed by the circutry. This discharger has much lower current transitors and large resistors that limit the discharge current. This is never used for discharging the capacitors fully as it will take longer than kicking and will release a lot of heat if the full capacitors were discharged over this section.

== 2008 Model of the 2013 Board ==

The 2013 kicker boards have redplaced out the previous models of the 2008 and 2011 boards. The 2013 board is based on the 2011 version with the addition of some updated parts and adding a voltage monitor for the capacitors. However, the 2008 board was very different. While the 2011 and 2013 kicker boards have a chip port, the 2008 boards and robots could not chip the ball. We have removed the chipping components from certain boards to avoid confusion with ports and plugs. Additionally, some of the 2008 model 2013 boards do not have voltage monitoring components because the control boards are unable to read the voltage monitor in 2008 mode

== Parts list ==

Disclaimer: Some of the parts are not used in the final kicker board, but are printed on the mini board that is removed to make room for the capacitors. The parts list can be downloaded [http://wiki.robojackets.org/mediawiki/Media%3AKicker%20parts.pdf here].

== References ==
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li>[http://en.wikipedia.org/wiki/Transformer http://en.wikipedia.org/wiki/Transformer]</li>
<li>[http://en.wikipedia.org/wiki/Inductor#Stored_energy http://en.wikipedia.org/wiki/Inductor]</li>
<li>[http://en.wikipedia.org/wiki/Flyback_converter http://en.wikipedia.org/wiki/Flyback_converter]</li>
<li>[http://cds.linear.com/docs/en/datasheet/3757Afd.pdf http://cds.linear.com/docs/en/datasheet/3757Afd.pdf]</li>
<li>[http://en.wikipedia.org/wiki/Field-programmable_gate_array http://en.wikipedia.org/wiki/Field-programmable_gate_array]</li>
<li>[http://en.wikipedia.org/wiki/Microprocessor http://en.wikipedia.org/wiki/Microprocessor]</li>
<li>[http://en.wikipedia.org/wiki/Boost_converter http://en.wikipedia.org/wiki/Boost_converter]</li>
<li>[http://en.wikipedia.org/wiki/%C4%86uk_converter http://en.wikipedia.org/wiki/%C4%86uk_converter]</li>
</ol>

RoboCup: Kicker Board 2013

2017-03-03T16:32:18Z

Rosawa3: /* Transformer Overview */ removed inaccurate information

== Overview ==

This is an overview of all the features and concepts on the 2013 kicker board made for the RoboCup competition by the electrical team of Georgia Institute of Technology's RoboCup team. This board's purpose is to drive a high voltage, high peak current solenoid to kick the ball. This page is to be used to farmiliarize new members of RoboCup with how the kicker board works.

== Safety and Handling ==

This board uses high voltage. Be extremely careful around high voltage. It can cause considerable damage. Until you know that the capacitors are discharged, assume that they are still charged up to 250V. Check if there is a red LED lit on the back of the the kicker board. This is the death light. It is powered directly by the capacitors. If this light is on, you should not touch the board.

== Kicker Charger ==

[[File:Kicker charger.PNG|thumb|center|1200px]]

This is the kicker board's charging circutry. This allows the board to charge large capacitors up to a very high voltage. This part of the board consists of three main components: bank capacitors, flyback regulator, and the discharge control. The bank capacitor is charged up to a high voltage and allows a high peak power delivery. The flyback controller is used to convert a low voltage, high current input to a high voltage, low current output. The final component is the discharge control to release the enrgy stored in the capacitors to the solenoid.

=== Flyback Converter ===
The board currently uses a flyback [3] or buck-boost converter along with a transformer to create a very high voltage which we can store in the capacitors. A boost converter allows the output voltage to increase above what can be supplied as input. A very high voltage potential must be reached as soon as possible. This is done through a process of transferring potential energy.

First the supply voltage charges the transformer to some potential energy specified by the LT3757. The load loop is effectively locked in place by the potential of our capacitive load and a diode which prevents current from being discharged over the capacitors. The supply loop is then locked with a transistor by the LT3757. This forces all of the potential gathered in the transistor into the load loop. Not all of potential energy is transferred because there is already potential energy on the capacitors from the last round of charging. Once enough energy has been transferred to the capacitors the LT3757 will open up the supply loop. This restarts our process recharging the supply loop.

=== LT3757/Converter controller ===

The converter controller that is on the board is a LT3757 [4]. This chip manages the switching of our Buck-boost converter. When the supply loop has reached full capacity it will lock the supply loop. When the potential is transferred to the capacitors the supply loop is again unlocked. The LT3757 is an integrated circuit that uses inputs to determine precisely when to switch in order maximize power transfer. We can not do this manually or with our FPGA [5] and CPU [6] because of the asymptotic nature of capacitors and inductors. Unfortunately the LT3757 was designed for a resistive load, and while it can handle capacitive loads quite well there may be other chips that do it even better. We are looking at other possibilities and may improve on this component in the future.

=== Other converter methods ===

It has been suggested that other converter types may be able to charge the capacitors faster. A boost converter [7] may allow us to create a higher voltage potential. This would allow a faster transfer from the inductor to the capacitor. The other converter that has been looked at is the cuk converter [8]. A cuk converter might be able to allow the capacitors to be charged while other inductors are charging which would increase the rate of power transfer without raising the voltage across the capacitor. The electrical team is looking at these and other possibilities to improve on these systems in the future.

== Voltage Monitor ==

This component is covered in detail on the control board page.

[http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker]

== Kicker Trigger ==

[[File:Kicker trigger.PNG|thumb|left|600px]]

This section of the board allows the control board to release the energy stored in the capacitors into the kicker or chipper. This is done by using the TC4427 to control two high current, high voltage power transitors. These transistors will allow all of the energy stored in the capacitors to be released over the solenoid. There is a very value resistor and a diode pointing from the ground side of the solenoid to the power side in case the there is voltage overflow from the solenoid.

== Auto-Discharge ==

The other way for the capacitors to discharge is the auto-discharger. This section is controled by either the control board, when it needs less voltage to kick with or the by the LT3757 when it has reached the maximum voltage allowed by the circutry. This discharger has much lower current transitors and large resistors that limit the discharge current. This is never used for discharging the capacitors fully as it will take longer than kicking and will release a lot of heat if the full capacitors were discharged over this section.

== 2008 Model of the 2013 Board ==

The 2013 kicker boards have redplaced out the previous models of the 2008 and 2011 boards. The 2013 board is based on the 2011 version with the addition of some updated parts and adding a voltage monitor for the capacitors. However, the 2008 board was very different. While the 2011 and 2013 kicker boards have a chip port, the 2008 boards and robots could not chip the ball. We have removed the chipping components from certain boards to avoid confusion with ports and plugs. Additionally, some of the 2008 model 2013 boards do not have voltage monitoring components because the control boards are unable to read the voltage monitor in 2008 mode

== Parts list ==

Disclaimer: Some of the parts are not used in the final kicker board, but are printed on the mini board that is removed to make room for the capacitors. The parts list can be downloaded [http://wiki.robojackets.org/mediawiki/Media%3AKicker%20parts.pdf here].

== References ==
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li>[http://en.wikipedia.org/wiki/Transformer http://en.wikipedia.org/wiki/Transformer]</li>
<li>[http://en.wikipedia.org/wiki/Inductor#Stored_energy http://en.wikipedia.org/wiki/Inductor]</li>
<li>[http://en.wikipedia.org/wiki/Flyback_converter http://en.wikipedia.org/wiki/Flyback_converter]</li>
<li>[http://cds.linear.com/docs/en/datasheet/3757Afd.pdf http://cds.linear.com/docs/en/datasheet/3757Afd.pdf]</li>
<li>[http://en.wikipedia.org/wiki/Field-programmable_gate_array http://en.wikipedia.org/wiki/Field-programmable_gate_array]</li>
<li>[http://en.wikipedia.org/wiki/Microprocessor http://en.wikipedia.org/wiki/Microprocessor]</li>
<li>[http://en.wikipedia.org/wiki/Boost_converter http://en.wikipedia.org/wiki/Boost_converter]</li>
<li>[http://en.wikipedia.org/wiki/%C4%86uk_converter http://en.wikipedia.org/wiki/%C4%86uk_converter]</li>
</ol>

RoboCup: Kicker Board 2013

2017-03-03T16:31:11Z

Rosawa3: /* Kicker Charger */ correction of information

== Overview ==

This is an overview of all the features and concepts on the 2013 kicker board made for the RoboCup competition by the electrical team of Georgia Institute of Technology's RoboCup team. This board's purpose is to drive a high voltage, high peak current solenoid to kick the ball. This page is to be used to farmiliarize new members of RoboCup with how the kicker board works.

== Safety and Handling ==

This board uses high voltage. Be extremely careful around high voltage. It can cause considerable damage. Until you know that the capacitors are discharged, assume that they are still charged up to 250V. Check if there is a red LED lit on the back of the the kicker board. This is the death light. It is powered directly by the capacitors. If this light is on, you should not touch the board.

== Kicker Charger ==

[[File:Kicker charger.PNG|thumb|center|1200px]]

This is the kicker board's charging circutry. This allows the board to charge large capacitors up to a very high voltage. This part of the board consists of three main components: bank capacitors, flyback regulator, and the discharge control. The bank capacitor is charged up to a high voltage and allows a high peak power delivery. The flyback controller is used to convert a low voltage, high current input to a high voltage, low current output. The final component is the discharge control to release the enrgy stored in the capacitors to the solenoid.

=== Transformer Overview ===

In the charger design of our kicker board a transformer [1] is used to increase the voltage potential of capacitors. For the design of this board we can think of a transformer as two inductors  with a shared potential energy. This means that we can transfer energy from one inductor to the other freely. These inductors [2] do not have to be identical. In fact it is the difference in inductance that allows the transistor to magnify voltage. For the charger of the transformer, we use the relationship that E = 1/2LI^2, where L is the inductance and I is the current. This allows us to change the current by having a difference in inductance acording to an inverse square root relationship. We can use this current multiplication to create a voltage multiplication effect. This is an ideal transformer, so in reality not all of the energy is transferred.

=== Flyback Converter ===
The board currently uses a flyback [3] or buck-boost converter along with a transformer to create a very high voltage which we can store in the capacitors. A boost converter allows the output voltage to increase above what can be supplied as input. A very high voltage potential must be reached as soon as possible. This is done through a process of transferring potential energy.

First the supply voltage charges the transformer to some potential energy specified by the LT3757. The load loop is effectively locked in place by the potential of our capacitive load and a diode which prevents current from being discharged over the capacitors. The supply loop is then locked with a transistor by the LT3757. This forces all of the potential gathered in the transistor into the load loop. Not all of potential energy is transferred because there is already potential energy on the capacitors from the last round of charging. Once enough energy has been transferred to the capacitors the LT3757 will open up the supply loop. This restarts our process recharging the supply loop.

=== LT3757/Converter controller ===

The converter controller that is on the board is a LT3757 [4]. This chip manages the switching of our Buck-boost converter. When the supply loop has reached full capacity it will lock the supply loop. When the potential is transferred to the capacitors the supply loop is again unlocked. The LT3757 is an integrated circuit that uses inputs to determine precisely when to switch in order maximize power transfer. We can not do this manually or with our FPGA [5] and CPU [6] because of the asymptotic nature of capacitors and inductors. Unfortunately the LT3757 was designed for a resistive load, and while it can handle capacitive loads quite well there may be other chips that do it even better. We are looking at other possibilities and may improve on this component in the future.

=== Other converter methods ===

It has been suggested that other converter types may be able to charge the capacitors faster. A boost converter [7] may allow us to create a higher voltage potential. This would allow a faster transfer from the inductor to the capacitor. The other converter that has been looked at is the cuk converter [8]. A cuk converter might be able to allow the capacitors to be charged while other inductors are charging which would increase the rate of power transfer without raising the voltage across the capacitor. The electrical team is looking at these and other possibilities to improve on these systems in the future.

== Voltage Monitor ==

This component is covered in detail on the control board page.

[http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker]

== Kicker Trigger ==

[[File:Kicker trigger.PNG|thumb|left|600px]]

This section of the board allows the control board to release the energy stored in the capacitors into the kicker or chipper. This is done by using the TC4427 to control two high current, high voltage power transitors. These transistors will allow all of the energy stored in the capacitors to be released over the solenoid. There is a very value resistor and a diode pointing from the ground side of the solenoid to the power side in case the there is voltage overflow from the solenoid.

== Auto-Discharge ==

The other way for the capacitors to discharge is the auto-discharger. This section is controled by either the control board, when it needs less voltage to kick with or the by the LT3757 when it has reached the maximum voltage allowed by the circutry. This discharger has much lower current transitors and large resistors that limit the discharge current. This is never used for discharging the capacitors fully as it will take longer than kicking and will release a lot of heat if the full capacitors were discharged over this section.

== 2008 Model of the 2013 Board ==

The 2013 kicker boards have redplaced out the previous models of the 2008 and 2011 boards. The 2013 board is based on the 2011 version with the addition of some updated parts and adding a voltage monitor for the capacitors. However, the 2008 board was very different. While the 2011 and 2013 kicker boards have a chip port, the 2008 boards and robots could not chip the ball. We have removed the chipping components from certain boards to avoid confusion with ports and plugs. Additionally, some of the 2008 model 2013 boards do not have voltage monitoring components because the control boards are unable to read the voltage monitor in 2008 mode

== Parts list ==

Disclaimer: Some of the parts are not used in the final kicker board, but are printed on the mini board that is removed to make room for the capacitors. The parts list can be downloaded [http://wiki.robojackets.org/mediawiki/Media%3AKicker%20parts.pdf here].

== References ==
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li>[http://en.wikipedia.org/wiki/Transformer http://en.wikipedia.org/wiki/Transformer]</li>
<li>[http://en.wikipedia.org/wiki/Inductor#Stored_energy http://en.wikipedia.org/wiki/Inductor]</li>
<li>[http://en.wikipedia.org/wiki/Flyback_converter http://en.wikipedia.org/wiki/Flyback_converter]</li>
<li>[http://cds.linear.com/docs/en/datasheet/3757Afd.pdf http://cds.linear.com/docs/en/datasheet/3757Afd.pdf]</li>
<li>[http://en.wikipedia.org/wiki/Field-programmable_gate_array http://en.wikipedia.org/wiki/Field-programmable_gate_array]</li>
<li>[http://en.wikipedia.org/wiki/Microprocessor http://en.wikipedia.org/wiki/Microprocessor]</li>
<li>[http://en.wikipedia.org/wiki/Boost_converter http://en.wikipedia.org/wiki/Boost_converter]</li>
<li>[http://en.wikipedia.org/wiki/%C4%86uk_converter http://en.wikipedia.org/wiki/%C4%86uk_converter]</li>
</ol>

RoboCup: Kicker Board 2013

2017-03-03T16:26:28Z

Rosawa3: /* Safety and Handling */ removed legacy feature

== Overview ==

This is an overview of all the features and concepts on the 2013 kicker board made for the RoboCup competition by the electrical team of Georgia Institute of Technology's RoboCup team. This board's purpose is to drive a high voltage, high peak current solenoid to kick the ball. This page is to be used to farmiliarize new members of RoboCup with how the kicker board works.

== Safety and Handling ==

This board uses high voltage. Be extremely careful around high voltage. It can cause considerable damage. Until you know that the capacitors are discharged, assume that they are still charged up to 250V. Check if there is a red LED lit on the back of the the kicker board. This is the death light. It is powered directly by the capacitors. If this light is on, you should not touch the board.

== Kicker Charger ==

[[File:Kicker charger.PNG|thumb|center|1200px]]

This is the kicker board's charging circutry. This allows the board to charge large capacitors up to very high voltage with the low voltage provided by the battery. This part of the board consists of three main components. First the capacitors are in the top left corner. The whole purpose of this section is to charge those capacitors. Sencondly to the left of the capacitors is the transistor. The fact that there are more coils on one side than the other signals that that side has more inductance. The final large component is the LT3757. The circutry in the bottom half of figure 1 is used to help the LT3757 chip control the flyback converter.

=== Transformer Overview ===

In the charger design of our kicker board a transformer [1] is used to increase the voltage potential of capacitors. For the design of this board we can think of a transformer as two inductors  with a shared potential energy. This means that we can transfer energy from one inductor to the other freely. These inductors [2] do not have to be identical. In fact it is the difference in inductance that allows the transistor to magnify voltage. For the charger of the transformer, we use the relationship that E = 1/2LI^2, where L is the inductance and I is the current. This allows us to change the current by having a difference in inductance acording to an inverse square root relationship. We can use this current multiplication to create a voltage multiplication effect. This is an ideal transformer, so in reality not all of the energy is transferred.

=== Flyback Converter ===
The board currently uses a flyback [3] or buck-boost converter along with a transformer to create a very high voltage which we can store in the capacitors. A boost converter allows the output voltage to increase above what can be supplied as input. A very high voltage potential must be reached as soon as possible. This is done through a process of transferring potential energy.

First the supply voltage charges the transformer to some potential energy specified by the LT3757. The load loop is effectively locked in place by the potential of our capacitive load and a diode which prevents current from being discharged over the capacitors. The supply loop is then locked with a transistor by the LT3757. This forces all of the potential gathered in the transistor into the load loop. Not all of potential energy is transferred because there is already potential energy on the capacitors from the last round of charging. Once enough energy has been transferred to the capacitors the LT3757 will open up the supply loop. This restarts our process recharging the supply loop.

=== LT3757/Converter controller ===

The converter controller that is on the board is a LT3757 [4]. This chip manages the switching of our Buck-boost converter. When the supply loop has reached full capacity it will lock the supply loop. When the potential is transferred to the capacitors the supply loop is again unlocked. The LT3757 is an integrated circuit that uses inputs to determine precisely when to switch in order maximize power transfer. We can not do this manually or with our FPGA [5] and CPU [6] because of the asymptotic nature of capacitors and inductors. Unfortunately the LT3757 was designed for a resistive load, and while it can handle capacitive loads quite well there may be other chips that do it even better. We are looking at other possibilities and may improve on this component in the future.

=== Other converter methods ===

It has been suggested that other converter types may be able to charge the capacitors faster. A boost converter [7] may allow us to create a higher voltage potential. This would allow a faster transfer from the inductor to the capacitor. The other converter that has been looked at is the cuk converter [8]. A cuk converter might be able to allow the capacitors to be charged while other inductors are charging which would increase the rate of power transfer without raising the voltage across the capacitor. The electrical team is looking at these and other possibilities to improve on these systems in the future.

== Voltage Monitor ==

This component is covered in detail on the control board page.

[http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker]

== Kicker Trigger ==

[[File:Kicker trigger.PNG|thumb|left|600px]]

This section of the board allows the control board to release the energy stored in the capacitors into the kicker or chipper. This is done by using the TC4427 to control two high current, high voltage power transitors. These transistors will allow all of the energy stored in the capacitors to be released over the solenoid. There is a very value resistor and a diode pointing from the ground side of the solenoid to the power side in case the there is voltage overflow from the solenoid.

== Auto-Discharge ==

The other way for the capacitors to discharge is the auto-discharger. This section is controled by either the control board, when it needs less voltage to kick with or the by the LT3757 when it has reached the maximum voltage allowed by the circutry. This discharger has much lower current transitors and large resistors that limit the discharge current. This is never used for discharging the capacitors fully as it will take longer than kicking and will release a lot of heat if the full capacitors were discharged over this section.

== 2008 Model of the 2013 Board ==

The 2013 kicker boards have redplaced out the previous models of the 2008 and 2011 boards. The 2013 board is based on the 2011 version with the addition of some updated parts and adding a voltage monitor for the capacitors. However, the 2008 board was very different. While the 2011 and 2013 kicker boards have a chip port, the 2008 boards and robots could not chip the ball. We have removed the chipping components from certain boards to avoid confusion with ports and plugs. Additionally, some of the 2008 model 2013 boards do not have voltage monitoring components because the control boards are unable to read the voltage monitor in 2008 mode

== Parts list ==

Disclaimer: Some of the parts are not used in the final kicker board, but are printed on the mini board that is removed to make room for the capacitors. The parts list can be downloaded [http://wiki.robojackets.org/mediawiki/Media%3AKicker%20parts.pdf here].

== References ==
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li>[http://en.wikipedia.org/wiki/Transformer http://en.wikipedia.org/wiki/Transformer]</li>
<li>[http://en.wikipedia.org/wiki/Inductor#Stored_energy http://en.wikipedia.org/wiki/Inductor]</li>
<li>[http://en.wikipedia.org/wiki/Flyback_converter http://en.wikipedia.org/wiki/Flyback_converter]</li>
<li>[http://cds.linear.com/docs/en/datasheet/3757Afd.pdf http://cds.linear.com/docs/en/datasheet/3757Afd.pdf]</li>
<li>[http://en.wikipedia.org/wiki/Field-programmable_gate_array http://en.wikipedia.org/wiki/Field-programmable_gate_array]</li>
<li>[http://en.wikipedia.org/wiki/Microprocessor http://en.wikipedia.org/wiki/Microprocessor]</li>
<li>[http://en.wikipedia.org/wiki/Boost_converter http://en.wikipedia.org/wiki/Boost_converter]</li>
<li>[http://en.wikipedia.org/wiki/%C4%86uk_converter http://en.wikipedia.org/wiki/%C4%86uk_converter]</li>
</ol>

RoboCup: Kicker Board 2013

2017-03-03T16:23:58Z

Rosawa3: /* Overview */ optimzie text

== Overview ==

This is an overview of all the features and concepts on the 2013 kicker board made for the RoboCup competition by the electrical team of Georgia Institute of Technology's RoboCup team. This board's purpose is to drive a high voltage, high peak current solenoid to kick the ball. This page is to be used to farmiliarize new members of RoboCup with how the kicker board works.

== Safety and Handling ==

This board uses high voltage. Be extremely careful around high voltage. It can cause considerable damage. Until you know that the capacitors are discharged, assume that they are still charged up to 250V. The best way to tell if your board is discharged is that there is one red LED on the back of the the kicker board. This is the death light. It is powered directly by the capacitors. If this light is on, you should not touch the board. The best way to discharge the capacitors is to push the button on the rear of the control board and then immediately power off the robot. This will cause the robot to manually kick, discharging the capacitors. Then turn off the power before it can build enough charge to cause much of a shock if any. This button can only be used if the robot is on, so make sure a kick is made. Also if the LED is on faintly it will likely not cause much of a shock, but you should either discharge it or wait for the LED dissipate the remaining energy.

== Kicker Charger ==

[[File:Kicker charger.PNG|thumb|center|1200px]]

This is the kicker board's charging circutry. This allows the board to charge large capacitors up to very high voltage with the low voltage provided by the battery. This part of the board consists of three main components. First the capacitors are in the top left corner. The whole purpose of this section is to charge those capacitors. Sencondly to the left of the capacitors is the transistor. The fact that there are more coils on one side than the other signals that that side has more inductance. The final large component is the LT3757. The circutry in the bottom half of figure 1 is used to help the LT3757 chip control the flyback converter.

=== Transformer Overview ===

In the charger design of our kicker board a transformer [1] is used to increase the voltage potential of capacitors. For the design of this board we can think of a transformer as two inductors  with a shared potential energy. This means that we can transfer energy from one inductor to the other freely. These inductors [2] do not have to be identical. In fact it is the difference in inductance that allows the transistor to magnify voltage. For the charger of the transformer, we use the relationship that E = 1/2LI^2, where L is the inductance and I is the current. This allows us to change the current by having a difference in inductance acording to an inverse square root relationship. We can use this current multiplication to create a voltage multiplication effect. This is an ideal transformer, so in reality not all of the energy is transferred.

=== Flyback Converter ===
The board currently uses a flyback [3] or buck-boost converter along with a transformer to create a very high voltage which we can store in the capacitors. A boost converter allows the output voltage to increase above what can be supplied as input. A very high voltage potential must be reached as soon as possible. This is done through a process of transferring potential energy.

First the supply voltage charges the transformer to some potential energy specified by the LT3757. The load loop is effectively locked in place by the potential of our capacitive load and a diode which prevents current from being discharged over the capacitors. The supply loop is then locked with a transistor by the LT3757. This forces all of the potential gathered in the transistor into the load loop. Not all of potential energy is transferred because there is already potential energy on the capacitors from the last round of charging. Once enough energy has been transferred to the capacitors the LT3757 will open up the supply loop. This restarts our process recharging the supply loop.

=== LT3757/Converter controller ===

The converter controller that is on the board is a LT3757 [4]. This chip manages the switching of our Buck-boost converter. When the supply loop has reached full capacity it will lock the supply loop. When the potential is transferred to the capacitors the supply loop is again unlocked. The LT3757 is an integrated circuit that uses inputs to determine precisely when to switch in order maximize power transfer. We can not do this manually or with our FPGA [5] and CPU [6] because of the asymptotic nature of capacitors and inductors. Unfortunately the LT3757 was designed for a resistive load, and while it can handle capacitive loads quite well there may be other chips that do it even better. We are looking at other possibilities and may improve on this component in the future.

=== Other converter methods ===

It has been suggested that other converter types may be able to charge the capacitors faster. A boost converter [7] may allow us to create a higher voltage potential. This would allow a faster transfer from the inductor to the capacitor. The other converter that has been looked at is the cuk converter [8]. A cuk converter might be able to allow the capacitors to be charged while other inductors are charging which would increase the rate of power transfer without raising the voltage across the capacitor. The electrical team is looking at these and other possibilities to improve on these systems in the future.

== Voltage Monitor ==

This component is covered in detail on the control board page.

[http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker]

== Kicker Trigger ==

[[File:Kicker trigger.PNG|thumb|left|600px]]

This section of the board allows the control board to release the energy stored in the capacitors into the kicker or chipper. This is done by using the TC4427 to control two high current, high voltage power transitors. These transistors will allow all of the energy stored in the capacitors to be released over the solenoid. There is a very value resistor and a diode pointing from the ground side of the solenoid to the power side in case the there is voltage overflow from the solenoid.

== Auto-Discharge ==

The other way for the capacitors to discharge is the auto-discharger. This section is controled by either the control board, when it needs less voltage to kick with or the by the LT3757 when it has reached the maximum voltage allowed by the circutry. This discharger has much lower current transitors and large resistors that limit the discharge current. This is never used for discharging the capacitors fully as it will take longer than kicking and will release a lot of heat if the full capacitors were discharged over this section.

== 2008 Model of the 2013 Board ==

The 2013 kicker boards have redplaced out the previous models of the 2008 and 2011 boards. The 2013 board is based on the 2011 version with the addition of some updated parts and adding a voltage monitor for the capacitors. However, the 2008 board was very different. While the 2011 and 2013 kicker boards have a chip port, the 2008 boards and robots could not chip the ball. We have removed the chipping components from certain boards to avoid confusion with ports and plugs. Additionally, some of the 2008 model 2013 boards do not have voltage monitoring components because the control boards are unable to read the voltage monitor in 2008 mode

== Parts list ==

Disclaimer: Some of the parts are not used in the final kicker board, but are printed on the mini board that is removed to make room for the capacitors. The parts list can be downloaded [http://wiki.robojackets.org/mediawiki/Media%3AKicker%20parts.pdf here].

== References ==
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li>[http://en.wikipedia.org/wiki/Transformer http://en.wikipedia.org/wiki/Transformer]</li>
<li>[http://en.wikipedia.org/wiki/Inductor#Stored_energy http://en.wikipedia.org/wiki/Inductor]</li>
<li>[http://en.wikipedia.org/wiki/Flyback_converter http://en.wikipedia.org/wiki/Flyback_converter]</li>
<li>[http://cds.linear.com/docs/en/datasheet/3757Afd.pdf http://cds.linear.com/docs/en/datasheet/3757Afd.pdf]</li>
<li>[http://en.wikipedia.org/wiki/Field-programmable_gate_array http://en.wikipedia.org/wiki/Field-programmable_gate_array]</li>
<li>[http://en.wikipedia.org/wiki/Microprocessor http://en.wikipedia.org/wiki/Microprocessor]</li>
<li>[http://en.wikipedia.org/wiki/Boost_converter http://en.wikipedia.org/wiki/Boost_converter]</li>
<li>[http://en.wikipedia.org/wiki/%C4%86uk_converter http://en.wikipedia.org/wiki/%C4%86uk_converter]</li>
</ol>

RoboCup: Kicker Board 2013

2017-03-03T16:21:15Z

Rosawa3: Remove span tags and some minor edits

== Overview ==

This is an overview of all the features and concepts on the 2013 kicker board made for the RoboCup competition by the electrical team of Georgia Institute of Technology's RoboCup team. This board's purpose is to contain all of the electric components to power a solenoid, to provide a working kick to play soccer with. This wiki be used to farmiliarize new members of robocup with how the kicker board works and learn other important facts about the board. If there are any questions about any of the concepts that we don't explain please refer to the references we have provided.

== Safety and Handling ==

This board uses high voltage. Be extremely careful around high voltage. It can cause considerable damage. Until you know that the capacitors are discharged, assume that they are still charged up to 250V. The best way to tell if your board is discharged is that there is one red LED on the back of the the kicker board. This is the death light. It is powered directly by the capacitors. If this light is on, you should not touch the board. The best way to discharge the capacitors is to push the button on the rear of the control board and then immediately power off the robot. This will cause the robot to manually kick, discharging the capacitors. Then turn off the power before it can build enough charge to cause much of a shock if any. This button can only be used if the robot is on, so make sure a kick is made. Also if the LED is on faintly it will likely not cause much of a shock, but you should either discharge it or wait for the LED dissipate the remaining energy.

== Kicker Charger ==

[[File:Kicker charger.PNG|thumb|center|1200px]]

This is the kicker board's charging circutry. This allows the board to charge large capacitors up to very high voltage with the low voltage provided by the battery. This part of the board consists of three main components. First the capacitors are in the top left corner. The whole purpose of this section is to charge those capacitors. Sencondly to the left of the capacitors is the transistor. The fact that there are more coils on one side than the other signals that that side has more inductance. The final large component is the LT3757. The circutry in the bottom half of figure 1 is used to help the LT3757 chip control the flyback converter.

=== Transformer Overview ===

In the charger design of our kicker board a transformer [1] is used to increase the voltage potential of capacitors. For the design of this board we can think of a transformer as two inductors  with a shared potential energy. This means that we can transfer energy from one inductor to the other freely. These inductors [2] do not have to be identical. In fact it is the difference in inductance that allows the transistor to magnify voltage. For the charger of the transformer, we use the relationship that E = 1/2LI^2, where L is the inductance and I is the current. This allows us to change the current by having a difference in inductance acording to an inverse square root relationship. We can use this current multiplication to create a voltage multiplication effect. This is an ideal transformer, so in reality not all of the energy is transferred.

=== Flyback Converter ===
The board currently uses a flyback [3] or buck-boost converter along with a transformer to create a very high voltage which we can store in the capacitors. A boost converter allows the output voltage to increase above what can be supplied as input. A very high voltage potential must be reached as soon as possible. This is done through a process of transferring potential energy.

First the supply voltage charges the transformer to some potential energy specified by the LT3757. The load loop is effectively locked in place by the potential of our capacitive load and a diode which prevents current from being discharged over the capacitors. The supply loop is then locked with a transistor by the LT3757. This forces all of the potential gathered in the transistor into the load loop. Not all of potential energy is transferred because there is already potential energy on the capacitors from the last round of charging. Once enough energy has been transferred to the capacitors the LT3757 will open up the supply loop. This restarts our process recharging the supply loop.

=== LT3757/Converter controller ===

The converter controller that is on the board is a LT3757 [4]. This chip manages the switching of our Buck-boost converter. When the supply loop has reached full capacity it will lock the supply loop. When the potential is transferred to the capacitors the supply loop is again unlocked. The LT3757 is an integrated circuit that uses inputs to determine precisely when to switch in order maximize power transfer. We can not do this manually or with our FPGA [5] and CPU [6] because of the asymptotic nature of capacitors and inductors. Unfortunately the LT3757 was designed for a resistive load, and while it can handle capacitive loads quite well there may be other chips that do it even better. We are looking at other possibilities and may improve on this component in the future.

=== Other converter methods ===

It has been suggested that other converter types may be able to charge the capacitors faster. A boost converter [7] may allow us to create a higher voltage potential. This would allow a faster transfer from the inductor to the capacitor. The other converter that has been looked at is the cuk converter [8]. A cuk converter might be able to allow the capacitors to be charged while other inductors are charging which would increase the rate of power transfer without raising the voltage across the capacitor. The electrical team is looking at these and other possibilities to improve on these systems in the future.

== Voltage Monitor ==

This component is covered in detail on the control board page.

[http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker http://wiki.robojackets.org/mediawiki/index.php?title=RoboCup:_Control_Board_2011#Voltage_Monitor_for_kicker]

== Kicker Trigger ==

[[File:Kicker trigger.PNG|thumb|left|600px]]

This section of the board allows the control board to release the energy stored in the capacitors into the kicker or chipper. This is done by using the TC4427 to control two high current, high voltage power transitors. These transistors will allow all of the energy stored in the capacitors to be released over the solenoid. There is a very value resistor and a diode pointing from the ground side of the solenoid to the power side in case the there is voltage overflow from the solenoid.

== Auto-Discharge ==

The other way for the capacitors to discharge is the auto-discharger. This section is controled by either the control board, when it needs less voltage to kick with or the by the LT3757 when it has reached the maximum voltage allowed by the circutry. This discharger has much lower current transitors and large resistors that limit the discharge current. This is never used for discharging the capacitors fully as it will take longer than kicking and will release a lot of heat if the full capacitors were discharged over this section.

== 2008 Model of the 2013 Board ==

The 2013 kicker boards have redplaced out the previous models of the 2008 and 2011 boards. The 2013 board is based on the 2011 version with the addition of some updated parts and adding a voltage monitor for the capacitors. However, the 2008 board was very different. While the 2011 and 2013 kicker boards have a chip port, the 2008 boards and robots could not chip the ball. We have removed the chipping components from certain boards to avoid confusion with ports and plugs. Additionally, some of the 2008 model 2013 boards do not have voltage monitoring components because the control boards are unable to read the voltage monitor in 2008 mode

== Parts list ==

Disclaimer: Some of the parts are not used in the final kicker board, but are printed on the mini board that is removed to make room for the capacitors. The parts list can be downloaded [http://wiki.robojackets.org/mediawiki/Media%3AKicker%20parts.pdf here].

== References ==
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li>[http://en.wikipedia.org/wiki/Transformer http://en.wikipedia.org/wiki/Transformer]</li>
<li>[http://en.wikipedia.org/wiki/Inductor#Stored_energy http://en.wikipedia.org/wiki/Inductor]</li>
<li>[http://en.wikipedia.org/wiki/Flyback_converter http://en.wikipedia.org/wiki/Flyback_converter]</li>
<li>[http://cds.linear.com/docs/en/datasheet/3757Afd.pdf http://cds.linear.com/docs/en/datasheet/3757Afd.pdf]</li>
<li>[http://en.wikipedia.org/wiki/Field-programmable_gate_array http://en.wikipedia.org/wiki/Field-programmable_gate_array]</li>
<li>[http://en.wikipedia.org/wiki/Microprocessor http://en.wikipedia.org/wiki/Microprocessor]</li>
<li>[http://en.wikipedia.org/wiki/Boost_converter http://en.wikipedia.org/wiki/Boost_converter]</li>
<li>[http://en.wikipedia.org/wiki/%C4%86uk_converter http://en.wikipedia.org/wiki/%C4%86uk_converter]</li>
</ol>

RoboCup: Competition 2014

2017-03-03T08:04:21Z

Rosawa3: Categorized

[[File:RoboCup-Competition-2014 Venue001.jpg|thumb|right|420px|The RoboCup competition's venue area in João Pessoa, Brazil.]]

This page is a compilation of the documentation, images, and other forms of information obtained at the RoboCup 2014 SSL competition in [http://en.wikipedia.org/wiki/Jo%C3%A3o_Pessoa,_Para%C3%ADba João Pessoa], Brazil.

__TOC__

== SSL Robot Gallery ==

The gallery below shows various teams that competed in the 2014 RoboCup SSL league.

<gallery align="center">
File:RoboCup-Competition-2014 ACES001.jpg | ACES
File:RoboCup-Competition-2014 ACES002.jpg | ACES
File:RoboCup-Competition-2014 ACES003.jpg | ACES
File:RoboCup-Competition-2014 ACES004.jpg | ACES
File:RoboCup-Competition-2014 ACES005.jpg | ACES
File:RoboCup-Competition-2014 ACES006.jpg | ACES
File:RoboCup-Competition-2014 CMDragons001.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons002.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons003.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons004.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons005.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons006.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons007.jpg | CMDragons
File:RoboCup-Competition-2014 ER-Force002.jpg | ER-Force
File:RoboCup-Competition-2014 ER-Force001.jpg | ER-Force
File:RoboCup-Competition-2014 Immortals001.jpg | Immortals
File:RoboCup-Competition-2014 Immortals002.jpg | Immortals
File:RoboCup-Competition-2014 Immortals003.jpg | Immortals
File:RoboCup-Competition-2014 Immortals004.jpg | Immortals
File:RoboCup-Competition-2014 KIKS001.jpg | KIKS
File:RoboCup-Competition-2014 KIKS002.jpg | KIKS
File:RoboCup-Competition-2014 KIKS003.jpg | KIKS
<-- File:RoboCup-Competition-2014 KIKS004.jpg | KIKS (This file number was skipped by accident when uploading)!-->
File:RoboCup-Competition-2014 KIKS005.jpg | KIKS
File:RoboCup-Competition-2014 KIKS006.jpg | KIKS
File:RoboCup-Competition-2014 KIKS007.jpg | KIKS
File:RoboCup-Competition-2014 KIKS008.jpg | KIKS
File:RoboCup-Competition-2014 KIKS009.jpg | KIKS
File:RoboCup-Competition-2014 KIKS010.jpg | KIKS
File:RoboCup-Competition-2014 KIKS011.jpg | KIKS
File:RoboCup-Competition-2014 KIKS012.jpg | KIKS
File:RoboCup-Competition-2014 KIKS013.jpg | KIKS
File:RoboCup-Competition-2014 KIKS014.jpg | KIKS
File:RoboCup-Competition-2014 KIKS015.jpg | KIKS
File:RoboCup-Competition-2014 KIKS016.jpg | KIKS
File:RoboCup-Competition-2014 KIKS017.jpg | KIKS
File:RoboCup-Competition-2014 KIKS018.jpg | KIKS
File:RoboCup-Competition-2014 KIKS019.jpg | KIKS
File:FileRoboCup-Competition-2014 MRL020.jpg | MRL
File:FileRoboCup-Competition-2014 MRL019.jpg | MRL
File:FileRoboCup-Competition-2014 MRL018.jpg | MRL
File:FileRoboCup-Competition-2014 MRL017.jpg | MRL
File:FileRoboCup-Competition-2014 MRL016.jpg | MRL
File:FileRoboCup-Competition-2014 MRL015.jpg | MRL
File:FileRoboCup-Competition-2014 MRL014.jpg | MRL
File:FileRoboCup-Competition-2014 MRL013.jpg | MRL
File:FileRoboCup-Competition-2014 MRL012.jpg | MRL
File:FileRoboCup-Competition-2014_MRL011.jpg | MRL
File:RoboCup-Competition-2014 MRL010.jpg | MRL
File:RoboCup-Competition-2014 MRL009.jpg | MRL
File:RoboCup-Competition-2014 MRL008.jpg | MRL
File:RoboCup-Competition-2014 MRL007.jpg | MRL
File:RoboCup-Competition-2014 MRL006.jpg | MRL
File:RoboCup-Competition-2014 MRL005.jpg | MRL
File:RoboCup-Competition-2014 MRL004.jpg | MRL
File:RoboCup-Competition-2014 MRL003.jpg | MRL
File:RoboCup-Competition-2014 MRL002.jpg | MRL
File:RoboCup-Competition-2014 MRL001.jpg | MRL
File:RoboCup-Competition-2014 RoboDragons001.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons002.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons003.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons004.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons005.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons006.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons007.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons008.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons009.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons010.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons011.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons012.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons013.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons014.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons015.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons016.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons017.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons018.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons019.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons020.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons021.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons022.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons023.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons024.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons025.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons026.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons027.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboIME001.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME002.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME003.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME004.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME005.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME006.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME007.jpg | RoboIME
File:RoboCup-Competition-2014 RoboJackets001.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets002.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets003.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets004.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets005.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets006.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets007.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets008.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets009.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets010.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets011.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets012.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets013.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets014.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets015.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets016.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets017.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets018.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets019.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets020.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets021.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets022.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets023.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets024.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets025.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets026.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets027.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets028.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets029.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets030.jpg | RoboJackets
File:RoboCup-Competition-2014 STOxs001.jpg | STOx's
File:RoboCup-Competition-2014 STOxs002.jpg | STOx's
File:RoboCup-Competition-2014 STOxs003.jpg | STOx's
File:RoboCup-Competition-2014 STOxs004.jpg | STOx's
File:RoboCup-Competition-2014 STOxs005.jpg | STOx's
File:RoboCup-Competition-2014 STOxs006.jpg | STOx's
File:RoboCup-Competition-2014 STOxs007.jpg | STOx's
File:RoboCup-Competition-2014 STOxs008.jpg | STOx's
File:RoboCup-Competition-2014 STOxs009.jpg | STOx's
File:RoboCup-Competition-2014 STOxs010.jpg | STOx's
File:RoboCup-Competition-2014 STOxs011.jpg | STOx's
File:RoboCup-Competition-2014 STOxs012.jpg | STOx's
File:RoboCup-Competition-2014 STOxs013.jpg | STOx's
File:RoboCup-Competition-2014 STOxs014.jpg | STOx's
File:RoboCup-Competition-2014 Thunderbolts001.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts002.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts003.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts004.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts005.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts006.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts007.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts008.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts009.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts010.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts011.jpg | Thunderbolts
File:RoboCup-Competition-2014 TigersMannheim012.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim011.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim010.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim009.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim008.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim007.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim006.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim005.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim004.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim003.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim002.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim001.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 WarthogRobotics001.jpg | Warthog Robotics
</gallery>

== SSL Team Notes ==

The following table of information was documented at the competition's venue.

Much of the information is incomplete because of the limited time at competition. The cells that contain only "--" indicate that no information was documented for that team's category. Blank cells indicate 1) an error occurred from transferring this information to the wiki or 2) the information was lost from a wiki edit.

{| class="wikitable"
|- style="height:20px;"
! id="0R0" style="height: 32px; white-space: nowrap; vertical-align: middle;" class="row-headers-background" |
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RoboDragons'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Warthog Robotics'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Thunderbolts'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Tigers Mannheim'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''NEUislanders'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''MRL'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RoboFEI'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Immortals'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''KIKS'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''ZJUNlict'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''ER-Force'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RoboIME'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''UaiSoccer'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''CMDragons'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Parsian'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''ACES'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''STOx's'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''BRocks'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Cyrus'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Eagle Knights'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''EMEnents'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''FURGbot'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''MCT Susanoo Logics'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''IRSS Deluxe'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RFC Cambridge'''</big>
! class="s2" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''KN2C'''</big>
|- style="height:25px;"
! id="0R0" style="height: 32px;" class="row-headers-background" |
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Japan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Canada''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Germany''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Cyprus''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Japan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''China''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Germany''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''United States''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Pakistan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Columbia''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Turkey''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Mexico''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Pakistan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Japan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Chile''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''United States''</var>
! class="s4" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
|- style="height:25px;"
| class="s5" dir="ltr" | '''Board Types/Qty'''
| class="s6" dir="ltr" | 1 board - outsourced
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | see Misc. Notes
| class="s6" dir="ltr" | custom boards
| class="s6" dir="ltr" | 1 main board; 1 small daughter board for ball sense
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | custom (3 total: control, kicker, power)
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Motor Capacitor(s)'''
| class="s8" dir="ltr" | none
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 1 large electrolytic capacitor
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | yes
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Antenna'''
| class="s6" dir="ltr" | see reference pictures
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | radio is from Microchip; they moved away from XBee
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | XBee
| class="s6" dir="ltr" | NRF
| class="s6" dir="ltr" | NRF
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s9" dir="ltr" | --
| class="s6" dir="ltr" | 2.5GHz
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | NRF 2401
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | NRF
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Microcotroller/FPGA'''
| class="s8" dir="ltr" | 4-5 chips; definitely had MCU and FPGA on board
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | STM32F4; ARM Cortex
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Atmel 312
| class="s8" dir="ltr" | Cyclone I FPGA, NXP Microcontroller (PN: LPC2378FBD144)
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Power Capacitor(s)'''
| class="s6" dir="ltr" | 2 x (250V, 2200�F)
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | total of 4000�F; voltage unknown
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | 2 large capacitors
| class="s6" dir="ltr" | 2 x (200V, 2700�F)
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | 4x 1200uF @ 200V
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Motor Wattage'''
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | 50W; removed standard plug and soldered wires directly
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | DC gearmotors
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Motor Gear Ratio (approx.)'''
| class="s6" dir="ltr" | ~1:2
| class="s6" dir="ltr" | 1:6
| class="s6" dir="ltr" | ~1:2
| class="s6" dir="ltr" | ~1:2
| class="s6" dir="ltr" | ~1:3
| class="s6" dir="ltr" | 1:3.6
| class="s6" dir="ltr" | dampened
| class="s6" dir="ltr" | ~1/3
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | 1:4
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~1:3
| class="s6" dir="ltr" | ~1:3
| class="s6" dir="ltr" | ~1/2.5?
| class="s6" dir="ltr" | 1:3.6
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Dribbler'''
| class="s8" dir="ltr" | dampened lower pivot; spring back via rubber; +5/8" OD; motor PN: 433326
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | diagonal sliding rail, clear polyurethane dribbler; ~5/8"; 3/2 ratio
| class="s8" dir="ltr" | ~1/2" OD; two separate rubber pieces to center ball; 2/1 ratio
| class="s8" dir="ltr" | undampened; 1/2" squishy foam/rubber; Also have concave dribbler but said it was untested
| class="s8" dir="ltr" | heavily dampened; lower pivot; 5/8" OD
| class="s8" dir="ltr" | 5/8" OD; 1:3 ratio; belt drive; dampened upper pivot
| class="s8" dir="ltr" | ~5/8" OD, damped, lower pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 1/2", damped, ~3/2 ratio
| class="s8" dir="ltr" | rubber; 5/8" OD; ~3/2 ratio; dampened lower pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 5/8" OD; squishy ruber; dampened top pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 5/8" OD, dampened lower pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Mouth Width'''
| class="s6" dir="ltr" | ~3.125"
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~2.4"
| class="s6" dir="ltr" | not blocked; open design; ~2.75" chipper plate
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~3.125"
| class="s6" dir="ltr" | ~2.5"
| class="s6" dir="ltr" | --
|
| class="s6" dir="ltr" | ~3.125
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~3.25"
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Kicker Solenoid'''
| class="s8" dir="ltr" | Flat
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | small cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Cylindrical
| class="s8" dir="ltr" | cylindrical; 7/8" OD
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Flat
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Chipper Solenoid'''
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Flat; pulls diagonally downward
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | cylindrical
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Cylindrical
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Shell'''
| class="s8" dir="ltr" | carbon fiber exterior; plastic top with stick on dots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | plastic sheet, colors taped on top; screws sticking up for alignment
| class="s8" dir="ltr" | plastic sheet for old ones; separate top section; screws sticking up for alignment
| class="s8" dir="ltr" | plastic top only
| class="s8" dir="ltr" | milled from single block of plastic; Significant amount of material is milled away
| class="s8" dir="ltr" | carbon fiber; 3 layers; flexible & rugged; possible radio interference; also uses a standard plastic sheet
| class="s8" dir="ltr" | Plastic wrapped with a separate top piece glued onto it
| class="s8" dir="ltr" | Looked to be casted in a plastic-type resin/epoxy (their shell had small bubbles in it that are usually seen n casted objects)
| class="s8" dir="ltr" | Plastic shell with paper top piece
| class="s8" dir="ltr" | magnetic top piece; wrapped plastic sheet for sides
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | plastic top
| class="s8" dir="ltr" | fiberglass; stick on dots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Plastic sheet wrapped around, separate paper top section for dots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Motor Driver/Configuration'''
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | similar to our 2014 proto
| class="s6" dir="ltr" | off the shelf
| class="s6" dir="ltr" | 3 drivers, 3 fets, and mystery chip on every motor; 100K between gate and source; see pictures for exact details
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | L6240 chip
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:86px;"
| class="s10" dir="ltr" | '''Misc. Notes'''
| class="s8" dir="ltr" | no hardware team; electronics outsourced to SMATS; robots are $10K each; they have 12 robots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | all electronics are open source
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | the routing was atrocious; they said they never replace parts during competition; they print boards every year. Email for contacting electrical lead: hosseinikia.adel@gmail.com
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | uses magnetic encoders (PN: AS4050) that have 210 resolution
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | the team said that the best electrical team were the tigers
| class="s8" dir="ltr" | contact: awaisazhar84@yahoo.com (M. Awais Azhar); their university was founded by several GT graduates
| class="s8" dir="ltr" | their electrical boards are printed locally in Colombia. Ball sensors are held on by screwed in U-blocks
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|}

[[Category:RoboCup]]
[[Category:Electrical]]
[[Category:Mechanical]]
[[Category:Year: 2013-2014]]

RoboCup: Competition 2014

2017-03-03T08:02:33Z

Rosawa3: ã

[[File:RoboCup-Competition-2014 Venue001.jpg|thumb|right|420px|The RoboCup competition's venue area in João Pessoa, Brazil.]]

This page is a compilation of the documentation, images, and other forms of information obtained at the RoboCup 2014 SSL competition in [http://en.wikipedia.org/wiki/Jo%C3%A3o_Pessoa,_Para%C3%ADba João Pessoa], Brazil.

__TOC__

== SSL Robot Gallery ==

The gallery below shows various teams that competed in the 2014 RoboCup SSL league.

<gallery align="center">
File:RoboCup-Competition-2014 ACES001.jpg | ACES
File:RoboCup-Competition-2014 ACES002.jpg | ACES
File:RoboCup-Competition-2014 ACES003.jpg | ACES
File:RoboCup-Competition-2014 ACES004.jpg | ACES
File:RoboCup-Competition-2014 ACES005.jpg | ACES
File:RoboCup-Competition-2014 ACES006.jpg | ACES
File:RoboCup-Competition-2014 CMDragons001.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons002.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons003.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons004.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons005.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons006.jpg | CMDragons
File:RoboCup-Competition-2014 CMDragons007.jpg | CMDragons
File:RoboCup-Competition-2014 ER-Force002.jpg | ER-Force
File:RoboCup-Competition-2014 ER-Force001.jpg | ER-Force
File:RoboCup-Competition-2014 Immortals001.jpg | Immortals
File:RoboCup-Competition-2014 Immortals002.jpg | Immortals
File:RoboCup-Competition-2014 Immortals003.jpg | Immortals
File:RoboCup-Competition-2014 Immortals004.jpg | Immortals
File:RoboCup-Competition-2014 KIKS001.jpg | KIKS
File:RoboCup-Competition-2014 KIKS002.jpg | KIKS
File:RoboCup-Competition-2014 KIKS003.jpg | KIKS
<-- File:RoboCup-Competition-2014 KIKS004.jpg | KIKS (This file number was skipped by accident when uploading)!-->
File:RoboCup-Competition-2014 KIKS005.jpg | KIKS
File:RoboCup-Competition-2014 KIKS006.jpg | KIKS
File:RoboCup-Competition-2014 KIKS007.jpg | KIKS
File:RoboCup-Competition-2014 KIKS008.jpg | KIKS
File:RoboCup-Competition-2014 KIKS009.jpg | KIKS
File:RoboCup-Competition-2014 KIKS010.jpg | KIKS
File:RoboCup-Competition-2014 KIKS011.jpg | KIKS
File:RoboCup-Competition-2014 KIKS012.jpg | KIKS
File:RoboCup-Competition-2014 KIKS013.jpg | KIKS
File:RoboCup-Competition-2014 KIKS014.jpg | KIKS
File:RoboCup-Competition-2014 KIKS015.jpg | KIKS
File:RoboCup-Competition-2014 KIKS016.jpg | KIKS
File:RoboCup-Competition-2014 KIKS017.jpg | KIKS
File:RoboCup-Competition-2014 KIKS018.jpg | KIKS
File:RoboCup-Competition-2014 KIKS019.jpg | KIKS
File:FileRoboCup-Competition-2014 MRL020.jpg | MRL
File:FileRoboCup-Competition-2014 MRL019.jpg | MRL
File:FileRoboCup-Competition-2014 MRL018.jpg | MRL
File:FileRoboCup-Competition-2014 MRL017.jpg | MRL
File:FileRoboCup-Competition-2014 MRL016.jpg | MRL
File:FileRoboCup-Competition-2014 MRL015.jpg | MRL
File:FileRoboCup-Competition-2014 MRL014.jpg | MRL
File:FileRoboCup-Competition-2014 MRL013.jpg | MRL
File:FileRoboCup-Competition-2014 MRL012.jpg | MRL
File:FileRoboCup-Competition-2014_MRL011.jpg | MRL
File:RoboCup-Competition-2014 MRL010.jpg | MRL
File:RoboCup-Competition-2014 MRL009.jpg | MRL
File:RoboCup-Competition-2014 MRL008.jpg | MRL
File:RoboCup-Competition-2014 MRL007.jpg | MRL
File:RoboCup-Competition-2014 MRL006.jpg | MRL
File:RoboCup-Competition-2014 MRL005.jpg | MRL
File:RoboCup-Competition-2014 MRL004.jpg | MRL
File:RoboCup-Competition-2014 MRL003.jpg | MRL
File:RoboCup-Competition-2014 MRL002.jpg | MRL
File:RoboCup-Competition-2014 MRL001.jpg | MRL
File:RoboCup-Competition-2014 RoboDragons001.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons002.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons003.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons004.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons005.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons006.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons007.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons008.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons009.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons010.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons011.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons012.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons013.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons014.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons015.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons016.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons017.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons018.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons019.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons020.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons021.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons022.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons023.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons024.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons025.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons026.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboDragons027.jpg | RoboDragons
File:RoboCup-Competition-2014 RoboIME001.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME002.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME003.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME004.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME005.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME006.jpg | RoboIME
File:RoboCup-Competition-2014 RoboIME007.jpg | RoboIME
File:RoboCup-Competition-2014 RoboJackets001.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets002.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets003.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets004.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets005.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets006.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets007.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets008.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets009.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets010.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets011.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets012.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets013.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets014.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets015.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets016.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets017.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets018.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets019.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets020.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets021.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets022.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets023.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets024.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets025.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets026.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets027.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets028.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets029.jpg | RoboJackets
File:RoboCup-Competition-2014 RoboJackets030.jpg | RoboJackets
File:RoboCup-Competition-2014 STOxs001.jpg | STOx's
File:RoboCup-Competition-2014 STOxs002.jpg | STOx's
File:RoboCup-Competition-2014 STOxs003.jpg | STOx's
File:RoboCup-Competition-2014 STOxs004.jpg | STOx's
File:RoboCup-Competition-2014 STOxs005.jpg | STOx's
File:RoboCup-Competition-2014 STOxs006.jpg | STOx's
File:RoboCup-Competition-2014 STOxs007.jpg | STOx's
File:RoboCup-Competition-2014 STOxs008.jpg | STOx's
File:RoboCup-Competition-2014 STOxs009.jpg | STOx's
File:RoboCup-Competition-2014 STOxs010.jpg | STOx's
File:RoboCup-Competition-2014 STOxs011.jpg | STOx's
File:RoboCup-Competition-2014 STOxs012.jpg | STOx's
File:RoboCup-Competition-2014 STOxs013.jpg | STOx's
File:RoboCup-Competition-2014 STOxs014.jpg | STOx's
File:RoboCup-Competition-2014 Thunderbolts001.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts002.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts003.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts004.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts005.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts006.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts007.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts008.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts009.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts010.jpg | Thunderbolts
File:RoboCup-Competition-2014 Thunderbolts011.jpg | Thunderbolts
File:RoboCup-Competition-2014 TigersMannheim012.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim011.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim010.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim009.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim008.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim007.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim006.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim005.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim004.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim003.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim002.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 TigersMannheim001.jpg | Tigers Mannheim
File:RoboCup-Competition-2014 WarthogRobotics001.jpg | Warthog Robotics
</gallery>

== SSL Team Notes ==

The following table of information was documented at the competition's venue.

Much of the information is incomplete because of the limited time at competition. The cells that contain only "--" indicate that no information was documented for that team's category. Blank cells indicate 1) an error occurred from transferring this information to the wiki or 2) the information was lost from a wiki edit.

{| class="wikitable"
|- style="height:20px;"
! id="0R0" style="height: 32px; white-space: nowrap; vertical-align: middle;" class="row-headers-background" |
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RoboDragons'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Warthog Robotics'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Thunderbolts'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Tigers Mannheim'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''NEUislanders'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''MRL'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RoboFEI'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Immortals'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''KIKS'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''ZJUNlict'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''ER-Force'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RoboIME'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''UaiSoccer'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''CMDragons'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Parsian'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''ACES'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''STOx's'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''BRocks'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Cyrus'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''Eagle Knights'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''EMEnents'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''FURGbot'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''MCT Susanoo Logics'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''IRSS Deluxe'''</big>
! class="s1" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''RFC Cambridge'''</big>
! class="s2" dir="ltr" style="text-align: center; white-space: nowrap; vertical-align: middle;" | <big>'''KN2C'''</big>
|- style="height:25px;"
! id="0R0" style="height: 32px;" class="row-headers-background" |
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Japan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Canada''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Germany''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Cyprus''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Japan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''China''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Germany''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''United States''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Pakistan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Columbia''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Turkey''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Mexico''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Pakistan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Brazil''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Japan''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Chile''</var>
! class="s3" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''United States''</var>
! class="s4" dir="ltr" style="text-align: center; vertical-align: middle;" | <var>''Iran''</var>
|- style="height:25px;"
| class="s5" dir="ltr" | '''Board Types/Qty'''
| class="s6" dir="ltr" | 1 board - outsourced
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | see Misc. Notes
| class="s6" dir="ltr" | custom boards
| class="s6" dir="ltr" | 1 main board; 1 small daughter board for ball sense
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | custom (3 total: control, kicker, power)
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Motor Capacitor(s)'''
| class="s8" dir="ltr" | none
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 1 large electrolytic capacitor
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | yes
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Antenna'''
| class="s6" dir="ltr" | see reference pictures
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | radio is from Microchip; they moved away from XBee
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | XBee
| class="s6" dir="ltr" | NRF
| class="s6" dir="ltr" | NRF
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s9" dir="ltr" | --
| class="s6" dir="ltr" | 2.5GHz
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | NRF 2401
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | NRF
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Microcotroller/FPGA'''
| class="s8" dir="ltr" | 4-5 chips; definitely had MCU and FPGA on board
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | STM32F4; ARM Cortex
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Atmel 312
| class="s8" dir="ltr" | Cyclone I FPGA, NXP Microcontroller (PN: LPC2378FBD144)
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Power Capacitor(s)'''
| class="s6" dir="ltr" | 2 x (250V, 2200�F)
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | total of 4000�F; voltage unknown
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | 2 large capacitors
| class="s6" dir="ltr" | 2 x (200V, 2700�F)
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | 4x 1200uF @ 200V
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Motor Wattage'''
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | 50W; removed standard plug and soldered wires directly
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | 30W
| class="s8" dir="ltr" | DC gearmotors
| class="s8" dir="ltr" | 50W
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Motor Gear Ratio (approx.)'''
| class="s6" dir="ltr" | ~1:2
| class="s6" dir="ltr" | 1:6
| class="s6" dir="ltr" | ~1:2
| class="s6" dir="ltr" | ~1:2
| class="s6" dir="ltr" | ~1:3
| class="s6" dir="ltr" | 1:3.6
| class="s6" dir="ltr" | dampened
| class="s6" dir="ltr" | ~1/3
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | 1:4
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~1:3
| class="s6" dir="ltr" | ~1:3
| class="s6" dir="ltr" | ~1/2.5?
| class="s6" dir="ltr" | 1:3.6
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Dribbler'''
| class="s8" dir="ltr" | dampened lower pivot; spring back via rubber; +5/8" OD; motor PN: 433326
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | diagonal sliding rail, clear polyurethane dribbler; ~5/8"; 3/2 ratio
| class="s8" dir="ltr" | ~1/2" OD; two separate rubber pieces to center ball; 2/1 ratio
| class="s8" dir="ltr" | undampened; 1/2" squishy foam/rubber; Also have concave dribbler but said it was untested
| class="s8" dir="ltr" | heavily dampened; lower pivot; 5/8" OD
| class="s8" dir="ltr" | 5/8" OD; 1:3 ratio; belt drive; dampened upper pivot
| class="s8" dir="ltr" | ~5/8" OD, damped, lower pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 1/2", damped, ~3/2 ratio
| class="s8" dir="ltr" | rubber; 5/8" OD; ~3/2 ratio; dampened lower pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 5/8" OD; squishy ruber; dampened top pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | 5/8" OD, dampened lower pivot
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Mouth Width'''
| class="s6" dir="ltr" | ~3.125"
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~2.4"
| class="s6" dir="ltr" | not blocked; open design; ~2.75" chipper plate
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~3.125"
| class="s6" dir="ltr" | ~2.5"
| class="s6" dir="ltr" | --
|
| class="s6" dir="ltr" | ~3.125
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | ~3.25"
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Kicker Solenoid'''
| class="s8" dir="ltr" | Flat
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | small cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Cylindrical
| class="s8" dir="ltr" | cylindrical; 7/8" OD
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | cylindrical
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Flat
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Chipper Solenoid'''
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Flat; pulls diagonally downward
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | cylindrical
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Cylindrical
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | Flat
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:25px;"
| class="s5" dir="ltr" | '''Shell'''
| class="s8" dir="ltr" | carbon fiber exterior; plastic top with stick on dots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | plastic sheet, colors taped on top; screws sticking up for alignment
| class="s8" dir="ltr" | plastic sheet for old ones; separate top section; screws sticking up for alignment
| class="s8" dir="ltr" | plastic top only
| class="s8" dir="ltr" | milled from single block of plastic; Significant amount of material is milled away
| class="s8" dir="ltr" | carbon fiber; 3 layers; flexible & rugged; possible radio interference; also uses a standard plastic sheet
| class="s8" dir="ltr" | Plastic wrapped with a separate top piece glued onto it
| class="s8" dir="ltr" | Looked to be casted in a plastic-type resin/epoxy (their shell had small bubbles in it that are usually seen n casted objects)
| class="s8" dir="ltr" | Plastic shell with paper top piece
| class="s8" dir="ltr" | magnetic top piece; wrapped plastic sheet for sides
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | plastic top
| class="s8" dir="ltr" | fiberglass; stick on dots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | Plastic sheet wrapped around, separate paper top section for dots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|- style="height:25px;"
| class="s7" dir="ltr" | '''Motor Driver/Configuration'''
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | similar to our 2014 proto
| class="s6" dir="ltr" | off the shelf
| class="s6" dir="ltr" | 3 drivers, 3 fets, and mystery chip on every motor; 100K between gate and source; see pictures for exact details
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | L6240 chip
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
| class="s6" dir="ltr" | --
|- style="height:86px;"
| class="s10" dir="ltr" | '''Misc. Notes'''
| class="s8" dir="ltr" | no hardware team; electronics outsourced to SMATS; robots are $10K each; they have 12 robots
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | all electronics are open source
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | the routing was atrocious; they said they never replace parts during competition; they print boards every year. Email for contacting electrical lead: hosseinikia.adel@gmail.com
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | uses magnetic encoders (PN: AS4050) that have 210 resolution
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | the team said that the best electrical team were the tigers
| class="s8" dir="ltr" | contact: awaisazhar84@yahoo.com (M. Awais Azhar); their university was founded by several GT graduates
| class="s8" dir="ltr" | their electrical boards are printed locally in Colombia. Ball sensors are held on by screwed in U-blocks
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
| class="s8" dir="ltr" | --
|}

 
[[Category:RoboCup]] [[Category:Electrical]] [[Category:Mechanical]]

RoboCup Electrical Videos

2016-10-15T17:39:44Z

Rosawa3: information correction and update

===Our Electronics===

{{#ev:youtube|QW-0nHqe_cs}}
{{#ev:youtube|gMIDPzHxAfQ}}
{{#ev:youtube|OMX8eMjGRJ0}}
{{#ev:youtube|06bCbVkQTWc}}
{{#ev:youtube|o4OC23Qmz_w}}

===General EE relevant to us===
{{#ev:youtube|06akxR14d1M}}
{{#ev:youtube|gUsHwi4M4xE}}
{{#ev:youtube|7AFGcAyK7kE}}
{{#ev:youtube|hpZFiR8kM2g}}
{{#ev:youtube|ZAY5JInyHXY}}
{{#ev:youtube|WyQInXjpGwU}}
{{#ev:youtube|H3Dj5g4qSoc}}
(We use a network analyzer to tune our antennas [pre-DecaWave])
{{#ev:youtube|KdW9ALJMk7s}}
(We use quaternions and Euler angles for our IMU [inertial measurement unit])
{{#ev:youtube|cM7t1Mpu7s4}}
{{#ev:youtube|EyHUfZxmP8s}}
{{#ev:youtube|Aju-Y08XlQ4}}
(Similar to how our kicker electronics work)

[[Category: RoboCup]]
[[Category: Electrical]]
[[Category: Resources for Learning]]

People with Keys

2016-10-14T06:01:17Z

Rosawa3: removed "_" in the Shop_Keys alias

'''These people have keys to the RoboJackets shop area. ''' See [[Shop_Keys|Shop Keys]] for details on key assignments.

{| class="wikitable sortable"
|-
! Key Number
! Assigned To
|-
| 3SB6: 1
| [[User:Rmartin|Ryan Martin]]
|-
| 3SB6: 4
| Kelvin Chong
|-
| 3SB6: 5
| [[User:Petersonev|Evan Peterson]]
|-
| 3SB6: 7
| Jonathan Spalten
|-
| 3SB6: 8
| [[User:Sastorer3|Sarah Storer]]
|-
| 3SB6: 9
| [[User:Biachonkov3|Boris Iachonkov]]
|-
| 3SB6:12
| [[User:Radebayo|Ransomed Adebayo]]
|-
| 3SB6:14
| Gabriel Nakajima An
|-
| 3SB6:15
| [[User:S|Sean Csukas]]
|-
| 3SB6:18
| [[User:Kberzinch|Kristaps Berzinch]]
|-
| 3SB6:19
| ''Unclaimed - In Money Box''
|-
| 3SB6:20
| ''Unclaimed - In Money Box''
|-
| 3SB6:21
| [[User:Guyfleeman|Will Stuckey]]
|-
| 3SB6:22
| Noah Daugherty
|-
| 3SB6:23
| [[User:Dchoi|Daniel Choi]]
|-
| 3SB6:24
| [[User:Rstrat|Ryan Strat]]
|-
| 3SB6:29
| [[User:Mbarulic|Matthew Barulic]]
|-
| 3SB6:31
| Orlin Velev
|}

People with Keys

2016-10-14T06:00:32Z

Rosawa3: removed some tags

'''These people have keys to the RoboJackets shop area. ''' See [[Shop_Keys|Shop_Keys]] for details on key assignments.

{| class="wikitable sortable"
|-
! Key Number
! Assigned To
|-
| 3SB6: 1
| [[User:Rmartin|Ryan Martin]]
|-
| 3SB6: 4
| Kelvin Chong
|-
| 3SB6: 5
| [[User:Petersonev|Evan Peterson]]
|-
| 3SB6: 7
| Jonathan Spalten
|-
| 3SB6: 8
| [[User:Sastorer3|Sarah Storer]]
|-
| 3SB6: 9
| [[User:Biachonkov3|Boris Iachonkov]]
|-
| 3SB6:12
| [[User:Radebayo|Ransomed Adebayo]]
|-
| 3SB6:14
| Gabriel Nakajima An
|-
| 3SB6:15
| [[User:S|Sean Csukas]]
|-
| 3SB6:18
| [[User:Kberzinch|Kristaps Berzinch]]
|-
| 3SB6:19
| ''Unclaimed - In Money Box''
|-
| 3SB6:20
| ''Unclaimed - In Money Box''
|-
| 3SB6:21
| [[User:Guyfleeman|Will Stuckey]]
|-
| 3SB6:22
| Noah Daugherty
|-
| 3SB6:23
| [[User:Dchoi|Daniel Choi]]
|-
| 3SB6:24
| [[User:Rstrat|Ryan Strat]]
|-
| 3SB6:29
| [[User:Mbarulic|Matthew Barulic]]
|-
| 3SB6:31
| Orlin Velev
|}

User:Rosawa3

2016-10-14T05:35:11Z

Rosawa3: update link

[[File:Kokkuri.png|right|kokkuri.png]]

'''Name:''' Ryo Osawa

'''E-mail:''' [mailto:rosawa@gatech.edu rosawa@gatech.edu]

'''Phone:''' 1-404-883-8143

'''Major:''' Electrical Engineering / Information and Intelligent Systems

'''Position:''' Alumni (RoboCup Electrical)

== Involvement ==

*[[RoboCup]]
**[[RoboCup Electrical 2012]]
**[[RoboCup Electrical 2013]]
**[[RoboCup Electrical 2014]]
**[[RoboCup Electrical 2015]]
**RoboCup Electrical 2016
**RoboCup Electrical 2017

*Tohoku University JYPE 2013-2014
**[http://www.eng.tohoku.ac.jp/english/academics/studies/bachelor/iis.html Department of Information and Intelligent Systems (now Department of Electrical, Information and Physics Engineering)]
***[http://www.riec.tohoku.ac.jp/introduction/organization/division/ultra-broad/ Ultra-Broadband Signal Processing]

User:Rosawa3

2016-10-14T05:32:47Z

Rosawa3: removed broken link (2013-2014 page was taken down)

[[File:Kokkuri.png|right|kokkuri.png]]

'''Name:''' Ryo Osawa

'''E-mail:''' [mailto:rosawa@gatech.edu rosawa@gatech.edu]

'''Phone:''' 1-404-883-8143

'''Major:''' Electrical Engineering / Information and Intelligent Systems

'''Position:''' Alumni (RoboCup Electrical)

== Involvement ==

*[[RoboCup]]
**[[RoboCup Electrical 2012]]
**[[RoboCup Electrical 2013]]
**[[RoboCup Electrical 2014]]
**[[RoboCup Electrical 2015]]
**RoboCup Electrical 2016
**RoboCup Electrical 2017

*Tohoku University JYPE 2013-2014
**[http://www.eng.tohoku.ac.jp/english/academics/studies/bachelor/iis.html Department of Information and Intelligent Systems (now Department of Electrical, Information and Physics Engineering)]
***[http://www.riec.tohoku.ac.jp/lab/ultra-broad/index-e.html Ultra-Broadband Signal Processing]

User:Rosawa3

2016-10-14T05:29:11Z

Rosawa3: removed no break space

[[File:Kokkuri.png|right|kokkuri.png]]

'''Name:''' Ryo Osawa

'''E-mail:''' [mailto:rosawa@gatech.edu rosawa@gatech.edu]

'''Phone:''' 1-404-883-8143

'''Major:''' Electrical Engineering / Information and Intelligent Systems

'''Position:''' Alumni (RoboCup Electrical)

== Involvement ==

*[[RoboCup]]
**[[RoboCup Electrical 2012]]
**[[RoboCup Electrical 2013]]
**[[RoboCup Electrical 2014]]
**[[RoboCup Electrical 2015]]
**RoboCup Electrical 2016
**RoboCup Electrical 2017

*[https://www.cefix.insc.tohoku.ac.jp/ASEP/JYPE_2013-2014/index.html Tohoku University JYPE 2013-2014]
**[http://www.eng.tohoku.ac.jp/english/academics/studies/bachelor/iis.html Department of Information and Intelligent Systems (now Department of Electrical, Information and Physics Engineering)]
***[http://www.riec.tohoku.ac.jp/lab/ultra-broad/index-e.html Ultra-Broadband Signal Processing]

User:Petersonev

2016-10-14T05:26:29Z

Rosawa3: removed no break spaces

'''Name:''' Evan Peterson

'''E-Mail:''' epeterson35@gatech.edu

'''Major:''' Computer Engineering

'''Position:''' RoboCup Electrical Lead

User:Petersonev

2016-10-14T05:25:44Z

Rosawa3: RoboCup

'''Name: '''Evan Peterson

'''E-Mail:''' epeterson35@gatech.edu

'''Major: '''Computer Engineering

'''Position: '''RoboCup Electrical Lead

RoboCup

2016-10-11T03:18:07Z

Rosawa3: fixed some links

[[File:RoboCup-Competition-2014 DisplayBot.jpg|thumb|right|420px|RoboJackets Current Design at Joao Pessoa, Brazil]]

The Georgia Tech RoboJackets RoboCup Small-Size League team competes in a 6-on-6 AI-driven soccer match against teams from around the world. The field is equipped with two overhead cameras, which act as the primary information source for the selection of plays and tactics. If you haven't already, subscribe to the [https://lists.gatech.edu/sympa/subscribe/robojackets-robocup RoboCup Mailing List].

== Important Items ==

*The [[RoboCup:_Redesign_2014-2015|2014-2015 Redesign]]
*[[TDP|Team Description Papers (TDP)]]
*[http://inventory.robojackets.org/ Electrical Inventory]
*[http://wiki.robojackets.org/images/e/ef/DISPOSAL-OF-LIPO-BATTERIES.pdf Battery Disposal] 
*[http://robocupssl.cpe.ku.ac.th/ RoboCup Small Size League (SSL) Website]
*[[RoboCup_System_Archive|System Archive]]

== Electrical ==

[[Electrical_Room_Equipment|Electrical Room Equipment]]

[http://wiki.robojackets.org/index.php?title=Special:MultiCategorySearch&&wpInCategory1=RoboCup&wpInCategory2=Electrical&limit=500&offset=0 List of RoboCup Electrical Wiki Pages]

[[Be_A_Great_EE|How to be a Great Electrical Engineer]]

[[RoboCup_Electrical_2015|RoboCup Electrical 2015]]

=== Control Board 2011 ===

[[RoboCup:_Control_Board_2011|Control Board 2011c Reference Page]]

[http://wiki.robojackets.org/images/c/c3/RC_LightDecoder.jpg LED Indicator Reference Sheet]

=== Reflow Oven ===

[[RoboCup:_Reflow_Soldering_Oven|Reflow Oven Project]]

=== Design Programs ===

[https://cadsoft.io/ CadSoft EAGLE]

*Schematic/PCB editor

[http://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/design-tools.html Xilinx ISE Design Suite]

*Verilog synthesis
*FPGA pin configurations

[https://www.pentalogix.com/viewmate.php ViewMate]

*Solder paste stencil editing/verification
**Download free trial and ''print ''to a PDF for keeping a [http://en.wikipedia.org/wiki/Vector_graphics vector] formatted file

[http://www.altium.com/altium-designer/overview Altium Designer]

*Schematic/PCB editor
*Same guys from [http://www.circuitmaker.com/#why_circuitmaker circuitmaker.com]
*PCB symbol font [http://techdocs.altium.com/sites/default/files/wiki_attachments/231684/2014Mar29_Font-Truetype.zip download]

[http://mayhewlabs.com/3dpcb Mayhew Labs 3-D Gerber Viewer]

*[http://www.instructables.com/files/orig/FQ3/FCYP/H0OJ0U5Y/FQ3FCYPH0OJ0U5Y.cam CAM Job]
**Export gerbers and drill
**Select all relevant gerber and drill files
**Drag-and-drop files
**Select the corresponding gerbers for each layer and the drill file
**Inspect the PCB

=== Learning Resources ===

[[RoboJackets_Electrical_Training|RoboJackets Electrical Training]]

[[RoboCup_Electrical_Videos|RoboCup Electrical Video Tutorials]]

== Mechanical ==

[http://wiki.robojackets.org/index.php?title=Special:MultiCategorySearch&&wpInCategory1=RoboCup&wpInCategory2=Mechanical&limit=500&offset=0 List of all RoboCup Mechanical Works]

[[RoboCup_Mechanical_2015|RoboCup Mechanical 2015]]

== Software ==

[http://wiki.robojackets.org/index.php?title=Special:MultiCategorySearch&&wpInCategory1=RoboCup&wpInCategory2=Software&limit=500&offset=0 List of all RoboCup Software Works]

[[RoboCup_Software|RoboCup Software]]

[[RoboCup_Live_Robot_Execution|Manual Drive Control]]

[[RC14IMU|IMU]]

== Example Matches ==

[http://www.youtube.com/watch?v=nl9YupK0Y7U SKUBA(blue) vs. ZJUNlict(yellow)]

[http://www.youtube.com/watch?v=vguuLGDdSnU Parsian(yellow) vs. KIKS(blue)]

== Current Officers ==

*Will Stuckey - Project Manager
*Evan Peterson - Electrical Lead
*Gabriel Nakajima An - Mechanical Lead
*Jay Kamat - Software Lead

== Reference Documents ==

[[Research_Papers|Research Papers]]

[[Resources_for_Learning|General Resources for Learning]]

[[RCResources|RoboCup-Specific Resources for Learning]]
[[Category:RoboCup]]

RoboCup

2016-10-11T03:17:24Z

Rosawa3: /* Design Programs */ updated EAGLE link

[[File:RoboCup-Competition-2014 DisplayBot.jpg|thumb|right|420px|RoboJackets Current Design at Joao Pessoa, Brazil]]

The Georgia Tech RoboJackets RoboCup Small-Size League team competes in a 6-on-6 AI-driven soccer match against teams from around the world. The field is equipped with two overhead cameras, which act as the primary information source for the selection of plays and tactics. If you haven't already, subscribe to the [https://lists.gatech.edu/sympa/subscribe/robojackets-robocup RoboCup Mailing List].

== Important Items ==

*The [[RoboCup:_Redesign_2014-2015|2014-2015 Redesign]]
*[[TDP|Team Description Papers (TDP)]]
*[http://inventory.robojackets.org/ Electrical Inventory]
*[http://wiki.robojackets.org/images/e/ef/DISPOSAL-OF-LIPO-BATTERIES.pdf Battery Disposal] 
*[http://robocupssl.cpe.ku.ac.th/ RoboCup Small Size League (SSL) Website]
*[[RoboCup_System_Archive|System Archive]]

== Electrical ==

[[Electrical_Room_Equipment|Electrical Room Equipment]]

[http://wiki.robojackets.org/index.php?title=Special:MultiCategorySearch&&wpInCategory1=RoboCup&wpInCategory2=Electrical&limit=500&offset=0 List of RoboCup Electrical Wiki Pages]

[[Be_A_Great_EE|How to be a Great Electrical Engineer]]

[[RoboCup_Electrical_2015|RoboCup Electrical 2015]]

=== Control Board 2011 ===

[[RoboCup:_Control_Board_2011|Control Board 2011c Reference Page]]

[http://wiki.robojackets.org/images/c/c3/RC_LightDecoder.jpg LED Indicator Reference Sheet]

=== Reflow Oven ===

[[RoboCup:_Reflow_Soldering_Oven|Reflow Oven Project]]

=== Design Programs ===

[https://cadsoft.io/ CadSoft EAGLE]

*Schematic/PCB editor

[http://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/design-tools.html Xilinx ISE Design Suite]

*Verilog synthesis
*FPGA pin configurations

[https://www.pentalogix.com/viewmate.php ViewMate]

*Solder paste stencil editing/verification
**Download free trial and ''print ''to a PDF for keeping a [http://en.wikipedia.org/wiki/Vector_graphics vector] formatted file

[http://www.altium.com/altium-designer/overview Altium Designer]

*Schematic/PCB editor
*Same guys from [http://www.circuitmaker.com/#why_circuitmaker circuitmaker.com]
*PCB symbol font [http://techdocs.altium.com/sites/default/files/wiki_attachments/231684/2014Mar29_Font-Truetype.zip download]

[http://mayhewlabs.com/3dpcb Mayhew Labs 3-D Gerber Viewer]

*[http://www.instructables.com/files/orig/FQ3/FCYP/H0OJ0U5Y/FQ3FCYPH0OJ0U5Y.cam CAM Job]
**Export gerbers and drill
**Select all relevant gerber and drill files
**Drag-and-drop files
**Select the corresponding gerbers for each layer and the drill file
**Inspect the PCB

=== Learning Resources ===

[[RoboJackets_Electrical_Training|RoboJackets Electrical Training]]

[[RoboCup_Electrical_Videos|RoboCup Electrical Video Tutorials]]

== Mechanical ==

[http://wiki.robojackets.org/mediawiki/index.php?title=Special:MultiCategorySearch&&wpInCategory1=RoboCup&wpInCategory2=Mechanical&limit=500&offset=0 List of all RoboCup Mechanical Works]

[[RoboCup_Mechanical_2015|RoboCup Mechanical 2015]]

== Software ==

[http://wiki.robojackets.org/mediawiki/index.php?title=Special:MultiCategorySearch&&wpInCategory1=RoboCup&wpInCategory2=Software&limit=500&offset=0 List of all RoboCup Software Works]

[[RoboCup_Software|RoboCup Software]]

[[RoboCup_Live_Robot_Execution|Manual Drive Control]]

[[RC14IMU|IMU]]

== Example Matches ==

[http://www.youtube.com/watch?v=nl9YupK0Y7U SKUBA(blue) vs. ZJUNlict(yellow)]

[http://www.youtube.com/watch?v=vguuLGDdSnU Parsian(yellow) vs. KIKS(blue)]

== Current Officers ==

*Will Stuckey - Project Manager
*Evan Peterson - Electrical Lead
*Gabriel Nakajima An - Mechanical Lead
*Jay Kamat - Software Lead

== Reference Documents ==

[[Research_Papers|Research Papers]]

[[Resources_for_Learning|General Resources for Learning]]

[[RCResources|RoboCup-Specific Resources for Learning]]
[[Category:RoboCup]]

RoboCup: Reflow Soldering Oven

2016-10-11T03:11:58Z

Rosawa3: /* I2C */ fixed location of space

For the Fall 2014 semester, an introductory project was laid out for the incoming members to become familiar with the basics of embedded systems.
To accomplish this, the incoming members were asked to design and develop a temperature controlling unit for a reflow oven.
This page outlines the technical details of the project's results and includes information for helping others learn the high-level basics of embedded systems.

== Project Specifications ==

=== Required ===
*The Arduino controller must integrate into a [http://www.amazon.com/Proctor-Silex-31111-Toaster-Broiler/dp/B004O0ANH2/ref=sr_1_17?ie=UTF8&qid=1412085077&sr=8-17&keywords=toaster+oven Proctor Silex 31111 Toaster Oven].
*A temperature sensor must be used in order to control the oven's temperature for [http://www.digikey.com/product-detail/en/SMD291SNL10/SMD291SNL10-ND/2057272 SMD291SNL10] solder paste.
*The temperature of the board (in the oven) must never exceed 260 °F for 40 seconds.
*A ''finalization'' stage must be incorporated that will evenly cool down the boards.
*An indicator must inform the user (visual and/or auditory) when the board is ready to be removed.
*Temperature control must be done by having a signal for the oven being on or off. Do not worry about directly controlling the oven - just provide the signal.
*Once started, the oven must automatically turn off all heating elements after the process is over (no user action required).
*The total costs of all required electrical components must be less than $45 (including any dev. boards).
*The final bill of materials ([http://en.wikipedia.org/wiki/Bill_of_materials BOM]) must be acquired from one (1) supplier.
*All electrical components in the electrical room are open for use and do not add to the project's cost ([http://inventory.robojackets.org/ http://inventory.robojackets.org])

=== Extended Features (Optional) ===
*Use a [https://www.sparkfun.com/products/255 monochrome] or [https://www.sparkfun.com/products/11377 color] LCD for displaying the oven's inside air temperature and/or other useful information.
*Create a method that will allow a user to create a ''custom temperature profile''.
*Create predefined temperature profiles for common types of solder pastes and allow the user to choose a thermal profile before beginning.

== Introductory Concepts ==
This section outlines a few of the most common terms one may encounter when learning about embedded systems.
An Arduino was used for the reflow oven's central controlling unit, so it is used below to help one relate to the reflow oven.

=== Arduino ===
The Arduino brought electronics to the hacking population. It has been credited as the device that started the DIY project boom. The device allows one to easily interface with some of Atmel's AVR microcontrollers. The rest of the board consists of voltage regulation (5V and 3.3V), an FTDI chip for serial communication over USB, connection headers (makes it easy to use with a breadboard), and a clocking crystal. It actually is not too much of a challenge to integrate all of an Arduino's parts to the reflow oven's circuit board.

Pins:
There are many types of Arduinos, and each one has advantages and disadvantages from the others. The standard models of the Arduino UNO and Arduino Nano will be discussed for this project. It is very easy to search Google for a diagram showing what the connection pins are attached to on the board. Additionally, the ATmega IC chips have datasheets if you are interested in the IC's pin diagram. Below are the basic pinouts for each Arduino. Notice that some pins are able to do multiple things.

==== Arduino UNO ====
*6 analog input pins [pins A0 - A5]
*14 digital I/O pins [pins 0 - 13]
*Rx and Tx [pins 0 and 1 respectively]
*6 PWM pins [pins 3, 5, 6, 9, 10, 11]
*SPI interface [pins 11, 12, 13]
*I2C interface [pins A4, A5]
*3.3V and 5V power

==== Arduino Nano ====
*8 analog input pins [pins A0 - A7]
*14 digital I/O pins
*Rx and Tx
*6 PWM pins [pins D3, D5, D6, D9, D10, D11]
*SPI interface [pins D10, D11, D12, D13]
*I2C interface [pins D4, D5]
*3.3V and 5V power

The nice thing about working with microcontrollers is that some pin functionality can be synthesized by other pins using code. For example, the [http://arduino.cc/en/Reference/SoftwareSerial SoftwareSerial library] can synthesize Tx and Rx pins on pins other than 0 and 1.

=== Communication Protocols ===

==== SPI ====
SPI is the fastest of these three protocols. It requires 4 wires which makes it more cumbersome to implement in large circuits. However, due to the size of this project, SPI shouldn't be an issue. SPI allows for direct, two-way communication between a master device (such as an Arduino) and a slave device (such as a display or sensor).

Here are the names of a typical SPI setup.
*SCLK - Serial Clock (output from master).
*MOSI - Master Output, Slave Input (output from master).
*MISO - Master Input, Slave Output (output from slave).
*SS - Slave Select (active low, output from master).

A nice visual representation of this setup can be found [http://goo.gl/Yv06RM here]:

==== I2C ====
I2C (Pronounced I-Squared-C or I-Two-C) Is one of the slower communication methods; however, it requires only two wires to implement, and new devices are easy to add while still using the same two wires. The difference between I2C and SPI is that I2C does not support simultaneous two way communication.

The system works with two wires that all devices are connected to (the master and all the slave devices).
*SDA - Line of communication between master/slave and slave/master.
*SCL - Clocking signal (from the master)

One very important thing to note about I2C is that the ''SDA'' and ''SCL'' pins must be "Pulled up" to Vcc with pull-up resistors. The reasons for this will not be explained here, but a quick Google search is all that's needed for those who are interested.

The master device sends out an address over the ''SDA '' signal wire corresponding to the target slave device. I2C slave devices are coded with an address that should be specified in its datasheet. All devices on the I2C wires will receive the address, and the device whose address was called responds to let the master device know that it is listening. Then communication can occur between the master and slave over the ''SDA '' signal wire in one direction at a time.

This system is similar to a leader wishing to communicate with an individual within a group. The leader (the master device) calls out the name of his or her assistant, and then they communicate openly with each other. Everyone in the room can hear the conversation, but only the leader and the assistant are engaging in conversation because it is understood who is being addressed.

==== RS-232 ====
RS-232 serial communication is one of the easiest to understand from a wiring standpoint and it is widely used with Arduino projects because of the supporting libraries for the Arduino. The difference between this form of communication and the others is that it does not make use of a clocking pin. The baud rate, or the clocking speed for the serial connection, must be specified and each device handles clocking independently. On each device, Rx and Tx pins are present. Data is transmitted from Tx on one device to the Rx on another. This allows for two way communication between only two devices. To communicate with additional devices, new COM ports must be implemented (either through hardware or software; see the [http://arduino.cc/en/Reference/SoftwareSerial SoftwareSerial library]) or the appropriate COM ports must be reconnected.

*Tx - Transmit pin
*Rx - Receive pin

To wire up a serial connection, connect the Rx of one device to the Tx of the other and vice versa.

==== Miscellaneous Acronyms ====

*PCB - Printed Circuit Board
*IC - Integrated Circuit. Basically a fancy packaged circuit. Densely packed logic reduces space and power usage while providing faster switching speeds.
*PWM - Pulse Width Modulation. A fake analog output can be synthesized by switching on and off quickly. The average voltage is adjusted by changing the duration of the high and low.

== Parts ==

[http://www.adafruit.com/products/1770 Touch Screen LCD]