RoboJackets Wiki - User contributions [en]

Outreach

2020-12-29T20:36:14Z

Mbayyari3:

== Overview ==
The RoboJackets Outreach team's mission is the promotion of science and engineering education in K-12 students. Working primarily though [https://www.firstinspires.org/ FIRST] programs, we engage students directly to facilitate hands-on learning through competitive robotics.

We currently have four projects we work on throughout the year to achieve this mission:

*Technology Enrichment Sessions - educational workshops leveraging the [http://www.usfirst.org/roboticsprograms/frc ''FIRST'' Robotics Competition] to teach fundamental robotics concepts to area students.
*FRC Kickoff - the announcement event for the [http://www.usfirst.org/roboticsprograms/frc ''FIRST'' Robotics Competition]. In 2016, over 1000 students were in attendance on campus.
*FRC Mentorship - working directly with an FRC team, we act as coaches and mentors to assist students throughout the academic year, including building a competition robot over an intensive six week build season. The team we are currently working with is FRC 6705, WildCat 5e.
*Robot In 1 Weekend - building a robot for the [http://www.usfirst.org/roboticsprograms/ftc ''FIRST'' Tech Challenge] in the span of one weekend when its build season starts. The aim of this is not to compete, but to inspire students in the competition at the start of their build season.

=== History ===

'''Past FRC Partner Teams'''

*WildCat 5e - FRC 6705
*Toaster Tech - FRC 5332
*Westlake Roarbotics - FRC 4163
*Reboot - FRC 4080
*Tech High School - FRC 2420
*Georgia Robotics Alliance "SOUP" - FRC 1848
*Wheeler High School "CircuitRunners" - FRC 1002
*Roswell High School "Chimera" - FRC 832

=== Awards ===

'''4080 - Reboot'''

*2012 - Rookie Inspiration Award
*2013 - Peachtree Regional Champions
'''5332 - Toaster Tech'''
* 2016- PCH DCMP Industrial Design Award
'''6705 - Wildcat5e'''
* 2018 - Gainesville District Event Finalist
* 2018 - Dalton District Event Winner
* 2018 - Dalton Innovation in Control Award
* 2018 - Duluth Quality Award
* 2018 - Duluth Safety Award
* 2018 - PCH DCMP Safety Award

=== Team Leaders ===

*Jevawn Roberts (Alumni Advisor)
*Project Manager - Michael Chen
*Kickoff Coordinator - Evan Strat
*Volunteer Coordinator - Malak Bayyari
*PR Representative - Cameron Loyd

== Meetings ==

TBD

== Project Dates ==

*Technology Enrichment Sessions - Every Saturday from September 16 to October 28
*FRC Kickoff - January 6, 2018
*FRC Mentorship - Fall and Spring Semesters with an intensive build season from January 6 to February 20
*Robot In 1 Weekend - September 9-10

== Resources and Detailed Project Information ==

*[[FIRST_Resources|FIRST Resources]]
*[[TE_Sessions|TE Sessions]]
*[[FIRST_Kickoff|FIRST Kickoff]]

[[Category: Outreach]]

Current Leadership

2020-09-25T19:11:12Z

Mbayyari3: /* Appointed Positions */

Below is a list of who are current leadership is during the 2020-2021 academic year.

__TOC__

==Core Officers==
<dt>[[President]] </dt>
<dd>Alex Field</dd>
<dt>[[Vice-President]] </dt>
<dd>Ava Thrasher</dd>
<dt>[[Treasurer]] </dt>
<dd>Christopher Bellflowers</dd>
<dt>[[Secretary]] </dt>
<dd>Malak Bayyari</dd>
<dt>[[Shop Manager]] </dt>
<dd>Vijay Srivastava</dd>
<dt>[[Promotions Chair]] </dt>
<dd>Cameron Loyd</dd>
</dl>

==Appointed Positions==
<dt>[[IT Coordinator]] </dt>
<dd>Todd Hayes</dd>
<dt>[[Sponsorship Chair]] </dt>
<dd>Brian Epstein</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software/Firmware_Training_Lead Mechanical Training Lead] </dt>
<dd>Sam Walters</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software/Firmware_Training_Lead Software Training Lead] </dt>
<dd>Kyle Stachowicz</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software/Firmware_Training_Lead Electrical Training Lead] </dt>
<dd>Asha Bhandarkar</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software/Firmware_Training_Lead Firmware Training Lead] </dt>
<dd>Arvind Srinivasan</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software_Discipline_Core_Chair Electrical Core Chair] </dt>
<dd>Arvind Srinivasan</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software_Discipline_Core_Chair Mechanical Core Chair] </dt>
<dd>Sam Morstein</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software_Discipline_Core_Chair Software Core Chair] </dt>
<dd>Oswin So</dd>
<dt>[[Outreach Chair]] </dt>
<dd>Michael Chen</dd>
<dt>[[Volunteer Coordinator]] </dt>
<dd>Malak Bayyari</dd>
<dt>[[Kickoff Coordinator]] </dt>
<dd>Evan Strat</dd>
<dt>[[SCCGB Delegate]] </dt>
<dd>Knute Broady</dd>
<dt>[[Web App Product Owner]] </dt>
<dd>Josh Oldenburg</dd>
<dt>[[Purchaser]] </dt>
<dd>Stefan Quaadgras</dd>
</dl>

==Team Leadership==

<dt>[[BattleBots]] </dt>
<dd>Project Manager: Cody Page</dd>
<dd>3lb Manager: Cade Tyler</dd>
<dd>Chonki Bot Lead: Brian Epstein</dd>
<dd>Hocki Bot Lead: Varun Madabushi</dd>
<dd>Maori Bot Lead: Dennis Crawford</dd>
<dd>Valkryi Bot Lead: Sam Li</dd>
<dd>Samurai Bot Lead: Dylan Adriano</dd>

<dt>[[RoboNav]] </dt>
<dd>Project Manager: Tan Gemicioglu</dd>
<dd>Mechanical Lead: Charles Li</dd>
<dd>Electrical Lead: </dd>
<dd>Software Lead: Matthew Hannay</dd>

<dt>[[RoboCup]] </dt>
<dd>Project Manager: Marine Maisonneuve</dd>
<dd>Chief Scientist: Christopher Lindbeck</dd>
<dd>Mechatronics Lead: Alyssa Gordon</dd>
<dd>Electrical Lead: Arthur Siqueira</dd>
<dd>Software Lead: Hussain Gynai</dd>

<dt>[[RoboRacing]] </dt>
<dd>Project Manager: Shishir Pandit-Rao</dd>
<dd>Mechanical Lead: Sam Morstein</dd>
<dd>Electrical Lead: Andrew Rocco</dd>
<dd>Software Lead: Daniel Martin</dd>

<dt>[[RoboWrestling]] </dt>
<dd>Project Manager: Caleb Chang</dd>
<dd>Mechanical Lead: Phillip Holloway</dd>
<dd>Electrical Lead: Juan Elizondo</dd>
<dd>Software Lead: Logan Schick</dd>
</dl>

[[Category: Leadership Positions]]

Submitting Bills

2020-09-23T17:50:17Z

Mbayyari3:

The Georgia Tech RoboJackets is sponsored in part by the Student Government Association(SGA). The following information pertains to submitting bills to request SGA funding.

== About the Process ==
=== Step 1: Contact an Undergraduate Representative and a Graduate Senator ===
*Contact an Undergraduate Representative and a Graduate Senator who are willing to serve as sponsors, or "authors", for your bill. A complete list of Representatives can be found on JacketPages.

=== Step 2: Submit a bill on JacketPages ===
*In order for the Undergraduate House of Representatives and Graduate Student Senate to consider a bill, it must first be submitted on JacketPages. Among other things, you will need to provide the following information:
**Contact information for your organization�s president and treasurer (or any other officers able to represent your organization at SGA meetings).
**An itemized budget outlining your request (including cost per unit).
**A description of the request (note: requests are also known as �allocations�).
*Please refer to the instructions for submitting your bill in JacketPages. Once your bill is in the JacketPages system, it will be placed on the agendas of the Undergraduate House of Representatives (UHR) and the Graduate Student Senate (GSS).
**Authors will need to review and sign the bill.

=== Step 3: Bill is New Business ===
*RSO Reviews Bill and makes recommendations
*Representatives and Senators review bill and RSO's recommendation

=== Step 4: Bill is Old Business ===
*Graduate Senate discusses and votes on bill.
*Undergraduate House of Representatives discusses and votes on bill.

=== Step 5: Bill Outcome ===
*If the bill fails you may resubmit a modified bill. The modified bill must go through the entire bill approval process outlined in steps 1 � 5.
*If the GSS and UHR pass different versions of your bill, it will be referred to a Conference Committee. The conference committee will reconcile the two versions and submit a conference committee version of the bill at the next UHR and GSS meetings. From the organization�s perspective, this means you may experience an additional delay in receiving your funding.
*If either the Undergraduate or Graduate SGA presidents vetoes your bill, the UHR and GSS will both hold a veto override vote. This could also result in a delay in receiving your funding.

===Conclusion===
*Nearly every financial bill submitted to SGA passes in some form (though maybe not for the full amount requested). Remember that SGA is here to make the process as easy as possible for you. If you have any additional questions regarding SGA funding procedures, contact a Senator or Representative.

== Tips on Writing a Winning Bill==
*Submit your bill four to five weeks in advance of the date that funds are needed; avoid submitting it at the last minute.
*Be prepared to show how you pursued alternative funding sources for your requested allocation (sponsors, fundraisers, donations, etc.).
*Consult your Representatives and Senators about Registered Student Organizations (RSO) Policy before writing your bill. Bills with multiple amendments from the Joint Finance Committee do not typically fare as well as those with fewer amendments.
*Be prepared to answer questions about how your allocation benefits the entire campus community. Keep in mind that all students pay the Student Activity Fee; therefore, allocations should benefit as many students as possible.

== Useful Links ==
* [http://sga.gatech.edu/undergraduate/info-for-organizations/bill-submission How Do I Get Funding For My Organization]
[[Category:Finance]][[Category:Core]]

People with Keys

2020-08-21T22:07:12Z

Mbayyari3:

'''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
| ''Unassigned''
|-
| 3SB6: 4
| Cameron Loyd
|-
| 3SB6: 5
| Logan Schick
|-
| 3SB6: 6
| Michael Benben
|-
| 3SB6: 7
| Christopher Bellflowers
|-
| 3SB6: 8
| Marine Maisonneuve
|-
| 3SB6: 9
| Vijay Srivastava
|-
| 3SB6: 12
| Ava Thrasher
|-
| 3SB6: 14
| Todd Hayes
|-
| 3SB6: 15
| Brian Epstein
|-
| 3SB6: 18
| ''Unassigned''
|-
| 3SB6: 19
| Will Stuckey
|-
| 3SB6: 21
| Ava Thrasher
|-
| 3SB6: 22
| Alex Field
|-
| 3SB6: 23
| Austin Keener
|-
| 3SB6: 24
| Kyle Stachowicz
|-
| 3SB6: 27
| Cade Tyler
|-
| 3SB6: 28
| Joseph Spall
|-
| 3SB6: 29 - Lost
|
|-
|3SB6: 30
| ''Unassigned''
|-
| 3SB6: 31
| Phillip Holloway
|-
|3SB6: 33
| Malak Bayyari
|-
|3SB6: 34
| Tan Gemicioglu
|-
|3SB6: 35
| Nikolay Tranakiev
|-
|3SB6: 36
| Varun Madabushi
|-
|3SB6: 39
| Ava Thrasher
|-
|3SB6: 40
| Dallas Downing
|-
|3SB6: 41
| Andrew Rocco
|-
|3SB6: 43
| Young Won
|-
|3SB6: 44
| Caleb Chang
|-
|3SB6: 45
| Juan Elizondo
|}

[[Category:Core]]
[[Category: Shop]]

SUMS Trainers

2020-08-08T01:07:51Z

Mbayyari3:

SUMS (Shared User Management System) is used to manage our tools in the CMA (Common Machining Area). RoboJackets members have the ability to become trainers on these machines. Trainers can train RoboJackets members and give them access to the specified machine. This page lists who our current trainers are.

== How to Become a Trainer ==

== Who are our current Trainers? ==


{| class="wikitable sortable"
|-
! Trainer
! General Shop
! Mill
! Lathe
! WaterJet
! CNC Mill
! CNC Lathe
|-
| Young Won
| Yes
| Yes
| Yes
| Yes
| Yes
| No
|-
| Alex Field
| Yes
| Yes
| Yes
| Yes
| No
| No
|-
| Michael Benben
| Yes
| Yes
| Yes
| Yes
| No
| No
|-
| Carrie Li
| Yes
| Yes
| Yes
| Yes
| No
| No
|}

[[Category: Shop]]

SCC Training Curriculums

2020-08-08T01:07:23Z

Mbayyari3:

[[File:SCC_CMA_Training_Curriculum_-_Manual_Mill.pdf]] 
[[File:SCC_CMA_Training_Curriculum_-_Vertbandsaw.pdf]] 
[[File:SCC_CMA_Training_Curriculum_-_Manual_Lathe.pdf]] 
[[File:SCC_CMA_Training_Curriculum_-_Haas_CNC_Mill.pdf]] 
[[File:SCC_CMA_Training_Curriculum_-_Horizbandsaw.pdf]] 
[[File:SCC_CMA_Training_Curriculum_-_Belt_Sander.pdf]]

[[Category: Shop]]

IT Hub

2020-08-08T01:06:19Z

Mbayyari3:

A wide variety of tools are available to RoboJackets members to help them communicate and work productively. On this page, you can find information to help you access and use these tools.

== Common Capabilities ==
{| class="wikitable"
!Status
!Meaning
|-
|bgcolor="#b7e1cd"|Required
|This is the only solution for the listed domain and capability.
|-
|bgcolor="#c9daf8"|Preferred
|This is a recommended solution for the listed domain and capability, but there are also other solutions available.
|-
|bgcolor="#fff2cc"|Available
|This is an optional solution for the listed domain and capability, but there's no requirement or recommendation that it's used.
|-
|bgcolor="#efefef"|Emerging
|This solution is still being investigated. Support and/or availability might be limited.
|-
|bgcolor="#efd7d2"|Deprecated
|Other solutions are available for the listed domain and capability. Support and/or availability of the solution may end in the future. If a sunset date for this solution is set, it will appear in the Notes column.
|}

{| class="wikitable sortable"
!Domain
!Capability
!Solution
!Status
!Help/Access
|-
|Communication
|Mailing Lists / Access Control
|[https://groups.google.com Google Groups (G Suite)]
|bgcolor="#fff2cc"|Available
|[[Google Groups Join Links]]
|-
|Communication
|Video Chat
|[https://meet.google.com Google Meet]
|bgcolor="#fff2cc"|Available
|[[Google Meet]]
|-
|Communication
|CRM
|[https://app.hubspot.com Hubspot]
|bgcolor="#b7e1cd"|Required
|
|-
|Communication
|Email
|[https://mail.robojackets.org RoboJackets Mail (G Suite)]
|bgcolor="#fff2cc"|Available
|[[G Suite Accounts]], [https://goo.gl/forms/YtKnRKmneuqBYZSf1 Request a G Suite Account], [https://goo.gl/forms/uz3bXcKE6lLQ8DWr2 Request @robojackets.org Email Alias]
|-
|Communication
|IM
|[https://robojackets.slack.com Slack]
|bgcolor="#b7e1cd"|Required
|[[Slack Etiquette]]
|-
|Communication
|Mailing Lists
|[https://lists.gatech.edu Sympa]
|bgcolor="#b7e1cd"|Required
|[https://goo.gl/forms/zx9CqyBMhddQJekk1 Request List Owner/Moderator Permissions]
|-
|File Storage
|CAD
|[https://vault.robojackets.org Autodesk Vault]
|bgcolor="#efd7d2"|Deprecated
|Vault has been deprecated by RJIT; use GrabCAD instead.
|-
|File Storage
|CAD
|[https://workbench.grabcad.com/workbench/myprojects#/account/1851406/projects/my_projects GrabCAD Workbench]
|bgcolor="#c9daf8"|Preferred
|Request access from your subteam lead or project manager.
|-
|File Storage
|Code
|[https://github.com GitHub]
|bgcolor="#c9daf8"|Preferred
|[[Git How-To]], [https://github.com/robojackets RoboJackets GitHub Organization]
|-
|File Storage
|Generic
|[https://cloud.robojackets.org RoboJackets Cloud]
|bgcolor="#c9daf8"|Preferred
|[[Accessing Cloud from macOS]]
|-
|File Storage
|Collaboration
|[https://drive.robojackets.org Shared Drives]
|bgcolor="#c9daf8"|Preferred
|
|-
|File Storage
|Generic
|[https://dropbox.com Dropbox]
|bgcolor="#fff2cc"|Available
|
|-
|Org Management
|Attendance, Dues, and Access Control
|[https://my.robojackets.org MyRoboJackets]
|bgcolor="#b7e1cd"|Required
|
|-
|Org Management
|SGA
|[https://orgsync.robojackets.org Engage]
|bgcolor="#b7e1cd"|Required
|
|-
|Org Management
|Website
|[https://robojackets.org Wordpress]
|bgcolor="#b7e1cd"|Required
|[[How to create a calendar event]]
|-
|Project Management
|Task Tracking
|[https://trello.com Trello]
|bgcolor="#c9daf8"|Preferred
|[[About Trello]]
|-
|Project Management
|Documentation
|[https://wiki.robojackets.org MediaWiki]
|bgcolor="#fff2cc"|Available
|
|-
|Project Management
|Task Tracking
|[https://clickup.com ClickUp]
|bgcolor="#c9daf8"|Preferred
|[[About ClickUp]]
|}

[[Category: Core]]

Software Review Guide

2020-08-08T01:05:24Z

Mbayyari3:

== Introduction ==
“PRs are O(n^2) to review”

== Style Guide ==
[[Generalized Software Style Guide]]

== General Guidelines ==

== How To Get Reviews ==

[[Category: Software]]

RoboRacing

2020-07-05T03:54:52Z

Mbayyari3: /* IARRC */

[[Category:RoboRacing]]
[[File:RoboRacing-team.jpg|thumb|right|400px| IARRC Result 2019 – First Place!]]
RoboRacing is a competitive robotics team geared towards autonomous racing of small scale automotive platforms. The team started in 2013 and has since built robots to compete in the IARRC competition since the team's inception, as well as the Sparkfun AVC competition since 2016. RoboRacing is additionally planning on competing in the evGrand Prix Autonomous competition in 2020.

RoboRacing puts its members at the forefront of emerging technology in self-driving cars through involvement in autonomous RC vehicle design, fabrication, and programming. Each competition has proven to be a great learning opportunity for everything from robust mechanical design to advanced programming skills that could be applied to diverse engineering applications. 

== Meeting Times ==

We meet in the Student Competition Center (575 14th St). If you are working in the machine shop or mechanical room you will need to wear closed-toe shoes and a t-shirt (no long sleeves). Bring a hair tie if needed.

* Mondays: 6:30-9:00 PM

* Sundays: 4:00-7:00 PM

* Carpool Pickup Locations: North Avenue Apartments & West Village

== Current Leadership ==
* Project Manager: Shishir Pandit-Rao
* Electrical Lead: Andrew Rocco
* Mechanical Lead: Sam Morstein
* Software Lead: Daniel Martin

==Competitions==

===International Autonomous Robot Racing Competition===
RC scale autonomous racing and navigation.

* [https://iarrc.org/ IARRC Website]
* [https://iarrc.org/rules/ Competition Guidelines]

===evGrand Prix===
Autonomous high-speed racing of full-size go-karts.

* [https://evgrandprix.org/autonomous/ evGP Website]
* [http://evgrandprix.org/forms/rulebook/2020%20Autonomous%20Rulebook.pdf Comptetion Guidelines]

== Past Competitions ==

===evGrand Prix===
{| class = "wikitable" style = "width:95%;"
|- style="font-size:15px;" |
| style="width:20%;" | '''Bot'''
| style="width:20%;" | '''Competition Years'''
| style="width:20%;" | '''Versions'''
| style="width:40%;" | '''Design Reports'''
|-
| style="font-size:15px;" | '''Rigatoni'''
| 2019 - 2020
| Rigatoni
|
* '''Version 1:'''
|}

===IARRC===
{| class = "wikitable" style = "width:95%;"
|- style="font-size:15px;" |
| style="width:20%;" | '''Bot'''
| style="width:20%;" | '''Competition Years'''
| style="width:20%;" | '''Versions'''
| style="width:40%;" | '''Design Reports'''
|-
| style="font-size:15px;" | '''Sedani'''
| 2018 - 2019
| Sedani, Sedanii, Sedaniii
|
* '''Version 1:''' [[:File:RoboJackets-IARRC-2018.pdf| Sedani Design Report]]
* '''Version 2:''' [[:File:RoboRacing_IAARC_2019_Sedanii_Design_Report.pdf| Sedanii Design Report]]
* '''Version 3:'''
|-
| style="font-size:15px;" | '''Macaroni'''
| 2017
| Macaroni
|
* '''Version 1:''' [[:File:RoboJackets_RoboRacing_IARRC_Design_Report_2017.pdf| Macaroni Design Report]]
|-
| style="font-size:15px;" | '''Speedi'''
| 2014-2016
| Speedi, Speedii, Speediii
|
* '''Version 1:''' [[:File:Robojackets-iarrc-2014.pdf| Speedi Design Report]]
* '''Version 2:''' [[:File:Robojackets-iarrc-2015.pdf| Speedii Design Report]]
* '''Version 3:''' [[:File:Robojackets-iarrc-2016.pdf| Speediii Design Report]]
|}

Results:
{| class = "wikitable" style = "width:95%;"
|- style="font-size:15px;" |
| style="width:20%;" | '''Year'''
| style="width:20%;" | '''Placement'''
|-
| style="font-size:15px;" | '''2019'''
| 1st Place Overall
|-
| style="font-size:15px;" | '''2018'''
| Did Not Place
|-
| style="font-size:15px;" | '''2017'''
| 3rd Place Overall
|-
| style="font-size:15px;" | '''2016'''
| 1st Place Overall
|-
| style="font-size:15px;" | '''2015'''
| 4th Place Overall
|-
| style="font-size:15px;" | '''2014'''
| 1st Place Overall
|}

===Sparkfun AVC===
{| class = "wikitable" style = "width:95%;"
|- style="font-size:15px;" |
| style="width:20%;" | '''Bot'''
| style="width:20%;" | '''Competition Years'''
| style="width:20%;" | '''Versions'''
|-
| style="font-size:15px;" | '''Bigoli'''
| 2016-2018
| [[Bigoli]], Bigolii
|}

Results:
{| class = "wikitable" style = "width:95%;"
|- style="font-size:15px;" |
| style="width:20%;" | '''Year'''
| style="width:20%;" | '''Car Wars'''
| style="width:20%;" | '''Speed Demons'''
|-
| style="font-size:15px;" | '''2018'''
| Did Not Place
| 1st Place
|-
| style="font-size:15px;" | '''2017'''
| 1st Place
| Did Not Place
|}

== Resources ==
[[How To Record Data On Sedani]]

[[Setting Up Ubuntu for Ethernet LAN While Preserving Wifi Internet Access]]

[[How to Setup CLion for ROS]]

[[Profiling ROS Nodes]]

[[RoboRacing Man vs Machine]]

File:RoboRacing IAARC 2019 Sedanii Design Report.pdf

2020-07-05T03:54:10Z

Mbayyari3:

Woodi

2020-07-04T05:13:02Z

Mbayyari3:

[[Category: IGVC]]
{{Infobox IGVC
| robot_name = Woodi
| image_path = Woodi.jpg
| image_alt_text = Woodi right after completion
| year_start = 2016
| year_end = 2017
| current_version = Woodi
| update_year_start = n/a
| update_year_end = n/a
| farthest_distance = n/a
| fastest_time = n/a
| highest_finish_autonav = n/a
| highest_finish_design = n/a
| last_robot = Jaymi
| next_robot = Jessi
}}

Woodi was a replacement robot, meant to take the place of [[Jaymi]] at the 2017 competition. It was a last ditch effort to bring a robot to competition that year. We started laying down the design approximately 15 hours before leaving for competition. After a couple trips to Home Depot, the effort of a few members who were not driving the next day produced the robot you see here. Despite it's sloppy appearance, Woodi was a good testing platform during the 2017-2018 year and served as a design inspiration for [[Jessi]].

= Competitions =

=== IGVC 2017 ===
*Results
** Distance:
** Design Competition Placement:
** AutoNav Competition Placement:

= Versions =

== Woodi ==

=== At Competition ===

Woodi was never able to qualify or compete. Software and electrical issues were persistent throughout competition, which prevent it from ever being in a usable state. The main issues are documented down below.

=== Mechanical Design & Issues ===

Woodi was designed to be a minimal working robot. It consisted of 3 main sections: the mast, the electrical box, and the "chassis". The mast was simply the mast originally made for [[Jaymi]], reattached to the electrical box. The electrical box was a simple wooden box. The sides of the box were removable panels with the RoboJackets logo on the side. Half of the top was on a hinge which allowed it to be opened to access the electronics. The back was also on a hinge so the batteries could be put in. The electronics themselves were mounted to a plastic sheet that was the initial electronics board for Jaymi, which sat unmounted in the box. The "chassis" was a jumble of 2x4 wood which held the motors and custom gear boxes. We reused the wheels and the custom caster assembly from ___.

Unfortunately, Woodi had a high center of mass (see WoodiTipping.mp4) due to the batteries being so high off the ground. This made Woodi very prone to tipping backwards when initially accelerating. The caster was also poorly designed (the wheel was not offset from the center of rotation enough) which made it hard to turn. The uneven ground at competition combined with the bad caster caused the robot to fall forward once, which damaged the SICK LiDAR mounted on the front. At competition, we added a wheelie in the back to prevent the robot from tipping too far back.

One of the main issues mechanically with Woodi was the custom gearboxes. These were originally part of the design for [[Jaymi]] and had to be used on Woodi as there were no alternatives. The gearboxes had many issues with design, tolerances, and manufacturing, but those are detailed in [[Jaymi#Mechanical_Design_.26_Issues]]. The main issue we encountered with Woodi was the motors were not powerful enough. Woodi moved fairly slowly, even at full speed, partially due to the motors themselves and partially due to the amount of friction generated in the gear box. Woodi would always produce high pitch whining sound with the old motors and gearbox. The motors were replaced with wheelchair motors that had built-in gearboxes (as seen on [[Jessi]]) during the 2017-2018 year for testing before Woodi was finally dismantled and deprecated.

=== Electrical Design & Issues ===

=== Software Design & Issues ===

= Additional Information =

=== Team Members ===

=== Gallery ===

Robot Basics

2020-07-04T05:12:19Z

Mbayyari3:

[[Category: BattleBots]]
== '''Overview''' ==
Welcome to Battlebots! The environment of Battlebots will be fairly fast-paced. We only meet once a week for the first semester, which in the first few meetings will be spent on the ground work for what is probably the most engaging and important phase ... designing your robot. The purpose of this guide is to educate the reader, our new battlebots members, on some key factors relating to designs of robots and analyzing the pros and cons. Often, new members try to design the perfect bot. However, designing the perfect robot is not possible. Everything has a disadvantage, a weakness that can be exploited. But that does not make it a bad design. It could be an effective one. However, it is important to consider all aspects of different types before determining what you will implement. This guide will also explore some ideas, and reasons behind that idea, that you can implement when designing your own bot.

== '''Types of Robots''' ==
The first step of designing your robot is to decide what type you want to build. There have been several different designs throughout the history of battlebots and competitions. However, this guide will cover some of the generic designs that show up consistently each year in competition. It is important to keep in mind that each type of robot has their own advantages. However, it goes without saying that they also have their disadvantages and difficulties.

=== Drum Spinners ===
[[File:drum.jpeg|right|thumb|320x180px|'''Drum Spinner - Radi and Radii''' Designed and built by RoboJackets Members (2016-2017)]]

Drum bots have a rotating cylindrical-shaped weapon (medium to large sized) usually attached with barbs or teeth attached to the cylindrical weapon to tear apart and flip opponent's bot. Drum bots are a good bot type for beginners and are quite common for new 3lb members to use as their first type.

==== Advantages ====
Drums, as mentioned, are a great bot for beginners. Their weapon is simple, yet quite reliable and destructive upon certain hits. Drum's weapons are generally sturdy because they are usually made from a block of metal, which means that it will be difficult for it to break. They allow your bot to be stable when you are attacking an opponent bot, dealing several quick and continuous attacks. If correctly designed, drums are capable of launching or flipping the opponent bots in the air. If your opponent's bot is not invertible and they get flipped, it is more than likely that they wont be able to continue and you will emerge victorious in that match. Speaking of invertibility, drums can be designed to be invertible which gives you an advantage when you get flipped.

==== Disadvantages ====
Because the nature of the weapon, Drum spinner bots generally have a very small strike zone. The heavy mass in the front of the bot rotating at high RPM will making driving your bot fairly difficult. Sometimes, with powerful weapons at high RPM, the gyroscopic forces acting on the bot could cause lift to occur on one side of the bot when turning. Similar to Horizontal/Vertical Bar Spinners, upon your weapon's contact on an opponent bot, the recoil from the impact could potentially cause damage to your own bot, sometimes making it immobile. If not properly designed or built, as with any heavy hitting weapon type, the weapon could be ripped apart. The weapon is generally sturdy, however, after direct attacks from opponent bot or extended contact, it is likely for your weapon to be damaged and will be less effective.
{| class="wikitable"
!'''''TL:DR: '''''Summary (Drum Spinners)
!
!
|-
!Advantages
!Disadvantages
!
|-
|Sturdy weapon
|Small strike zone
|
|-
|Powerful weapon capable of flipping opponent bot
|Gyroscopic effects cause control and turning issues
|
|-
|Could be designed invertible
|Potential self-inflicting damage
|
|-
|High damage output
|Weapon could get ripped off / damaged
|
|}

----

=== Horizontal Spinners ===
[[File:chewi.jpg|thumb|320x240px|'''Horizontal Bar Spinner - Chewi''' Designed and built by RoboJackets Members (2017-2018)]]

Briefly, there are two common variations to spinners: bar spinners and disk spinners. Bar spinners are similar to disk spinners, except, as stated in the name, the weapons of bar spinners are shaped like a bar. The robot's weapon motor is a factor that determines the effectiveness of the weapon of spinners. The structure of the weapon system is similar to that of a drum spinner, where the weapon's spin up is controlled by the weapon motor, commonly connected by a pulley system. Horizontal Bar spinners are commonly known for their destructive power. Weapons of this types enable both offensive, as well as defensive, advantage (explained in "Advantages").

==== Advantages ====
The body of the bar spinners are generally similar. However, the uniqueness of the bot comes with the weapon design. This weapon types offers very versatile weapons, meaning that there can be many variations to it. Bar either be single-edged or multi-edged where the hitting edge could be (one or more combinations of) a blunted edge, sharp-bladed edges, or spiked edges, and so on. The more edges of contact you have, the damage will lose effectiveness. For example, a single-edged weapon, upon weapon's contact, will not have interference until its next contact. This allows more spin up, which maximizes damage per hit. However, with multi-edged weapon, the more edges there are, the weapon will have difficulty with spinning the weapon because it has more than one edge that will make contact, which will slow the weapon speed upon each contact. However, this is not necessarily a bad thing because multi-edges will hit more frequently, doing decreasing damage upon each hit. Regardless of the design, bar spinners have a large strike zone, much greater than drum spinners, and if made properly, the weapon can be highly destructive. Similar to the drum spinners, horizontal bar spinners can be designed to be invertible, which will make it more difficult for the opponent to try and defeat you. The gyroscopic forces at high to to full speed of a horizontal bar spinner, depending on size and power of the weapon, can help stabilize your robot and stop it self from being flipped over.

==== Disadvantages ====
Because of the design of the weapon and its front placement, robot must be designed to where the front (where the weapon system is held) is elongated from the main body of the robot. This is because you need to have it designed so that the the robot does not get hit by its own weapon. Generally, regardless of the design, the weapon is powerful and it does a lot of damage. However, this is could also be disadvantageous. Generally, a lot of the weight for this robot type is focused on the weapon. Its also important to keep in mind that the structure of the robot itself needs to be strong. Upon a hit, your robot, more than likely will experience recoil. If your robot is not structurally strong over all, parts of your bot, including your electronics, could be adversely affected. Not only can recoil potentially harm your robot, it could also affect your driving ability. Upon contact it could redirect your robot in a different direction. In some cases, it could cause your robot to go airborne and/or be flipped over, but it is every easy to design your robot to be invertible. Gyroscopic effects caused by the spinning of the heavy weapon can cause an issues with driving abilities. The robot will want to turn in the opposite direction from the direction that your weapon is spinning. However, driving ability stabilizes as the weapon spins at high to full speed. Like the drum spinner, the weapon is attached using a pulley system that connects it to the weapon motor using a belt. Impacts could damage your belt, which could cause weapon failure. If your weapon or weapon system fails in some way, or if your belt spinning your weapon fails in some way, your bot will no longer have a functioning weapon. Usually, this is the only weapon your robot is equipped with, so there is no secondary weapon. If you end up with an inactive weapon, it is more than likely that you will lose that match.

{| class="wikitable"
!'''''TR:DL''''' Summary (Horizontal Spinners)
|-
!Advantages
!Disadvantages
!
|-
|Effective type + type advantage against most other types
|Weapon could hit chassis (FIX: elongated front)
|
|-
|Versatile weapon designs with variable edges for max speed and power
|Gyroscopic effects cause control and turning issues (No longer a problem at higher rotations)
|
|-
|Weapons acts offensively and defensively
|Recoil effects upon weapon's impact
|
|-
|invertible design
|Could get redirected or flipped upon impact (FIX: invertible design)
|-
|larger attack zone
|Weapon could get ripped off / weapon failure due to damage to the belt
|
|-
|High damage output (one of the highest of all types)
|
|
|}

== Mobility and Defense ==

=== Wedges ===
As you may recall, wedges are one of the most common implemented designs. Remember, wedges do not have actual weapons. Because it does not have a weapon, which normally would take up majority of the robot's weight, it allows for a stronger structural design of the robot or for the use of better (or more) drive motors for better mobility, maybe a combination of both.

The big picture of wedges is to temporarily (or, in some cases, permanently) disable the opponents mobility. In other words, your "weapon" is the wedge that tries to get under the opponent's robot. Once this is done, they will lose traction, thus their mobility. In some cases, the opponent's bot will be flipped. At that point, you have control of that match. If your opponent's bot is not invertible or has no self-right mechanism, it is more than likely that you won that match. In order to get under the robot, the easiest way to achieve this is to design your wedge, varying the bot's height and size of the wheels, such that it is as close to the ground as possible. It goes with out saying, this tactic of getting under the opponent requires a strong drive system, which is made possible by the weight saved by not having a weapon.

A wedge bot will find racking up points to win to be difficult. It is possible to include spikes, on either the wedge or its body as a defense mechanism (while also potentially dealing very limited offensive damage). The potential tradeoff, depending on the how you implement this addition to the design, is that it may or may not be possible to make your robot be invertible.

The concept seems pretty simple and straightforward, however it turns out to be pretty effective type when put to use. They have a type advantage against most other bot types. In other words, as long as your wedge can get under an opponent bot, you have some advantage. Pretty much the only counter type to a wedge bot are types such as undercutters, lifters, other wedges; basically anything that is closer to the ground than your type. In some instances, vertical spinners could pose a threat as well.

== Component Design/Placement ==

Be careful on where you place certain things. There are things to consider while you are initially designing your bot. For example, is your weapon far enough to where it wont hit the body? How do you want to incorporate your wheels, attached inside the body or attached to outside of the robot? If it is inside the wheels, how will it affect the overall layout, including the electronic layout of the bot? How will locations of certain object placements affect the center of gravity? Small things like this can have a bigger impact of the robot as a whole.

Do not underestimate the space that wires could take up. Wire management, in many battlebots member's experience, is one of the most difficult things to overcome. This is usually one of the last phases of completion, so wiring would happen at the end (closer to the time of competition). If you dont want to get to this phase and figure you have to redo wiring and rework the wire management to a more tightly packed system, it is recommended that you consider this during the design phase, giving enough room in the bot.

Important things to consider during design process includes, but no limited to the following (some are restated as above):

=== Electronics ===

For more accurate and detailed information, i.e. images, weights, dimensions, and models, there is table under the ''Standard Robot Components'' in a different RoboJackets Wikipedia page [[3lb Beginner's Guide]]

The electronics on the robot comprises of the following:

''One'' 11.1 volt, three-cell '''power supply''' to power the other electrical components.

''Two'' '''drive motors''', one for each wheel to drive the robot and ''two'' '''drive electronic speed controllers''' (Drive ESC) that support and control the weapon motor.

''One'' '''weapon motor''' that spins up the weapon with the help of ''one'' '''weapon ESC'''

For a better idea, a CAD example of a 3lb robot shows the layout and compactness of the interior after the electronics added.
[[File:ElectronicsLayout.jpeg|320x240px]]
[[File:ElectronicsLayout2.jpeg|320x240px]]
[[File:DrumLayout.png|320x240px]]

There are a lot electrical components, including that wiring that is required, that goes into making your robot, which is why it was earlier advised to consider the an interior layout for the spacing for the electrical components. It is important to remember that, yes, these electronic components take a lot interior space. However, they also take up a lot of weight, approximately .85 pounds.

=== Weapon ===

[[File:weapon4.jpeg|thumb|left|100x100px]]
[[File:weapon1.jpeg|thumb|right|100x100px]]
[[File:weapon2.jpeg|thumb|right|100x100px]]
[[File:weapon3.jpeg|thumb|left|100x100px]]

- Is your weapon short enough to avoid hitting its own body?
- How are you planning on attaching your weapon to the chassis?
- What materials are incorporated in the weapon assembly?
- Where is the pulley going to go and how is it attached to the weapon?
- Is the dimension required for making your weapon/pulley available to be bought from our parts retailer?
- How heavy is your weapon? Typically, weapons weigh about one-third of the total weight of the bot. For example, for 3lb battlebots, an ideal weight for the weapon is in the range of .85lbs to .95lbs.

The images provided are examples of just a few of the countless designs of horizontal bar spinner weapons. For more examples of other bot's weapons, including all types of bots, can be found in the [[List of 3lb Robots]].

===Chassis===
[[File:chassis.jpeg|thumb|right|320x240px]]

- How big is your chassis? If its too small, it might conflict with interior space for the electronics. If its too large, it is just unnecessary weight, which you can use to allocated to other aspects of the bot; for example, the weapon.
- How are you chassis components attached together? Puzzle fitting the chassis parts have been commonly used among many battlebots designs.
- Earlier, we brought up the topic of wheel attachments. Will the wheels be attached to the exterior of the bot or the interior of the bot? Interior wheel placements has an advantage when it comes to protecting the wheels. However, it will elongate your chassis, which will increase the weight of the chassis, but this can be solved by implementing weight relief. Exterior wheel placements are more prone to damage to the wheel. However, there are techniques to help avoid any damage to the wheels. For example, one way is to have an armor piece stretch over the wheel and around the entire robot. An example of interior and exterior wheel placements along with their respective armor solution are shown by the two iterations of the 3lb weight class battlebot, [[Chewi]].
- Is it out of the weapon's range?
- As a suggestion, it is a good idea to have some sort of barricade in front of the chassis. This is just to prevent any sort of external components flying into your bot and damaging the electronics. Typically, since this front plate is used just to block entrance for external and unwanted materials, a thin piece of plastics should be more than sufficient for this task. You may think the front plate should be the same material as rest of the chassis, however plastic is stronger than many people realize. It is more than capable for this task and it will help reduce a lot of weight rather than using the same material as the rest of the chassis.

For a better visual of what puzzle fits and a complete chassis looks like, an example image is provided to the right

The electronics plus the weapon, together, make up more than half the restricted weight limit for the 3lb class. The remainder weight plays an important factor to the dimensions/amount of weight reliefs required for the chassis.

RC15Motors&Gears

2020-07-04T05:10:44Z

Mbayyari3:

[[Category: RC Mechanical]]
The robots for the 2015 RoboCup SSL competition utilize new 50 Watt brushless motors from [http://www.maxonmotorusa.com/maxon/view/content/index Maxon Motors]. The previous two fleets of robots designed and built by the teams used 30 Watt motors, also from Maxon.

= Background =

== 2008 Robot Fleet ==

The 2008 fleet of robots utilize a 30W Maxon Motor. Power was transmitted through a spur gear fixed to the shaft. This spur gear is held in place by a set screw that was set onto a flat grinded onto the shaft. There are no encoders on these robots.

=== Performance ===

These motors perform fine to this day (several years later). However, the lack of encoders makes it difficult to control the robots with any degree of precision.

== 2011 Robot Fleet ==

The 2011 fleet of robots utilize the same 30W Maxon Motor. Power was transmitted through a spur gear built into the motor shaft. The custom shafts were outsourced, and were effectively pinion wire that was turned down on a lathe to have appropriate sizing for:
<ol style="line-height: 20.7999992370605px;">
<li>Pressing the shaft into the brushless motor shell</li>
<li>Pressing an encoder wheel onto the end of the shaft</li>
<li>Terminating the shaft such that the encoder housing could be capped and kept undisturbed from outside elements</li>
</ol>

=== Performance ===

These motors perform extremely poorly due to the in-house manipulation. Due to errors during the team's manufacturing process in previous years, the brushless motor shell can slip on the custom shaft (i.e. the press fit is not strong enough to prevent slip), thereby degrading power transmission. This was rectified to an extent by epoxying the shaft onto the shell. However, this process is messy, inconsistent and sometimes results in deformation of components when assembled, thereby degrading the motors even further. 

The 2011 robots suffer from hall faults due the misalignment of components, and the fleet is largely unusable due to these problems. However, the encoders do prove to be useful if the robot has little to no motor issues.

= Requirements =

The motors and drive gears of the 2015 robot fleet is intended combine the good aspects of both the 2008 and 2011 fleets, without any of the problems. These requirements are as follows:

== Primary requirements ==
<ol style="line-height: 20.7999992370605px;">
<li>The team should not have to disassemble the motors in order to assemble the drivetrain. (The 2011 robots required a custom shaft, which required pressing combing apart and then reassembling. This results in degraded performance due to a variety of issues).</li>
<li>No epoxy to be used anywhere in the process</li>
<li>Any motor shaft manipulation should be able to be done safely and easily on in-house equipment</li>
<li>Compact design following that of the 2011 robots, as the large 50W motors do not permit such broad drive module as seen in the 2008 fleet.</li>
</ol>

== Secondary requirements ==
<ol style="line-height: 20.7999992370605px;">
<li>The gears for the drivetrain are manufactured in-house on either the laser cutter, waterjet cutter, or injection molding machine</li>
</ol>

= Motor Specifications =

The 2015 fleet uses new 50W Maxon motors for the drivetrain. In order to utilize these motors, some modifications were done to them.

== Modifications by Manufacturer ==

A set of modification were done by the manufacture by the teams request:

*'''Decreased wire length.''' The length of the wires was requested to be 6 inches. This length is sufficient (with extra) for wire routing from the bottom plate to the connectors. If some of the wire is left, it can be easliy clamped together. The reason long wires were not advisable is because the electrical team would need to cut them and cramp them (with much less quality than the factory is capable of).
*'''Decreased shaft length.''' The shaft length of the motor was decreased to fir the design. The shaft was accustomed to the first draft of the drivetrain plates. However, if the new shaft does not fit properly, the driveplate thickness would be changed to have the shaft stick out more or less.
*'''Added flat.''' A flat was added to the shaft on one side alon the whole length. This shaft is required to hold the motor gear from slipping on the shaft.

== Modifications by Team ==

One modification to the motors was done by the team:

*'''A groove.''' This groove is designed to hold a retaining ring, which will keep the motor gear in place.

In order to create this groove on each motor, a jig was created for the lathe. This jig is designed to hold the motor by the shaft and face (by 3 m3 screws). This way, the shaft rotates with the shaft and it is possible to create a groove.

= Testing and Prototyping =

== Waterjet ==

The two main materials cut via the waterjet have been aluminum 6061 and mild steel. Because of the nature of the waterjet process, parts are often produced with taper. When trying to achieve flat gear teeth, this is undesirable. Below are tests we ran to understand the taper produced by the process and account for it.

For these materials, we modeled a 1"x2" rectangle and cut it out to determine understand the tolerances of the waterjet process. By understanding the taper produced by the waterjet, we could account for that by using the tilting capability of the waterjet. The results are below.

=== Steel ===

Thickness - 0.117"[[File:2015-01-12 22.53.20.jpg|thumb|right|x300px|2015-01-12 22.53.20.jpg]]

{| style="width: 500px" border="1" cellpadding="1" cellspacing="1"
|-
| style="text-align: center" | 
| style="text-align: center" | '''Trial 1''' 
| style="text-align: center" | '''Trial 2''' 
| style="text-align: center" | '''Zero-Taper Attempt''' 
|-
| Waterjet set thickness 
| style="text-align: center" | 0.117"
| style="text-align: center" | 0.130"
| style="text-align: center" | 0.117" 
|-
| Taper compensation? (Yes/No) 
| style="text-align: center" | No
| style="text-align: center" | No
| style="text-align: center" | Yes 
|-
| Estimated time to cut (minutes) 
| style="text-align: center" | 0.583
| style="text-align: center" | 0.636
| style="text-align: center" | 0.938 
|-
| Measured dimension on top (Nominal 1") 
| style="text-align: center" | 0.9937
| style="text-align: center" | 0.9877
| style="text-align: center" | 0.9945 
|-
| Measured dimension on bottom (Nominal 1") 
| style="text-align: center" | 1.0016
| style="text-align: center" | 1.0002
| style="text-align: center" | 0.9931 
|-
| Resulting Taper (degrees) 
| style="text-align: center" | 1.93 
| style="text-align: center" | 6.25
| style="text-align: center" | '''0.342''' 
|}

As can be seen, through some basic computation, we were able to significantly reduce the draft encountered in the waterjet process.

Estimated time for cutting one of the motor gears: 1.6 minutes

=== Aluminum ===

Thickness - 0.125" thick

{| style="width: 500px" border="1" cellpadding="1" cellspacing="1"
|-
| 
| Trial 1
| Trial 2
|-
| Waterjet set thickness
| 
| 
|-
| Taper compensation? (Yes/No)
| 
| 
|-
| Estimated time to cut (minutes)
| 
| 
|-
| Measured dimension on top (Nominal 1")
| 
| 
|-
| Measured dimension on bottom (Nominal 1")
| 
| 
|-
| Resulting Taper (degrees)
| 
| 
|}

== Laser Cutter ==

Laser cutters are great machines for cutting a variety of materials, primarily plastics and woods. The minimal setup and overhead, as well as the cleanliness of the process makes it a more preferred process when compared to the waterjet or mill. However, metals cannot be cut on this machine - only metal marked with a marking compound.

Specifically, we have access to a variety of laser cutters on campus. The most common ones that we use are Trotec Speedy 300 laser cutters ([http://www.troteclaser.com/en-US/Laser-Machines/Mid-Size/Pages/Speedy300.aspx http://www.troteclaser.com/en-US/Laser-Machines/Mid-Size/Pages/Speedy300.aspx]). There is 1 machine at the MRDC that is 45 Watts, and 2 more that are 120 Watts.

==== Delrin/Acetal ====

Our primary material to laser cut was delrin. Delrin exhibits nice properties in terms of strength and smoothness. It also cuts nicely on the laser when the proper settings are determined.

*Special care should be taken when cutting delrin. The cutting process produces formaldehyde gas. Additionally, the material burns with a fairly colorless flame.

===== Cut Settings =====

In short, we did several (25) high power, slow passes in etch mode on the laser. This was followed up with 2 cut passes at a relatively low speed. Below are the settings we used to cut the delrin gears with reasonable accuracy.[[File:Gear Set - Delrin.jpg|thumb|right|x300px|Gear Set - Delrin.jpg]]

{| style="width: 212px" border="1" cellpadding="1" cellspacing="1"
|-
| style="width: 158px" | Etch/Cut? 
| style="width: 41px" | Etch 
|-
| style="width: 158px" | Line Thickness 
| style="width: 41px" | 0.001"
|-
| style="width: 158px" | Power 
| style="width: 41px" | 90 
|-
| style="width: 158px" | Speed
| style="width: 41px" | 4.5
|-
| style="width: 158px" | PPI/Hz
| style="width: 41px" | 1000 
|-
| style="width: 158px" | Passes
| style="width: 41px" | 25 
|-
| style="width: 158px" | Lens (Black/Red/Blue)
| style="width: 41px" | Black 
|}

This was followed by a cut at the following settings:

{| style="width: 222px" border="1" cellpadding="1" cellspacing="1"
|-
| style="width: 159px" | Etch/Cut?
| style="width: 50px" | Cut 
|-
| style="width: 159px" | Line Thickness
| style="width: 50px" | Vector
|-
| style="width: 159px" | Power
| style="width: 50px" | 90
|-
| style="width: 159px" | Speed
| style="width: 50px" | 6 
|-
| style="width: 159px" | PPI/Hz
| style="width: 50px" | 1000
|-
| style="width: 159px" | Passes
| style="width: 50px" | 2
|-
| style="width: 159px" | Lens (Black/Red/Blue
| style="width: 50px" | Black 
|}

It is likely very possible to cut the gears without as many passes. We hypothesize that increasing the PPI/Hz may help to fully cut all edges of the material so that it is fully removed without the final 2 cut passes.

== Wire EDM ==

The Wire EDM machine has the capability of providing great precision and the capability of processing multiples of the same part at once.

This process was done in the MRDC Machine Shop by Mr. Steven Sheffield.

[[File:Wire EDM Gears.jpeg|thumb|400px]]

Personal Project Guidelines

2020-07-04T05:09:49Z

Mbayyari3:

[[Category: Core]]
* RJ members are permitted to use RJ and Common Machining Area equipment for personal projects, provided that the following conditions hold:
** The individual must be a dues-paying member for that semester
** The individual must be an active member of RoboJackets and in attendance of the majority of his respective team’s meetings, at the discretion of the project manager
** All RoboJackets and Student Competition Center team machine use takes precedence over the individual’s project, and the individual must verbally make it clear to any other members with an interest of using equipment that they are working on a personal project
* Members fulfilling these requirements are permitted to use surplus stock materials (including but not limited to sheets of metal, plastic, 3D printer filament, etc), granted that they ascertain that the material does not belong to any team and do so sparingly. They are to stop use of these supplies immediately should they be asked to by any RJ project manager or officer.
* Members fulfilling these requirements should not store their projects in RoboJackets space for extended periods of time, and when holding their project at the shop should do so in an out-of-the-way location
** Examples of permissible temporary storage locations include beneath the RoboCup field
** The project must promptly be removed upon request by any of the officers, project managers, or SCC administrators.
* Any of these privileges may, in their entirety or in part, be denied at any time by any RoboJackets officer or Project Manager

Leadership Changes Spring 2019

2020-07-04T05:09:00Z

Mbayyari3:

[[Category: Core]]

== Motivation: ==

The motivation of these changes is that the first line of contact leadership positions (bot lead, 3lb czar, subteam lead, mentor, etc) are instrumental to retaining new members. Often being younger leaders, they tend to struggle with what the position means. We want to provide guidelines in order to make them as successful as they can be in that role.

Furthermore we are making all responsibilities explicit and giving team leads the ability to delegate responsibility. All the responsibilities below have been unofficially required of leadership without ever explicitly telling them beforehand. The team should be able to choose whomever they think is the leader of the team. That leader should be able to do what they are most interested in and qualified for, but all responsibilities must be handled by someone.

=== These are the main reasons why the changes below are being made: ===

* Leaders should know the training curriculum so they can plan their team based activities in conjunction.

* Building the community of leads of a discipline is instrumental in giving younger leaders exposure to the larger RoboJackets knowledge base. They can learn from older leaders and have a direct line to other teams if there are possible avenues for collaboration or assistance. Discipline core is the most direct application of this, but training gives further exposure.

* Training should serve all teams. The cornerstone of training is that there are skills that all new members should learn and RoboJackets as a whole benefits from it.

* The leaders that work directly with new members are their first exposure to the organization. A leader in that role should understand what the expectation is when it comes to meetings with new members present.

Teams that have shown investment in new members during the early phases in the way outlined below have shown greater engagement and retention. We want all leaders to benefit from this knowledge. While the above reasons are targeted at new members, the learning in this organization never stops and can be applied to everyone across the board.

We acknowledge that this is an increase in the workload of our introductory leadership positions. The intention is to clarify their roles rather than add additional ones. In an ideal world there would be enough capable people to cover all specialization of any role, each person would have a single responsibility, and all projects would work as expected. Unfortunately we are lacking people and at this time cannot add additional roles. Historically leads have taken all the roles outlined below and we want to give further power to leads to make the decision that is the best for their team at the moment.

We wanted to give out the ability for team leads to appoint people to the different roles we have recognized. We believe that giving as much autonomy to teams with regards to deciding their own future is paramount for creating long term stability. Team members understand their needs in the present than we can hope to in the past. The intention is to create a framework that can be extended and contracted as the team shrinks and grows.

''' Disclaimer: Just because someone is not required to participate in training does not mean that others shouldn’t. We encourage all members who are interested to participate in training. The more trainers, the less work on an individual. '''

== Subteam lead/bot lead: ==

The role of a subteam/bot lead is to ensure that their section of the team is functioning. It is your responsibility to ensure that the members of your team are taken care of. If you are interacting with new members, it is your responsibility to spend the meeting walking around and ensuring they feel supported in their technical projects. There is a good chance this means that you will be doing less technical work; this is expected. Your main focus is to build the team. You do not have to make all of the technical decisions, that can be left to the team at large and older members.

You are required to go to the discipline cores. If you are unable to attend, you are responsible for communicating this to the chair of that meeting, writing up your report, and sending someone else that can present on your progress. Additionally, it is advised to pull in members to these meetings when a topic they are particularly knowledgeable comes up.

'''Definition: participate in training - you will help plan the curriculum and lessons over the summer and then help with teaching at least one day a week during the training period in the fall.'''

== Subteam lead (IGVC, RR, RC): ==

You must participate or appoint a member to participate in the appropriate discipline training. This means you or a delegate of your choosing will attend at least one training a week during the training period to assist with teaching.

You are advised to create a training curriculum for your specific team in the summer to be implemented during the fall. You have complete latitude to do whatever you think is most beneficial to your team. The training curriculum can be made up of anything that helps teach new members the skills they need.

Additionally the subteam lead can appoint a technical lead. The job of the technical lead would be to focus in on the technical projects going on within the team and be less involved in training. The subteam lead can appoint themselves to this role with the expectation that someone within the team is responsible for their general training requirement and their team specific training requirements. It is heavily encouraged that the STL be aware of general training curriculum as described in the motivation section.

== How this applies to BattleBots: ==

The team must send a single electrical member to the discipline cores and to participate in training. This person will be appointed by the BattleBots project manager.

The 3lb czar is required to be involved in the preparation of training over the summer. The czar should know the curriculum and be able to plan the 3lb schedule around it.

A single mentor will be required to participate in mechanical training. The mentor will be appointed by the 3lb czar.

An experienced bot lead will be appointed by the BattleBots project manager and will be required to participate in mechanical training.

Buzzbot

2020-07-04T05:08:14Z

Mbayyari3:

[[Category: IGVC]]
{| class="wikitable" align="right"
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Buzzbot II
|-
! scope="row" colspan="2" align="center" |[[File:Buzzbot.png|right|frameless|480x480px|DrumRoll, please]]
|-
! scope="row" style="text-align:left" | Year Of Creation
| {{{year|2002-2003}}}
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Versions
|-
! scope="row" style="text-align:left" | Current Version
| {{{currver|deprecated}}}
|-
! scope="row" style="text-align:left" | Update Year
| {{{updyr|2002-2003, 2003-2004}}}
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Information and Statistics
|-
! scope="row" style="text-align:left" | Farthest Distance
| {{{mat|Finished}}}
|-
! scope="row" style="text-align:left" | Fastest Time
| {{{mat|4 min 32 sec}}}
|-
! scope="row" style="text-align:left" | Highest Placement AutoNav
| {{{hfin|9th}}}
|-
! scope="row" style="text-align:left" | Highest Placement Design
| {{{hfin|10th}}}
|}

= Competitions =

=== IGVC 2003 ===
*Bot Version: Buzzbot
*Results:
** Distance: 77 feet 8 inches
** Design Competition Placement: 10th (X points)
** AutoNav Competition Placement: 9th

=== IGVC 2004 ===
*Bot Version: Buzzbot II
*Results:
** Time: 4 minutes 32 seconds
** Design Competition Placement: 24th (X points)
** AutoNav Competition Placement: 9th

= Versions =

== Buzzbot (V1.0) ==

=== At Competition ===

=== Mechanical Design & Issues ===

=== Electrical Design & Issues ===

=== Software Design & Issues ===

== Buzzbot II (V2.0) ==

=== At Competition ===

=== Mechanical Design & Issues ===

=== Electrical Design & Issues ===

=== Software Design & Issues ===

= Additional Information =

=== Team Members ===

=== Gallery ===
<gallery mode="packed-hover">

Image:BenCode 83 small.jpg | BenCode 83
Image:BenCode 534 small.jpg | BenCode 534
Image:BenCode 536 small.jpg | BenCode 536

</gallery>

Gucci

2020-07-04T05:07:20Z

Mbayyari3:

[[Category: RoboWrestling]]
==Introduction==
Gucci is the sumo robot created by Battlebots between Summer and Fall of 2018. It competed in the 2018 All-Japan Sumo Robotics Competition in Tokyo, Japan. It was the first of the next line of sumo bots in RoboJackets after the Pushi line. This guide is designed to walk you through our process for designing Gucci. We hope you can learn from our successes and failures when designing your own Sumo bot.

Gucci was defined by being the successor to Pushiv. Pushiv did not win a match at its competition, our main goal was to win at least one match. This may be in actuality too high of an initial goal, but when we looked into how we could stand a better chance there were some clear directions. Pushiv was a very unique sumobot, primarily in its use of worm gears. The purpose of Gucci was to create a solid bot that sticks close to the meta. Instead of trying something untested, we wanted to create a quality sumo robot that future bots could build from.

==Mechanical Design==

===Drive===

====Introduction====

We designed the drive wrong with Gucci. If you want to know what we think is right, scroll down to Gucc$$$. The mistake we made was that we believed we should be designing around a desired speed and then picking a reasonable acceleration. Turns out, when you do this you reach your target speed but drive off the edge. Because of this blunder, we used a fraction of the power our motors could have output. This is what really cost Gucci from being a competitive sumobot.

A general tip for sumo drives is to plan to use shims. Shims are very thin spacers. The spacing of the drive components is very important, especially because a small change in magnet height drastically impacts its force, and using shims can help you correct tolerancing issues or wheel deformation.

====Design Decisions====

We got really nice motors from Maxon, which came down to our budget and negotiating a discount. We used [https://www.jsumo.com/steel-gear-bundle-06-module-4301-reduction these] gears, which seemed standard from Jsumo, with a 4.3:1 gear ratio. We used [https://www.jsumo.com/jsumo-robot-wheel-45x30mm-pair these] wheels from JSumo, which in reality were a millimeter less in diameter than advertised. In addition, they deformed about another millimeter.

====Differences from Pushiv/How it fits the Meta====

We did not use worm gears. We used a much lower gear ratio, because it appeared to us that speed was much more important in the meta than Pushiv had been designed around.

----
===Baseplate Magnets and Skids===

====Introduction====

The baseplate is the core of a sumo robot. A sumobot is pretty much motors and magnets, so the thing that connects those two is important. The main intellectual task of designing a baseplate is deciding where you want your centroid, or center of magnet force, to be. Weight on the wheels is going to increase friction and prevent you from slipping. Weight farther forward is going to resist your robot from being flipped. This is important because in a plow versus plow contact the robot that wins is typically the one that gets beneath the other one. Remember that bar magnets have an inverse cubed relationship between force and distance, and thus getting lifted a small amount has a large effect on magnet force. If you are designing a sumo robot that uses skids, like most sumo robots, moving the centroid farther forward will put weight on them. This is probably a good idea, but you have to analyze what capacity they have and how that weight will affect their behavior. You also have to consider whether you want the plow to bend, and if so you need to be very precise about how much it is allowed to bend and how much weight it will take.

====Design Decisions====

For our magnet layout, we decided to surround the wheels with magnets to create our friction. We then added a row of thicker magnets at the front of the baseplate. We wanted the magnet force to be generally at the front. Aligned with the magnets in the front were our skids. We decided to use [https://www.mcmaster.com/6421k66 ball casters]. The ball casters we used could support the weight of the magnets concentrated at the front of the bot.

====Differences from Pushiv/How it fits the Meta====

Our magnet centroid was closer to the front than pushiv, which seemed to be very centered. We also used ball casters instead of small, solid, HDPE skids.

----
===Plow===

====Introduction====

Most plows seem to be rigid flat sheets that are angled at a shallow angle against the ground. Some plows are made of flexible spring steel that flexes to contour against the ground. We don’t really have the data to say whether one is superior to the other at this point. At competition we only pushed one bot, and we weren’t able to scoop them. This could have been due to low power, however.

====Design Decisions====

We inherited a unique strategy from Pushiv, which was to attempt to use both strategies. The way this works is to have a first stage (the stage closest to the enemy bot) that is springsteel, but after a short distance overlap that with a second stage that is made of rigid steel.

====Differences from Pushiv/How it fits the Meta====

In this case we decided to give Pushiv’s strategy another try because we didn’t see anything wrong with it and had no data from Pushiv on whether it was effective or not.

----
===Exterior===

Walls on a sumobot are only important for protecting your electronics, and potentially mounting sensors. Unlike battlebots you won’t be facing any weapons, but there is a high likelihood of your robot being flipped. If your walls are well designed, the electronics won’t take the brunt of the impact when the robot lands. Our walls were 1/8” HDPE, and while they were not used intensively we did not see a problem with that design.

==Electrical Design==

===Microcontroller===

The microcontroller of choice was the Particle Photon. The main driving force for the decision was the thought of keeping the software we had at the time without changes so that the software team could focus on expanding on strategy and teaching new members how to work with the microcontroller. Gucc$$$ and newer sumo robots have moved away from the Particle Photon towards Teensy for more flexibility on pins and types of communication.

----
===Sensors and Sensor Locations===

====Line Sensors====

We used a total of four [https://www.sparkfun.com/products/9453 line sensors], each mounted in a corner of the robot. The idea being that we would be able to detect not only if we hit the line, but in what orientation we are in relation to it. We decided to go with the analog version of the sensors because when the field gets dirty, the white lines become grey, which could cause non deterministic behavior.

====Distance Sensors====

For the [https://www.adafruit.com/product/3317 distance sensors], we chose the Adafruit VL53L0X. These sensors are analog and communicate with the microcontroller through I2C. We put 6 of them in an array covering the front half of the robot; that is, two facing front, two facing diagonally, and two facing to the sides. The main reason we chose these sensors was because they provide you with a better idea of where the opponent is; however, we encountered some difficulties while mounting them.

The main problem is that we neglected accounting for the sensors’ vision spread because we assumed it would be something resembling a straight line coming from the sensor. It turned out that the vision spread is more of a cone, which was obstructed in most of the sensors. The sensors at the front had to be moved higher up to prevent interference from the plow, and the angled sensors had to be moved from a 45 degree angle to about a 60 degree angle from the front.

----
===PCB===

We decided to go with the same approach as Pushiv towards the pcbs. We made a main board and an auxiliary board. The auxiliary board was connected to the main board through a bus and broke out the lines for all the distance sensors and the front line sensors. Unfortunately, the CAD exported by EAGLE into Fusion 360 did not represent the height of the auxiliary pcb appropriately, which meant that the planned space under the plow was not sufficient for it. We ended up moving the auxiliary pcb to the electrical plate in front of the main board, which made it redundant and somewhat difficult to work with because of the position.
All the pcb files are in GitHub for reference

----
===Electrical Plate Design for ESC and PCB===

The electrical plate was made of ⅛” HDPE and was made to accommodate the main pcb between the ESCs. The only annoying, but unavoidable part of the setup was that if we needed to remove an ESC or the pcb for any reason, the electrical plate had to come off first because the ESCs are screwed in from the bottom, and the PCB had nuts holding its screws in place at the bottom.

==Software==

* Software remained largely the same from past years, adopting a ‘seek-and-destroy’ tactic. Some things of note:
** Software drove the robot at the maximum speed it could without the robot stopping after its entire body crossed the line
** The input from the line sensors always took priority over other move logic
** Input from the distance sensors was piped into a framework called “Fuzzy Logic” for the Particle Photon. Essentially, the library would read the input from the sensors and decide the next movement based on the ranges we defined in rulesets
** It must be noted that Fuzzy Logic defaults to the lower end of the number range for the output, and previous code decided that output in that range was a command to make a hard left. This was fixed before the competition
* Logic to turn sensor input into movement commands was expanded to account for the two extra sensors, basically doubling the number of sensor rules we needed
* '''It must be noted that this code implemented logic for the start module the same as previous years’. This was actually incorrect, as the robots this year were to start as soon as the judge pressed the button on the remote. More in-depth reading of the rules is suggested so that we do not make this mistake again.'''
* This differed from high-performing robots in that the other robots seemed to make movement commands based on the actions of the opposing robot. That means that if the opponent moved, the robot would try and position itself in a way in which the plow was always pointed towards the opponent. If the opponent didn’t move, then the robot would jolt forward periodically (~10cm at a time). Once the opponent was close enough, the robot would turn its speed up to push to opponent out, as the chance that the opponent would be able to dodge the robot became significantly smaller.

==Competition Review==

===What happened at Competition?===

At our competition, we quickly lost our first point. Our opposing bot stopped working after this. We were able to push this bot out of the ring when it wasn’t moving. The judges repeatedly gave the opposing bot “redos” until after many attempts they gave us the win. This was the first ever RoboJackets win at this competition. We also received a 2nd round bye, advancing us to day 2 (The top 32). In our round of 32 match, we were launched out of the arena very quickly. This ended our run. It must be noted that we were in fact pushing the 2nd robot when it was pushing us back. That means that either we were not providing enough power to the motors, or our magnet force was too weak, or a mixture of both.

----
===What did we discover?===

Firstly, we found that our bot using 5% motor power (It was doing this so the line sensors could react), which was too slow. It was programmed to move at higher motor power when we entered a pushing match, but our magnet force was too weak (150 lbs) to actually achieve this. Most bots seem to move at a higher speed when the front sensors detect the opposing bot a certain distance away. We also found that input from the distance sensors didn’t really matter if the opponent made the first move and pushed us out.

----
===What issues did we find with our design?===

Mechanically, we found that we did not have enough magnet force and our spring steel plow system was not very useful because the spring steel never bent enough to be a smooth plow. Also through shop testing, we found that ball casters were not the ideal choice for our skids. As mentioned before, the distance sensors also gave unreliable input. '''Sensor logic was disabled during the entire tournament.'''

----
===What did we learn about the Meta?===

We learned that most teams are a lot less concerned with scratching. They even have magnets touching the ground. We also learned how other teams design skids. A lot of bots use carbon fiber base plates which is lighter. Bar magnets are also a lot more common than we thought. There was a pretty even balance between bar magnets and ring magnets.

==Gucc$$$==

At the competition we discovered that there were many parts of the metagame that we did not understand. Gucc$$$ is a partial update to Gucci. We did not feel that an entirely new bot needed to be designed and fabricated, but we made a few crucial changes that fixed some of the severe discrepancies between Gucci and the meta.

==Gucc$$$ Mechanical Design==

===Drive and Magnets===

====Why did we change and how?====

The most important thing we learned this year was how to spec motors/magnet weight. We made the mistake of trying to choose motors and magnets based off of how fast we wanted to move and how quickly we wanted to accelerate to that speed. What we learned at competition was that the only statistic we should have been designing for is how quickly we can stop moving. The reason for this is because our firmware operates by repeatedly checking for the thick border of the field using a line sensor while driving forward. When the border is detected, we need to decelerate quickly enough that we do not drive off the edge of the track. By designing without this in mind, we built a sumobot that could not go near its max power without driving off the edge. There are some possible workarounds by doing clever things with software (if we know we are approaching the edge beforehand we could slow down), but until we are there, the priority for the mechanical team should be not driving off the edge. To assist with this problem, we moved our wheels to the back of the bot rather than the center. This gives more time and distance for the line sensors to react. Another drive problem we had previously was magnets behind the wheels causing us to tilt backwards and get stuck on the floor. We had to remove these before competition. Now that the wheels are in the back, the bot only leans forward from magnet force.

The other thing we were wrong about for Gucci’s drive was that we worried too much about scraping the ground. We had a lot of distance between the bottom of our magnets and the field. When we talked to Sumozade at competition, they told us that they did not have any space between their magnets and the field (they dragged). The field is harder to scratch than we expected, because our practice field is not a great representation. Scratching is illegal, so the tricky problem is discovering how much force is ok before the robot starts scratching. We did not figure that out. Our plan for Gucc$$$ is to have nearly no distance between our magnets and the ground, but use shims to be sure that the weight of the bot is supported by our wheels and skids (shims are necessary to account for wheel deformation). When we moved the magnets closer to the ground in CAD, our Magnet force increased from under 200 lbs to over 450 lbs.

----
===Skids===

====Why did we change?====

While Ball Casters initially seemed like a good idea, we found that small particles get inside of them really easily, making them “Crunchy”. We were constantly having to buy replacements. Most bots are competition used skids that were kind of like small wheels. We did our best to do something similar, because this bot was designed around matching the meta.

====How does the new design work?====

The new skid design is a 0.25 inch thick rectangle. It has a hole for a small steel axle to slide though, and 2 small PEEK plastic bushings sit on this axle. This is closer to the small rollers we saw bots use at competition (with some different material used) and it helps us stay closer to the ground.

----
===Plow===

====Why did we change?====

While the 2 stage spring steel concept was a cool idea, we found most teams used a sharpened blade that stayed close to the ground. The main issue with our spring steel design is that it could never bend enough for a smooth connection to be formed with the solid steel portion of the plow. Using this design, we would never be able to fully get under our opposing bots. The opposing bots plows would get stuck in that gap which is interesting, but not really effective unless in very specific cases. Also, most bots at competition used aluminum plows and only sometimes had steel, but when they did it was only at the very front.

====How does the new design work?====

The new design is still 2 stages, however both stages are aluminum. Each stage is at a different angle. The first stage can be sharpened to be flush with the ground. The front plate is also now angled so we have 3 different angles in the front of the bot. This aligns more with the curve shape other bots seem to have.

==Gucc$$$ Electrical Design==

===Microcontroller===

We moved to the Teensy 3.6 since it gives more flexibility to the components we can use. All of its digital pins are interruptible, it has 2 pins with DACs, and it can use most communication methods (I2C, serial, CAM, etc). The controller is also programmable through the Arduino IDE, which makes things a bit simpler for Windows users.

----
===Sensor Mounting===

On the previous bot, we ran into issue with the TOF sensors being too close to the ground. We moved the sensors up on the robot (Using cutouts on the side plate and front plate) and design new 45 degree mounts that are internal. We also added a standoff for the front line sensors to add greater distance between them and the wheels.

----
===PCB===

We removed the auxiliary pcb due to the redundancy created in the previous iteration. The main pcb now has a comparator IC to allow us to use pin interrupts on the Teensy while being able to adjust the interrupt threshold and keeping the analog signal going to the Teensy as a debug tool. To give the robot better control over its motion, we routed the motors’ encoder outputs to the Teensy and added an IMU as well. The only downside is that the board operates at three different voltages now. 5V comes from the ESCs and is used for the encoders and Teensy. The line and distance sensors are run at 3.3V since the Teensy’s pins cannot handle more than that. And the IMU runs at 1.8V.

==Gucc$$$ Software==

===New Tactics===

* In April 2019, an experimental project began with the new software members to implement code that would help the robot adopt a more “cowardly” strategy in which the robot would dodge out of the way and then push the opponent once the opponent crossed in front of the robot again. Only the timed movements were created for the experiment, but it looked pretty promising.

* This could probably be used at the very beginning of the matches, as many opponents like charging straight at us.

==Team==

Here was the team that worked on this project:

Mentor: Mason Murray-Cooper

Mechanical Leads: Alex Field and Hank Hellstrom

Electrical Lead: Juan Elizondo

Software Lead: Andrew Chang

Team Members: Phillip Holloway (Mechanical), Christopher Quinn Johnson (Mechanical), Logan Schick (Software)

Special Thanks to Varun Madabushi and Joe Spall for helping with Electrical and [[Jonathan Spalten]] for helping with Mechanical during crunch time

BattleBots

2020-06-24T17:40:53Z

Mbayyari3: /* Current Leadership */

Welcome to the '''[http://www.robojackets.org/ RoboJackets]''' BattleBots wiki! [[File:bb pic.jpg|thumb|right|400px|BattleBots team at Motorama 2018]]

Everyone has seen BattleBots on T.V., fighting to the death in a gladiatorial-style arena in a shower of steel, sparks, and glory, and yet many people haven't the first clue about what it takes to build one!

RoboJackets' BattleBots team tries to solve this, by teaching members to design and build a robot 1) robust enough to take multiple beatings, but 2) strong enough to deliver its own beatings in return. A good technical challenge that takes hundreds of man-hours and buckets of love. We have built battle-ready robots in the 120 lb, 60 lb, 30 lb, 12 lb, and 3 lb weight classes, including (based on their active weapon) drum spinners, ring spinners, shell spinners, veritical and horizontal bar spinners, sumo bots, walkers, and even the occassional wedge.

We use mostly mechanical skills with some degree of electrical experience to implement our carefully CAD'ed designs, to personally manufacture the majority of our robots. Ultimately our goal is to build an awesome machine to fight one-on-one with another robot in the same weight class, all the while learning practical applications of tooling and machining, and gaining invaluable experience in the design and manufacturing process.

== Meeting Times ==

We meet in the Student Competition Center (Building on 14th Street). Wear closed-toe shoes and a t-shirt (long sleeves must be rolled up) since we will be using the machine shop. Bring a hair tie if needed. Consult the #carpool Slack channel for information regarding the time and place of the carpool. Please note that once 3 pound program members are placed on teams, that they will only meet on either Thursday OR Friday until further notice.

* Thursday: 6:30 pm to 9:30 pm
* Friday 6:30 pm to 9:30 pm

== Current Leadership ==
* Project Manager: Cody Page
* 3lb Manager: Cade Tyler
* Chonki Bot Lead: Brian Epstein
* Hocki Bot Lead: Varun Madabushi
* Maori Bot Lead: Dennis Crawford
* Valkryi Bot Lead: Sam Li
* Samurai Bot Lead: Dylan Adriano

== The Competition ==

The competition consists of fights between robots in the same weight class. Competition rules place certain limits on weapon design and robot weight, for a fair contest and for the safety of the observers. For instance, entanglement weapons such as ropes or nets are prohibited along with invisible weapons such as electrical interference. This focuses the robot design on aggressive weapons designed to break apart or incapacitate the other robot, and the only limit on this type of weapon is that it is well engineered so as to not harm the people around it. The presence of these aggressive weapons forces the robots to be designed to withstand large shock loads, both mechanically and electrically. The challenge of the BattleBots team is unique in that a balance needs to be reached between defensive and offensive abilities, all while ensuring that the robot is very robust in all aspects. Even a single wire or bolt coming loose will cause defeat in an intense fight!  This year we plan on attending two competitions, Motorama in Harrisburg, PA and RoboBrawl in Champaign, IL.

== 3 Pound Program ==

The three pound program is for new BattleBot/Sumo members to learn the technical skills needed to succeed in BattleBots and create their very first 3 pound BattleBot. Members of this program will have the opportunity to work on a team to create a 3 pound bot for competition. Through this process they will become proficient in Inventor CAD, machining abilities, electrical work, and teamwork. Once graduated from the 3 pound program, members can take what they've learned to the next level on either a Sumo team or a bigger bot team. Check out the links below for some advice on your 3 pound bot.

'''3 Pound Links'''

*[[3lbers]]
*[[3lb Beginner's Guide]]
*[[Electronics Basics]]
*[[List of 3lb Robots]]

== Documentation ==

===== 2020 Competition =====
* [[Motorama 2020]]

===== 2019 Competition =====
* [[Motorama 2019]]
* [[RoboJackets 20th Anniversary Competition]]

===== 2018 Competition =====
* [[Motorama 2018]]
* [[RoboGames 2018]]

===== 2017 Competition =====
* [[Motorama 2017]]
* [[RoboGames 2017]]

===== 2016 Competition =====

*[[Motorama_2016|Motorama 2016]]
*[[RoboGames_2016|RoboGames 2016]]

===== 2015 Competition =====

*[[Motorama_2015|Motorama 2015]]
*[[RoboGames_2015|RoboGames 2015]]

===== 2014 Competition =====

*[[BattleBots_2014_Tasks|Tasks]]
*[[BattleBots_2014_Meeting_Notes|Meeting Notes]]

===== 2013 Competition =====

*[[BattleBots_2013_Tasks|Tasks]]
*[[BattleBots_2013_Meeting_Notes|Meeting Notes]]

===== 2012 Competition =====

*[[BattleBotsPhotos2012|Photos]]
*[[BattleBots_2012_Tasks|Tasks]]
*[[BattleBots_2012_Meeting_Notes|Meeting Notes]]

===== 2011 Competition =====

*[http://www.robojackets.org/gallery/main.php?g2_itemId=7317 2011 Competition Pictures]

== Resources ==

*[http://www.robojackets.org/teams/battlebots/ RJ BattleBots Overview Page]
*[https://lists.gatech.edu/sympa/info/robojackets-battlebots RJ BattleBots Mailing List]
*[http://robogames.net/ RoboGames]
*[http://www.riobotz.com.br/tutorial.html Riobotz Tutorial] (400 page book on how to build a BattleBot. Great resource.)
*[http://www.battlebots.com/ Battlebots.com]
*[http://www.botrank.com/ BattleBots Ranking]
*[http://www.buildersdb.com/ Buidersdb.com]
*[http://www.robotmarketplace.com Robot Marketplace] (good source for motors, drivers, etc.)
*[[BattleBots BeetleWeight Wiki Template]]
*[[Competition Tool Packing List]]
*[[Robot Basics]]
[[Category:BattleBots]]

Current Leadership

2020-06-24T17:40:40Z

Mbayyari3: /* Team Leadership */

Below is a list of who are current leadership is during the 2020-2021 academic year.

__TOC__

==Core Officers==
<dt>[[President]] </dt>
<dd>Alex Field</dd>
<dt>[[Vice-President]] </dt>
<dd>Ava Thrasher</dd>
<dt>[[Treasurer]] </dt>
<dd>Christopher Bellflowers</dd>
<dt>[[Secretary]] </dt>
<dd>Malak Bayyari</dd>
<dt>[[Shop Manager]] </dt>
<dd>Vijay Srivastava</dd>
<dt>[[Promotions Chair]] </dt>
<dd>Cameron Loyd</dd>
</dl>

==Appointed Positions==
<dt>[[IT Coordinator]] </dt>
<dd>Todd Hayes</dd>
<dt>[[Sponsorship Chair]] </dt>
<dd>Brian Epstein</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software/Firmware_Training_Lead Mechanical Training Lead] </dt>
<dd>Sam Walters</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software/Firmware_Training_Lead Software Training Lead] </dt>
<dd>Dylan Siegler</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software/Firmware_Training_Lead Electrical Training Lead] </dt>
<dd>Asha Bhandarkar</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software/Firmware_Training_Lead Firmware Training Lead] </dt>
<dd>Arvind Srinivasan</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software_Discipline_Core_Chair Electrical Core Chair] </dt>
<dd>Arvind Srinivasan</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software_Discipline_Core_Chair Mechanical Core Chair] </dt>
<dd>Sam Morstein</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software_Discipline_Core_Chair Software Core Chair] </dt>
<dd>Oswin So</dd>
<dt>[[Outreach Chair]] </dt>
<dd>Michael Chen</dd>
<dt>[[Volunteer Coordinator]] </dt>
<dd>Malak Bayyari</dd>
<dt>[[Kickoff Coordinator]] </dt>
<dd>Evan Strat</dd>
<dt>[[SCCGB Delegate]] </dt>
<dd>Knute Broady</dd>
<dt>[[Web App Product Owner]] </dt>
<dd>Josh Oldenburg</dd>
<dt>[[Purchaser]] </dt>
<dd>Stefan Quaadgras</dd>
</dl>

==Team Leadership==

<dt>[[BattleBots]] </dt>
<dd>Project Manager: Cody Page</dd>
<dd>3lb Manager: Cade Tyler</dd>
<dd>Chonki Bot Lead: Brian Epstein</dd>
<dd>Hocki Bot Lead: Varun Madabushi</dd>
<dd>Maori Bot Lead: Dennis Crawford</dd>
<dd>Valkryi Bot Lead: Sam Li</dd>
<dd>Samurai Bot Lead: Dylan Adriano</dd>

<dt>[[RoboNav]] </dt>
<dd>Project Manager: Tan Gemicioglu</dd>
<dd>Mechanical Lead: Charles Li</dd>
<dd>Electrical Lead: </dd>
<dd>Software Lead: Matthew Hannay</dd>

<dt>[[RoboCup]] </dt>
<dd>Project Manager: Marine Maisonneuve</dd>
<dd>Chief Scientist: Christopher Lindbeck</dd>
<dd>Mechatronics Lead: Alyssa Gordon</dd>
<dd>Electrical Lead: Arthur Siqueira</dd>
<dd>Software Lead: Hussain Gynai</dd>

<dt>[[RoboRacing]] </dt>
<dd>Project Manager: Shishir Pandit-Rao</dd>
<dd>Mechanical Lead: Sam Morstein</dd>
<dd>Electrical Lead: Andrew Rocco</dd>
<dd>Software Lead: Daniel Martin</dd>

<dt>[[RoboWrestling]] </dt>
<dd>Project Manager: Caleb Chang</dd>
<dd>Mechanical Lead: Phillip Holloway</dd>
<dd>Electrical Lead: Juan Elizondo</dd>
<dd>Software Lead: Logan Schick</dd>
</dl>

[[Category: Leadership Positions]]

Category:IGVC

2020-06-01T18:58:59Z

Mbayyari3:

Links to anything relevant to IGVC.
[[Category: RoboNav]]

Current Leadership

2020-06-01T05:40:31Z

Mbayyari3: /* Team Leadership */

Below is a list of who are current leadership is during the 2020-2021 academic year.

__TOC__

==Core Officers==
<dt>[[President]] </dt>
<dd>Alex Field</dd>
<dt>[[Vice-President]] </dt>
<dd>Ava Thrasher</dd>
<dt>[[Treasurer]] </dt>
<dd>Christopher Bellflowers</dd>
<dt>[[Secretary]] </dt>
<dd>Malak Bayyari</dd>
<dt>[[Shop Manager]] </dt>
<dd>Vijay Srivastava</dd>
<dt>[[Promotions Chair]] </dt>
<dd>Cameron Loyd</dd>
</dl>

==Appointed Positions==
<dt>[[IT Coordinator]] </dt>
<dd>Todd Hayes</dd>
<dt>[[Sponsorship Chair]] </dt>
<dd>Brian Epstein</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software/Firmware_Training_Lead Mechanical Training Lead] </dt>
<dd>Sam Walters</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software/Firmware_Training_Lead Software Training Lead] </dt>
<dd>Dylan Siegler</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software/Firmware_Training_Lead Electrical Training Lead] </dt>
<dd>Asha Bhandarkar</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software/Firmware_Training_Lead Firmware Training Lead] </dt>
<dd>Arvind Srinivasan</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software_Discipline_Core_Chair Electrical Core Chair] </dt>
<dd>Arvind Srinivasan</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software_Discipline_Core_Chair Mechanical Core Chair] </dt>
<dd>Sam Morstein</dd>
<dt>[https://wiki.robojackets.org/Electrical/Mechanical/Software_Discipline_Core_Chair Software Core Chair] </dt>
<dd>Oswin So</dd>
<dt>[[Outreach Chair]] </dt>
<dd>Michael Chen</dd>
<dt>[[Volunteer Coordinator]] </dt>
<dd>Malak Bayyari</dd>
<dt>[[Kickoff Coordinator]] </dt>
<dd>Evan Strat</dd>
<dt>[[SCCGB Delegate]] </dt>
<dd>Knute Broady</dd>
<dt>[[Web App Product Owner]] </dt>
<dd>Josh Oldenburg</dd>
<dt>[[Purchaser]] </dt>
<dd>Stefan Quaadgras</dd>
</dl>

==Team Leadership==

<dt>[[BattleBots]] </dt>
<dd>Project Manager: Cody Page</dd>
<dd>3lb Manager: Cade Tyler</dd>
<dd>Chonki Bot Lead: Brian Epstein</dd>
<dd>MeltyBrai Bot Lead: Varun Madabushi</dd>
<dd>Maori Bot Lead: Dennis Crawford</dd>
<dd>Valkryi Bot Lead: Sam Li</dd>
<dd>Samurai Bot Lead: Dylan Adriano</dd>

<dt>[[RoboNav]] </dt>
<dd>Project Manager: Tan Gemicioglu</dd>
<dd>Mechanical Lead: Charles Li</dd>
<dd>Electrical Lead: </dd>
<dd>Software Lead: Matthew Hannay</dd>

<dt>[[RoboCup]] </dt>
<dd>Project Manager: Marine Maisonneuve</dd>
<dd>Chief Scientist: Christopher Lindbeck</dd>
<dd>Mechatronics Lead: Alyssa Gordon</dd>
<dd>Electrical Lead: Arthur Siqueira</dd>
<dd>Software Lead: Hussain Gynai</dd>

<dt>[[RoboRacing]] </dt>
<dd>Project Manager: Shishir Pandit-Rao</dd>
<dd>Mechanical Lead: Sam Morstein</dd>
<dd>Electrical Lead: Andrew Rocco</dd>
<dd>Software Lead: Daniel Martin</dd>

<dt>[[RoboWrestling]] </dt>
<dd>Project Manager: Caleb Chang</dd>
<dd>Mechanical Lead: Phillip Holloway</dd>
<dd>Electrical Lead: Juan Elizondo</dd>
<dd>Software Lead: Logan Schick</dd>
</dl>

[[Category: Leadership Positions]]

MediaWiki:Sidebar

2020-06-01T02:30:32Z

Mbayyari3:

Main Page

2020-06-01T02:29:53Z

Mbayyari3:

__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. For information, [https://robojackets.org/contact-us/ contact us]. New members are always welcome.
|-

| style="vertical-align: middle; width: 200px; | '''<big>Teams</big>'''
<ul style="line-height: 20.7999992370605px;">
<li>[[BattleBots]]</li>
<li>[[RoboNav]]</li>
<li>[[RoboCup]]</li>
<li>[[RoboRacing]]</li>
<li>[[RoboWrestling]]</li>
</ul>

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

| style="vertical-align: middle; width: 400px; | '''<big>Resources</big>'''
<ul style="line-height: 20.7999992370605px;">
<li>[[:Category:How to Guides: Technical | How to Guides - Technical]]</li>
<li>[[:Category:How to Guides: Administrative| How to Guides - Administrative]]</li>
<li>[[SCC Training Curriculums]]</li>
<li>[https://sums.gatech.edu/ SCC SUMS Webpage]</li>
<li>[https://wiki.scc.gatech.edu/Main_Page SCC Wiki]</li>
</ul>

|-

| style="vertical-align: middle; width: 350px;" | '''<big>Core Leadership</big>'''
<ul style="line-height: 20.7999992370605px;">
<li>[[President]]</li>
<li>[[Vice-President]]</li>
<li>[[Treasurer]]</li>
<li>[[Secretary]]</li>
<li>[[Shop Manager]]</li>
<li>[[Promotions Chair]]</li>
<li>[[Current Leadership]]</li>
</ul>

| style="vertical-align: middle; width: 200px;" | '''<big>Info</big>'''
<ul style="line-height: 20.7999992370605px;">
<li>[[IT Hub]]</li>
<li>[[Shop Management]]</li>
<li>[https://robojackets.org RoboJackets Information]</li>
</ul>
!
|}

Category:RoboNav

2020-06-01T02:29:30Z

Mbayyari3: Created blank page

RoboNav

2020-06-01T02:28:36Z

Mbayyari3:

[[Category: RoboNav]]
[[File:Jessii.jpg|thumb|right|400px|Our 2019 robot, Jessii]]
The IGVC competition is centered around building the next generation of off-road, all-weather autonomous vehicles. The idea is to create a vehicle and tech stack that can navigate through an obstacle course to given GPS waypoints without human intervention. The map is not known beforehand, and while there are certain obstacles that are commonly used, theoretically anything can be placed onto the course. The competition is scored in three main areas. First is the design of the robot as presented in the TDP (a written report on the vehicle) that is given to industry experts for judging. Next, the team is scored based on their presentation of the robot, including a Q&A from the judges. Finally, the robot is put to the test by trying to navigate the fastest route on the AutoNav course. '''If''' multiple robots complete the course, the winner is the robot that completed it in the fastest time. Otherwise, the robot that navigates the farthest is the winner. In other words, speed is second to safety.



== Meeting Times ==
We meet in the Student Competition Center (575 14th St). If you are working in the machine shop or mechanical room you will need to wear closed-toe shoes and a t-shirt (no long sleeves). Bring a hair tie if needed.

* Wednesdays 6:30PM to 9PM
* Sundays 4PM to 7PM

== Current Leadership ==
* Project Manager: Tan Gemicioglu
* Mechanical Lead: Charles Li
* Software Lead: Matthew Hannay

== Competition ==
==== Guidelines ====
* [http://www.igvc.org/rules.htm Rules]
==== Important Dates ====
* June 5-8, 2020: 28th Annual IGVC

== Past Competitions ==

{| class = "wikitable" style = "width:95%;"
|- style="font-size:15px;" |
| style="width:20%;" | '''Bot'''
| style="width:20%;" | '''Competition Years'''
| style="width:20%;" | '''Versions'''
| style="width:40%;" | '''Design Reports'''
|-
| style="font-size:15px;" | '''[[Jessi]]'''
| 2018 - 2019
| Jessi, Jessii, Jessiii
|
* '''Version 1:''' [[Media:IGVC_Design_report_2018.pdf | Jessi Design Report]]
* '''Version 2:''' [[Media:IGVC_Design_report_2019.pdf | Jessii Design Report]]
|-
| style="font-size:15px;" | '''[[Woodi]]'''
| 2017
| See [[Jaymi]]
| Jaymi's design report was submitted for Woodi.
|-
| style="font-size:15px;" | '''[[Jaymi]]'''
| 2016
| See [[Woodi]]
| [[Media:IGVC_Design_report_2017.pdf | Jaymi Design Report]]
|-
| style="font-size:15px;" | '''[[Misti (IGVC)]]'''
| 2013 - 2015
| Misti, Mistii
|
* '''Version 1:''' [[Media:Igvc_paper_2013.pdf | Misti Design Report]]
* '''Version 2:''' [[Media:6.pdfIGVC_Design_report_2014.pdf | Mistii Design Report]]
* '''Version 2.2:''' [[Media:IGVC_Design_report_2015.pdf | Mistii Design Report 2]]
|-
| style="font-size:15px;" | '''[[Roxi]]'''
| 2011-2012
| Roxi, Roxii
|
* '''Version 1:''' [[Media:RoxiDesignPresentation.pdf | Roxi Design Report]]
* '''Version 2:''' [[Media:RoxiiDesignReport.pdf | Roxii Design Report]]
|-
| style="font-size:15px;" | '''[[Jeanni]]'''
| 2010
| Jeani
| [[Media:JeaniDesignReport.pdf | Jeani Design Report]]
|-
| style="font-size:15px;" | '''[[Candi]]'''
| 2007 - 2009
| Candi, Candii, Candiii
|
* '''Version 1:''' [[Media:CandiDesignReport.pdf | Candi Design Report]]
* '''Version 2:''' [[]]
* '''Version 3:''' [[Media:IGVC_Design_report_2009.pdf | Candiii Design Report]]
|-
| style="font-size:15px;" | '''[[Trixxie]]'''
| 2006
| Trixxie
| [[Media:TrixxieDesignReport.pdf | Trixxie Design Report]]
|-
| style="font-size:15px;" | '''[[Buzzbot]]'''
| 2003 - 2004
| Buzzbot, Buzzbot II
|
* '''Version 1:''' [[Media:BuzzBotDesignReport.pdf | BuzzBot Design Report]]
* '''Version 2:''' [[Media:BuzzBotIIDesignReport.pdf | BuzzBot II Design Report]]
|}

====Gallery of Past Robots====

====The Year of No Robot====
In 2005, a year of transition, RoboJackets lacked the manpower to send a team to competition.

== Subteam Resources ==
=== [[IGVC Electrical]] ===
* Overview
The IGVC Electrical Team focuses on the development of a high-power motor control system with various other subsystems for other forms of robot control. Motor control is centered around an mbed LPC1768 development board who handles Proportional-Integral-Derivative (PID) and light control.

* Training info

=== Mechanical ===
* Overview
* Training info
=== Software ===
* Overview
* Training info

RoboNav

2020-06-01T02:27:21Z

Mbayyari3: Created page with "Category: RoboNav Our 2019 robot, Jessii The IGVC competition is centered around building the next generation of off-road, all-weathe..."

[[Category: RoboNav]]
[[File:Jessii.jpg|thumb|right|400px|Our 2019 robot, Jessii]]
The IGVC competition is centered around building the next generation of off-road, all-weather autonomous vehicles. The idea is to create a vehicle and tech stack that can navigate through an obstacle course to given GPS waypoints without human intervention. The map is not known beforehand, and while there are certain obstacles that are commonly used, theoretically anything can be placed onto the course. The competition is scored in three main areas. First is the design of the robot as presented in the TDP (a written report on the vehicle) that is given to industry experts for judging. Next, the team is scored based on their presentation of the robot, including a Q&A from the judges. Finally, the robot is put to the test by trying to navigate the fastest route on the AutoNav course. '''If''' multiple robots complete the course, the winner is the robot that completed it in the fastest time. Otherwise, the robot that navigates the farthest is the winner. In other words, speed is second to safety.

<noinclude>
{{countdown
|year = 2019
|month = 6
|day = 8
|hour = 13
|minute = 1
|event = IGVC Competition
|duration = 1400
|eventstart = Let's go
|eventend = Did we win?}}
</noinclude>

== Meeting Times ==
We meet in the Student Competition Center (575 14th St). If you are working in the machine shop or mechanical room you will need to wear closed-toe shoes and a t-shirt (no long sleeves). Bring a hair tie if needed.

* Wednesdays 6:30PM to 9PM
* Sundays 4PM to 7PM

== Current Leadership ==
* Project Manager: Tan Gemicioglu
* Mechanical Lead: Charles Li
* Software Lead: Matthew Hannay

== Competition ==
==== Guidelines ====
* [http://www.igvc.org/rules.htm Rules]
==== Important Dates ====
* June 5-8, 2020: 28th Annual IGVC

== Past Competitions ==

{| class = "wikitable" style = "width:95%;"
|- style="font-size:15px;" |
| style="width:20%;" | '''Bot'''
| style="width:20%;" | '''Competition Years'''
| style="width:20%;" | '''Versions'''
| style="width:40%;" | '''Design Reports'''
|-
| style="font-size:15px;" | '''[[Jessi]]'''
| 2018 - 2019
| Jessi, Jessii, Jessiii
|
* '''Version 1:''' [[Media:IGVC_Design_report_2018.pdf | Jessi Design Report]]
* '''Version 2:''' [[Media:IGVC_Design_report_2019.pdf | Jessii Design Report]]
|-
| style="font-size:15px;" | '''[[Woodi]]'''
| 2017
| See [[Jaymi]]
| Jaymi's design report was submitted for Woodi.
|-
| style="font-size:15px;" | '''[[Jaymi]]'''
| 2016
| See [[Woodi]]
| [[Media:IGVC_Design_report_2017.pdf | Jaymi Design Report]]
|-
| style="font-size:15px;" | '''[[Misti (IGVC)]]'''
| 2013 - 2015
| Misti, Mistii
|
* '''Version 1:''' [[Media:Igvc_paper_2013.pdf | Misti Design Report]]
* '''Version 2:''' [[Media:6.pdfIGVC_Design_report_2014.pdf | Mistii Design Report]]
* '''Version 2.2:''' [[Media:IGVC_Design_report_2015.pdf | Mistii Design Report 2]]
|-
| style="font-size:15px;" | '''[[Roxi]]'''
| 2011-2012
| Roxi, Roxii
|
* '''Version 1:''' [[Media:RoxiDesignPresentation.pdf | Roxi Design Report]]
* '''Version 2:''' [[Media:RoxiiDesignReport.pdf | Roxii Design Report]]
|-
| style="font-size:15px;" | '''[[Jeanni]]'''
| 2010
| Jeani
| [[Media:JeaniDesignReport.pdf | Jeani Design Report]]
|-
| style="font-size:15px;" | '''[[Candi]]'''
| 2007 - 2009
| Candi, Candii, Candiii
|
* '''Version 1:''' [[Media:CandiDesignReport.pdf | Candi Design Report]]
* '''Version 2:''' [[]]
* '''Version 3:''' [[Media:IGVC_Design_report_2009.pdf | Candiii Design Report]]
|-
| style="font-size:15px;" | '''[[Trixxie]]'''
| 2006
| Trixxie
| [[Media:TrixxieDesignReport.pdf | Trixxie Design Report]]
|-
| style="font-size:15px;" | '''[[Buzzbot]]'''
| 2003 - 2004
| Buzzbot, Buzzbot II
|
* '''Version 1:''' [[Media:BuzzBotDesignReport.pdf | BuzzBot Design Report]]
* '''Version 2:''' [[Media:BuzzBotIIDesignReport.pdf | BuzzBot II Design Report]]
|}

====Gallery of Past Robots====

====The Year of No Robot====
In 2005, a year of transition, RoboJackets lacked the manpower to send a team to competition.

== Subteam Resources ==
=== [[IGVC Electrical]] ===
* Overview
The IGVC Electrical Team focuses on the development of a high-power motor control system with various other subsystems for other forms of robot control. Motor control is centered around an mbed LPC1768 development board who handles Proportional-Integral-Derivative (PID) and light control.

* Training info

=== Mechanical ===
* Overview
* Training info
=== Software ===
* Overview
* Training info

IGVC

2020-06-01T02:26:51Z

Mbayyari3: Redirected page to RoboNav

#REDIRECT [[RoboNav]]
[[Category:IGVC]]
[[File:Jessii.jpg|thumb|right|400px|Our 2019 robot, Jessii]]
The IGVC competition is centered around building the next generation of off-road, all-weather autonomous vehicles. The idea is to create a vehicle and tech stack that can navigate through an obstacle course to given GPS waypoints without human intervention. The map is not known beforehand, and while there are certain obstacles that are commonly used, theoretically anything can be placed onto the course. The competition is scored in three main areas. First is the design of the robot as presented in the TDP (a written report on the vehicle) that is given to industry experts for judging. Next, the team is scored based on their presentation of the robot, including a Q&A from the judges. Finally, the robot is put to the test by trying to navigate the fastest route on the AutoNav course. '''If''' multiple robots complete the course, the winner is the robot that completed it in the fastest time. Otherwise, the robot that navigates the farthest is the winner. In other words, speed is second to safety.

<noinclude>
{{countdown
|year = 2019
|month = 6
|day = 8
|hour = 13
|minute = 1
|event = IGVC Competition
|duration = 1400
|eventstart = Let's go
|eventend = Did we win?}}
</noinclude>

== Meeting Times ==
We meet in the Student Competition Center (575 14th St). If you are working in the machine shop or mechanical room you will need to wear closed-toe shoes and a t-shirt (no long sleeves). Bring a hair tie if needed.

* Wednesdays 6:30PM to 9PM
* Sundays 4PM to 7PM

== Current Leadership ==
* Project Manager: Tan Gemicioglu
* Mechanical Lead: Charles Li
* Software Lead: Matthew Hannay

== Competition ==
==== Guidelines ====
* [http://www.igvc.org/rules.htm Rules]
==== Important Dates ====
* June 5-8, 2020: 28th Annual IGVC

== Past Competitions ==

{| class = "wikitable" style = "width:95%;"
|- style="font-size:15px;" |
| style="width:20%;" | '''Bot'''
| style="width:20%;" | '''Competition Years'''
| style="width:20%;" | '''Versions'''
| style="width:40%;" | '''Design Reports'''
|-
| style="font-size:15px;" | '''[[Jessi]]'''
| 2018 - 2019
| Jessi, Jessii, Jessiii
|
* '''Version 1:''' [[Media:IGVC_Design_report_2018.pdf | Jessi Design Report]]
* '''Version 2:''' [[Media:IGVC_Design_report_2019.pdf | Jessii Design Report]]
|-
| style="font-size:15px;" | '''[[Woodi]]'''
| 2017
| See [[Jaymi]]
| Jaymi's design report was submitted for Woodi.
|-
| style="font-size:15px;" | '''[[Jaymi]]'''
| 2016
| See [[Woodi]]
| [[Media:IGVC_Design_report_2017.pdf | Jaymi Design Report]]
|-
| style="font-size:15px;" | '''[[Misti (IGVC)]]'''
| 2013 - 2015
| Misti, Mistii
|
* '''Version 1:''' [[Media:Igvc_paper_2013.pdf | Misti Design Report]]
* '''Version 2:''' [[Media:6.pdfIGVC_Design_report_2014.pdf | Mistii Design Report]]
* '''Version 2.2:''' [[Media:IGVC_Design_report_2015.pdf | Mistii Design Report 2]]
|-
| style="font-size:15px;" | '''[[Roxi]]'''
| 2011-2012
| Roxi, Roxii
|
* '''Version 1:''' [[Media:RoxiDesignPresentation.pdf | Roxi Design Report]]
* '''Version 2:''' [[Media:RoxiiDesignReport.pdf | Roxii Design Report]]
|-
| style="font-size:15px;" | '''[[Jeanni]]'''
| 2010
| Jeani
| [[Media:JeaniDesignReport.pdf | Jeani Design Report]]
|-
| style="font-size:15px;" | '''[[Candi]]'''
| 2007 - 2009
| Candi, Candii, Candiii
|
* '''Version 1:''' [[Media:CandiDesignReport.pdf | Candi Design Report]]
* '''Version 2:''' [[]]
* '''Version 3:''' [[Media:IGVC_Design_report_2009.pdf | Candiii Design Report]]
|-
| style="font-size:15px;" | '''[[Trixxie]]'''
| 2006
| Trixxie
| [[Media:TrixxieDesignReport.pdf | Trixxie Design Report]]
|-
| style="font-size:15px;" | '''[[Buzzbot]]'''
| 2003 - 2004
| Buzzbot, Buzzbot II
|
* '''Version 1:''' [[Media:BuzzBotDesignReport.pdf | BuzzBot Design Report]]
* '''Version 2:''' [[Media:BuzzBotIIDesignReport.pdf | BuzzBot II Design Report]]
|}

====Gallery of Past Robots====

====The Year of No Robot====
In 2005, a year of transition, RoboJackets lacked the manpower to send a team to competition.

== Subteam Resources ==
=== [[IGVC Electrical]] ===
* Overview
The IGVC Electrical Team focuses on the development of a high-power motor control system with various other subsystems for other forms of robot control. Motor control is centered around an mbed LPC1768 development board who handles Proportional-Integral-Derivative (PID) and light control.

* Training info

=== Mechanical ===
* Overview
* Training info
=== Software ===
* Overview
* Training info

How to Set Shaded With Edges as Default

2020-05-30T05:27:24Z

Mbayyari3:

If you've ever been in a BattleBots design review, the one thing they all have in common is "Can you turn on shaded with edges?" This is a useful setting that differentiates parts in an assembly through the use of bold lines. Here you'll learn to set it as a defualt viewing mode for your Inventor application. This means that no matter what assembly/part you open you will be viewing it as Shaded with Edges.

*From within the Inventor application, navigate to the 'Tools' tab
**Under the 'Options' category, you will see a button labeled 'Application Settings'
**Click that
*That opens an options dialogue. Choose the 'Display' tab
**Under the 'Appearance' heading, click the 'Settings...' button
*This opens another dialogue with the title 'Display Appearance'
**Under 'Initial Display Appearance', there is a drop-down labeled 'Visual Style'
**Expand that drop-down and select 'Shaded with Edges'
*Click 'Ok' or 'Apply' on each of the dialogues to ensure your settings save
**You may get an error message along the lines of "Inventor is currently configured to use appearance settings stored in document settings..." which is alright.
**Choose 'Ok' and to the left of 'Settings...' there are two radio buttons to choose between 'Use document settings' and 'Use application settings'
**Select 'Use application settings.' Now your inventor will ignore all those inferior drawing styles and always shade with edges!

[[Category: How to Guides: Technical]]

Volunteering Opportunities

2020-05-30T05:23:15Z

Mbayyari3:

== FIRST Events ==

=== Competitions ===

==== AV camera operator ====
You will spend the weekend sitting field side operating one of the three PTZ cameras to give amazing footage of the on going match while the switcher is controlling which camera is shown live. Everyone enjoys this job.

[[Category: Outreach]]

List of 3lb Robots

2020-05-30T05:22:25Z

Mbayyari3:

= Drum Spinners =

==== 2019-2020 ====
*[[Barbi]]

==== 2018-2019 ====
*[[Crispi]]
*[[Entropi]]
*[[Furi]]
*[[Groovi]]

==== 2017-2018 ====
*[[I]]

==== 2016-2017 ====
*[[Snuti]]
*[[Radii]]

==== 2015-2016 ====
*[[Emmii]]
*[[Misti]]

==== 2014-2015 ====
*[[Emmi]]

= Horizontal Bar Spinners =

==== 2019-2020 ====
*[[Hibachi]]
*[[Perri]]

==== 2018-2019 ====
*[[Dadi]]

==== 2017-2018 ====
*[[Chewi]]
*[[Loki]]

==== 2015-2016 ====
* None :(

==== 2014-2015 ====
*[[Vicki]]

= Vertical Bar Spinners =

==== 2019-2020 ====
*[[Huski]]
*[[Spooki]]

==== 2018-2019 ====
*[[Doori]]
*[[(un)Lucki]]

==== 2017-2018 ====
*[[Esci]]
*[[Grizzli]]

==== 2016-2017 ====
*[[Dat_Boi]]

= Ring/Shell Spinners =

==== 2019-2020 ====
*[[Sauci]]
*[[Spinni-Boi]]

==== 2018-2019 ====
*[[WakiSmaki]]

==== 2017-2018 ====
*[[Personal Injuri]]

==== 2016-2017 ====
*[[Qti]]

==== 2015-2016 ====
*[[Sandi]]
*[[Shelli]]

==== 2014-2015 ====
*[[Smitti Werbenjagermanjensen]]

= Miscellaneous Bots =

==== 2017-2018 ====
*[https://hkim702.blogspot.com/2018/02/dynastinai.html Dynastinai]

==== 2014-2015 ====
*[[Group 5]]
*[[Flippi/MrWedge]]

= Graveyard of Bots with no Documentation =

==== 2016-2017 ====
*Schwifti
*Standi

==== 2015-2016 ====
*Ami
*Ghoti
*Flipboi

[[Category: BeetleWeights]]

List of 3lb Robots

2020-05-30T05:21:19Z

Mbayyari3:

Accessing Cloud from macOS

2020-05-30T05:20:17Z

Mbayyari3:

The URL provided in the Nextcloud interface does not work in any of the clients tested. You will need to use https://cloud.robojackets.org/remote.php/dav/files/gburdell3/ instead, replacing gburdell3 with your GT username.

As with other uses of the WebDAV interface, you will need to generate an app password to log in, as Nextcloud does not know your GT password.

Information taken from https://docs.nextcloud.com/server/13/user_manual/files/access_webdav.html.
[[Category:How to Guides: Technical]]

Google Groups Join Links

2020-05-30T05:20:04Z

Mbayyari3:

These links will give anyone with a Google account Contributor access to a variety of RoboJackets Shared Drives.

If you have trouble joining one of these groups, message [https://robojackets.slack.com/messages/C29Q3D8K0 #it-helpdesk] in Slack.

'''Teams'''

Link your Google account to MyRoboJackets [https://my.robojackets.org/google here], then make sure you're in the correct teams on the [https://my.robojackets.org/teams teams page]. You will automatically be added to the shared drives for those teams.

'''Discipline Cores'''

Follow the steps under Teams above and join the team for the relevant training. That will automatically add you to the shared drive for the discipline core.

'''Trainings'''

Follow the steps under Teams above.

[[Category:How to Guides: Administrative]]

Accessing Cloud from macOS

2020-05-30T05:19:45Z

Mbayyari3:

About ClickUp

2020-05-30T05:19:35Z

Mbayyari3:

Website: https://clickup.com/

Support: https://docs.clickup.com/

== How to Get Access ==
Access to ClickUp requires an invitation from a service administrator. If you need access, ask for an invitation in the [https://robojackets.slack.com/messages/C29Q3D8K0 #it-helpdesk] Slack channel.
[[Category:How to Guides: Administrative]]

Electronics Basics

2020-05-30T05:18:33Z

Mbayyari3:

[[Category: Electrical]]
== Overview ==
Electronics are an important consideration of all Combat bots. Robots without strong electronics can suffer from shorts and over-voltage, which can ruin components and disable the robot. Creating a strong electrical system is crucial to increasing the durability and maximizing the damage output of the robot. Additionally, compact electronics allow the designer to decrease the size and footprint of the robot, making it a harder target and allowing more weight to be distributed to the armor and weapons.This guide will offer a detailed explanation of the components used in a combat robot's electronics and describe how to assemble the components into a strong and small circuit.

== 3lb Circuit ==
[[File:3lbCircuit.png|right|thumb|300px|Standard 3lb Circuit]]
The standard 3lb electrical layout consists of a 1000 mAh 11.1 V battery connected to a mechanical switch, which powers 2 drive ESCs and a Weapon ESC.
The ESCs are each connected to a receiver and send power to the motors in 3 phases.

'''Parts List'''

{| class="wikitable"
|-
! scope="col"| Component
! scope="col"| Size
! scope="col"| Weight
|-
! scope="row"| DYS BE1806 2300KV ('''Drive Motor''')
| 0.91x0.91x0.83in
| 0.053 lbs
|-
! scope="row"| DYS BL20A Mini 20A BLHeli ESC OPTO ('''Drive ESC''')
| 0.91x0.47x0.18in
| 0.017 lbs
|-
! scope="row"| HobbyKing 2.4Ghz 6Ch V2 ('''Receiver''')
| 1.75x0.53x0.88in
| 0.029 lbs
|-
! scope="row"| Turnigy nano-tech 1000mah 3S 45~90C Lipo Pack ('''Battery''')
| 2.80x1.38x0.75in
| 0.21 lbs
|-
|}

== Motors ==
=== Overview ===
Motors consist of a rotor (rotating part) and a stator (stationary part). The rotor is made up of an armature that drives the load which is surrounded by magnets and supported by a bearing to reduce friction. The stator is made up of a core surrounded by coils of wire connected to a power source that is used to drive the motor. The stator has a core made up of laminated sheets of metal to reduce energy losses. A commutator is also included in brushed motors to flip the magnetic field as the motor spins.
[[File:Outrunner.jpeg|right|thumb|200px|Brushless Motor]]
[[File:MotorBrushed.png|right|thumb|200px|Brushed Motor]]
===Brushed vs Brushless ===

Brushed motors operate by sending current through coils of wire to induce a magnetic field and cause the motor’s permanent magnets to turn. Once the magnets have spun 180°, the current is reversed using a communicator, and the magnets continue to spin another 180° and the process repeats. Brushed motors are more durable than brushless motors, but suffer from less control and slower speeds than brushless motors.

Brushless motors operate using three phase AC current generated by a switching power source or an ESC. The 3 phases of the current are 120 defrees out of phase, meaning that when one line has no current, the other lines have a current at plus and minus cos(120°). These wires are connected in loops around the motor in alternating phases so that at any moment, one wire is pushing the motor forward, one is pulling the motor forward, and the last has no current.
Brushless motor’s have a higher power to weight ratio and higher speed than brushed motors. Battlebots uses brushless motors for its robots due to the control and speeds that they posses. Note that the direction of the motor can be reversed by switching any 2 of the wires.

=== Inrunner vs Outrunner ===
[[File:InvsOut.png|right|thumb|200px|An example of Inrunner vs Outrunner Motors]]
Inrunner motors have the permanent magnet rotor inside a ring of electromagnets with the armature connected directly to the rotor. Inrunner motor’s have high rpm and are more efficient than outrunners, but have less torque and weigh more.

Outrunner motor’s have the permanent magnet rotor outside a core of electromagnets with the armature connected to a plate on the back of the rotor. Outrunner motors provide more torque than inrunners, but suffer from less rpm and a spinning body that can be constricted by wires.

=== Choosing a Motor ===
When choosing a motor there are several parameters that need to be considered to make an informed decision. These values will affect the speed and power output by the motor and will affect how hard your weapon hits, how long it takes to spin up, and could change how your robot drives. These are the constants you should be familiar with when you look for a motor.

'''Kv:''' How fast the motor spins per Volt supplied to it. A 1000 Kv motor will spin at 1110 rpm when supplied with 11.1 V. Note this is the unloaded speed and will be lower when your weapon is attached. Kv is inversely related to torque, which relates

'''Weight:''' Weight is an important consideration when choosing a motor. You may be tempted to choose the fastest and most powerful motor for your robot, however larger motors will quickly burn through your available weight and require you to use bigger and heavier ESCs.

'''Max Current:''' The max current will determine the ESC that you need to control the motor. Your ESC should be at least as large as the max current the motor can draw. Typically motors with a max current of 40 A or less are used to keep the ESC small and light. The size of the ESC tends to increase significantly at 50 A.

== ESCs ==
[[File:ESC.jpg|right|thumb|300px|An ESC with the shrink wrap removed.]]
=== Overview ===
An ESC (Electronic Speed Control) receives a control signal from the receiver that dictates how much power to output to the motor. It then generates a signal of the proper power and sends it to the motor. For brushless motors the ESC will generate a three phase AC signal, and for brushed motors the ESC will generate a constant signal. [http://www.hooked-on-rc-airplanes.com/brushed-vs-brushless-esc.html| Click here] to learn more about the difference between brushed and brushless ESCs. The ESCs adjust the phase of the output based on the motor rotation, which it measures using the back emf response from the motor. This allows the user to spin the motor at different speeds to control the speed and direction of the robot
=== Choosing an ESC ===
ESCs are chosen based on the max current they will experience. Generally the ESC’s rated current should be higher than the motor’s rated current. For example a 30A motor will generally require a 40 A ESC to prevent overvoltage. The ESCs will also need a Battery Eliminator Circuit (BEC) to step down the voltage sent to the receiver. The presence of a BEC will be listed in the ESC’s product specifications.
=== Flashing ESC Firmware ===
Often times ESCs come with firmware that differs from what is needed. The most common way this presents itself is that the motor has no reverse drive. To fix this, you have to flash new firmware onto the ESC. To do this, you'll need an Afro ESC USB Linker and a program called RapidFlash. First plug the white and black cable that typically is attached to the receiver into the Afro ESC USB Linker, being careful to line up the signal pin to the white wire, and the "-" pin to the black wire. Once you have that set up, plus the USB into your computer, power your ESC (either using a DC Power Supply or a battery), and launch RapidFlash. You'll need to set the port (there should only be one option on the drop down), the programmer (Afro ESC USB Linker), the release (using master is fine), and finally you'll need to select the firmware. To determine what firmware to use, consult [https://docs.google.com/spreadsheets/d/13tMlu5ldLNpZXwbe6UhDHJhcgTVuljm8HDiDp9WO9Pk/edit#gid=0 this sheet] to see what firmware is recommended for your ESC. Next you'll need to select which features you'll want to flash under the advanced tab. Uncheck "RC_CALIBRATION" because our motors do not calibrate. "RC_PULS_REVERSE" and "BEACON" are recommend. Finally, press "Flash Firmware" and wait until the terminal says that the serial terminal connection has been terminated.

== Batteries ==
[[File:LipoBattery.jpg|right|thumb|200px|Lithium Polymer battery typically used by 3lb robots.]]
[[File:Puffed-lipo.jpg|right|thumb|200px|An example of a swollen LiPo. The battery on the right should not be used or charged.]]
Battlebots uses Lithium Polymer batteries to power our electronics. Lithium polymer batteries are compact rechargeable batteries made using a polymer electrolyte to reduce weight. LiPo batteries have high energy density and low weight, making them perfect for applications with weight restrictions. When selecting a battery, it is important to consider the voltage and capacity. The voltage is the level necessary to power the circuit and must be calculated using the power consumption of the components. The capacity will tell you how long the battery will run and is measured in milliamp hours. The 3lb robots use a 11.1V 1000mAh 3-cell battery which has enough charge to power the robots for their three minute matches.

'''Safety:'''
LiPo batteries can be very dangerous if mishandled or punctured, therefore you should be careful when handling charged or charging batteries. Also remember that a battle bot with a battery plugged in should be treated as powered on with a live weapon. Below are some guidelines on how to safely handle and use LiPo batteries.

'''1. Never use a damaged battery.''' If you believe that your battery is damaged, bury it in a bucket of sand. The sand bucket at the SCC is the metal bucket outside the office. At competition, the officials will tell you where the bucket is at the drivers meeting. A damaged battery will puff up and/or keep heating heat up after unplugged. '''''If a battery is visibly expanding, there is an extreme risk of exploding and it should be buried in sand ASAP.'''''

'''2. Use the balancing board when charging.''' If the voltage of the cells in the battery become unbalanced, it could become unstable and explode.

'''3. Store batteries in a fireproof bag.''' Overcharged or damaged batteries can spontaneously catch fire, and should be stored properly to be safe.

'''4. Never overcharge or use an overcharged a battery.''' Our chargers should automatically stop when the battery is full, but the voltage should never exceed 4.2 V per cell.

'''5. Store batteries at room temperature.''' Hot temperatures can melt the battery and cold temperatures may result in condensation inside the battery, which can result in shorts and fires.

'''6. Never use an undercharged battery.''' Batteries last around 300 charges, throw out the battery when the voltage is below 3 V per cell.
== Receiver ==
===Overview===
[[File:Receiver.png|right|thumb|200px|The receiver used by 3lb teams with the binding ring included.]]
The controllers that you will use contain a transmitter which broadcasts a control signal to the receiver on the robot. The receiver decodes the signal and transmits instructions through different channels that connect to each component in the circuit. These signals tell the ESCs how much power to route to each motor which allows the user to control the robot from a distance.

The receivers that Battlebots uses have six channels, but we only use three of them to control the robot. The first channel is connected to the weapon ESC which controls how fast the weapon spins. The control stick connected to this channel has a fixed position, which is useful for keeping a constant power to the motor. The next two channels connect to each drive ESC and are used to maneuver the robot. The drive stick uses the vertical position of the stick to control the power sent to both motors and the horizontal position to send more power to one motor when executing a turn. The final channel that is present in all newer receivers is the binding channel. This channel is used to bind the transmitter in the controller directly to the receiver int the robot. This step only needs to be completed once and lasts until the receiver is re-bound to a different transmitter. Note that when binding the receiver, the trim of the controller might need to be adjusted for the receiver to detect all channels. Trim are sliders that finely tune how much power is transmitted when the stick is pushed a specific amount. These will need to be adjusted if the robot lists to one side when driven forward.

===How to Bind===
{| class="wikitable floatright"
|+ Channel List
|-
! scope="col"| Channel
! scope="col"| Motor
|-
! scope="row"| 1
| Left Drive Motor
|-
! scope="row"| 2
| Right Drive Motor
|-
! scope="row"| 3
| Weapon Motor
|-
|}
Below is a step by step guide on how to bind your receiver to the transmitter on your controller.

1. Plug the binding clip into the BAT slot on the receiver.

2. Connect the receiver to a powered ESC in any slot. Make sure the metal prongs are facing the top of the receiver when you plug it in.

3. While holding the pair button on the controller, switch it on. You should see a solid light on the receiver.

4. Turn off the controller and remove the binding clip. The receiver is now paired with the controller.

== Manufacturing ==
=== Wire Selection ===
[[File:AmpacityChart.png|right|frameless|300px]]
When wiring your circuit together, you need to choose wires with a large enough diameter that they can conduct the current flowing through them without melting. However you also want wires that are thin enough to fit into the empty space inside your robot. Wires are graded by their gauge or thickness, with larger diameter correlating with a smaller gauge. To find the minimum gauge wires needed to effectively power the components, you can consult an ampacity chart. The ampacity of the wires should exceed the maximum rating of your ESCs.

=== Soldering ===
'''In general, the purpose of soldering is to heat the wire/connector up enough to melt the solder, rather than melting the solder onto the cool material, which ensures a solid continuous connection between the solder and the material it is attached to.'''
==== Setup ====
[[File:Desolder.jpg|thumb|border|200px|Desolder wick sucking solder from a circuit board.]]
When you are ready to begin soldering components together, first plug in the soldering iron's power supply and turn it on with the iron in its housing. Be careful, always treat a soldering iron as hot when it is plugged in and keep the iron in its holder when not in use. Keep the iron away from power wires and flammable materials. Begin by melting some solder onto the tip, which helps the heat transfer from the tip. This is called tinning and it should be done if the iron has not been used in several minutes. Clean the iron occasionally by rolling the tip in the brass shavings to deposit any solder, then a wet sponge to clean the tip. Once you have finished soldering, tin the iron before cooling to protect the tip.

Try to use lead-free solder, or wash your hands after handling solder. Use a fume extractor if possible or work in a well ventilated area as the fumes can be irritating. It is helpful to use solder that has 2-3% rosin flux, which is an acid that cleans the surface of the wires and forms a stronger bond.

If you put too much solder on a joint, take some desolder wick, put it on the joint, and press the iron to it to draw the excess solder up the wick.

==== Wire Splicing ====
When it is necessary to connect two wires without connectors, it is important to mechanically connect the wires to form a bond that is as strong as possible, rather than just globing solder on them. A short step by step procedure with images can be found [https://www.instructables.com/id/Soldering-wires-together/| here]. To summarize, twist each wire in your fingers to braid the filaments and melt some solder onto them. Then, wrap the tip of one wire several times around the base of the other. Wrap the remaining wire's tip around the base of the first, then apply the iron to the splice to form a strong electrical connection.

==== Bullet Connectors ====
[[File:BulletSolder.jpg|right|thumb|300px|A step by step guide on how to solder on bullet connectors]]
Bullet connectors are used to attach components that may need to be replaced quickly, such as motors or ESCs. To solder a wire to a bullet, clamp a bullet into some helping hands/pliers and press the iron to the outside of the bullet for several seconds to heat up the metal. Apply solder inside the connector and build up a pool of melted solder. Place a stripped wire inside the pool and remove the iron to allow the solder to cool around the wire. When applying heat shrink, make sure it covers the entire female bullet and the thick portion of the male bullet. Keep your male/female bullets consistent between replacements so you don't have to re-solder all of the bullets.

==== Crimps ====
[[File:HeatShrink.jpg|thumb|border|200px|A terminal crimp with heat shrink applied]]
There are two types of crimps used in electronics. Wire crimps are used to attach two wires together securely with two female ends. Terminal crimps are used to connect wires to terminal blocks, or to each other, to easily make parallel connections. Terminal crimps have one female end that receives the wire, and a loop that can be screwed to a terminal. Make sure that you use the proper size crimp for the wire you are connecting. To attach a crimp, strip a quarter inch of insulation off the wire. For a stronger connection, apply some solder to the wire before inserting it into the crimp. Then use the crimping tool to compress the middle of the crimp around the wire. You may want to rotate the crimp 90 degrees and crimp it again to compress the wire on four sides. Be careful not to overcrimp the connector to prevent damaging the insulation. Once the wire is crimped, you can use a screw to attach several crimps together and a nut to secure them together. For larger bots, a larger terminal block can be used to screw several wires in an organized parallel connection. [https://www.youtube.com/watch?v=i5LBf19MqPk| Here] is a video showing proper procedure for crimping wires together.

=== Insulation ===
Once you've soldered your components to their respective wires, you will need to insulate them to prevent the exposed connections from grounding to your robot's chassis. Generally this is done by wrapping the component in heat shrink. Heat shrink is a material that, as the name suggests, shrinks as heat is applied to it. Simply thread a pre-cut piece around the component, then use a heat gun to shrink it until it is wrapped firmly around the part. Additionally, if heat shrink is unavailable or time is of the essence, you may simply wrap electrical tape around the joint to protect it. For extra insulation, it is recommended that you coat your metal plates in an an insulating substance, like spray paint, to further prevent your electronics from grounding to the chassis.

[[File:Bullet.jpg|frameless|right|200px]][[File:Connector.jpg||frameless|left|200px]][[File:SolderingIron.jpg|frameless|center|200px]]

Bigoli

2020-05-26T01:47:52Z

Mbayyari3: /* Sparkfun AVC 2017 */

Bigoli was a RoboRacing competitive bot that competed through the 2016-2018 academic years in the Sparkfun Autonomous Vehicle Competiton (AVC) before the competition's retirement in 2019. The competition tested the robot's ability to carry a human passenger while autonomously navigating a course. The emphasis was on relatively smooth controls, enforced with the human passenger having to carry a water cup and shoot a foam dart gun at targets during the competition.

For more information on the competition, visit the official [https://avc.sparkfun.com/ website].

==Competitions==
===Sparkfun AVC 2018===
Bigolii placed 1st in the Speed Demons competition.
* [https://info.sparkfun.com/hubfs/Events/AVC/2018/AVC%20Speed%20Demon%20Rules%202018.pdf 2018 Competition Rules]
====Bigolii====

===Sparkfun AVC 2017===
Bigoli placed 1st in the Car Wars competition.
*[https://cdn.sparkfun.com/assets/7/b/b/1/e/Autonomous-Car-Wars-2017-Rules.pdf 2017 Competition Rules]
====Bigoli====
Bigoli was powered by two 12V batteries, running at a total of 24V. The drive motor used was designed for a scooter, with a custom-designed gearbox attached. The motor is controlled by the Open Source Motor Controller (OSMC). The steering motor was CIM motor controlled by the Talon SRX with position monitored by a potentiometer. A custom control PCB was created using the mbed LPC1768 as the base to actuate the steering and drive. The safety system is implemented using a solenoid contractor system that cuts power to both motors utilizing onboard safety pushbuttons or the wireless remote. An Intel NUC provides high-level computation utilizing a SICK Lidar and multiple cameras for object avoidance, detection, and planning.

==Photo Gallery==

<gallery mode='packed-hover'>

Image: Bigoli img 1.jpg| Joe and Bigoli at Sparkfun AVC
Image: Bigoli img 2.jpg| Bigoli before competiton
Image: Bigoli img 3.jpg| Buzz and Bigoli

</gallery>
[[Category: RoboRacing]]

Bigoli

2020-05-26T01:47:41Z

Mbayyari3: /* Sparkfun AVC 2018 */

Bigoli was a RoboRacing competitive bot that competed through the 2016-2018 academic years in the Sparkfun Autonomous Vehicle Competiton (AVC) before the competition's retirement in 2019. The competition tested the robot's ability to carry a human passenger while autonomously navigating a course. The emphasis was on relatively smooth controls, enforced with the human passenger having to carry a water cup and shoot a foam dart gun at targets during the competition.

For more information on the competition, visit the official [https://avc.sparkfun.com/ website].

==Competitions==
===Sparkfun AVC 2018===
Bigolii placed 1st in the Speed Demons competition.
* [https://info.sparkfun.com/hubfs/Events/AVC/2018/AVC%20Speed%20Demon%20Rules%202018.pdf 2018 Competition Rules]
====Bigolii====

===Sparkfun AVC 2017===
Bigoli placed 1st in the Car Wars competition.
*[https://cdn.sparkfun.com/assets/7/b/b/1/e/Autonomous-Car-Wars-2017-Rules.pdf Competition Rules]
====Bigoli====
Bigoli was powered by two 12V batteries, running at a total of 24V. The drive motor used was designed for a scooter, with a custom-designed gearbox attached. The motor is controlled by the Open Source Motor Controller (OSMC). The steering motor was CIM motor controlled by the Talon SRX with position monitored by a potentiometer. A custom control PCB was created using the mbed LPC1768 as the base to actuate the steering and drive. The safety system is implemented using a solenoid contractor system that cuts power to both motors utilizing onboard safety pushbuttons or the wireless remote. An Intel NUC provides high-level computation utilizing a SICK Lidar and multiple cameras for object avoidance, detection, and planning.

==Photo Gallery==

<gallery mode='packed-hover'>

Image: Bigoli img 1.jpg| Joe and Bigoli at Sparkfun AVC
Image: Bigoli img 2.jpg| Bigoli before competiton
Image: Bigoli img 3.jpg| Buzz and Bigoli

</gallery>
[[Category: RoboRacing]]

Bigoli

2020-05-26T00:08:29Z

Mbayyari3: /* Bigoli */

Bigoli was a RoboRacing competitive bot that competed through the 2016-2018 academic years in the Sparkfun Autonomous Vehicle Competiton (AVC) before the competition's retirement in 2019. The competition tested the robot's ability to carry a human passenger while autonomously navigating a course. The emphasis was on relatively smooth controls, enforced with the human passenger having to carry a water cup and shoot a foam dart gun at targets during the competition.

For more information on the competition, visit the official [https://avc.sparkfun.com/ website].

==Competitions==
===Sparkfun AVC 2018===
Bigolii placed 1st in the Speed Demons competition.
* [https://info.sparkfun.com/hubfs/Events/AVC/2018/AVC%20Speed%20Demon%20Rules%202018.pdf Competition Rules]
====Bigolii====

===Sparkfun AVC 2017===
Bigoli placed 1st in the Car Wars competition.
*[https://cdn.sparkfun.com/assets/7/b/b/1/e/Autonomous-Car-Wars-2017-Rules.pdf Competition Rules]
====Bigoli====
Bigoli was powered by two 12V batteries, running at a total of 24V. The drive motor used was designed for a scooter, with a custom-designed gearbox attached. The motor is controlled by the Open Source Motor Controller (OSMC). The steering motor was CIM motor controlled by the Talon SRX with position monitored by a potentiometer. A custom control PCB was created using the mbed LPC1768 as the base to actuate the steering and drive. The safety system is implemented using a solenoid contractor system that cuts power to both motors utilizing onboard safety pushbuttons or the wireless remote. An Intel NUC provides high-level computation utilizing a SICK Lidar and multiple cameras for object avoidance, detection, and planning.

==Photo Gallery==

<gallery mode='packed-hover'>

Image: Bigoli img 1.jpg| Joe and Bigoli at Sparkfun AVC
Image: Bigoli img 2.jpg| Bigoli before competiton
Image: Bigoli img 3.jpg| Buzz and Bigoli

</gallery>
[[Category: RoboRacing]]

Bigoli

2020-05-26T00:08:02Z

Mbayyari3: /* Sparkfun AVC 2018 */

Bigoli was a RoboRacing competitive bot that competed through the 2016-2018 academic years in the Sparkfun Autonomous Vehicle Competiton (AVC) before the competition's retirement in 2019. The competition tested the robot's ability to carry a human passenger while autonomously navigating a course. The emphasis was on relatively smooth controls, enforced with the human passenger having to carry a water cup and shoot a foam dart gun at targets during the competition.

For more information on the competition, visit the official [https://avc.sparkfun.com/ website].

==Competitions==
===Sparkfun AVC 2018===
Bigolii placed 1st in the Speed Demons competition.
* [https://info.sparkfun.com/hubfs/Events/AVC/2018/AVC%20Speed%20Demon%20Rules%202018.pdf Competition Rules]
====Bigolii====

===Sparkfun AVC 2017===
Bigoli placed 1st in the Car Wars competition.
*[https://cdn.sparkfun.com/assets/7/b/b/1/e/Autonomous-Car-Wars-2017-Rules.pdf Competition Rules]
====Bigoli====
Bigoli is powered by two 12V batteries, running at a total of 24V. The drive motor used is designed for a scooter, with a custom-designed gearbox attached. The motor is controlled by the Open Source Motor Controller (OSMC). The steering motor was CIM motor controlled by the Talon SRX with position monitored by a potentiometer. A custom control PCB was created using the mbed LPC1768 as the base to actuate the steering and drive. The safety system is implemented using a solenoid contractor system that cuts power to both motors utilizing onboard safety pushbuttons or the wireless remote. An Intel NUC provides high-level computation utilizing a SICK Lidar and multiple cameras for object avoidance, detection, and planning.

==Photo Gallery==

<gallery mode='packed-hover'>

Image: Bigoli img 1.jpg| Joe and Bigoli at Sparkfun AVC
Image: Bigoli img 2.jpg| Bigoli before competiton
Image: Bigoli img 3.jpg| Buzz and Bigoli

</gallery>
[[Category: RoboRacing]]

Bigoli

2020-05-26T00:05:16Z

Mbayyari3:

Bigoli was a RoboRacing competitive bot that competed through the 2016-2018 academic years in the Sparkfun Autonomous Vehicle Competiton (AVC) before the competition's retirement in 2019. The competition tested the robot's ability to carry a human passenger while autonomously navigating a course. The emphasis was on relatively smooth controls, enforced with the human passenger having to carry a water cup and shoot a foam dart gun at targets during the competition.

For more information on the competition, visit the official [https://avc.sparkfun.com/ website].

==Competitions==
===Sparkfun AVC 2018===
====Bigolii====

===Sparkfun AVC 2017===
Bigoli placed 1st in the Car Wars competition.
*[https://cdn.sparkfun.com/assets/7/b/b/1/e/Autonomous-Car-Wars-2017-Rules.pdf Competition Rules]
====Bigoli====
Bigoli is powered by two 12V batteries, running at a total of 24V. The drive motor used is designed for a scooter, with a custom-designed gearbox attached. The motor is controlled by the Open Source Motor Controller (OSMC). The steering motor was CIM motor controlled by the Talon SRX with position monitored by a potentiometer. A custom control PCB was created using the mbed LPC1768 as the base to actuate the steering and drive. The safety system is implemented using a solenoid contractor system that cuts power to both motors utilizing onboard safety pushbuttons or the wireless remote. An Intel NUC provides high-level computation utilizing a SICK Lidar and multiple cameras for object avoidance, detection, and planning.

==Photo Gallery==

<gallery mode='packed-hover'>

Image: Bigoli img 1.jpg| Joe and Bigoli at Sparkfun AVC
Image: Bigoli img 2.jpg| Bigoli before competiton
Image: Bigoli img 3.jpg| Buzz and Bigoli

</gallery>
[[Category: RoboRacing]]

Bigoli

2020-05-25T23:44:40Z

Mbayyari3: /* Photo Gallery */

==Competitions==
===Sparkfun AVC 2018===
====Bigolii====

===Sparkfun AVC 2017===
====Bigoli====

==Photo Gallery==

<gallery mode='packed-hover'>

Image: Bigoli img 1.jpg| Joe and Bigoli at Sparkfun AVC
Image: Bigoli img 2.jpg| Bigoli before competiton
Image: Bigoli img 3.jpg| Buzz and Bigoli

</gallery>
[[Category: RoboRacing]]

File:Bigoli img 1.jpg

2020-05-25T23:40:12Z

Mbayyari3:

File:Bigoli img 2.jpg

2020-05-25T23:39:46Z

Mbayyari3:

File:Bigoli img 3.jpg

2020-05-25T23:39:22Z

Mbayyari3:

Bigoli

2020-05-25T23:37:43Z

Mbayyari3: /* Sparkfun AVC 2017 */

==Competitions==
===Sparkfun AVC 2018===
====Bigolii====

===Sparkfun AVC 2017===
====Bigoli====

==Photo Gallery==

Bigoli

2020-05-25T23:37:31Z

Mbayyari3: /* Sparkfun AVC 2018 */

==Competitions==
===Sparkfun AVC 2018===
====Bigolii====

===Sparkfun AVC 2017===

==Photo Gallery==

Bigoli

2020-05-25T23:36:54Z

Mbayyari3:

==Competitions==
===Sparkfun AVC 2018===
===Sparkfun AVC 2017===

==Photo Gallery==

Bigoli

2020-05-25T23:36:28Z

Mbayyari3: /* Versions */

==Competitions==
===Sparkfun AVC 2018===
===Sparkfun AVC 2017===

==Versions==
===Bigoli===
===Bigolii===

==Photo Gallery==

Bigoli

2020-05-25T23:36:04Z

Mbayyari3: /* Competitions */

==Competitions==
===Sparkfun AVC 2018===
===Sparkfun AVC 2017===

==Versions==
==Photo Gallery==