RoboJackets Wiki - User contributions [en]

Laptop/CAN Interface

2018-06-14T03:01:27Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2005-2006]]
The Laptop/CAN Interface sits at the head of the CAN bus and has a CAN address of 1, giving it highest device priority next to the [[E-Stop]].

==Parts==

Part numbers listed are those of the Digi Key Corporation parts database.

===Processor===

*[[IGVC Laptop]]

===CAN Specific===

*[http://www.microchip.com/stellent/idcplgidcplg?IdcService=SS_GET_PAGE&nodeId=1335&dDocName=en010406 MCP2515] - U2 - Microchip CAN Controller with [http://en.wikipedia.org/wiki/Serial_Peripheral_Interface SPI] Interface
*[http://www.microchip.com/stellent/idcplgidcplg?IdcService=SS_GET_PAGE&nodeId=1335&dDocName=en010405 MCP2551] - U1 - Microchip CAN TransponderP966-ND
*770-61-R10K-ND - RN1 - 10k ohm Resistor Network, 5 of 6 pins are used

===Onboard Power Control===

*[http://www.national.com/pf/LM/LM78M05.html UA78M05DCY] - U4 - 5V Linear Regulator
*[http://www.onsemi.com/PowerSolutions/product.do?id=1N4004 1N4004GICT-ND] - D1 - Diode
*P966-ND - C1,C2 - 10 microfarad Capacitor
*399-2127-ND - C3,C4 - 0.1 microfarad Capacitor

===Oscillator===

*300-7022-1-ND - U3 - 11.0592 MHZ Clock Siqnal Oscillator

===Headers===

*A19423-ND - J1 - Power 2-pin header
*A19430-ND - J2 - CAN 3-pin header
*A19434-ND - J3 - Connect laptop to interface 7-pin header

===Misc.===

*377-1090-ND - Box to contain the module
*1892K-ND - Standoffs

==Electrical==

[[Image:LaptopCAN Schematic.png]]
[[Image:LaptopCAN Board.png]]

==Code==

See [[IGVC Laptop]] for information on code that talks with this interface.

KlausDirections

2018-06-14T03:00:27Z

Ndaugherty6:

[[Category:Outreach]]
Directions to Parking Lot W21
==If you are driving North on 75/85==
# Take I-85 North to Exit #250 (10th Street/14th Street/Ga Tech).
# Take a left on 10th Street at the light at the end of the ramp.
# Take a left on Fowler Street (first light after crossing the interstate).
# Take a right on Ferst Drive.
# Take a left into Parking Lot W21 (on the corner of Ferst and Atlantic).

==If you are driving south on I-75/I-85==
# Get off at North Ave.
# Make a right on to North Ave
# Make a right on to Techwood Dr.
# At Ferst Drive / 5th (second traffic light) make a left.
# Take a left into Parking Lot W21 (on the corner of Ferst and Atlantic)

KlausDirections

2018-06-14T03:00:17Z

Ndaugherty6:

[[Category:"Outreach"]]
Directions to Parking Lot W21
==If you are driving North on 75/85==
# Take I-85 North to Exit #250 (10th Street/14th Street/Ga Tech).
# Take a left on 10th Street at the light at the end of the ramp.
# Take a left on Fowler Street (first light after crossing the interstate).
# Take a right on Ferst Drive.
# Take a left into Parking Lot W21 (on the corner of Ferst and Atlantic).

==If you are driving south on I-75/I-85==
# Get off at North Ave.
# Make a right on to North Ave
# Make a right on to Techwood Dr.
# At Ferst Drive / 5th (second traffic light) make a left.
# Take a left into Parking Lot W21 (on the corner of Ferst and Atlantic)

Kickoff planning

2018-06-14T02:57:53Z

Ndaugherty6:

[[Category:Outreach]]
== The President ==

=== August ===
* Verify IRIM and the CoC can support the event
* Contact Ferst Theater to reserve the theater venue
** Office of the Arts Event Coordinator
* Identify the RoboJackets Kickoff Coordinator
** Introduce to Ga FIRST Regional Director and Kickoff Coordinator
* Identify the RoboJackets A/V Lead
* Identify the RoboJackets Volunteer Coordinator

=== September ===
* Inform Youth Programs (YP) that an event of 1000+ minors will be held on campus
** [http://youthprograms.gatech.edu/youth-programs-registration Register the event with YP]
** Ensure the expected adult/child ratio is better than 1:10
* Request Proof of Liability Insurance from Ga FIRST
** This should be coordinated through YP, and delivered to Georgia Tech Insurance, Claims, and Property Control

=== October ===
* Reserve non-Ferst rooms
** Workshops
*** Klaus 1116E/W
**** Through KACB Building Manager
*** Klaus 1443, 1447, 1456, 2443, 2447, 2456
**** Through IRIM Administrative Manager
** Student Center
*** Ballroom
*** Theater
*** Piedmont
* Schedule meetings or notify emergency services at Georgia Tech
** May be coordinated through YP
** Requires rooms to be booked first
** Notify Police Chief
** Notify Fire Marshall
* Coordinate with RJ PR Chair to design banners
** Paper and Clay has 36" vinyl stock

=== November ===
* Invite Speakers
** Dean of the CoE
** Director of IRIM
** CoC Assistant Dean for Outreach, Enrollment, and Community
** RoboJackets Advisor
** We want two speakers typically
* Finalize Breakfast Catering
** Talk with the Director of the Computing Community at the CoC
** Plan for 750-1000 with gluten-free options
** On campus venue, so requires on-campus catering
* Confirm with Youth Programs that requirements have been met
* Confirm with IRIM that the Ferst theater has been paid for
** Office of the Arts Event Coordinator will reach out early Nov. to get IRIM's payment information
** Give payment info the IRIM Administrative Manager
* Confirm with the IRIM Administrative Manager non-Ferst rooms have been invoiced and paid for
* Schedule Theater Walkthrough
** Office of the Arts Event Coordinator will reach out
** Request their technical assistant to attend
** The President, RJ Kickoff Coordinator, RJ A/V Lead, and RJ Outreach PM should be in attendance
* Schedule Meeting with Student Center Reservations and Events Coordinator
** Describe catering requirements (so they verify compliance)
** Describe room configurations
*** Ballroom with 35, 10 person, 72" tables
*** Theater in default config
*** Additional overflow rooms in theater configuration
*** Volunteer Kickoff room in roundtable configuration with projector
* Place banner order
** Paper and Clay
** Grommets to hang
* Pickup banner order
* Verify volunteer count

=== December ===
* finalize volunteer logistics
* determine stage schedule
* create presentation materials
* deliver materials to A/V

=== January ===
* handle volunteer lunch
* hold status meeting Friday night

== The Kickoff Coordinator ==

== A/V Lead ==

== Volunteer Coordinator ==

== Important Non-RJ People ==

=== College of Computing ===
* Director of Computing Community - Troy Peace
* Assistant Dean of Outreach - Cedric Stallworth
* Administrative Professional to Assitant Dean of Outreach - Alyshia Jackson
* Educational Outreach Manager - Jen Whitlow

=== Ferst Theater ===
* Office of the Arts event Coordinator - Rachel Haage
* Technical Lead - Paul

=== IRIM ===
* Executive Director - Magnus Egerstedt
* Administrative Manager - Nina Climes

=== Student Center ===
* Reservations and Event Coordinator - Jillian Cruser

=== Safety ===
* Youth Programs Compliance Specalist - Kelly Cross
* Fire Marshall - Larry Labbe
* Police Chief - Sgt. Archie Hill
* Director of Insurance, Claims, and Property Control - Tom Provancher
* Attorney - Shelley Hildebrand

=== Georgia FIRST ===
* Regional Director - Connie Haynes
* Kickoff Coordinator - Val
* Photographer/Media - Karen

=== Other ===
* Building Access
** Klaus
*** Stacey Greyson (OWA directory John Grayson)
*** Daron Foreman
** CoC
*** Keith Watson

== Rooms ==

Ki

2018-06-14T02:55:59Z

Ndaugherty6:

[[Category:BattleBots]]
[[Category:BeetleWeights]]
[[Category:2016-2017]]
Ki is a senior-designed 3lber, introduced as a project to test out experimental 3lber ideas. It was designed and built during the Summer and early Fall of 2016 for Sparkfun, a competition in Colorado.

It was then redesigned for Motorama 2017.

Its central concept is an asymmetrical horizontal bar spinner. The original design's horizontal bar looked like a key, hence the name. Other features include .25" UHMW armor in Ki and .5" UHMW armor on Kii.
{| class="wikitable" align="right"
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Kii
|-
! scope="row" colspan="2" | [[File:Kii.jpeg|frameless|right|480x360px|What a beautiful DUWANG]]
|-
! scope="row" style="text-align:left" | Year Of Creation
| 2016
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Versions
|-
! scope="row" style="text-align:left" | Current Version
| 2.0
|-
! scope="row" style="text-align:left" | Update Year
| 2016-2017
|-
! scope="row" style="text-align:left" | Wins/Losses
| 0/2
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Information and Statistics
|-
! scope="row" style="text-align:left" | Weight Class
| BeetleWeight
|-
! scope="row" style="text-align:left" | Weapon Class
| Horizontal Bar Spinner
|-
! scope="row" style="text-align:left" | Combined Wins/Losses
| 1/4
|-
! scope="row" style="text-align:left" | Weapon Speed
| 3500 RPM
|-
! scope="row" style="text-align:left" | ("Temporary")
| ("Temporary")
|}

== Competitions ==

=== Sparkfun 2016 ===
Results: 1-2

Bracket type: double elimination
* [https://www.youtube.com/watch?v=8859JUgBsgk Loss vs Margin of Safety]
**First fight against Margin of Safety. Great odds.
**At first, Ki and Margin are exchanging weapon hits. This pattern soon ends as Margin rips off all 3 armor pieces. Ki loses by tapout.

* [https://www.youtube.com/watch?v=d2yqKAeegfE Win vs Kamikaze]
** Kamikaze is a full-body bar spinner with an ABS frame and massive weapon.
** Kamikaze and Ki exchange blows for around 30 seconds, after which Kamikaze tears Ki's back armor off. It then ricochets, breaking its own ABS chassis and KO'ing itself.
* [https://www.youtube.com/watch?v=xuLOtSz8j1w Loss vs Just a Wedge]
** Just a Wedge is, as its name suggests is just a wedge.
** It was a wedge fight for most of it. Just a Wedge got its wedge stuck under a saw field hazard. Ki then bumped it free after a short time. Ki loses by judges' decision.

=== Motorama 2017 ===
Results: 0-2

Bracket type: double elimination
* [https://www.youtube.com/watch?v=C9A7yOEwpJc Loss vs Meili]
** Meili is another horizontal bar spinner. Oddly, its bar is at the exact height of Kii's belt.
** At first, Kii and Meili are exchanging blows. Meili then knocked Kii's back armor around in such a way to lift Kii's drive wheel off the ground. Then Meili's bar cut Kii's belt, at which point Kii lost by tap-out.
* [https://www.youtube.com/watch?v=0bYzrz1AfDQ&t=1s Loss vs Deathcap]
** Deathcap is an drum spinner with an elevated drum.
** Early on, Deathcap and Kii hit, resulting in Kii's right wheel being knocked off. Kii held Deathcap off for the full 3 minutes, and then lost by judges' decision.

== Version ==

=== Ki ===
Created by: Jonathan Spalten

{| border="1" cellspacing="1" cellpadding="1" style="width: 500px;"
|-
| Drive Motors
| 12V medium-power 25D mm 9.7:1 Pololu Metal Gear Motor
|-
| Drive Motor Controllers
| Scorpion Mini
|-
| Weapon Motor
| NTM Prop Drive Series 28-26A 1200kv/286W
|-
| Weapon Motor Controllers
| Afro Slim 20A ESC
|-
| Receiver
| <span style="line-height: 20.7999992370605px;">Hobby King 2.4Ghz Receiver 6Ch V2</span>
|-
| Remote Control
| <span style="line-height: 20.7999992370605px;">Hobby King 2.4Ghz 6Ch Tx and Rx V2</span>
|-
| Battery
| Turnigy Nano-Tech 2200mah 3S 25~50C Lipo Pack
|-
|Wheels
|Banebots T40s
|}

==== Problems ====

*Ki's weapon shaft was bolted on by only 4 4-40 screws.
*Its weapon shaft had two pieces that screwed together by threaded rod, resulting in odd interfaces with the weapon support system.
*Ki's top and bottom plate used 3/16" that had pockets to be milled down to 1/16". Not a good idea.
*Ki's armor pieces were screwed into the 3/16". 3/16" is too small to support 4-40s, and screws in general.
*Body is unecessarily large.

==== Good aspects ====

*The central concept of the bar support pieces was good.
*The weapon, when its support screws weren't shearing, performed well.

==== Changes/Improvements ====

*Reduce body size
*Use a screw for the shaft
*Make bar counterweight smaller
*Improve armor mounting

=== Kii ===

Created by: <span style="color: rgb(0, 0, 0); font-family: sans-serif; font-size: 12.6999998092651px; line-height: 20.7999992370605px;">Jonathan Spalten, Tyler Hiu, Tristen Smith,</span> Sidharth Eleswarapu

{| border="1" cellspacing="1" cellpadding="1" style="width: 500px;"
|-
| Drive Motors
| 12V medium-power 25D mm 9.7:1 Pololu Metal Gear Motor
|-
| Drive Motor Controllers
| Scorpion Mini
|-
| Weapon Motor
| Quantum MT Series 2814 880KV
|-
| Weapon Motor Controllers
| Afro 30A Race Spec Mini ESC
|-
| Receiver
| <span style="line-height: 20.7999992370605px;">Hobby King 2.4Ghz Receiver 6Ch V2</span>
|-
| Remote Control
| <span style="line-height: 20.7999992370605px;">Hobby King 2.4Ghz 6Ch Tx and Rx V2</span>
|-
| Battery
| Turnigy Nano-Tech 1000mah 3S 25~50C Lipo Pack
|-
|Wheels
|Fingertech Snap Wheels
|}

==== Problems ====

*The wheels were unarmored and came off frequently.
*There were still issues with enemy bots tearing armor off.
*Weapon motor was mounted to 1/16" Al. It bent, resulting in the belt coming off relatively frequently.
*The belt was an easy target.

==== Good aspects ====

*The weapon was effective.
*The wheels worked well, when they weren't torn off.
*It was easy to access electronics with the weapon support layer made of 3/16" Al with 1/16" Al top and bottom plates.

==== Changes/Improvements ====

*Putting armor on the wheels is a good idea
*Increase effective weapon area
*Protect belt
*Mount weapon motor more effectively

== See also ==
<ul style="line-height: 20.7999992370605px;">
<li>[[Dat_Boi]]</li>
<li>[[Qti]]
</li>
<li>[[Schwifti]]
</li>
<li>[[Snuti]]
</li>
<li>[[Radii]]
</li>
</ul>

== Notes: ==
[[File:-tyler-.jpeg|thumb]]
Based Tyler is the reason for Kii's major success.

Originally built by Jonathan Spalten

Joystick Interface

2018-06-14T02:54:08Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2005-2006]]
If you're looking for how to '''use''' the joystick see the [[Joystick]] page.

==Parts==

Part numbers listed are those of the Digi Key Corporation parts database. Note - some generic parts do not have part numbers listed.

===Processor===

*[http://www.atmel.com/dyn/products/product_card.asp?part_id=2967 ATTINY26-16SI-ND] - U3 - Atmel [http://en.wikipedia.org/wiki/Avr AVR] Microcontroller
*LED2 - Green LED for use by programs running on the microcontroller
*R3 - 470 ohm resistor in series with LED2
*R4 - 470 ohm pullup resistor for joystick DATA
*R5 - 470 ohm pullup resistor for joystick ACK

===CAN Specific===

*[http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1335&dDocName=en010406 MCP2515] - U2 - Microchip CAN Controller with [http://en.wikipedia.org/wiki/Serial_Peripheral_Interface SPI] Interface
*[http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1335&dDocName=en010405 MCP2551] - U1 - Microchip CAN TransponderP966-ND
*R1 - 10k ohm pullup resistor for the RESET command
*R6 - 10k ohm pullup resistor for the CAN chip select

===Onboard Power Control===

*[http://www.national.com/pf/LM/LM78M05.html UA78M05DCY] - U4 - 5V Linear Regulator
*1N4004GICT-ND - D1 - Diode
*P966-ND - C1,C2 - 10 microfarad Capacitor
*399-2127-ND - C3,C4,C5 - 0.1 microfarad Capacitor
*LED1 - Red LED to indicate power activity
*R2 - 470 ohm resistor in series with LED1

===Oscillator===

*300-7022-1-ND - U4 - 11.0592 MHZ Clock Siqnal Oscillator

===Headers===

*A19423-ND - J1 - Power 2-pin header
*A19430-ND - J2 - CAN 3-pin header
*A19436-ND - J3 - 9 pin header to joystick
*A19520-ND - J4 - SPI connection to the MCU, 10 pin header

===Misc.===

*377-1090-ND - Box to contain the module
*1892K-ND - Standoffs

==Electrical==

[[Image:Joystick Schematic.png]]
[[Image:Joystick Board.png]]

===Port Pin Assignments on MCU===

* Port A:
* Bit Dir Description
* 0 I Pad DATA
* 1 O Pad COMMAND
* 2 O Pad ATT
* 3 O Pad CLOCK
* 4 I Pad ACK
* 5 Unused
* 6 Unused
* 7 O Status LED

* Port B:
* Bit Dir Description
* 0 I SPI data input, with pull-up
* 1 O SPI data output
* 2 O SPI clock
* 3 O CAN /CS
* 4 I Clock, not usable as I/O
* 5 Unused
* 6 I CAN INT
* 7 I /RESET, not usable as I/O

==Code==

===C Source Files===

*can.c - communicates with the CAN controller, pretty much the same for all modules

*joystick.c - code that controls the joystick's inputs

*Makefile - programmer created file for configuring the compilation for gcc

*psx.c - code that interfaces with the psx controller

*spi_usi - hardware based spi

ImageFilterDemo

2018-06-14T02:49:35Z

Ndaugherty6:

[[Category:IGVC]]
[[Image:ImageFilterDemoScreenshot.jpg|thumb|right|Screenshot]]

'''ImageFilterDemo''' is a program that allows rapid prototyping of image filters in [http://java.sun.com Java].
This program was written by [[User:DavidF|David Foster]].

It appears that [http://www.cc.gatech.edu/~tucker/ Tucker Blach] has written a similar program, but in C instead of Java. See the [[Talk:ImageFilterDemo|talk page]].

The '''BarrelBlobFinder''' filter, bundled with ImageFilterDemo v1.2.3 and later, is an implementation of one of the [[Barrel Detection|barrel detection]] algorithms.

== Program & Source Code ==
* [[:Image:ImageFilterDemo_v1_5_2.zip|v1.5.2]]
** Enhanced some existing filters:
*** Enhanced '''LinearHoughTransform2''' to superimpose identified lines on top of the original image.
**** Looks really cool! Check the [[Hough Transform]] page for screenshots.
**** The old behavior of the filter can be attained by setting the "Output Type" parameter to <tt>1</tt>.
*** Enhanced '''GrayscaleFilter''' with the <tt>Binary Output</tt> boolean filter parameter.
** Added some new filters:
*** Added '''LocalMaximaHilighter''', a new filter that hilights local maxima in grayscale images.
*** Added '''GaussianBlurFilter''', a new filter that performs a Gaussian blur on the input image. Implemented according to [http://homepages.inf.ed.ac.uk/rbf/HIPR2/gsmooth.htm this page].
*** Added '''NormalizeGrayscaleFilter''', a new filter that linearly transforms the gray levels in the input image such that there are at least some pixels with the minimum and maximum intensities.
** Enhanced the '''Pixels''' utility class with some additional methods for converting between ARGB and grayscale pixels.
** Enhanced the GUI so that filters are no longer reapplied when a filter parameter is changed to a "new value" that is the same as its old value.
** Extended the plugin architechure to support plugin classes that contain nested classes

* [[:Image:ImageFilterDemo_v1_5_1.zip|v1.5.1]]
[[Image:LinesOnBlack.png|thumb|right|Before...]]
[[Image:LinesOnBlackWithHoughTransform.png|thumb|right|...and after application of the '''LinearHoughTransform2''' filter.]]
** Added some new filters:
*** Added '''LinearHoughTransform2''', an experimental new filter that detects lines of white pixels in a grayscale image.
**** This implementation of the [[Hough Transform]] is more CPU intensive than the original '''LinearHoughTransform''' filter, but has a number of advantages:
****# the output is far easier to interpret
****# lines in all orientations are detected equally well - sensitivity to near-diagonal lines is better
**** ''Filter Writers:'' This is the first standard filter that produces an output image that is of a different size of an input image. Those wishing to implement similar filters may want to take a look at the code of this filter.
*** Added '''LineGenerator2''', a new filter that displays a line at a specified (<tt>r</tt>, <tt><math>\theta</math></tt>) coordinate (relative to the center pixel of the input image).
**** The lines that this filter can generate are precisely the ones that '''LinearHoughTransform2''' can search for.
** Enhanced the '''BufferedImages''' utility class:
*** Added the <tt>createSizeCompatibleBufferedImage</tt> and <tt>createSizeCompatibleARGBBufferedImage</tt> methods.
*** Added the <tt>copyImageToBufferedImage</tt> and <tt>copyImageToARGBBufferedImage</tt> methods.
*** Added the <tt>createSizeCompatiblePixelBuffer</tt> method.
*** Added the <tt>copyBufferedImageToPixelBuffer</tt> and <tt>copyBufferedImageToARGBPixelBuffer</tt> methods.

* [[:Image:ImageFilterDemo_v1_5.zip|v1.5]]
** Added a "scaling factor" slider to the ImageFilterDemo UI. Scaling images to smaller sizes improves performance in general.
** Added some new filters
*** Added '''WhiteHilighterFilter''', a new filter that hilights white pixels (in a binary fashion)
**** The method used to identify white pixels is the same as the one that '''BarrelBlobFinder''' uses to find white stripes on barrels.
*** Added '''BarrelBlobDeleter''', a new filter that fills the boundaries of identified barrels with the background color of the image.
**** The parameters of this filter precisely match those of '''BarrelBlobFinder'''.
*** Added contour extraction filters for the diagonal, antidiagonal, and star (horizontal + vertical + diagonal + antidiagonal) directions.
**** DiagonalContourExtractionFilter
**** AntidiagonalContourExtractionFilter
**** StarContourExtractionFilter
*** Added '''GrayscaleFilter''', a new filter that converts images to grayscale (and optionally thresholds that grayscale image).
*** Added '''LinearHoughTransform''', an experimental new filter that detects lines of white pixels in a grayscale image.
**** This implementation of the Hough transform is still rather rudimentary - the format of the output is difficult to interpret without detailed knowledge of the implementation.
**** It is quite likely that I will release another implementation of the Hough transform whose output is easier to interpret.
**** I might mention that this filter has difficulty detecting lines that are almost but not exactly diagonal.
***** The directional resolution of the implementation is low for lines approaching a diagonal (or antidiagonal) direction.
*** Added '''LineGenerator''', a new filter that displays a line with a specified axis, slope, and intercept.
**** The lines that this filter can generate are precisely the ones that the current implementation of '''LinearHoughTransform''' can search for.
** Enhanced some existing filters
*** Made the list of barrel-boundaries identified by '''BarrelBlobFinder''' accessible to external code via the <tt>getBarrelBoundList()</tt> function.
** Enhanced the '''Pixels''' utility class
*** Added the <tt>grayToColor</tt> and <tt>graysToColors</tt> methods. These methods are useful for converting levels of gray into <tt>java.awt.Color</tt>s.
*** Added the <tt>grayToARGB</tt> method.
*** Added <tt>WHITE_ARGB_PIXEL</tt> and <tt>BLACK_ARGB_PIXEL</tt> constants.

* [[:Image:ImageFilterDemo_v1_4_1.zip|v1.4.1]]
** Extended the '''Pixels''' class with methods for converting to/from grayscale pixels.
** Added '''Histograms''', a utility class with methods for creating and analyzing normal histograms as well as probability histograms.

* [[:Image:ImageFilterDemo_v1_4.zip|v1.4]]
** Fixed a behavioral bug in '''ImageFilterDemo''' that caused the filter pipeline to be cleared continuously while image sequences were being played.
** Optimized the input pipeline for the internal classes '''PixelBufferToBufferedImageFilterAsBufferedImageFilter2''', '''PixelBufferFilterAsBufferedImageFilter''', and '''PixelBufferFilter2AsBufferedImageFilter''' (from 170-280 ms to 30-50 ms - 3.2 times faster), which implicitly improves the performance of ''all'' filters that implement '''PixelBufferToBufferedImageFilter''', '''PixelBufferFilter''', '''PixelBufferFilter2''', or '''PixelFilter''', including:
*** BarrelBlobFilter
*** BarrelHilighterFilter
*** GrayscaleLevelHistogram (filter)
*** HorizontalContourExtractionFilter, VerticalContourExtractionFilter
*** PlusContourExtractionFilter ''(special case - speedup x 3, or 9.6 times faster)''
*** HorizontalFlipFilter
*** RGBInversionFilter
*** RedChannelFilter, GreenChannelFilter, BlueChannelFilter
*** HueChannelFilter, SaturationChannelFilter, BrightnessChannelFilter
** Optimized the output pipeline for the internal classes '''PixelBufferFilterAsBufferedImageFilter''' and '''PixelBufferFilter2AsBufferedImageFilter''' (from 90-105 ms to 20-30 ms - 4 times faster), which implicitly improves the performance of ''all'' filters that implement '''PixelBufferFilter''', '''PixelBufferFilter2''', or '''PixelFilter''', including:
*** BarrelHilighterFilter
*** HorizontalContourExtractionFilter, VerticalContourExtractionFilter
*** PlusContourExtractionFilter
*** HorizontalFlipFilter
*** RGBInversionFilter
*** RedChannelFilter, GreenChannelFilter, BlueChannelFilter
*** HueChannelFilter, SaturationChannelFilter, BrightnessChannelFilter
** Added '''BufferedImages''', a new utility class for performing certain operations on <tt>BufferedImage</tt>s in a optimized fashion.
** Modified the GUI name of '''BarrelHilighterFilter''' to <tt>"Barrel Hilighter (Orange = Red-Green)"</tt>.

* [[:Image:ImageFilterDemo_v1_3_2.zip|v1.3.2]]
** Added '''OtsuThresholdingAlgorithm''', an implementation of the [[Adaptive Thresholding#Otsu Threshholding|Otsu thresholding algorithm]].
** Modified '''GrayscaleLevelHistogram''' to display the optimal threshold value for the output histogram, as calculated by the [[Adaptive Thresholding#Otsu Threshholding|Otsu thresholding algorithm]].

* [[:Image:ImageFilterDemo_v1_3_1.zip|v1.3.1]]
[[Image:Histogram.png|thumb|right|Example histogram generated by '''GrayscaleLevelHistogram''']]
** Added '''GrayscaleLevelHistogram''', a new filter that displays a histogram showing the frequencies of different levels of grays in the input image.
*** Created to assist in evaluating [[Adaptive Thresholding|adaptive thresholding]] algorithms.
[[Image:HistogramWithOtsuThreshold.png|thumb|right|Example histogram with optimal [[Adaptive Thresholding#Otsu Threshholding|Otsu]] thresholding level indicated]]

* [[:Image:ImageFilterDemo_v1_3.zip|v1.3]]
** New input source: Image sequences
**# Choose an input file from a folder of images.
**# Click the "Play" button in the lower-left corner of the window.

* [[:Image:ImageFilterDemo_v1_2_5.zip|v1.2.5]]
** Enhanced '''BarrelBlobFinder''' to determine barrel widths a lot more accurately.
*** Specifically, '''BarrelBlobFinder''' can now deal with barrels whose bottoms appear curved (which is common) more robustly.

* [[:Image:ImageFilterDemo_v1_2_4.zip|v1.2.4]]
** Addressed issue with loading certain images on Mac OS X:
*** Specifically <tt>java.awt.image.ImageProducer.startProduction(ImageConsumer)</tt> on Mac OS X incorrectly invokes <tt>imageComplete(...)</tt> on the passed <tt>ImageConsumer</tt>.
**** When a ''valid'' input image is loaded, <tt>imageComplete(...)</tt> is (correctly) invoked with the status <tt>STATICIMAGEDONE</tt>. But at the time of this invocation, attempts to query the loaded image's width/height fail (incorrectly).
**** Also, after this first invocation of <tt>imageComplete(...)</tt>, it is invoked yet again, but this time (incorrectly) with the status <tt>IMAGEERROR</tt>. This is a nonsensical status value, given that the image was already reported as being fully loaded.
*** Due to the particular way in which ImageFilterDemo checked whether the image was loaded successfully, this strange pattern of invocation resulted in the message "Unable to load image!" being briefly displayed before the input image was rendered.
*** To address this issue, the image loading code was rewritten to use the Image I/O API instead of the AWT Image API.

* [[:Image:ImageFilterDemo_v1_2_3.zip|v1.2.3]]
[[Image:IdentifiedBarrel.png|thumb|right|A barrel and its bounding box, as identified by '''BarrelBlobFinder''']]
** Added '''FloatFilterParam''', a new type of filter parameter.
** Added '''DoubleFilterParam''', a new type of filter parameter.
** Added a <tt>Threshold</tt> parameter to ''BarrelHilighterFilter''.
** Added '''BarrelBlobFinder''', an experimental new filter that locates and draws bounding boxes around barrels.

* [[:Image:ImageFilterDemo_v1_2_2.zip|v1.2.2]]
** Added '''BufferedImageFilter2''', a new type of filter.
** Added '''PixelBufferToBufferedImageFilter''', a new type of filter.

* [[:Image:ImageFilterDemo_v1_2_1.zip|v1.2.1]]
** Minor corrections make to the Makefile.
** Added [[Color Mode Changing|color conversion routines]] (between ARGB and AHSB) to the '''Pixels''' utility class.
** Added several new filters:
*** '''RGB Channel Filters'''
***# <tt>RedChannelFilter</tt>
***# <tt>GreenChannelFilter</tt>
***# <tt>BlueChannelFilter</tt>
*** '''HSB Channel Filters'''
***# <tt>HueChannelFilter</tt>
***# <tt>SaturationChannelFilter</tt>
***# <tt>BrightnessChannelFilter</tt>
*** '''BarrelHilighterFilter''' (''experimental'') - hilights areas of images where the difference <tt>(Red - Green) = Orange</tt> is large

* [[:Image:ImageFilterDemo_v1_2.zip|v1.2]]
** Made plugin architecture easier to use.
*** To add a plugin to the GUI now, just add its <tt>.class</tt> file to the <tt>plugins</tt> folder.
*** This can be done automatically if you write your plugin inside the <tt>srcplugins</tt> folder and then build it using the <tt>make pluginsWithDist</tt> command.
** Updated <tt>README</tt> file to explain the new way of adding plugins to the GUI.

* [[:Image:ImageFilterDemo_v1_1_1.zip|v1.1.1]]
** Fixed bug: The GUI editors for the filter parameters now check to make sure that the inputted value for a parameter is within the parameter's minimum and maximum values.

* [[:Image:ImageFilterDemo_v1_1.zip|v1.1]]
** Added support for filter parameters that are manipulatable in the GUI.
** Cleaned up and updated the <tt>README</tt> file.

* [[:Image:ImageFilterDemo_v1_0_4.zip|v1.0.4]]
** Added ability to save filtered images to disk.

* [[:Image:ImageFilterDemo_v1_0_3.zip|v1.0.3]]
** "Select..." button for selecting files now remembers the last file that was selected (even across different invocations of the program).
** Added support for dragging & dropping files into the "file well".

* [[:Image:ImageFilterDemo_v1_0_2.zip|v1.0.2]]
** Addressed issue with loading certain images on Windows systems.
*** Specifically, <tt>java.awt.Toolkit.prepareImage(Image, int, int, ImageObserver)</tt> on Windows does not notify the specified ImageObserver when images are finished loading under certain conditions.
*** Credit goes to [[User:AndyB|Andy]] for discovering this bug.

* [[:Image:ImageFilterDemo_v1_0_1.zip|v1.0.1]]
** Added '''PixelBufferFilter2''', a new type of filter.
** Added contour extraction filters for the horizontal, vertical, and plus (horizontal+vertical) directions.

* [[:Image:ImageFilterDemo.zip|v1.0]]
** Original version

== Future Versions (Planned) ==
* v2.0
** New input source: Movies (.mov, or other formats that QuickTime can handle)
** Added support for ''temporal filters''. These are filters that are designed for processing several images in sequence.

== Feature Requests ==

* Ability to apply multiple filters simultaneously (in a specific order) --[[User:AndyB|Andy]]
** ''Workaround:''
**# Load the original image.
**# Select the first filter.
**# Save the filtered image.
**# Load the filtered image.
**# Select the next filter.
**# Repeat until no more filters.
* Ability to save config profiles for each filter. --[[User:AndyB|Andy]]
** ''...to file, to preferences, or to both?'' --[[User:DavidF|David]]

== See Also ==
* [[Barrel Blob Finder]]

How to Guide Inventor

2018-06-14T02:47:21Z

Ndaugherty6:

[[Category: How to Guides]]

[http://en.wikipedia.org/wiki/Autodesk_Inventor Inventor], produced by [http://www.autodesk.com Autodesk], is the 3D solid modeling software currently used by the RoboJackets. The software can be downloaded for free at [http://students.autodesk.com http://students.autodesk.com] (you need a valid email address from a college ie. your @gatech.edu address). This guide is based off of Inventor 2008 and 2009. Inventor 2010 still works the same and has the shortcut keys, but has a ribbon style GUI.

Autodesk has released a set of [http://help.autodesk.com/view/INVNTOR/2014/ENU/?guid=GUID-A8795BBB-D723-444D-B36F-81573A6E1022 Essential Skills Videos] that is a great place to start learning.

==Setting Up Inventor==
In order to do anything, you need to setup your project file. By creating this you can more easily keep track of just project X or project Y and have them on the same machine.

To Do This:
# Go to File
# Projects
# Click the new button
# Fill in the requested info
Note: There are many ways to get to the projects window.

Now you will have you new project listed in the project window. However when you start inventor you will not by default be working in it. To make this the default project just double click on your project in the list. Now when you start you will always be working with it.

==Making a Part==
First we need to create a part file. To do this File > New > Select Standard.ipt

===Making a Sketch===
[[Image:Inv_sketch_start.jpg|thumb|left|Starting out a sketch]]
Like AutoCAD (also made by Autodesk) Inventor has many shortcut keys (some of them are the same). To your left you will see two panels. On the top you have Model and on the bottom you have 2D Sketch. The bottom panel will change depending on what you are doing (Note: these are the default locations and these windows are movable). You will also notice beside each title there is a drop down arrow these provide more features which you can explore. Though generally you will not use these additional features.

Generally (by default) the top panel will house info about the current file you are in and the bottom panel will hold commands that you can use to create your product.
<br clear="all" />
====Lines====
To do a line you can hit L and then click around to draw what you need to. To stop drawing lines (along with any other command) hit Esc. By default lines will attempt to orient them selves parallel and perpendicular with other lines.

====Circles====
There is more than one way to make a circle. By default and when you hit C it will make one from the center of the point that you select. To change this click the down arrow beside the circle button.

====More====
You can also create boxes. More importantly there is a trim command short cut X. With trim you could draw a triangle and place a circle on the end of it. Then remove only the lines that you want and end up with an ice cream cone.

Project Geometry is is by far one of the most useful tools (later on once you have more than one file). With this you can bring forward outlines from other parts or features on the same part and create sketches that a driven off of something else. These sketches will automatically update when that something else is changed.

====Dimensioning====
Before we go any further we need to fully dimension our sketch. This keeps it from changing and locks it in place. As of now all of our lines will be green and once we are done they will be black. To get started hit D. (Note: You can auto dimension the sketch however sometimes it is better to manually do it. You may want your sketch to be based off of direction X or Y and keep this or that side more readily adjustable.) You may need to specify its distance from the origin. To do this make the axises visible and project their geometry.

Once you have created a dimension you can edit it by click on it (it will go from black to red while hovering). You can input any formula you want.

A dimension can also be based of off of other dimensions. To do this simply create a dimension like you would normally and edit it. Once the window is up for you to key in a formula or number click on the dimension(s) you want it to be based off of. You can then manipulate them as if they were variables in an equation (which they are).

===Make Features===
In order to make your 2-dimensional sketch into something more tangible you will need to utilize various features depending on your situation. Overtime you will figure out what your situation is and what to do.

====Extrude====
[[Image:Inv_extrude_win.jpg|thumb|right|Normal Extrusion Window in Inventor]]
This makes a perpendicular projection of set length from a selected profile (sketch). To do this hit E. A window will appear with options on how to preform the extrusion.

To preform a Normal Extrusion:
# Hit E
# Select profile or sketch
# Key in distance
# Select direction (Forward, Backward, or 1/2 forward & 1/2 backward)
<br clear="all" />
====Revolve====
[[Image:Inv_rev_win.jpg|thumb|right|Revolve Extrusion Window]]
Produces a rotation of X degrees around a specified axis. You can added a line to your sketch and use it as that rotation axis or use an edge of the sketch.

To preform an Revolved Extrusion:
# Hit R
# Select the profile or sketch
# Select axis of rotation
# Specify extent (Full = 360, To = To a face, To From = From one location to another location, Angel = Specify degree)
<br clear="all" />
====Sweep====

====Loft====

====Hole====
When making holes for a bolted connection, it is better to use the hole tool instead of drawing them into your sketch initially and extruding or doing a cut.
Benefits of using the hole tool include:
* standard hole sizes for bolts
* thread and depth
* finishing options (counter sink, counter bore, etc.)
* easy adjustment of parameters

Other types of holes may be generated using the [[#Normal|extrude]] tool.

====Fillet====

====Chamfer====

===Properties===
[[Image:Inv_iprop_win.jpg|thumb|right|iProperties Window in Inventor]]
Now that you part is complete you are not done! Go to File > iProperties > Physical Tab

Set your material type and hit update. Then apply and close the window. Doing this allows inventor to: a) give you and estimated weight of your robot and b) give you a estimated cg location. Note: If you have a part like fan or an entire assembly like a motor you can weight the thing and then manually key in its mass on that window.

<br clear="all" />

==Assembling Parts==
Now that you have your parts lets put them together to make some sort of subsystem, product, etc. To do this you will need to create an assembly. Note: Assemblies can be composed of parts and other assemblies.

Ideally your robot's assembly structure could look like this:<br/>
#Main Robot Assem
## Drive Train Assem
### Gearbox Assem
#### Gears (Parts)
#### Plates (Parts)
#### Shaft (Part)
## Frame Assem
### Tubes / Angle (parts)
### Bolts (parts)
## Manipulators
## Bumpers

[[Image:Inv_assembly_win.jpg|thumb|right|Constraint dialog in Inventor]]
===Constraints===

Constraints, like in the sketching phase, are used in assembly phase to align parts in the fashion it will resemble in real life. First components must be placed, with the first component as grounded. Then the constraints dialog can be pulled up by hitting the key.

The first tab deals with assembly constraints and it is what we will be working with here. The options here are mate, angle, tangent and insert. They respectively align faces, corners, circular objects and cylinders to other faces, corners, surfaces and holes.

=== Mate ===

[[File:Inv assembly 4.jpg|thumb|left|text-top|upright|Flush with a .2 in offset]] [[File:Inv assembly 2.jpg|thumb|right|text-top|upright|Mate]] Mate is the first option and it comes in two modes, flush and mate. Two surfaces are selected and then they are stuck next to each other when using mate.

Flush (seen left) on the other aligns surfaces or planes with each other. A typical set of constraints use a single mate and two flushes to firmly stick two components to each other in a rigid orientation (three dimensions of movement requires three constraints). Offsets can also be described for additional flexibility in binding components together.

=== ===

=== ===

=== Insert ===

[[File:Inv assembly 5.jpg|thumb|left|text-top|upright|Axial arrows on circular faces when selecting surfaces for insertion]] [[File:Inv assembly 6.jpg|thumb|right|text-top|upright|Axes are aligned in the same direction]] Insert typically inserts a cylindrical object into a hole. The first two selections of the participating circular faces also show an axial arrow.

There is an option to have the arrows oppose each other or point in the same direction. This gives two different types of inserts, so choose the circular face correctly may save time and additional constraints.

Insert constraints have variable offsets as well, and if no offset is specified, then the components are free to slide along the highlighted axis of insertion.

---

== Making your Parts and Assemblies Useful ==

=== Drawing Files ===

'''Drawing files''' (.dwg) in Inventor are essentially 2D schematics of your parts and assemblies, which can be used for presentations, machining guides, and as fleshed out design documents.  We also use drawings as the 2D input for the waterjet.

To add contents to a drawing file, first import the "base view" of each .ipt file for the parts you want to add (right click, then select "base view", then select your file).  Then choose a 2D perspective of the part to display in the schematic.  Some of these perspectives include: Top, Left, Right, Back, and Bottom. For''3D designs'', you will usually show 3 perspectives, the top, the broad side, and the short side (x, y, and z, essentially).  Any unique part of a component or set of components should be highlighted from its most descriptive angle.  It is essential that the drawings give anyone with the schematic enough information to understand and/or physically create the the full part or set of parts.  Essential information may include: a bill of materials, material types, special notes, cut-outs and insets ("details"), and most importantly, your parts' dimensions'''.'''

=== Dimensioning ===

<span style="line-height: 20.8px;">The most important information you can include in a drawing file is its dimensioning.  This is essential for understanding and crafting the parts in your drawing in the real world.  You can annotate most of this information using the Dimension tool, under the "Annotate" section.</span>

<span style="line-height: 20.8px;">Required dimensioning includes:</span>

*<span style="line-height: 20.8px;">the length, width, and height (thickness) of all components</span>
*<span style="line-height: 20.8px;">the radius of all holes </span>
*<span style="line-height: 20.8px;">relative locations of all holes or cuts </span>
**e.g. <span style="line-height: 20.8px;">radius from center, distance from edge</span>
*<span style="line-height: 20.8px;">fillet, chamfer, polygon, and extrude angles</span>
*<span style="line-height: 20.8px;">any pattern details</span>
**<span style="line-height: 20.8px;">e.g. 5 holes over a distance of 5.5 inches</span>

==Appendix==
===Useful Short Cut Keys===
* Inventor Wide
** Zoom to fit = Home
** Look at face = Page Up
** Ending a command = Esc
** Pan = F2 (Hold)
** Zoom = F3 (Hold)
** Rotate = F4 (Hold)
** Cycle Through Views = F5
** Isometric View = F6
* Parts
** 2D Sketches
*** Line = L
*** Circle = C
*** Trim = X
*** Dimension = D
** Modeling
*** Extrude = E
*** Revolve = R
*** Fillet = F
*** Mirror = Ctrl + Shift + M
*** Circular Pattern = Ctrl + Shift + C
*** Rectangular Pattern = Ctrl + Shift + R
*** Loft = Ctrl + Shift + L
*** Sweep = Ctrl + Shift + S
* Assemblies
* Drawings

===Mouse Use===
* Pan = Center Click
* Zoom in / out = Scroll up / down

===Changing Units===
* When entering a dimension, simply type in the abbreviation for the unit. Inventor will convert automatically.
* To change the entire part, click Tools>Document Settings. On the Units tab, select your new units appropriately.

===Resources===
*[http://help.autodesk.com/view/INVNTOR/2014/ENU/?guid=GUID-A8795BBB-D723-444D-B36F-81573A6E1022 Essential Skills Videos]
*[http://help.autodesk.com/view/INVNTOR/2014/ENU/ Autodesk Inventor WikiHelp]
*[http://www.cadsetterout.com/inventor-tutorials/101-autodesk-inventor-productivity-tips/ Productivity Tips]

IT Coordinator

2018-06-14T02:45:50Z

Ndaugherty6:

[[Category:Information Technology]]
[[Category:Leadership Positions]]
The RoboJackets IT Coordinator is the leader of a committee that consists of previous IT Coordinators as they are willing to help. The role is to ensure that all non-robot technology is in good working order. This article outlines the current and legacy systems that RoboJackets IT must maintain. it is intended to be an overview of tasks, rather than an instructional guide or documentation of systems.

The IT Coordinator is responsible for submitting a proposal and budget document every fall, just like project managers. This document will outline the key goals of RJ IT for the year and outline any costs.

== Relation to other Tech Support Organizations ==

Officially, RoboJackets is officially supported by Mechanical Engineering Information Technology. However, they do not provide us with computers or build custom OS images. Historically, they have been too busy to adequately support SCC teams. As a result RoboJackets develops its own OS images and maintains its own internal network. ME IT will be able to answer questions about how to configure devices to plug into the network ports in the shop. See the documentation for details.

Historically, RoboJackets has had members who work for ResNet/Wreck Techs, which enjoys a close relation to ITG (IT for Campus Services). ITG has been very friendly towards RoboJackets in the past if you go through a ResNet staff member.

OIT Backbone maintains the wired network drops in the shop. Call OIT Technology Support Center for issues during business hours and OIT Operations for issues after hours.

OIT wireless supports GTwifi and Cisco access points within the shop. Open help requests directly with OIT for wireless issues. Nathan Wilder is specifically very helpful.

== Shop Computers ==

The IT coordinator will keep office computers up to date by patching the operating system and updating programs. During hardware upgrades or installs, the IT coordinator will build an operating system image and image computers. As departments move to MDT and SCCM, RoboJackets will join either ME IT's or ITG's implementation.

Computers that exist for a dedicated purpose, such as the RoboCup field computer are to be maintained in partnership by the IT coordinator and a designee of the user (RoboCup Software in this example).

Since shop computers run both Windows and Linux, it is expected that the IT coordinator is comfortable working on both platforms.

When new hardware is to be purchased, the IT coordinator has the final say on the specifications of the hardware to be procured.

== Shop Network ==

The IT coordinator will ensure that all computers in the shop have access to the internet at all times.

In the event of internet outages caused by Georgia Tech OIT, the IT coordinator will call OIT Operations and report the issue. OIT operations will expect the IT coordinator to make a judgement call on the urgency of the matter. While our meetings are important, we do not want to have someone on call drive 30+ minutes each way to fix the internet. In most cases, a workaround can be developed and the issue can wait until the next business day. Access to GT tools like Book of Knowledge is useful for this; however access can only be obtained via an on campus job in IT. Wireless outages should be reported via email to OIT. Please include in your report the name of the down AP by reading the label on the device and the status of the LED (e.g. Flashing Red, Green, Off). The light will be either solid blue or green during normal operation.

The IT coordinator will configure any routers, access points, and switches needed to keep the internal RoboJackets network running. Operation of RJwifi falls under this duty. When hardware ages or fails, a recommendation of replacement hardware will be made to core officers. Solid understanding of basic networking principles is required to adequately perform this aspect of the position.

The IT coordinator will maintain and repair network cables and ports throughout the shop as required. Certain tools may need to be borrowed from on campus tech support organizations like ResNet, ITG, ME IT, or OIT. We do not use consumables from these departments.

== Servers ==

Servers are racked at the CoC in the Orgs Rack. Buzzcard access to the rack can be added for anyone who completes Machine Room Training.

At a minimum, the IT coordinator will ensure that the servers are running properly and are backed up.

The IT Coordinator may propose ideas for changing services at RoboJackets Core Meetings.

IKArm

2018-06-14T02:43:59Z

Ndaugherty6:

[[Category:2005-2006]]
[[File:IKarm.jpg|right|300px|IKarm.jpg]]

Welcome to the '''[http://www.robojackets.org/ RoboJackets]''' Inverse Kinematic Arm wiki!

== Description ==

The Inverse Kinematic Arm project is an independent research endeavor that isn't affiliated with a robotics competition. The goal of the project is to explore control algorithms for implementing inverse kinematic control. This form of control is where the position of the end of the manipulator is controlled directly by giving it coordinates in 3 dimensional space to move to. The control algorithm is designed to determine what motions all the joints of the arm need to perform in order to achieve the desired end effector position.

The project will be conducted using a 3 degree of freedom arm that was taken off of an old bomb disposal robot(bombbot) that was donated to the RoboJackets by Dr. Wayne Book. Each joint is controlled independently by Vantec Motor drivers taken from the bombbot. Also, each joint has a potentiometer connected to it for positional sensing. All of the motor drivers and potentiometers are connected to an Atmel AVR development board which serves as an RS-232 adapter for the robot. Currently, the AVR board will connect to the serial port of a computer, which will control the robot using Labview.

Initially the goal will be to implement forward kinematic control of the robot, which entails independent PID control of each joint and determining the position of the end effector. Then several different inverse kinematic control algorithms including:

*Velocity controlled IK
*Path Controlled IK

The last goal of the project will be to implement hybrid control of the arm position in order to achieve multiple objectives simultaneously.

== Announcements ==

*9/28/06 - Current progress for this week has been updated [[IK Current Progress|here]].
*9/26/06 - Current Project progress page has been created [[IK Current Progress|here]]. Also, the Labview VI has been uploaded: [[:Image:IKarm Labview VI.zip|Labview VI]]
*9/1/06 Project timeline has been posted [[Project Timeline|here]] and the code for the AVR development board has been uploaded: [[:Image:IKarm AVR code.zip|AVR code]]
*8/23/06 IK Arm meetings will resume soon. Check back for updates

== Important Items ==

*'''[[Project Timeline]]'''
*'''[[IK Current Progress|Current Progress]]'''
*AVR code to translate IK motor driver and sensor data to RS-232: [[:Image:IKarm AVR code.zip|AVR code]]
*IK arm Labview VI code: [[:Image:IKarm Labview VI.zip|Labview VI]]

== System Components ==

*[[IKarm MCU2CPU|Robot to Computer Interface]]
*[[IKarm FK|Forward Kinematic control]]
*[[IKarm IK control|Inverse Kinematic control]]
*[[IKarm Path Hybrid|Path planning and hybrid control]]

== Links ==

*[http://zone.ni.com/devzone/labviewzone.nsf/OpenPage?openagent&lvsection=labviewzone%7C National Instruments Developer zone (Labview coding resources)]

== Motor Controller Docs ==

Pictures courtesy of Ben Johnson

[[File:Img 1134.jpg|300px|Img 1134.jpg]][[File:Img 1135.jpg|300px|Img 1135.jpg]]

IGVC Software Standards

2018-06-14T02:42:19Z

Ndaugherty6:

[[Category:IGVC]]
== Introduction ==
We strive to follow all of the ROS standards with a couple deviations listed below. If not explicitly mentioned on this page refer to the ROS standards.

*[http://wiki.ros.org/CppStyleGuide\ C++ Style Guide]

=== REP Guidelines ===
*[http://www.ros.org/reps/rep-0103.html\ Coordinate Frames]
*[http://www.ros.org/reps/rep-0105.html\ Link Naming Conventions]

=== Comments ===
Comment should describe the intent of the code not explain every syntactical oddity. If you feel that a certain line needs extensive explanation then you likely should reconsider that line.

IGVC Software Installation Instructions

2018-06-14T02:41:51Z

Ndaugherty6:

[[Category:IGVC]]
Welcome! Let's jump right in.

Robojackets IGVC currently supports the Ubuntu 16.04 and ROS-kinetic environment. If you don't know what those are, don't worry! The project may build/run in other environments, but we can't guarantee it.

Ok, lets get down to business.

== Step 1 - Get Terminator ==

Forget the default Ubuntu terminal, we need both horizontal and vertical splits for productive activity. Start up the default terminal and type:
<div style="background:#eee; border:1px solid #ccc; padding:5px 10px"><span style="font-family:courier new,courier,monospace">sudo apt install terminator</span><br/></div>
You should now be using this from now on, it will help later,

== Step 2 - Set up your sources.list ==

Now for these next steps you don't need to understand what they do, only make sure they complete properly. So if you see any errors come up, tell one of us immediately. Copy this into your terminal:
<div style="background:#eee; border:1px solid #ccc; padding:5px 10px"><span style="font-family:courier new,courier,monospace">sudo sh -c 'echo "deb [http://packages.ros.org/ros/ubuntu http://packages.ros.org/ros/ubuntu] $(lsb_release -sc) main" > /etc/apt/sources.list.d/ros-latest.list'</span><br/></div>
== Step 3 - Set up your keys ==
<div style="background:#eee; border:1px solid #ccc; padding:5px 10px">sudo apt-key adv --keyserver hkp://ha.pool.sks-keyservers.net:80 --recv-key 421C365BD9FF1F717815A3895523BAEEB01FA116
</div>
== Step 4 - Update your Debian packages ==
<div style="background:#eee; border:1px solid #ccc; padding:5px 10px"><span style="font-family:courier new,courier,monospace">sudo apt update</span><br/></div>
== Step 5 - Get Ros Kinetic ==
<div style="background:#eee; border:1px solid #ccc; padding:5px 10px">
sudo apt install ros-kinetic-desktop-full<br /></div>
== Step 6 - Initialize rosdep ==
<div style="background:#eee; border:1px solid #ccc; padding:5px 10px"><span style="font-family:courier new,courier,monospace">sudo rosdep init</span><br/></div><div style="background:#eee; border:1px solid #ccc; padding:5px 10px"><span style="font-family:courier new,courier,monospace">rosdep update</span><br/></div>
== Step 7 - Environment Variable Setup ==
<div style="background:#eee; border:1px solid #ccc; padding:5px 10px"><span style="font-family:courier new,courier,monospace;">echo "source /opt/ros/kinetic/setup.bash" >> ~/.bashrc</span><br/></div><div style="background:#eee; border:1px solid #ccc; padding:5px 10px"><span style="font-family:courier new,courier,monospace;">source ~/.bashrc</span><br/></div>
== Step 8 - Initialize catkin workspace ==
<div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="font-family:courier new,courier,monospace;">cd <path to where you want to keep the project></span></div><div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="font-family:courier new,courier,monospace;">mkdir catkin_ws</span></div><div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="font-family:courier new,courier,monospace;"><span style="line-height: 20.8px;">cd catkin_ws</span></span></div><div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="font-family:courier new,courier,monospace;"><span style="line-height: 20.8px;">mkdir src</span></span><br/></div><div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="font-family:courier new,courier,monospace;"><span style="line-height: 20.8px;">cd src</span></span><br/></div><div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="font-family:courier new,courier,monospace;"><span style="line-height: 20.8px;">catkin_init_workspace</span></span><br/></div><div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="font-family:courier new,courier,monospace;"><span style="line-height: 20.8px;">cd ..</span></span><br/></div><div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="font-family:courier new,courier,monospace;"><span style="line-height: 20.8px;">catkin_make</span></span><br/></div>
*Command should complete and not really do anything
*If init_catkin_workspace failed then ROS did not install correctly and/or try "sudo apt-get update" which may fix the issue where catkin_init_workspace command can not be found

== Step 9 - Clone IGVC Repository ==

*Fork IGVC Github Repository
<div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="font-family:courier new,courier,monospace;">cd src</span></div><div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="font-family:courier new,courier,monospace;"><span style="line-height: 20.8px;">git clone <your fork></span></span></div>
== Step 10 - Install ROS Dependencies ==
<div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><font face="courier new, courier, monospace">cd ..</font></div><div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="font-family:courier new,courier,monospace;">echo "source ~/catkin_ws/devel/setup.bash" >> ~/.bashrc</span>
</div><div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);">rosdep install --from-path src --ignore-src -y<br/></div>
*rosdep will download and install all of the necessary ros package dependencies, type "y" whenever it asks if it is ok to continue installation

== Step 11 - Build the Code ==
<div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="font-family:courier new,courier,monospace;">catkin_make</span></div>
*If this fails the first time try running catkin_make again
*If it continues to fail because it could not find some of the igvc_msgs header files, run "catkin_make igvc_msgs_gencpp" and then "catkin_make"

== Step 12 - Run the Code ==
<div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);">''In a separate terminal ''<span style="font-family:courier new,courier,monospace;">roscore</span></div><div style="line-height: 20.8px; border: 1px solid rgb(204, 204, 204); padding: 5px 10px; background: rgb(238, 238, 238);"><span style="line-height: 20.8px;">''In a terminal that isn't running roscore ''<span style="font-family:courier new,courier,monospace;">roslaunch igvc igvc.launch</span></span></div>
* The code should now be running and complaining about not being able to connect to various devices, this is all good and you are ready to start writing igvc code

IGVC Packing List

2018-06-14T02:37:27Z

Ndaugherty6:

[[Category:IGVC]]
Items to bring

*Red extension cable
*Orange extension cable x2
*Joystick and receiver x2
*Camera
*Cable box
*Laptop
*GPS
*Second Computer
*Ethernet Cable
*Wrenches (Adjustable)
*Allen keys
*7/16 wrench (for GPS)
*Volt meter
*White spray paint
*Barrels
*Extra batteries
*Battery charger
*Measuring tape
*Screwdriver
*Battery coords
*Lidar box
*E-stop

IGVC Overview 2015

2018-06-14T02:36:38Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2014-2015]]
= =
<div id="bodyContent" class="mw-body" style="color: rgb(0, 0, 0); font-family: sans-serif; line-height: 19.0499992370605px;"><div id="contentSub" style="font-size: 11px; line-height: 1.2em; margin: 0px 0px 1.4em 1em; color: rgb(84, 84, 84); width: auto;"></div><div id="jump-to-nav" class="mw-jump" style="overflow: hidden; height: 0px; zoom: 1; -webkit-user-select: none; margin-top: -1.4em; margin-bottom: 1.4em;"></div><div id="mw-content-text" lang="en" dir="ltr" class="mw-content-ltr" style="direction: ltr;">
The 2015 build season is underway!

We will be building upon the foundations laid last year to produce a competitive robot.
<ul style="/* insecure input */">
<li>Leadership<ul style="/* insecure input */">
<li>Orlin Velev - Project Manager and Mechanical Lead</li>
<li>Al Chaussee - Software Lead</li>
<li>Rohan Iyengar - Electrical Lead</li>
</ul></li>
</ul>
<ul style="/* insecure input */">
<li>Mistii<ul style="/* insecure input */">
<li>[[IGVC_Mechanical_2015|<span style="background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;">Mechanical Information</span>]]</li>
<li><span style="background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;">Electrical Information</span></li>
<li><span style="background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;">Software Information</span></li>
</ul></li>
<li><span style="background-attachment: initial; background-size: initial; background-origin: initial; background-clip: initial; background-position: initial; background-repeat: initial;">Meeting Notes</span></li>
</ul>
</div></div>

IGVC Overview 2013

2018-06-14T02:35:47Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2012-2013]]
2013 introduced many changes for the RoboJackets' entry into IGVC.

Completely new mechanical and software systems were developed, laying the foundation for a rejuvenated effort in the coming years.

* Leadership
** Joseph Hickey - Project Manager and Mechanical Lead
** Alex Trimm - Software and Electrical Lead
* Misti Documentation
** [[IGVC_Mechanical_2013|Mechanical Information]]
** [[IGVC_Electrical_2013|Electrical Information]]
** [[IGVC_Software_2013|Software Information]]
* [[IGVC 2013 Meeting Notes|Meeting Notes]]
<gallery>
Image:igvc_paper_2013.pdf|Misti Design Report
Image:igvc_presentation_2013.pdf|Misti Design Presentation
</gallery>
* [http://www.robojackets.org/gallery/main.php?g2_itemId=16339 Image Gallery]

IGVC Mechanical 2015

2018-06-14T02:33:46Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2014-2015]]
This page houses the information for IGVC Mechanical build for the 2015 competition year. Below are details pertaining to the team's design for the 2015 year, and the motivation behind all engineering decisions.

== Background ==

=== Current Robot ===

<font size="2">The team has taken part in IGVC for many years. Generally the mechanical base is a rugged design intended to serve as a platform for offroad autonomous navigation, In recent years, the vehicles generally exhibit 4 wheel drive with significant emphasis on suspension and power transmission.</font>

=== Previous Issues ===

<font size="2">The primary robot used in the 2013 and 2014 competition was a 4 wheel drive vehicle that utilized chains and sprockets to transmit power. Due to the suspension setup and the weight of the robot, there was significant misalignment with the interior and exterior sprockets, causing the chain to derail. Efforts in 2014 to improve this design proved to be insufficient.</font>

<font size="2">Additionally, these robots utilized skid-steer/differential drive, which works very well in the terrain encountered in competition, but presents odometry problems that needlessly complicate the efforts of the software development team. It is also not uncommon for inclement weather to occur during the competition, which further complicates the odometry issues.</font>

=== Improvements ===

<font size="2">The primary goals of the 2015 build season are to rebuild the drivetrain such that it is robust, while making drivetrain changes to also improve the odometry of the system.</font>

== <span style="line-height: 20.7999992370605px;">Requirements</span> ==

=== Primary Goals ===

<span style="font-size: small; line-height: 20.7999992370605px;">The team for the 2015 competition year has met several times to discuss the primary goals for the system rebuild. These requirements are outlined below, in order of highest priority to lowest priority.</span>
<ol style="line-height: 20.7999992370605px;">
<li>Eliminate chain and sprocket design and replace with a more reliable design given our suspension setup.</li>
<li>Maintain the use of our wheel decoupling mechanism</li>
<li>Eliminate skid-steer/differential drive design</li>
<li>Improve weatherproofing</li>
<li>Add a newer, more low-profile LIDAR.</li>
<li>Hot-swap batteries/recharging circuit</li>
</ol>

=== Secondary Goals ===

The team has also considered other desired characteristics of the robots that are not necessarily competition-oriented goals. The list is below (in no particular order).
<ol style="line-height: 20.7999992370605px;">
<li>Make a more compact, lightweight gearbox</li>
<li>Improve vehicle aesthetics</li>
</ol>

== Specifications ==
<ul style="line-height: 20.7999992370605px;">
<li>Robot dimensions should not exceed AA x BB x CC inches for competition</li>
<li>Robot dimensions should not exceed DD inches in width for ease of transportation through common door thresholds</li>
<li>Robot dimensions should not exceed EE inches in height for ease of transportation in our trailer.</li>
<li>E-stop should be located at FF inches from the ground</li>
<li>E-stop to be located at approximately GG inches from the ground for safety purposes while testing (RoboJackets criteria)</li>
<li>Mechanical chassis to exhibit rounded corners for safety purposes</li>
</ul>

== Mechanical Systems ==

:[http://wiki.robojackets.org/mediawiki/IGVC15-Components System Components and Bill of Materials]

=== Chassis ===

=== Drivetrain ===

=== Suspension ===

=== Mast ===

=== Weatherproofing ===

== Current Mechanical Tasks ==

For progress timelines see our [[IGVC 2015 Meeting Notes|meeting notes]]

Caster Wheel:<s>?</s>

*<s>Lubricate Bearings on caster wheel</s>
*Determine whether spacers are needed on the bottom of the caster plate to avoid running out of threading on screws
*Determine need for wirebrushing/sandblasting welded components
*Cut steel for turntable mount
*<s>Weld struts underneath electronics tray</s>
*Drill holes for screws through electronics tray
*machine axle
**<s>face off both sides of axle stock and cut to appropriate length</s>
**<s>lathe retaining ring grooves</s>
**mill axle pin slot
*paint caster wheel

Suspension:

*Confirm control arm mounting points and shock absorber bracket
*<s>Determine replacement tube structure for rear LIDAR tray</s>
*Cut off rear lidar tray
*Machine control arms and brackets
**water jet brackets, uprights
**lathe control arms and threading
**weld brackets

Drivetrain:<s>?</s>

*Generate G-Code
**CAM for gearbox
**CAM for motor mount
*Machine Gearboxes
*Verify and machine decoupled axle
*Machine worm axle
*Waterjet uprights

== Development ==

;[http://wiki.robojackets.org/mediawiki/Autodesk Inventor Autodesk Inventor] 
:We model our robot in Autodesk Inventor, and perform FEA with the inbuilt stress analysis tools.

== Structure ==

Our robot frame consists of primarily 1" steel tubing that has been custom designed and welded in-house. Steel tubing is chosen largely for its rigidity, with design emphasis on ruggedness and high payload capabilities, similar to that seen in military environments. The frame provides partitions for electronics, motors and sensors.

== Suspension ==

Much emphasis has been placed into the design of the robot's suspension. The primary objectives of off-road capability and vibration damping (for sensors) have been achieved by allowing for independent suspension for the rear wheels. The robot sports 3 ATV wheels and heavy-duty shock absorbers, allowing it to traverse rough terrains at high speeds while damping residual and transient vibrations to the sensors and giving each wheel up to 5 inches of vertical travel.

== Drivetrain ==

The vehicle utilizes caster wheel mechanics by with each of the two rear wheels being powered by a motor through a gearbox with a reduction of 30 to 1. The two 4.5 HP Ampflow motors ensure that the robot will not get bogged down in muddy or rocky terrain. Additionally, this allows for a top speed upwards of 20 MPH to be achieved.

== Weatherproofing ==

Heavy emphasis is placed on making the robot resistant to weather. The custom-machined gearboxes are sealed shut and snap-on body panels cover the entirety of the robot to keep water from directly seeping in. Additionally, water run-off flaps are attached to all sides of the body panels. Splash guards are also employed to keep water and debris thrown from the wheels from entering the region with the motor controllers and other electronics.

The button panel and electronics mounted on the mast also reside in weather resistant enclosures.

== Other things ==

The robots sports a variety of features that make it easy to maintain and operate. The body panels are easily removed via thumbscrews from any location, providing easy access to anywhere on the robot.

Emphasis is also being placed on ensuring ease of testing and transportation of the robot. Basic design parameters have been adhered to, such as making the width of the vehicle fits through a standard doorway and making vehicle such that the overall height fits with the transportation trailer.

IGVC Mechanical 2014

2018-06-14T02:33:04Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2013-2014]]

==Tasks==

==Development==
; [[Autodesk Inventor]] : We model our robot in Autodesk Inventor, and perform FEA with the inbuilt stress analysis tools.

==Structure==
Our robot frame consists of primarily 1" steel tubing that has been custom designed and welded in-house. Steel tubing is chosen largely for its rigidity, with design emphasis on ruggedness and high payload capabilities, similar to that seen in military environments. The frame provides partitions for electronics, motors and sensors.

==Suspension==
Much emphasis has been placed into the design of the robot's suspension. The primary objectives of off-road capability and vibration damping (for sensors) have been achieved by allowing for independent suspension for each wheel. The robot sports 4 ATV wheels and heavy-duty shock absorbers, allowing it to traverse rough terrains at high speeds while damping residual and transient vibrations to the sensors and giving each wheel up to 5 inches of vertical travel.

==Drivetrain==
The vehicle utilizes skid-steer mechanics by mechanically linking the wheels on each side of the robot. This is accomplished via a central motor and gearbox per side with two separate outputs, one going to the front and back wheels. The sprockets and gearbox give a combined reduction of 30 to 1. This coupled with the two 4.5 HP Ampflow motors ensures that the robot will not get bogged down in muddy or rocky terrain. Additionally, this allows for a top speed upwards of 20 MPH to be achieved.

==Weatherproofing==
Heavy emphasis is placed on making the robot resistant to weather. The custom-machined gearboxes are sealed shut and snap-on body panels cover the entirety of the robot to keep water from directly seeping in. Additionally, water run-off flaps are attached to all sides of the body panels. Splash guards are also employed to keep water and debris thrown from the wheels from entering the region with the motor controllers and other electronics.

The button panel and electronics mounted on the mast also reside in weather resistant enclosures.

==Other things==
The robots sports a variety of features that make it easy to maintain and operate. The body panels are easily removed via thumbscrews from any location, providing easy access to anywhere on the robot.

Emphasis is also being placed on ensuring ease of testing and transportation of the robot. Basic design parameters have been adhered to, such as making the width of the vehicle fits through a standard doorway and making vehicle such that the overall height fits with the transportation trailer.

IGVC Mechanical 2013

2018-06-14T02:30:20Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2012-2013]]
Misti was a completely new mechanical build over previous years.

She was designed to have a similar footprint to Jeanni and Roxi(i) while making the electronics more accessible, being more waterproof, and being much more offroad capable.

== Organization ==
* Blue � Drivetrain and Suspension
* Red � Sensors
* Green � Interface
* Pink - Electronics

[[File:2013IGVC_Organization.jpg|thumb|400px|Misti Zones]]

== Frame ==

== Drivetrain ==
; Drive: Tank/skid steer
; Motor: AmpFlow A28-400 Motor
*Website: [http://www.ampflow.com/ampflow_motors.htm AmpFlow Motors]
*[http://www.ampflow.com/A28-400_Chart.png Performance Charts]
* Quantity: 2
** Combined 9 peak horsepower
** [[IGVC_2013_Electrical_Drive_System|Redundant motor controllers]]
; Custom gearboxes
* CNC milled boxes
* 2 stage reduction
* Total reduction 30:1

== Suspension ==

== Sensors ==
Misti was designed to accommodate all the [[IGVC_2013_Sensors|sensors]] with the following design principles:
* Protect from environment
* Maintain accessibility
* Modular mounts: Isolate change propagation

== Interface ==
* Panel with clearly identified and accessible buttons, switches, and guages
* Safety:
** Multiple remotes for wireless E-stop
** Wired E-stop at operator�s forehead level

== Electronics ==
Misti took advantage of the wider front and rear trays to make the [[IGVC_Electrical_2013|electronics]] more accessible:
* Power distribution tray mounted to removable static dissipative panel for servicing.
* Reduce wiring mess:
** Motor controllers mounted near motors
** Micro-controllers mounted near laptop

IGVC 2014 Sensors

2018-06-14T02:28:26Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2013-2014]]
==Camera==
;Point Grey Bumblebee2
*Website: [http://www.ptgrey.com/products/bumblebee2/bumblebee2_stereo_camera.asp Bumblebee2]
*References:
**[http://www.ptgrey.com/products/bumblebee2/bumblebee2_xb3_datasheet.pdf BB2 Data Sheet]
**[http://www.ptgrey.com/support/downloads/documents/Bumblebee2%20Getting%20Started%20Manual.pdf BB2 Getting Started Manual]
**[http://www.ptgrey.com/support/downloads/downloads_admin/Dlds/Point%20Grey%20Digital%20Camera%20Register%20Reference.pdf PGR Digital Camera Register Reference]
*Voltage Requirement: 8-30V

==GPS==
;Hemisphere A321:
*Upgrade for 2014 competitive season
*Website : http://www.outbackguidance.com/Products/GNSS/OutbackA321.aspx
*Users Guide:[http://www.outbackguidance.com/Portals/3/Documentation/Outback%20A320-A321%20User%20Guide%20875-0291-000_A2.pdf A321]

==IMU==

;ArduPilot Mega 2.5+:
*Website: [https://code.google.com/p/ardupilot-mega/wiki/APM25board APM 2.5+]
*From [http://3drobotics.com/ 3DRobotics]

==LIDAR==
;SICK LMS 200
*[https://www.mysick.com/partnerPortal/ProductCatalog/DataSheet.aspx?ProductID=33755 Online Information]

==Encoder==
;US DIGITAL

IGVC 2014 Electrical Drive System

2018-06-14T02:27:26Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2013-2014]]
*Open Source Motor Controller
**Website: [http://www.robotpower.com/products/osmc_info.html OSMC Product Info]
**Resources
***[http://www.robotpower.com/downloads/OSMC_project_documentation_V4_25.pdf OSMC Project Documentation]
***[http://www.robotpower.com/downloads/osmc3-22sch-clean.pdf OSMC Schematic]
***[http://www.robotpower.com/downloads/osmc3-2-08222001.zip Schematic and Board Layout]
***[http://www.robotpower.com/downloads/osmc3-2-08222001-gerbers.zip Gerber Files]
***[http://www.robotpower.com/downloads/osmc-3.21-bom.pdf Bill of Materials]

*AmpFlow A28-400 Motor
**Website: [http://www.ampflow.com/ampflow_motors.htm AmpFlow Motors]
**[http://www.ampflow.com/A28-400_Chart.png Performance Charts]

*Arduino Uno
**Website: [http://arduino.cc/en/Main/arduinoBoardUno Arduino Uno]
**Resources
***[http://arduino.cc/en/uploads/Main/arduino_Uno_Rev3-02-TH.zip EAGLE Files]
***[http://arduino.cc/en/uploads/Main/Arduino_Uno_Rev3-schematic.pdf Schematic]
**[[ArduinoCode|Arduino Code Overview]]

*Custom Motor Shield

IGVC 2013 Sensors

2018-06-14T02:24:50Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2012-2013]]
==Camera==
;Point Grey Bumblebee2
*Website: [http://www.ptgrey.com/products/bumblebee2/bumblebee2_stereo_camera.asp Bumblebee2]
*References:
**[http://www.ptgrey.com/products/bumblebee2/bumblebee2_xb3_datasheet.pdf BB2 Data Sheet]
**[http://www.ptgrey.com/support/downloads/documents/Bumblebee2%20Getting%20Started%20Manual.pdf BB2 Getting Started Manual]
**[http://www.ptgrey.com/support/downloads/downloads_admin/Dlds/Point%20Grey%20Digital%20Camera%20Register%20Reference.pdf PGR Digital Camera Register Reference]
*Voltage Requirement: 8-30V

==GPS==
;Hemisphere A100 Smart Antenna
*Website:Defunct
*Users Guide:[http://www.hemispheregps.com/Portals/2/download/A100/A100_User_Guide_8750163000_RevC1.pdf A100 Smart Antenna]
*Voltage Requirement: 7-36V

==IMU==

=====ArduPilot Mega 2.5+=====
*Website: [http://store.diydrones.com/APM_2_5_Assembled_p/br-apmpwrkt.htm APM 2.5+]

=====SparkFun Razor IMU=====
*Website: [https://www.sparkfun.com/products/10736? Razor SEN-10736]

==LIDAR==
;SICK NAV200-1111
*Voltage Requirements: 24V+/-25%
*[http://www.circuitben.net/nav200 Ben's Reverse Engineering]
*[https://www.mysick.com/saqqara/im0020797.pdf Operating Instructions (NAV200-1132)]
*[https://www.mysick.com/saqqara/im0014460.pdf Telegram Listing (NAV200-1132)]

==Encoder==
;US DIGITAL

IGVC 2013 Electrical Drive System

2018-06-14T02:23:07Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2012-2013]]
*Open Source Motor Controller
**Website: [http://www.robotpower.com/products/osmc_info.html OSMC Product Info]
**Resources
***[http://www.robotpower.com/downloads/OSMC_project_documentation_V4_25.pdf OSMC Project Documentation]
***[http://www.robotpower.com/downloads/osmc3-22sch-clean.pdf OSMC Schematic]
***[http://www.robotpower.com/downloads/osmc3-2-08222001.zip Schematic and Board Layout]
***[http://www.robotpower.com/downloads/osmc3-2-08222001-gerbers.zip Gerber Files]
***[http://www.robotpower.com/downloads/osmc-3.21-bom.pdf Bill of Materials]

*AmpFlow A28-400 Motor
**Website: [http://www.ampflow.com/ampflow_motors.htm AmpFlow Motors]
**[http://www.ampflow.com/A28-400_Chart.png Performance Charts]

*Arduino Uno
**Website: [http://arduino.cc/en/Main/arduinoBoardUno Arduino Uno]
**Resources
***[http://arduino.cc/en/uploads/Main/arduino_Uno_Rev3-02-TH.zip EAGLE Files]
***[http://arduino.cc/en/uploads/Main/Arduino_Uno_Rev3-schematic.pdf Schematic]
**[[ArduinoCode|Arduino Code Overview]]

*Custom Motor Shield

IGVC 2010 Tasks

2018-06-14T02:22:19Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2009-2010]]

This page lists all of the tasks that need to be done for IGVC 2010.

==Mechanical Tasks==
===Build a full practice course===
This should be prepared as soon as possible so real testing will always be available. It should have all of the things that are on the real course including various colors of traffic barrels, road blocks, speed bumps, white lines, and a ramp. Since we want the course to be near the Tin Building and none of the areas around there will allow us to paint the grass, the white lines should be simulated with painted boards or white tape. The ramp should also be very portable, but sturdy enough for someone to walk on.
===Design and build a new mechanical base===
(TODO: split this into smaller sub-tasks) We would like the new robot to be more off-road capable than Candi. While Candi's ball caster design is great on flat, smooth ground, traversing ramps and gravelly areas caused problems. Building an off-road would also allow us to use it as a platform for other competitions such as RoboCup Rescue and the University Rover Challenge. For this to happen, the new robot would need to have multiple mounting points for other sensors and manipulators used in those competitions but not in IGVC. The new robot should also be water-resistant, as we had issues with rain at the last competition. We would also like the new robot to be smaller than Candi, which had more internal room than we ever used.
===Cable-management system===
In Candi, we often needed to re-route cables, which is really annoying when zip-ties are used to hold them in place. For both robots, we need a more convent way to route and re-route cables.
==Electrical Tasks==
===Motor system for new robot===
Design on this should not begin until mechanical design is well underway. We will need a different, probably smaller, motors for the new robot. The motors we use for Candi are overkill, so they will be far more powerful and expensive than needed for the new, smaller robot. It would be possible to use the same motor controllers (OSMC) as are used on Candi, then the same motor interface board could be used, too. However, the OSMC is fairly expensive and is likely be more powerful than needed. In any case, the new motor controller should be electrically isolated to prevent coupling noise from the motors and possibly damaging the digital electronics. The least expensive solution will be to build or buy a motor controller that meets the motor's power requirements and also has the isolation circuity and a digital interface on-board.
===New E-stop system===
Design on this should not begin until mechanical design is well underway. The new robot will also need a new e-stop. It is fine if it is a copy of Candi's e-stop, so long as a good relay is chosen. If we have the time, it would be nice to find a new wireless transmitter which doesn't require the button to be held down for so long.
===Power supply===
Design on this can begin immediately. Last year, the robot was powered with separate batteries for each device. This worked, but was annoying because each battery had to be charged separately. We should build a power supply that is powered off of the main batteries that provides regulated power to everything on the robot. The supply should be designed so it can be used for Candi and the new robot. This means that each rail should be able to provide more current than needed in case more devices are added to either robot. It is fine to buy this, but it might be difficult to find exactly what we need. A very nice but optional feature is to have the ability to run the robot and charge the batteries off of an AC socket. This will however make the power system harder to design.
===IMU===
Design on this can begin immediately. This will be the same for Candi and the new robot. Design was begun on this last year, but not finished. It will have 3-axis accelerometers, gyroscopes, and magnetometers.

==Software Tasks==

==Administrative Tasks==
===Enforce deadlines===
Deadlines and milestones are useless if they aren't enforced. While this is a voluntary club where we can't force anyone to do anything, team leaders can prevent people from doing work by pull funding and other resources from a task. It is the job of everyone in the team to ensure that all of the members are making progress on the work for which they have taken responsibility.
===Obtain an outdoor LIDAR===
Our team is one of the few IGVC teams that have gone without a outdoor LIDAR, mainly because of lack of funding. It has made the tasks of vision and navigation significantly more difficult. Next year, we should try as hard as possible to buy or find someone to donate a LIDAR.
===Create good documentation===
If we want to use the new robot as a platform for other competitions, we have to make a concerted effort to document our design. Traditionally, we have only created designs for our own personal use, but the new robot may be used by many different people. This means that all of the design files (including CAD drawings) should go into SVN and everything should be documented both in SVN and on the wiki.

IGVC 2008 General Schedule and Progress Review

2018-06-14T02:21:05Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2007-2008]]
Here is a nearly week-by-week schedule that we hope to stick to throughout the year. Each month, key members will meet to review documentation and progress that has been made. We will compare our actual progress against the plan and attempt to alleviate any sluggishness in development. Expected results will appear in normal font - actual results will appear in bold.

{| cellspacing="0" border="1"
! colspan="2" style="background:gainsboro;"|August
|-
|'''Week of August 20th'''
|
*Initial IGVC pre-planning meeting.
*'''General RJ pre-planning meeting.'''
|-
|'''Week of August 27th'''
|
*Research on new technology solutions begins.
*'''Initial IGVC pre-planning meeting and research on new technology solutions begins.'''
|-
! colspan="2" style="background:gainsboro;"|September
|-
|'''Week of September 3rd'''
|
*'''New members are welcomed''' and are guided into filling necessary positions.
*At this time, dues should be paid and wiki accounts signed up.
|-
|'''Week of September 10th'''
|
*'''Research continues.'''
*'''Dues should be paid and wiki accounts signed up.'''
*'''Subversion accounts signed up.'''
|-
|'''Week of September 17th'''
|
*'''Research continues.'''
|-
|'''Week of September 24th'''
|
*'''Technology solutions are finalized''' and design work begins.
|-
! colspan="2" style="background:gainsboro;"|October
|-
|'''Week of October 1st'''
|
*'''Design work continues.'''
|-
|'''Week of October 8th'''
|
*'''Design work continues.'''
|-
|'''Week of October 15th'''
|
*'''Design work continues.'''
|-
|'''Week of October 22nd'''
|
*'''Finish design work''' and purchase necessary components.
|-
|'''Week of October 29th'''
|
*'''Begin work on initial implementation.'''
|-
! colspan="2" style="background:gainsboro;"|November
|-
|'''Week of November 5th'''
|
*'''Implementation continues.'''
|-
|Week of November 12th
|
*Implementation continues.
|-
|Week of November 19th
|
*On board testing and demonstration of first design iteration.
|-
|Week of November 26th
|
*On board testing and demonstration of first design iteration.
|-
! colspan="2" style="background:gainsboro;"|December
|-
|Week of December 3rd
|
*Dead week – no work expected.
|-
|Week of December 10th
|
*Final exams week – no work expected.
|-
|Week of December 17th
|
*Independent design work may be pursued.
|-
|Week of December 24th
|
*Independent design work may be pursued.
|-
|Week of December 31st
|
*Independent design work may be pursued.
|-
! colspan="2" style="background:gainsboro;"|January
|-
|Week of January 7th
|
*Evaluation of current progress – have we kept up with the plan?
|-
|Week of January 14th
|
*Backup implementation and testing period of first iteration.
|-
|Week of January 21st
|
*Backup implementation and testing period of first iteration.
|-
|Week of January 28th
|
*Backup implementation and testing period of first iteration.
|-
! colspan="2" style="background:gainsboro;"|February
|-
|Week of February 4th
|
*Backup implementation and testing period of first iteration.
|-
|Week of February 11th
|
*Secondary design phase.
|-
|Week of February 18th
|
*Secondary design phase.
|-
|Week of February 25th
|
*Secondary design phase.
|-
! colspan="2" style="background:gainsboro;"|March
|-
|Week of March 3rd
|
*Secondary design phase.
|-
|Week of March 10th
|
*Implementation of secondary design features.
|-
|Week of March 17th
|
*Implementation of secondary design features.
|-
|Week of March 24th
|
*Implementation of secondary design features.
|-
|Week of March 31st
|
*On board testing, optimization, and full systems integration.
|-
! colspan="2" style="background:gainsboro;"|April
|-
|Week of April 7th
|
*On board testing, optimization, and full systems integration.
|-
|Week of April 14th
|
*On board testing, optimization, and full systems integration.
|-
|Week of April 21st
|
*Dead week – no work expected.
|-
|Week of April 28th
|
*Final exams week – no work expected.
|-
! colspan="2" style="background:gainsboro;"|May
|-
|Week of May 5th
|
*Documentation gathered. Design paper and presentation prepared.
|-
|Week of May 12th
|
*Last minute implementation, optimization, and testing.
|-
|Week of May 19th
|
*Last minute implementation, optimization, and testing.
|-
|Week of May 26th
|
*Last minute implementation, optimization, and testing.
|-
! colspan="2" style="background:gainsboro;"|June
|-
|Week of June 2nd
|
*''16th Annual Intelligent Ground Vehicle Competition!''
|}

IGVC 2008 General Schedule and Progress Review

2018-06-14T02:20:38Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2008-2009]]
Here is a nearly week-by-week schedule that we hope to stick to throughout the year. Each month, key members will meet to review documentation and progress that has been made. We will compare our actual progress against the plan and attempt to alleviate any sluggishness in development. Expected results will appear in normal font - actual results will appear in bold.

{| cellspacing="0" border="1"
! colspan="2" style="background:gainsboro;"|August
|-
|'''Week of August 20th'''
|
*Initial IGVC pre-planning meeting.
*'''General RJ pre-planning meeting.'''
|-
|'''Week of August 27th'''
|
*Research on new technology solutions begins.
*'''Initial IGVC pre-planning meeting and research on new technology solutions begins.'''
|-
! colspan="2" style="background:gainsboro;"|September
|-
|'''Week of September 3rd'''
|
*'''New members are welcomed''' and are guided into filling necessary positions.
*At this time, dues should be paid and wiki accounts signed up.
|-
|'''Week of September 10th'''
|
*'''Research continues.'''
*'''Dues should be paid and wiki accounts signed up.'''
*'''Subversion accounts signed up.'''
|-
|'''Week of September 17th'''
|
*'''Research continues.'''
|-
|'''Week of September 24th'''
|
*'''Technology solutions are finalized''' and design work begins.
|-
! colspan="2" style="background:gainsboro;"|October
|-
|'''Week of October 1st'''
|
*'''Design work continues.'''
|-
|'''Week of October 8th'''
|
*'''Design work continues.'''
|-
|'''Week of October 15th'''
|
*'''Design work continues.'''
|-
|'''Week of October 22nd'''
|
*'''Finish design work''' and purchase necessary components.
|-
|'''Week of October 29th'''
|
*'''Begin work on initial implementation.'''
|-
! colspan="2" style="background:gainsboro;"|November
|-
|'''Week of November 5th'''
|
*'''Implementation continues.'''
|-
|Week of November 12th
|
*Implementation continues.
|-
|Week of November 19th
|
*On board testing and demonstration of first design iteration.
|-
|Week of November 26th
|
*On board testing and demonstration of first design iteration.
|-
! colspan="2" style="background:gainsboro;"|December
|-
|Week of December 3rd
|
*Dead week – no work expected.
|-
|Week of December 10th
|
*Final exams week – no work expected.
|-
|Week of December 17th
|
*Independent design work may be pursued.
|-
|Week of December 24th
|
*Independent design work may be pursued.
|-
|Week of December 31st
|
*Independent design work may be pursued.
|-
! colspan="2" style="background:gainsboro;"|January
|-
|Week of January 7th
|
*Evaluation of current progress – have we kept up with the plan?
|-
|Week of January 14th
|
*Backup implementation and testing period of first iteration.
|-
|Week of January 21st
|
*Backup implementation and testing period of first iteration.
|-
|Week of January 28th
|
*Backup implementation and testing period of first iteration.
|-
! colspan="2" style="background:gainsboro;"|February
|-
|Week of February 4th
|
*Backup implementation and testing period of first iteration.
|-
|Week of February 11th
|
*Secondary design phase.
|-
|Week of February 18th
|
*Secondary design phase.
|-
|Week of February 25th
|
*Secondary design phase.
|-
! colspan="2" style="background:gainsboro;"|March
|-
|Week of March 3rd
|
*Secondary design phase.
|-
|Week of March 10th
|
*Implementation of secondary design features.
|-
|Week of March 17th
|
*Implementation of secondary design features.
|-
|Week of March 24th
|
*Implementation of secondary design features.
|-
|Week of March 31st
|
*On board testing, optimization, and full systems integration.
|-
! colspan="2" style="background:gainsboro;"|April
|-
|Week of April 7th
|
*On board testing, optimization, and full systems integration.
|-
|Week of April 14th
|
*On board testing, optimization, and full systems integration.
|-
|Week of April 21st
|
*Dead week – no work expected.
|-
|Week of April 28th
|
*Final exams week – no work expected.
|-
! colspan="2" style="background:gainsboro;"|May
|-
|Week of May 5th
|
*Documentation gathered. Design paper and presentation prepared.
|-
|Week of May 12th
|
*Last minute implementation, optimization, and testing.
|-
|Week of May 19th
|
*Last minute implementation, optimization, and testing.
|-
|Week of May 26th
|
*Last minute implementation, optimization, and testing.
|-
! colspan="2" style="background:gainsboro;"|June
|-
|Week of June 2nd
|
*''16th Annual Intelligent Ground Vehicle Competition!''
|}

IGVC 2007 Travel Details

2018-06-14T02:17:37Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2006-2007]]
Here are the financial details and itinerary for the 2006-2007 trip to IGVC.

=Itinerary=

*We'll need to take off June 7th - June 12th. PLEASE inform your employer as soon as possible if you're working. The actual competition is June 8th - June 11th, but since the competition is in Michigan, we need about 12 hours of travel time.

==Wednesday June 6th==

*Meet at the Tin Building at 6 pm to pack all of our gear and get everything ready. We won't have the cargo van until the next day, and we'll need to have everything in order so we can load it quickly.

==Thursday June 7th==

*Meet at the Tin Building around 7:00 - 7:30 am. I should have our cargo van there by then. You are responsible for getting yourself to the Tin Building somehow. If this is impossible, let [[User:LoganS|Logan]] know and we'll see if we can work around it. I'd like to leave around 8:00 am.
*We will drive for approximately 12 hours to get to our hotel. Here's a link below if you want to check it out.
*[http://marriott.com/hotels/travel/dtwah-fairfield-inn-detroit-auburn-hills/ Fairfield Inn at Auburn Hills]

==Friday June 8th==

*We need to be at Oakland University for sign-in registration around 12:00 pm.
*We'll spend the rest of the time playing around with Candi on the practice courses.

==Saturday June 9th==

*We need to be at Oakland University around 8:00 am to continue our work on Candi.
*From 3:00 pm to 3:30 pm is our design presentation. A select few of us (no more than 3) will try to "sell" our robot to the judges.

==Sunday June 10th==

*We need to be at Oakland University around 8:00 am to continue our work on Candi.
*Candi needs to be able to pass the qualifying tests by now.

==Monday June 11th==

*We need to arrive at Oakland University around 7:00 am most likely to get things ready for the opening ceremonies.
*Opening ceremonies from 8:00 am to 8:30 am.
*The competition has officially begun! We'll have 3 runs on the autonomous challenge. The navigation challenge appears to run on a first-come-first-serve basis. If we haven't qualified by now, there's still time - we just might have to forfeit one of our runs.

==Tuesday June 12th==

*Check out of the hotel as quickly as possible. I'm aiming for 8:00 am. Begin 12 hour ride home. We'll be getting back to the Tin Building rather late and will have to do some unloading. Try and have a plan for someone to come and pick you up. I can drop people off if I absolutely must, but it'd be more convenient not to have to.

=Costs=

==Hotel==

*This is the major personal cost to the members. We're staying five nights and I've reserved 2 rooms with 2 double beds each. There will be 8 of us, so that means we'll have to share beds. If sharing a bed scares you, then bring a LIGHT sleeping bag (remember, luggage space is a hot commodity).
*The total cost of the hotel per person is $94.44. Please give [[User:LoganS|Logan]] a check or cash for this fee.

==Food==

*Cost: unknown. Food is also self-covered.

==Vehicles + Fuel==

*Vehicle and fuel charges will be covered by RoboJackets one way or another.

IGVCMechanical2012

2018-06-14T02:14:51Z

Ndaugherty6:

[[Category:IGVC]]
[[Category:2011-2012]]
==Tasks==

==Gantt Chart==
[[File:IGVC_2012_Gantt.png]]

IGVC/Design Reports

2018-06-14T02:13:59Z

Ndaugherty6:

[[Category:IGVC]]
== IGVC Design Reports ==
{| class="wikitable"
!Year
!Report
|-
|2009
|[[Media:IGVC_Design_report_2009.pdf|Report]]
|-
|2010
|[[Media:IGVC_Design_report_2010.pdf|Report]]
|-
|2011
|[[Media:IGVC_Design_report_2011.pdf|Report]]
|-
|2012
|[[Media:IGVC_Design_report_2012.pdf|Report]]
|-
|2013
|[[Media:IGVC_Design_report_2013.pdf|Report]]
|-
|2014
|[[Media:IGVC_Design_report_2014.pdf|Report]]
|-
|2015
|[[Media:IGVC_Design_report_2015.pdf|Report]]
|-
|2016
|[[Media:IGVC_Design_report_2016.pdf|Report]]
|-
|2017
|[[Media:IGVC_Design_report_2017.pdf|Report]]
|}

IGVC

2018-06-14T02:11:21Z

Ndaugherty6:

[[Category:IGVC]]
[[File:Jessi.jpg|thumb|right|400px|Our 2018 robot, Jessi]]
== Overview ==
What is IGVC?

== Meetings ==
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 7PM to 9PM
* Sundays 4PM to 7PM

== Leadership ==
* Project Manager: Dallas Downing
* Electrical Lead: Ryan Waldheim
* Mechanical Lead: Young Won
* Software Lead: Andrew Tuttle

== Competition ==
* Guidelines
[[IGVC Rules]] - FIXME brief summary of what the competition is, and should the IGVC Rules page linked here be an external link?
* Important Dates

== Subteam Resources ==
=== Electrical ===
* Overview
* Training info
=== Mechanical ===
* Overview
* Training info
=== Software ===
* Overview
* Training info

== Documentation ==
[[Past IGVC Competitions]] should be summarized here, like the [[BattleBots]] main page.

RoboRacing

2018-06-14T02:07:39Z

Ndaugherty6:

[[Category:RoboRacing]]
If you love RC vehicle sized autonomous race cars or are interested in learning about autonomous cars on a small scale, RoboRacing is for you! Our RoboRacing team started in 2013. The team initially competed in the [http://robotracing.wordpress.com/ International Autonomous Robot Racing Challenge] (IARRC) competition. Starting in 2016, RoboRacing also competes in [https://avc.sparkfun.com/ Sparkfun’s Autonomous Vehicle Competition (AVC)].

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

== Meeting Times ==

Mondays  - 6:30 PM

Sundays - 4 PM

Carpool locations - North Avenue Apartments & West Village

== Important Dates ==

=== IARRC 2018 ===

July 13-15, 2018

https://robotracing.wordpress.com/

=== Sparkfun AVC ===

September 7-9, 2018

https://avc.sparkfun.com/

== Competition Info ==

=== IARRC ===
*[http://robotracing.wordpress.com/rules/ Rules]
*[[IARRC_Equipment|Equipment]]

=== Sparkfun AVC ===
* [https://avc.sparkfun.com Rules]

== Results ==

=== 2017 ===
* IARRC
** 3<sup>rd</sup> overall
* AVC
** Autonomous Car Wars
*** 1<sup>st</sup>
** Speed Demons
*** Did not finish

=== 2016 ===
* IARRC
** 1<sup>st</sup> overall
* AVC
** Classic AVC
*** Did not finish

=== 2015 ===
* IARRC
** 4<sup>th</sup> overall
** [[:File:Robojackets-iarrc-2015.pdf|Team Report]]

=== 2014 ===
* IARRC
** 1<sup>st</sup> overall

=== NOTE ===
This page formerly included a description of the Homecoming Car project. That project now has a dedicated page at [[Homecoming car]].

I

2018-06-14T02:05:57Z

Ndaugherty6:

[[Category:BattleBots]]
[[Category:BeetleWeights]]
[[Category:Year: 2017-2018]]
{| class="wikitable" align="right"
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | I
|-
! scope="row" colspan="2" | [[File:(Image filename)|frameless|right|480x360px|(Highlight text)]]
|-
! scope="row" style="text-align:left" | Year Of Creation
|2017-2018
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Versions
|-
! scope="row" style="text-align:left" | Current Version
| 1.0
|-
! scope="row" style="text-align:left" | Update Year
| {{{updyr|20XX-20XX}}}
|-
! scope="row" style="text-align:left" | Wins/Losses
| 1/2
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Information and Statistics
|-
! scope="row" style="text-align:left" | Weight Class
| {{{wc|BeetleWeight}}}
|-
! scope="row" style="text-align:left" | Weapon Class
|Drum Spinner
|-
! scope="row" style="text-align:left" | Combined Wins/Losses
| 1/2
|-
! scope="row" style="text-align:left" | Weapon Speed
| 3700 kv
|}

I is an invertible 3 pound drum spinner with an 1/4 puzzle-fit aluminum frame. We chose a drum spinner design because we thought that drum spinners were an interesting challenge, and we chose to make our frame puzzle-fit because we wanted it to be very robust. I's drum is nearly 1 pound.

== Competitions ==

=== [[Motorama_20XX|Motorama 2018]] ===
Results:
*Bracket Style: Double Elimination
**[https://www.youtube.com/watch?v=soRjOmGh6VU&feature=youtu.be Loss vs Mombot]
***The belt for the drum was too tight so it would not spin up to full speed. The drive worked but was not strong enough. It was pushed around by Mombot who had a much stronger drive.
**[https://www.youtube.com/watch?v=sodLuI27hdI&feature=youtu.be Win vs Personal Injuri]
***A wire was pressed against one of our motors keeping it from spinning. Personal Injuri was also missing a motor and their weapon. Although the drum did spin during the fight, the belt rubbed against the motor guard causing it to snap.
**Loss vs Nautiloid
***We tried fusing a belt together using a soldering iron. While the belt remained intact, it wasn't smooth enough to spin easily. This kept the drum form spinning properly. We lost quickly and allowed Nautiloid to have a finishing blow while we were disabled.
== Version ==

=== I V1.0 ===

Created by: Alex Field, Alex 'Richard' Lee, Phillip Holloway, Allen Zhang

{| border="1" cellspacing="1" cellpadding="1" style="width: 500px;"
|-
| Drive Motors
| Maxon gearboxes coupled with a DSY outrunner
|-
| Drive Motor Controllers
| ztw spider 18a OPTO esc
|-
| Weapon Motor
| Turnigy 2836 Brushless 450-Size Heli Motor 3700kv
|-
| Weapon Motor Controllers
| Turnigy MultiStar 40A BLHeli-S Rev 16 ESC
|-
| Receiver
| <span style="line-height: 20.7999992370605px;">Hobby King 2.4Ghz Receiver 6Ch V2</span><br/>
|-
| Remote Control
| <span style="line-height: 20.7999992370605px;">Hobby King 2.4Ghz 6Ch Tx and Rx V2</span><br/>
|-
| Battery
| 3S Lightbelt 1000 mah
|-
| Wheels
| Snaphubs Foam Wheel
|}

==== Problems ====

*Drum failed to spin up consistently because the belt was never stretched to the correct amount.
*Belt snapped after spinning due to rubbing against the motor guard.
*The wires and motor guard prevented drive motors from spinning at times.
*The drive was inconsistent.

==== Good aspects ====

*The drum and rest of the robot had a good weight.
*The frame was sturdy due to having a front wall puzzle fit into the side plates.
*The front wall prevented the electronics from hitting the drum.

==== Changes/Improvements ====

*Find a consistent belt length.
*Redo the electronics to make working in the robot easier.
*Find a more consistent drive motor.
*Optimize weight to re-attach the armor..

== See also ==
<ul style="line-height: 20.7999992370605px;">
<li>[[Grizzli]]</li>
<li>[[Personal Injuri]]
</li>
<li>[[Esci]]
</li>
<li>[[Chewi]]
</li>
<li>[[Loki]]
</li>
</ul>

== Notes: ==

It is unclear whether the robot's name is pronounced "AYE" or "EEE"

<span style="line-height: 20.7999992370605px">The name was originally meant to represent the Roman numeral 1. With successive generations this naming origin is expected to make less and less sense.</span>

The Team - Alex Field, Alex 'Richard' Lee, Phillip Holloway, Allen Zhang, Eun Chang Park (Mentor)

How to use Google Photos

2018-06-14T02:01:30Z

Ndaugherty6:

[[Category:How to Guides]]
[[Category:Public Relations]]
As of December 2016 we've moved to using Google Photos on the RoboJackets brand account to manage photos. To get access to the brand account, contact the current IT coordinator. It will then show up under the account picker on some Google products, including Google Photos.

==Creating a shared album==
#Open [https://photos.google.com/ Google Photos] and make sure you're on the RoboJackets brand account - RoboBuzz should show up in the top right corner. If it does not, click your profile picture, then choose RoboJackets (Brand Account) from the account picker.
#In the top navigation bar, click "Create" then "Shared Album".
#Pick one or more photos to start off the album - you can remove it later if it shouldn't actually be in the album.
#Click Create in the top right and you'll be taken to the album page.
#Set a title for the album, then click Share in the top right.
#You can send invites directly to certain Google accounts, or use the bottom-left option to create a link. By default, anyone will be able to join the album and add photos, but you can disable this by clicking the lock in the top right.
#At this point, you can remove the starter photo by opening it, then clicking the three dots in the top right corner, then choose "Remove from album."

How to give a great Core report

2018-06-14T01:57:09Z

Ndaugherty6:

[[Category:How to Guides]]
[[Category:Public Relations]]
This document is largely intended as guidance for new officers, although project managers may also find it helpful.

#Start early. You get the agenda document on Sunday - that gives you two full days and then some to make your report as good as possible. Do a quick writeup off the top of your head Sunday or Monday, and revisit it and revise as needed until Wednesday night. By the time Core starts, your report should be substantially done.
#Ask yourself whether your report is meaningful to the other people in the room. Is this going to affect other teams? Did you reach a cool milestone (or have a learning moment?) Did you highlight any action items for other Core members with clear steps to take? Follow up important action items with a separate email to the mailing list soon after the meeting.
#Keep it concise. There's a lot of content covered in Core as is - people won't remember all the details, if they're paying attention at all - so just provide the necessary context, hit your major points, and be prepared to answer questions from the floor from those that are interested. That all being said, if you have an important and complex topic, take the time to explain it - Core is the time and place to discuss these things.

How to be BattleBots Project Manager

2018-06-14T01:52:41Z

Ndaugherty6:

[[Category:How to Guides]]
[[Category:BattleBots]]
Welcome to BattleBots Project Management. The purpose of this document is to guide future project managers as they take on the role and to serve as a reference for future BattleBot’s members.

=== What is your job? ===
While answers may vary, I see the role of Battlebots Project Manager as the driving force behind the robots, without actually building the robots. Looking at the team as a “robot building machine,” the team members are the various components which actually build the robots. While people will not be as reliable as mechanical parts, the role of the project manager is still to facilitate their work. It is not the PMs job to machine parts, be the best machinist, or have the most knowledge about robotics. The Project Manager is responsible for making sure the “robot building machine” functions as efficiently as possible.

'''The specific duties of the PM are as follows:'''
* Appoint robot leads
* Set the schedule for each bot’s progress
* Schedule design reviews
* Monitor the progress of the robots
* Take action if a robot falls behind
* Register for competitions
* Work with the robot leads to create a budget
* Make sure spending does not exceed budget
* Make sure the shop is clean after meetings
* Make sure new members are sticking around and taking on leadership positions
** Ensure these active members receive the leadership advice and training they need(in this case, “training” is practice doing something ex. leading)
** Ensure active members get a chance to practice leadership even if they don’t want or receive a position. RJ needs people who lead, even if they do not have a title
** In order to be an effective leader, you need to be able to rely on your team being productive without you present
* Ensure new members take advantage of opportunities to learn from the work of more senior members, both CAD, machining, and other technical skills
* Ensure older members are teaching new members these skills

=== Communication: ===
You need to make sure you are communicating with your team effectively. Make sure every member is kept updated on the current progress of the robots and make sure you are aware of the current progress of each robot. An important part of staying on schedule is identifying roadblocks before/when they occur. '''You can’t solve a problem until you fully understand the cause.''' You are also not responsible for solving the problem yourself, only seeing that the problem is solved.

You need to set a timeline for each robot from the beginning of the year to the competition. This timeline should have specific checks for progress, and the robot leads should agree that the timeline is reasonable. If they miss a progress check, you need to work with them to get back on schedule ASAP. You should also make sure the rest of the team is updated on the progress of every robot.

'''Regularly ask robot leads:'''
* What they have accomplished
* What they are doing next
* What they need to continue work
** This may include outside expertise, knowledge, or human resources; it is not limited to materials/time

Make sure every member working on the robot is up to date on the progress and knowledgeable of the robot.

Take notes. If something is said that you want an action to come from, write it down. Memory is often bad, and you’ll forget more than you expect. Often, a conversation about long term goals or about a list of things to do will happen spontaneously. You need to make sure all of this actually happens or is taken into account for future decision making.

Lastly, make sure everyone gets along. If you or a team member is having a personal issue with another team member, you need to sit down, and talk it out. Make sure there is mutual respect. Without this respect, your team members will not communicate effectively with you or each other.

Below is a spread sheet previously used to track the progress of the robots. It's advantage is allowing you to see whether the robot is accomplishing previously set goals, and to easily examine the progress made over time. The expectations must be set ahead of time and revisited throughout the semester. The accomplished is what was actually completed at the time of the check, and it is filled via report from the robot lead. If the expectation was not met, plans to meet the expectation should be added.
{| class="wikitable"
!Check Dates
!Robot 1 Expectation
!Robot 1 Accomplished
!Robot 2 Expected
!Robot 2 Accomplished
!And so on for N robots
|-
|mm/dd/yyy
|Have Design Reviewed
|Robot was successfully design reviewed
|Have Chassis Finished
|One plate left to machine (will be done tomorrow)
|
|-
|mm/dd/yyy
|Design changes made and
next design review planned
|Changes made, but next review has not
been planned
|Have robot driving
|Robot will be driving tonight
|
|-
|mm/dd/yyy
|Design review complete
|
|weapon assembly done
|
|
|}

=== The Robot Build Process: ===
[[File:BattleBots Flow Diagram.png|thumb|475x475px|Process of Building a Battlebot]]
To the right is the high level process for building a robot. You should expect your robot leads to accomplish all of these steps in some form or another.

You must also make sure that the robot leads are progressing through these steps. If they have been working on “CAD” for an entire semester, they are likely behind schedule. Monitoring a robot’s timeline is crucial for making sure the robot is complete. Members will work on the robot, but you must make sure enough work is being done.

=== Registering for Competition: ===
Registering for competition should be completed as soon as possible. Googling your desired competition and clicking “register” should give you a starting point. You should know the dates, rules, and location of the competition months in advance. In the past, registrations have filled over night, and so you need to make sure you are proactive when registering for competition.

'''The process for registration is as follows:'''
# Decide you are going to set competition
# Check rules, requirements for entry, registration dates, etc.
# Decide which robots will be going
# Decide which people are going (~1month before registration opens)
# Collect necessary information about those team members/enter them into whatever database the competition uses
# Register for the competition (~1-3 days within registration opening)
# Contact Faculty sponsor for permission to go to competition and for excused absence forms.
# Pay for competition (Some competitions have a delay in when payment is due and when you can register). Do this as soon as possible, some registrations are expensive or require physical check. This can take additional time.
# Book lodging and travel as necessary (hotel 1-2 months in advance, travel 2-4 months in advance)
# Decide how much each going member will pay and collect the amount before traveling
# Wait for the competition to contact you with info about what to do when you arrive
# Make sure you receive passes if they are being shipped to you
'''Registering for Motorama:'''

Website: https://www.motoramaevents.com/

Motorama has been our new member’s intro competition. Given it is the “freshman competition,” the main focus should be taking as many new members as possible. You only need enough senior members to drive the cars and maybe one or two more to help corral new members. We have historically taken about 21 members. Senior members may bring a 30 lb robot as well.
* Motorama - Builder’s database - Use this to manage our team and robots. This site can also be used for other competitions
* Contact an old PM for the login info
* New team members can be added via “add new team members”
* New robots can be added via “add new robot”
* Select “motorama” to register for this competition
* Select who is going, which robots are going, and register for “parking passes”
* Once the registration is finalized, they will process it and request payment later.
* Once this happens, you must cancel the registration to change it, which means you will likely lose your spots. Contact the event coordinator to make changes.
* Book rental cars and hotels
'''RoboGames'''

Website: http://robogames.net/index.php

This is the 120 lb senior competition. Historically 6-8 people have attended this competition. 7 people is the most you can take and rent a single car, but if you have the money, drivers, and robots, you can bring more people. This competition currently fields the sumo, 120 lb, and now the 60lb robot. We also try and bring a 3 lb robot and the freshman who worked on it. Taking 1 or 2 freshman is advised, but they should be selected carefully. This trip is a ton of fun and it could lock in a future leader. Consider shipping robots to reduce carry on weight, but you will need to plan further in advance to make this work. Shipping the robot means it must be done weeks in advance, and SGA money cannot be used.

'''Going to competition'''

When leaving for competition, it is your job to make sure everything we need is packed, rides to the airport and campus pickups are arranged, and that every team member knows where they need to be and when they need to be there.
* Make sure every robot has a controller, all tools necessary for assembly, whatever spare parts they have, and a completed robot
* Refer to the packing list on the wiki for tools you should pack

When you are travelling, make sure nobody is alone, and you know where everyone is. It is your job to make sure you make it to the competition venue on time, and that you are checked in and ready to compete.

=== Monitoring Budget: ===
Currently, RoboJackets receives money from Student Government Association (SGA), corporate sponsors (Through the ME foundation account) and student dues. SGA allocates money for specific purposes such as “stock material,” “electronics,” etc. Part of your job is preparing a budget proposal to inform the treasurer and president of the amount of money your project will require. A budget proposal is a justification of why and how you want to spend money and a breakdown of where that money is going.

'''How to write a budget proposal:'''
# Write a few paragraphs detailing your goals for the year:
## What robots you intend to build
## What competitions you plan on attending
## What you want to accomplish with each robot
# Tabulate how much each robot will spend on various components (This can be as detailed as the current president wants)
# Tabulate Competition and travel costs (includ hotel, plane tickets, and car rentals).
# Compare the planned costs with last year’s costs and be able to justify each expense
# Set each robot’s timeline

[https://docs.google.com/document/d/1AsQ209ePdHW4svBznNipMNucRaU729qJTTXRS09T9i8/edit?usp=sharing<nowiki>] This document is an example, but each proposal should be generated from scratch. You should review the previous year’s spending for a starting point. </nowiki>

Once the president/treasurer has cleared your budget proposal, you are ready to start spending money from approved SGA line items. No money should ever be spent without your knowledge, and it is your responsibility to spend it wisely.

Trusted senior members may be given access to fill out POs for your approval. If they have edit access, they can mark orders ready: make sure anyone with edit access knows the order must be cleared with you first. If there are any budget problems, it is your fault, not whoever is in charge of the robot.
* When buying stock, check multiple sites for the cheapest price. The wiki has a list of suppliers.
** Midwest steel and Al has cheap stock, but it takes time to ship
** Online metals is nice
** McMaster should be reserved for rush orders
** Typically, sheets of stock are more expensive than bars. Either can give you the metal you need.
* Remember to take shipping into account by
** Adding it into the “spent” category once the order has been placed
** Ordering from places where shipping is cheaper
* For some orders, try emailing the vendor and asking for a discount/sponsorship. Please notify the president, VP, or treasurer before reaching out. Sometimes the development office is already in negotiation with a company, and we don’t want to step on their toes.
** If you say you are a student on a robotics team, they will often try to accommodate you. It is important to make it clear we are a student organization, not a research lab. Research labs have money, student orgs don’t. If you want help drafting an email for sponsorship or academic discount, contact the president.
* Watch your metal alloys and plastic types, some are more expensive yet have little performance benefit
* Check what stock and materials we have in the shop. This includes other teams. Sometimes they have spare stock in a thickness they don’t intend on using in the near future
* Make DXF files before ordering waterjet stock to ensure efficient use of material
* Order spare material because there will be mistakes
* Be careful ordering electronics, balancing benefits and tradeoffs is important as prices and specs can vary widely. Again, feel free to consult electrical leads of other teams on any items you and your leader are unsure of.

=== Sponsors: ===
As mentioned earlier, many companies will sponsor us with free/discounted products or services. Make sure you keep the treasurer and president informed of sponsors.

Current Sponsors:
* Braddock Metallurgical: heat treatment to harden steel- etc.
** Tim Waters - twaters@braddockmt.com
* Hudson Tool Steel: gave us a discount on steel for Mandiii’s weapon
** Brad Piontkowski - brad@hudsontoolsteel.com

=== The 3lb Program: ===
The 3lb program is currently our way of training new members. Each new member of BattleBots joins a “3lb team.” These teams work to build a 3lb robot. The idea is that these robots are cheap, relatively simple, and new members will come out of the program familiar with our build process and machining capability. The teams currently compete at Motorama Robot Conflict. The freshman should do all of the design, CAD and manufacturing.

The 3lb lead and the 3lb council exist to guide the freshman. The 3lb lead acts as the PM for all of the 3lb robots. The 3lb council consists of a few senior members who will mentor the freshmen teams. They will watch the 3lb teams in order to determine if they are on schedule, find who the highest contributing/ most dedicated members are, and provide direction to the new members. Ensure the most dedicated members are engaging in as many learning opportunities as possible. These are the people to which you want to pass knowledge as they are the most likely to pass it on themselves. (They may also point the new members to other senior members if they cannot confidently answer the new member’s question.)

Your job with the 3lb program should be to treat the 3lb lead as one of your robot leads. Depend on the 3lb lead to run the 3lb program, but monitor the program to make sure they are progressing properly, the 3lb members are engaged, and money is being spent properly.

You should work with the 3lb lead to schedule additional work times outside of the Thurs/Fri meetings. It is impossible to finish the robot on time if you are only meeting 2 days/week.

=== Shop Cleanliness ===
As an officer within the organization, it is your job to make sure the shop and your space is kept clean and organized. If the shop is messy, your productivity will suffer, sponsors will be put off when they visit, new members will not be impressed, and the other teams will be mad at us.
* Make sure every tool is put away (in its correct location)
* Make sure any machine used is cleaned
* Make sure all of our parts and stock is returned to our shelf
* Make sure the tables and work surfaces are clean

With regards to our shelves, it is your job to make sure they are kept organized. The organizational system is up to you. Make sure every part on the shelf is useful. It is too easy to accumulate clutter. No system can fix having too much stuff.
* Regularly go through the shelf and make sure it is organized
** Throw away useless stuff. Seriously.
** Make sure everything is in its proper place
* Make sure every piece of stock has a planned robot use
** Any stock without a planned use can be moved to general shop stock (which you can later reclaim)
* Make sure electronics on the shelf still function

Group 5

2018-06-14T01:48:51Z

Ndaugherty6:

[[Category:BattleBots]]
[[Category:BeetleWeights]]
[[Category:Year: 2014-2015]]

{| class="wikitable" align="right"
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Group5
|-
! scope="row" colspan="2" | [[File:Group5.jpg|frameless|right|480x360px|Decapitator]]
|-
! scope="row" style="text-align:left" | Year Of Creation
| {{{year|2014-2015}}}
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Versions
|-
! scope="row" style="text-align:left" | Current Version
| {{{currver|1.0}}}
|-
! scope="row" style="text-align:left" | Update Year
| {{{updyr|2014-2015}}}
|-
! scope="row" style="text-align:left" | Wins/Losses
| {{{winloss|0/2}}}
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Information and Statistics
|-
! scope="row" style="text-align:left" | Weight Class
| {{{wc|BeetleWeight}}}
|-
! scope="row" style="text-align:left" | Weapon Class
| {{{weapc|Bent Bar Spinner}}}
|-
! scope="row" style="text-align:left" | Combined Wins/Losses
| {{{winloss|0/2}}}
|-
! scope="row" style="text-align:left" | ("Temporary")
| {{{TBA|("Temporary")}}}
|-
! scope="row" style="text-align:left" | ("Temporary")
| {{{TBA|("Temporary")}}}
|}

== Competitions ==
<ul style="line-height: 20.7999992370605px;">
<li>
=== [[Motorama 2015|Motorama 2015]] ===

*Results:
**Bracket Style:
***[http://youtu.be/fxYOFSVNv64?list=PLa4DDbMiSUTWb6HBYu5YBsfiZMhEr4SHY Loss vs Thunder Child]
****Was held back by the ram design of the opponent
****Top plate flew off
***[http://youtu.be/q-YmRDJZhGw?list=PLa4DDbMiSUTWb6HBYu5YBsfiZMhEr4SHY Loss vs Gemini]
****Top plate flew off immediately
****Was flipped over, and lost by KO</li>

== Version ==

=== V1 ===

Created By: 

{| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 500px;"
|-
| Drive Motors
| <br/>
|-
| Drive Motor Controllers
| <br/>
|-
| Weapon Motor
| <br/>
|-
| Weapon Motor Controllers
| <br/>
|-
| Reciever
| <br/>
|-
| Remote Control
| <br/>
|-
| Battery
| <br/>
|-
| (OTHER:)
| <br/>
|}

==== Problems: ====

==== Good aspects: ====

==== Changes/Improvements: ====

*Improved Structural Connection Between Top and Bottom

== See also ==
<ul style="line-height: 20.7999992370605px;">
<li>[http://wiki.robojackets.org/w/Emmi Emmi]</li>
<li>[http://wiki.robojackets.org/w/Vicki Vicki]</li>
<li>[http://wiki.robojackets.org/w/Flippi/MrWedge Flippi/MrWedge]</li>
<li>[http://wiki.robojackets.org/w/Smitti_Werbenjagermanjensen Smitti Werbenjagermanjensen]</li>
</ul>

== Notes: ==

*Group 5 used Struggle*

Grizzli

2018-06-14T01:48:07Z

Ndaugherty6:

[[Category:BattleBots]]
[[Category:BeetleWeights]]
[[Category:Year: 2017-2018]]

{| class="wikitable" align="right"
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Grizzli
|-
! scope="row" colspan="2" | [[File:(Image filename)|frameless|right|480x360px|(Highlight text)]]
|-
! scope="row" style="text-align:left" | Year Of Creation
| {{{year|20XX-20XX}}}
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Versions
|-
! scope="row" style="text-align:left" | Current Version
| {{{currver|X.X}}}
|-
! scope="row" style="text-align:left" | Update Year
| {{{updyr|20XX-20XX}}}
|-
! scope="row" style="text-align:left" | Wins/Losses
| {{{winloss|X/X}}}
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Information and Statistics
|-
! scope="row" style="text-align:left" | Weight Class
| {{{wc|BeetleWeight}}}
|-
! scope="row" style="text-align:left" | Weapon Class
| Vertical Bar Spinner
|-
! scope="row" style="text-align:left" | Combined Wins/Losses
| {{{winloss|X/X}}}
|-
! scope="row" style="text-align:left" | Weapon Speed
| 0 RPM
|-
! scope="row" style="text-align:left" | ("Temporary")
| {{{TBA|("Temporary")}}}
|}

Flippable Vertical Bar Spinner

== Competitions ==

=== [[Motorama 2018]] ===

*Results:
**Bracket Style:
***[(Video Link) (result) vs (opponent)]
****(notes)
****(observations))

== Version ==

=== Grizzli V1.0 ===

Created by: <span style="color: rgb(0, 0, 0); font-family: sans-serif; font-size: 12.6999998092651px; line-height: 20.7999992370605px;">(Names of Builders/Group Members of aforementioned version of bot)</span>

{| border="1" cellspacing="1" cellpadding="1" style="width: 500px;"
|-
| Drive Motors
| <span style="color: rgb(0, 0, 0); font-family: arial, sans, sans-serif; line-height: normal; white-space: pre-wrap;">(Drive Motor Name)</span><br/>
|-
| Drive Motor Controllers
| (Drive Motor Controller Name)
|-
| Weapon Motor
| Turnigy 2836 Brushless 450 Size Heli Motor 3700KV
|-
| Weapon Motor Controllers
| HobbyKing 30A BlueSeries Brushless Speed Controller
|-
| Receiver
| <span style="line-height: 20.7999992370605px;">Hobby King 2.4Ghz Receiver 6Ch V2</span><br/>
|-
| Remote Control
| <span style="line-height: 20.7999992370605px;">Hobby King 2.4Ghz 6Ch Tx and Rx V2</span><br/>
|-
| Battery
| (Battery Name)
|-
| (OTHER:)
| <br/>
|}

==== Problems ====

*HDPE walls bowed during assembly, causing parts to rub
*Not enough room for weapon between inner plates
*Center of mass was too far forward, leading to low traction for wheels
*Nut bar assembly took up too much space

==== Good aspects ====

*(List of good aspects, 1 per bullet point)

==== Changes/Improvements ====

*HDPE-Aluminum combination walls
*No Nut bar assembly

== See also ==
<ul style="line-height: 20.7999992370605px;">
<li>[(link to other bot made this year) (Name of other bot made this year)]</li>
</ul>

== Notes: ==

<span style="line-height: 20.7999992370605px">(random joke, optional)</span>

<span style="line-height: 20.7999992370605px">(Naming inspiration, optional)</span>

<span style="line-height: 20.7999992370605px">(Names of original builders)</span>

How to Guide udev

2018-06-14T01:44:56Z

Ndaugherty6:

[[Category:How to Guides]]

===Introduction===
'''udev''' is the system that Ubuntu, among other Linux-based systems, uses to manage devices and the aliases the user uses to access those devices.

'''udev rules''' allow developers and users to give meaningful names to these aliases.

A tutorial on writing a udev rule to name a device can be found here:

[[File:How to write udev rules - Hack a Day.pdf | Tutorial]]

How to Guide Inventor

2018-06-14T01:42:24Z

Ndaugherty6:

[[Category: How to Guides]]
[[Category: Mechanical]]

[http://en.wikipedia.org/wiki/Autodesk_Inventor Inventor], produced by [http://www.autodesk.com Autodesk], is the 3D solid modeling software currently used by the RoboJackets. The software can be downloaded for free at [http://students.autodesk.com http://students.autodesk.com] (you need a valid email address from a college ie. your @gatech.edu address). This guide is based off of Inventor 2008 and 2009. Inventor 2010 still works the same and has the shortcut keys, but has a ribbon style GUI.

Autodesk has released a set of [http://help.autodesk.com/view/INVNTOR/2014/ENU/?guid=GUID-A8795BBB-D723-444D-B36F-81573A6E1022 Essential Skills Videos] that is a great place to start learning.

==Setting Up Inventor==
In order to do anything, you need to setup your project file. By creating this you can more easily keep track of just project X or project Y and have them on the same machine.

To Do This:
# Go to File
# Projects
# Click the new button
# Fill in the requested info
Note: There are many ways to get to the projects window.

Now you will have you new project listed in the project window. However when you start inventor you will not by default be working in it. To make this the default project just double click on your project in the list. Now when you start you will always be working with it.

==Making a Part==
First we need to create a part file. To do this File > New > Select Standard.ipt

===Making a Sketch===
[[Image:Inv_sketch_start.jpg|thumb|left|Starting out a sketch]]
Like AutoCAD (also made by Autodesk) Inventor has many shortcut keys (some of them are the same). To your left you will see two panels. On the top you have Model and on the bottom you have 2D Sketch. The bottom panel will change depending on what you are doing (Note: these are the default locations and these windows are movable). You will also notice beside each title there is a drop down arrow these provide more features which you can explore. Though generally you will not use these additional features.

Generally (by default) the top panel will house info about the current file you are in and the bottom panel will hold commands that you can use to create your product.
<br clear="all" />
====Lines====
To do a line you can hit L and then click around to draw what you need to. To stop drawing lines (along with any other command) hit Esc. By default lines will attempt to orient them selves parallel and perpendicular with other lines.

====Circles====
There is more than one way to make a circle. By default and when you hit C it will make one from the center of the point that you select. To change this click the down arrow beside the circle button.

====More====
You can also create boxes. More importantly there is a trim command short cut X. With trim you could draw a triangle and place a circle on the end of it. Then remove only the lines that you want and end up with an ice cream cone.

Project Geometry is is by far one of the most useful tools (later on once you have more than one file). With this you can bring forward outlines from other parts or features on the same part and create sketches that a driven off of something else. These sketches will automatically update when that something else is changed.

====Dimensioning====
Before we go any further we need to fully dimension our sketch. This keeps it from changing and locks it in place. As of now all of our lines will be green and once we are done they will be black. To get started hit D. (Note: You can auto dimension the sketch however sometimes it is better to manually do it. You may want your sketch to be based off of direction X or Y and keep this or that side more readily adjustable.) You may need to specify its distance from the origin. To do this make the axises visible and project their geometry.

Once you have created a dimension you can edit it by click on it (it will go from black to red while hovering). You can input any formula you want.

A dimension can also be based of off of other dimensions. To do this simply create a dimension like you would normally and edit it. Once the window is up for you to key in a formula or number click on the dimension(s) you want it to be based off of. You can then manipulate them as if they were variables in an equation (which they are).

===Make Features===
In order to make your 2-dimensional sketch into something more tangible you will need to utilize various features depending on your situation. Overtime you will figure out what your situation is and what to do.

====Extrude====
[[Image:Inv_extrude_win.jpg|thumb|right|Normal Extrusion Window in Inventor]]
This makes a perpendicular projection of set length from a selected profile (sketch). To do this hit E. A window will appear with options on how to preform the extrusion.

To preform a Normal Extrusion:
# Hit E
# Select profile or sketch
# Key in distance
# Select direction (Forward, Backward, or 1/2 forward & 1/2 backward)
<br clear="all" />
====Revolve====
[[Image:Inv_rev_win.jpg|thumb|right|Revolve Extrusion Window]]
Produces a rotation of X degrees around a specified axis. You can added a line to your sketch and use it as that rotation axis or use an edge of the sketch.

To preform an Revolved Extrusion:
# Hit R
# Select the profile or sketch
# Select axis of rotation
# Specify extent (Full = 360, To = To a face, To From = From one location to another location, Angel = Specify degree)
<br clear="all" />
====Sweep====

====Loft====

====Hole====
When making holes for a bolted connection, it is better to use the hole tool instead of drawing them into your sketch initially and extruding or doing a cut.
Benefits of using the hole tool include:
* standard hole sizes for bolts
* thread and depth
* finishing options (counter sink, counter bore, etc.)
* easy adjustment of parameters

Other types of holes may be generated using the [[#Normal|extrude]] tool.

====Fillet====

====Chamfer====

===Properties===
[[Image:Inv_iprop_win.jpg|thumb|right|iProperties Window in Inventor]]
Now that you part is complete you are not done! Go to File > iProperties > Physical Tab

Set your material type and hit update. Then apply and close the window. Doing this allows inventor to: a) give you and estimated weight of your robot and b) give you a estimated cg location. Note: If you have a part like fan or an entire assembly like a motor you can weight the thing and then manually key in its mass on that window.

<br clear="all" />

==Assembling Parts==
Now that you have your parts lets put them together to make some sort of subsystem, product, etc. To do this you will need to create an assembly. Note: Assemblies can be composed of parts and other assemblies.

Ideally your robot's assembly structure could look like this:<br/>
#Main Robot Assem
## Drive Train Assem
### Gearbox Assem
#### Gears (Parts)
#### Plates (Parts)
#### Shaft (Part)
## Frame Assem
### Tubes / Angle (parts)
### Bolts (parts)
## Manipulators
## Bumpers

[[Image:Inv_assembly_win.jpg|thumb|right|Constraint dialog in Inventor]]
===Constraints===

Constraints, like in the sketching phase, are used in assembly phase to align parts in the fashion it will resemble in real life. First components must be placed, with the first component as grounded. Then the constraints dialog can be pulled up by hitting the key.

The first tab deals with assembly constraints and it is what we will be working with here. The options here are mate, angle, tangent and insert. They respectively align faces, corners, circular objects and cylinders to other faces, corners, surfaces and holes.

=== Mate ===

[[File:Inv assembly 4.jpg|thumb|left|text-top|upright|Flush with a .2 in offset]] [[File:Inv assembly 2.jpg|thumb|right|text-top|upright|Mate]] Mate is the first option and it comes in two modes, flush and mate. Two surfaces are selected and then they are stuck next to each other when using mate.

Flush (seen left) on the other aligns surfaces or planes with each other. A typical set of constraints use a single mate and two flushes to firmly stick two components to each other in a rigid orientation (three dimensions of movement requires three constraints). Offsets can also be described for additional flexibility in binding components together.

=== ===

=== ===

=== Insert ===

[[File:Inv assembly 5.jpg|thumb|left|text-top|upright|Axial arrows on circular faces when selecting surfaces for insertion]] [[File:Inv assembly 6.jpg|thumb|right|text-top|upright|Axes are aligned in the same direction]] Insert typically inserts a cylindrical object into a hole. The first two selections of the participating circular faces also show an axial arrow.

There is an option to have the arrows oppose each other or point in the same direction. This gives two different types of inserts, so choose the circular face correctly may save time and additional constraints.

Insert constraints have variable offsets as well, and if no offset is specified, then the components are free to slide along the highlighted axis of insertion.

---

== Making your Parts and Assemblies Useful ==

=== Drawing Files ===

'''Drawing files''' (.dwg) in Inventor are essentially 2D schematics of your parts and assemblies, which can be used for presentations, machining guides, and as fleshed out design documents.  We also use drawings as the 2D input for the waterjet.

To add contents to a drawing file, first import the "base view" of each .ipt file for the parts you want to add (right click, then select "base view", then select your file).  Then choose a 2D perspective of the part to display in the schematic.  Some of these perspectives include: Top, Left, Right, Back, and Bottom. For''3D designs'', you will usually show 3 perspectives, the top, the broad side, and the short side (x, y, and z, essentially).  Any unique part of a component or set of components should be highlighted from its most descriptive angle.  It is essential that the drawings give anyone with the schematic enough information to understand and/or physically create the the full part or set of parts.  Essential information may include: a bill of materials, material types, special notes, cut-outs and insets ("details"), and most importantly, your parts' dimensions'''.'''

=== Dimensioning ===

<span style="line-height: 20.8px;">The most important information you can include in a drawing file is its dimensioning.  This is essential for understanding and crafting the parts in your drawing in the real world.  You can annotate most of this information using the Dimension tool, under the "Annotate" section.</span>

<span style="line-height: 20.8px;">Required dimensioning includes:</span>

*<span style="line-height: 20.8px;">the length, width, and height (thickness) of all components</span>
*<span style="line-height: 20.8px;">the radius of all holes </span>
*<span style="line-height: 20.8px;">relative locations of all holes or cuts </span>
**e.g. <span style="line-height: 20.8px;">radius from center, distance from edge</span>
*<span style="line-height: 20.8px;">fillet, chamfer, polygon, and extrude angles</span>
*<span style="line-height: 20.8px;">any pattern details</span>
**<span style="line-height: 20.8px;">e.g. 5 holes over a distance of 5.5 inches</span>

==Appendix==
===Useful Short Cut Keys===
* Inventor Wide
** Zoom to fit = Home
** Look at face = Page Up
** Ending a command = Esc
** Pan = F2 (Hold)
** Zoom = F3 (Hold)
** Rotate = F4 (Hold)
** Cycle Through Views = F5
** Isometric View = F6
* Parts
** 2D Sketches
*** Line = L
*** Circle = C
*** Trim = X
*** Dimension = D
** Modeling
*** Extrude = E
*** Revolve = R
*** Fillet = F
*** Mirror = Ctrl + Shift + M
*** Circular Pattern = Ctrl + Shift + C
*** Rectangular Pattern = Ctrl + Shift + R
*** Loft = Ctrl + Shift + L
*** Sweep = Ctrl + Shift + S
* Assemblies
* Drawings

===Mouse Use===
* Pan = Center Click
* Zoom in / out = Scroll up / down

===Changing Units===
* When entering a dimension, simply type in the abbreviation for the unit. Inventor will convert automatically.
* To change the entire part, click Tools>Document Settings. On the Units tab, select your new units appropriately.

===Resources===
*[http://help.autodesk.com/view/INVNTOR/2014/ENU/?guid=GUID-A8795BBB-D723-444D-B36F-81573A6E1022 Essential Skills Videos]
*[http://help.autodesk.com/view/INVNTOR/2014/ENU/ Autodesk Inventor WikiHelp]
*[http://www.cadsetterout.com/inventor-tutorials/101-autodesk-inventor-productivity-tips/ Productivity Tips]

Tool Guide: Injection Molder

2018-06-14T01:40:56Z

Ndaugherty6:

[[Category:How to Guides]]

{| id="go" style="color: #ffffff; width:20em; margin:0 0 0.5em 1em; float: right;"
! align="center" bgcolor="#808080" colspan="3" |
|-
|align="center" colspan="3"|[[File:IMG_4316.jpg|200px|Injection Molder]]
|-
! align="center" bgcolor="#808080" colspan="3" |
|-
!align="left" valign="top"|<font color="#000000">Something</font>
|colspan="2" valign="top"|<font color="#000000">More Something</font>
|-
|}

The machine is pretty simple... just a few buttons.

==Needed Items==
#Adapter that connects the nozzle to your mold... it's blue
#Plastic beads
#Mold
#Gloves
#Hotplate

==Steps==
# Turn on the machine and make sure there is plastic in it.
## The switch is on the left side.
## The plastic is held on the right. There is a gate, so lift it and fill that area with the beads.
# Set the heating temperatures for the nozzle ad barrel. These are specified on the front of the machine, and they are entered into the little screens on the left.
# Check clamp force..... still figuring out how to choose the right amount
# Heat up your mold's parts and the adapter on the hotplate. Heat them until the mold side is warm to the touch, this isn't an exact science. This just prevents the plastic from cooling to fast or clogging parts of the mold.
# Place optional supporting material, the mold, and the adapter on the table to test table height and how the adapter is aligned with the nozzle. There is a divot in the top of the adapter that interfaces with the nozzle. When you place the adapter on the mold, it should look like a T.
# Check to make the table will be at the proper height for injecting. Proper height is the height where when raised, the arm will click and the adaptor connects well with the nozzle.
## Table height can be adjusted on the side with a hex key. Supporting material can be added or removed under the mold to adjust the height.
## On the bottom left, move the black latch behind the red button and push to raise the table. The arm should make a clicking noise and the adapter should have a tight fit with the nozzle.
## To lower the table after the button has been pressed, pull the button back out.
# Adjust the position of the mold so it is aligned with the nozzle.
# Push the red button to raise the table and when it is raised, push the black button on the right to inject the plastic.
## Release the black button when the hissing subsides, or you see plastic leaking from the sides.
## Pull the red button back out to lower the table.
# Take the mold off of the table, and pull the part out of it.
# Clean parts(drill out plastic), reheat as needed, and repeat.

==Notes and Troubleshooting==
* If plastic consistently leaks out the sides of the mold, check your clamp force and if the arm locks.
* If it just wont work and you don't know why, check to make sure the ram is raising all the way in the part where you insert the plastic beads.
* It won't work if the gate on the side is open.
* ABS is easier to mold than Delrin.
* There are other buttons on the front we don't know how to use.

How to Guide External Mail List

2018-06-14T01:39:38Z

Ndaugherty6:

[[Category:How to Guides]]
[[Category:Public Relations]]

{| id="go" style="color: #ffffff; width:20em; margin:0 0 0.5em 1em; float: right;"
!align="center" bgcolor="#808080" colspan="3"|RoboJackets Email List
|-
|align="center" colspan="3"|[[Image:Robojackets.jpg|200px|RobJackets Email List]]
|-
!align="center" bgcolor="#808080" colspan="3"| Hosted on GT Lists
|-
|}

External mailing list can be used to post messages to all the students in a particular school or college.
====Needed Items====
#Internet
#Mozilla Firefox
#E-Mail account (Has to be a GT account)
#Must be a member of the list

====Lists====
=====ECE=====
news_grads@ece.gatech.edu and news_ugrads@ece.gatech.edu
=====Robotics=====
robotics_all@cc.gatech.edu
====Posting Items====
#Send the e-mail you'd like to post to the list
#Wait for moderator approval
#World Domination!

==Links==
* http://www.sympa.org/

How to Guide Battlebots

2018-06-14T01:37:21Z

Ndaugherty6:

[[Category:How to Guides]]
[[Category:BattleBots]]

== Basic Guide to 3lbers ==

== Ring Spinners ==

Examples: [[Qti]],[[Smitti Werbenjagermanjensen]]

== Drum Spinners ==

Examples: [[Radii]] [[Misti]]

A robot that does damage with a cylinder attached to the front that has teeth on it. Two

== Shell Spinner ==

Examples: [[Shelli]]

== Vertical Spinner ==

Examples: [[Dat Boi]]

== Horizontal Spinner ==
Examples: [[Ki]] [[Schwifti]]

Hough Transform

2018-06-14T01:36:33Z

Ndaugherty6:

[[Category:How to Guides]]
[[Category:IGVC]]

This algorithm is implemented as the '''LinearHoughTransform2''' filter for the [[ImageFilterDemo]] program.

A good description is on [http://homepages.inf.ed.ac.uk/rbf/HIPR2/hough.htm this page].

Wikipedia also has its own [http://en.wikipedia.org/wiki/Hough_transform Hough Transform article].

== Pros ==
* Able to detect dashed lines

== Cons ==
* Designed for detecting ''straight'' lines, making it tricky to use for curved lines - which will probably be common
* Designed to detect ''lines'' as opposed to detecting ''line segments''
* Computationally expensive (when compared to simple filters)

== Input ==
* A binary/grayscale image hilighting the line-pixels in the input image

== Output ==
* A list of the positions/orientations of the lines detected in the input image

== Issues with the Current Implementation ==
* The current implementation does not work well with input images containing no lines. This, however, is due to the way that Hough output is thresholded - the Hough algorithm itself still works well.

== Pictures ==
[[Image:LinesOnBlack.png|thumb|left|150px|Two solid straight lines]]
[[Image:LinesOnBlackWithHoughTransform.png|thumb|left|150px]]
[[Image:LinesOnBlackWithIdentifiedLines.png|thumb|left|150px]]
{{clr}}

[[Image:CurvyLine.png|thumb|left|150px|One solid curvy line]]
[[Image:CurvyLineAsHoughSpace.png|thumb|left|150px|]]
[[Image:CurvyLineWithIdentifiedLines.png|thumb|left|150px|]]
{{clr}}

[[Image:TwoSolidCurvyLines.png|thumb|left|150px|Two solid curvy lines]]
[[Image:TwoSolidCurvyLinesAsHoughSpace.png|thumb|left|150px|]]
[[Image:TwoSolidCurvyLinesWithIdentifiedLines.png|thumb|left|150px|]]
{{clr}}

[[Image:TwoDashedCurvyLines.png|thumb|left|150px|Two dashed curvy lines]]
[[Image:TwoDashedCurvyLinesAsHoughSpace.png|thumb|left|150px|]]
[[Image:TwoDashedCurvyLinesWithIdentifiedLines.png|thumb|left|150px|]]
{{clr}}

[[Image:NoLines.png|thumb|left|150px|No lines at all! Just some salt noise.]]
[[Image:NoLinesAsHoughSpace.png|thumb|left|150px|Yikes!]]
[[Image:NoLinesWithIdentifiedLines.png|thumb|left|150px|Double yikes! The robot would probably panic upon seeing this. :P]]
{{clr}}

Homecoming car

2018-06-14T01:34:35Z

Ndaugherty6:

[[Category:Core]]

Welcome! You've found yourself on the page for the Homecoming Car.

[[File:10644703 601719963291031 2139300614443510723 o.jpg|300px|10644703 601719963291031 2139300614443510723 o.jpg]]

== History ==
The Homecoming Car, a.k.a. the Buzzmobile, was a joint effort between The Agency and RoboJackets. Commissioned and sponsored by the CoC's [https://www.cc.gatech.edu/student-life/gt-computing-community/oec-office Office of Outreach, Enrollment, and Community], was an autonomous parade float modeled after the Ramblin' Wreck for Georgia Tech's Wreck Parade homecoming event.

The Homecoming Car was decommissioned in the spring of 2018 in a joint decision among RoboJackets, The Agency, and the OEC, citing ongoing difficulties with storage space constraints and accessibility.

== Hardware ==
The Homecoming Car is a nearly full sized replica of the Wreck. It has a body made of plywood supported by a steel frame. Many of the components on the car overlap with components found on a standard FRC robot. The car has a 6-CIM chain drive train. The CIM motors are controlled by Victor motor controllers from Cross the Road Electronics. The victors receive their messages from an on board Arduino Uno. The Arduino also talks to the pneumatic break on the car.

== Software ==
The code powering the Homecoming Car can be found on [https://www.github.com/gtagency/buzzmobile Github]. This is also where documentation on operating the car can be found.

The majority of the code running the robot is written with Python and ROS, although there are some nodes written in C++.

Hall of Robots

2018-06-14T01:33:34Z

Ndaugherty6:

[[Category:Core]]
[[Category:IGVC]]
[[Category:RoboCup]]
[[Category:BattleBots]]
[[Category:Outreach]]
[[Category:RoboRacing]]

The Hall of Robots is a record of the robots created by the RoboJackets. From this page one might find links to technical information relating to each robot.

== 2000 ==

== 2001 ==

== 2002 ==

=== FIRST ===

== 2003 ==

=== IGVC ===

;BuzzBot

BuzzBot was created for the [[Competitions#2003 - Buzzbot|2003 IGVC Competition]].

*[[File:BuzzBotDesignReport.pdf|RTENOTITLE]]

=== FIRST ===

;D.O.T.

== 2004 ==

=== IGVC ===

;BuzzBot II

BuzzBot II was created for the [[Competitions#2004 - Buzzbot II|2004 IGVC Competition]].

*[[File:BuzzBotIIDesignReport.pdf|RTENOTITLE]]

=== FIRST ===

;C.C.

== 2005 ==

=== FIRST ===

;GNAT

== 2006 ==

=== IGVC ===

;Trixxie

Trixxie was created for the [[Competitions#2006 - Trixxie|2006 IGVC Competition]].

*[[Trixxie Robot Guide]]
*[[File:TrixxieDesignReport.pdf|RTENOTITLE]]

=== FIRST ===

;C4

== 2007 ==

=== BattleBots ===

;Bambi

=== IGVC ===

;Candi

Candi was created for the [[Competitions#2007 - Candi|2007 IGVC Competition]].

*[[Candi Robot Guide]]
*[[File:CandiDesignReport.pdf|RTENOTITLE]]

=== FIRST ===

;Slick Rick

=== RoboCup ===

== 2008 ==

=== BattleBots ===

;Bambii

=== IGVC ===

;Candii

Candii was derived from Candi for the [[Competitions#2008 - Candii|2008 IGVC Competition]].

*[[Candii Robot Guide]]

== 2009 ==

=== IGVC ===

;Candiii

Candiii was derived from Candii for the [[Competitions#2009 - Candii|2009 IGVC Competition]].

*[[Candiii Robot Guide]]

== 2010 ==

=== IGVC ===

;Jeanni

Jeanni was created for the [[Competitions#2010 - Jeanni|2010 IGVC Competition]]

== 2011 ==

=== BattleBots ===

[[Soafi|Sum of All Fears (SOAFi)]]

=== IGVC ===

;Roxi

Roxi was created for the [[Competitions#2011 - Roxi|2011 IGVC Competition]]

== 2012 ==

=== BattleBots ===

;[[Mandi|Metal, Armor, and Death Incarnate (MANDi)]]

=== IGVC ===

;Roxii

Roxii was derived from Roxi for the [[Competitions#2012 - Roxii|2012 IGVC Competition]]

== 2013 ==

=== BattleBots ===

;[[Mandi|Metal, Armor, and Death Incarnate (MANDii)]]
;[[Sindi|Sindi]]
;MOAR PIT PASSES! (MPP)
;[[Cathi]]

=== IGVC ===

;Misti

Misti was created for the [[Competitions#2013 - Misti|2013 IGVC Competition]].

== 2014 ==

== 2015 ==

=== BattleBots ===

;[[Emmi]]
;[[Vicki]]
;[[Flippi/MrWedge|Flippi/Mr Wedge]]
;[[Smitti_Werbenjagermanjensen|Smitti Werbenjagermanjensen]]
;[[Group_5|Group 5]]
;[[Melani]]
;[[Kenni]]

FASET

2018-06-14T01:31:05Z

Ndaugherty6:

[[Category:How to Guides]]

This article is intended to assist RoboJackets members in effectively utilizing FASET as a Recruiting tool.

== Background info (FASET 2016) ==

There were a total of 9 FASETs in 2016: 1 summer freshman, 7 regular, and 1 transfer. The last two FASETs are the largest due to being reserved for students far away from tech.

== Registering ==

Registration info for FASET is distributed via OrgSync to leaders in April. If sign-up is not completed in time, there is a waitlist.

== What to Bring ==

#Robots
#Banner / Table Runner
#Gaffers Tape
#Informational flyers or brochures
#Laptops for completing the sign-up form (See below)
#Paper Registration sheets as backup for laptops (and pens)
#Water - It's hot out!

== The Sign Up form ==

Create a single Google Form that is branded heavily that asks the following questions:

#First and last name (required)
#Email (required) (textbox with email validation)
#Did you head about RoboJackets before FASET? (radio buttons)
#*Yes
#*No
#If so, how? (Checkboxes)
#*Campus Tour
#*From a current RoboJackets Member
#*From a Friend not in RoboJackets
#*Social Media (Facebook, Twitter, YouTube, etc)
#*Website (RoboJackets.org)
#*FRC Event
#*FTC Event
#*VEX Event

Group 5

2018-06-14T01:30:46Z

Ndaugherty6:

[[Category:BattleBots]]
[[Category:BeetleWeights]]

{| class="wikitable" align="right"
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Group5
|-
! scope="row" colspan="2" | [[File:Group5.jpg|frameless|right|480x360px|Decapitator]]
|-
! scope="row" style="text-align:left" | Year Of Creation
| {{{year|2014-2015}}}
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Versions
|-
! scope="row" style="text-align:left" | Current Version
| {{{currver|1.0}}}
|-
! scope="row" style="text-align:left" | Update Year
| {{{updyr|2014-2015}}}
|-
! scope="row" style="text-align:left" | Wins/Losses
| {{{winloss|0/2}}}
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Information and Statistics
|-
! scope="row" style="text-align:left" | Weight Class
| {{{wc|BeetleWeight}}}
|-
! scope="row" style="text-align:left" | Weapon Class
| {{{weapc|Bent Bar Spinner}}}
|-
! scope="row" style="text-align:left" | Combined Wins/Losses
| {{{winloss|0/2}}}
|-
! scope="row" style="text-align:left" | ("Temporary")
| {{{TBA|("Temporary")}}}
|-
! scope="row" style="text-align:left" | ("Temporary")
| {{{TBA|("Temporary")}}}
|}

== Competitions ==
<ul style="line-height: 20.7999992370605px;">
<li>
=== [[Motorama 2015|Motorama 2015]] ===

*Results:
**Bracket Style:
***[http://youtu.be/fxYOFSVNv64?list=PLa4DDbMiSUTWb6HBYu5YBsfiZMhEr4SHY Loss vs Thunder Child]
****Was held back by the ram design of the opponent
****Top plate flew off
***[http://youtu.be/q-YmRDJZhGw?list=PLa4DDbMiSUTWb6HBYu5YBsfiZMhEr4SHY Loss vs Gemini]
****Top plate flew off immediately
****Was flipped over, and lost by KO</li>

== Version ==

=== V1 ===

Created By: 

{| border="1" cellspacing="1" cellpadding="1" style="line-height: 20.7999992370605px; width: 500px;"
|-
| Drive Motors
| <br/>
|-
| Drive Motor Controllers
| <br/>
|-
| Weapon Motor
| <br/>
|-
| Weapon Motor Controllers
| <br/>
|-
| Reciever
| <br/>
|-
| Remote Control
| <br/>
|-
| Battery
| <br/>
|-
| (OTHER:)
| <br/>
|}

==== Problems: ====

==== Good aspects: ====

==== Changes/Improvements: ====

*Improved Structural Connection Between Top and Bottom

== See also ==
<ul style="line-height: 20.7999992370605px;">
<li>[http://wiki.robojackets.org/w/Emmi Emmi]</li>
<li>[http://wiki.robojackets.org/w/Vicki Vicki]</li>
<li>[http://wiki.robojackets.org/w/Flippi/MrWedge Flippi/MrWedge]</li>
<li>[http://wiki.robojackets.org/w/Smitti_Werbenjagermanjensen Smitti Werbenjagermanjensen]</li>
</ul>

== Notes: ==

*Group 5 used Struggle*

Grizzli

2018-06-14T01:27:33Z

Ndaugherty6:

[[Category:BattleBots]]
[[Category:BeetleWeights]]

{| class="wikitable" align="right"
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Grizzli
|-
! scope="row" colspan="2" | [[File:(Image filename)|frameless|right|480x360px|(Highlight text)]]
|-
! scope="row" style="text-align:left" | Year Of Creation
| {{{year|20XX-20XX}}}
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Versions
|-
! scope="row" style="text-align:left" | Current Version
| {{{currver|X.X}}}
|-
! scope="row" style="text-align:left" | Update Year
| {{{updyr|20XX-20XX}}}
|-
! scope="row" style="text-align:left" | Wins/Losses
| {{{winloss|X/X}}}
|-
! scope="row" colspan="2" style="background-color:#FFFF99" | Information and Statistics
|-
! scope="row" style="text-align:left" | Weight Class
| {{{wc|BeetleWeight}}}
|-
! scope="row" style="text-align:left" | Weapon Class
| Vertical Bar Spinner
|-
! scope="row" style="text-align:left" | Combined Wins/Losses
| {{{winloss|X/X}}}
|-
! scope="row" style="text-align:left" | Weapon Speed
| 0 RPM
|-
! scope="row" style="text-align:left" | ("Temporary")
| {{{TBA|("Temporary")}}}
|}

Flippable Vertical Bar Spinner

== Competitions ==

=== [[Motorama 2018]] ===

*Results:
**Bracket Style:
***[(Video Link) (result) vs (opponent)]
****(notes)
****(observations))

== Version ==

=== Grizzli V1.0 ===

Created by: <span style="color: rgb(0, 0, 0); font-family: sans-serif; font-size: 12.6999998092651px; line-height: 20.7999992370605px;">(Names of Builders/Group Members of aforementioned version of bot)</span>

{| border="1" cellspacing="1" cellpadding="1" style="width: 500px;"
|-
| Drive Motors
| <span style="color: rgb(0, 0, 0); font-family: arial, sans, sans-serif; line-height: normal; white-space: pre-wrap;">(Drive Motor Name)</span><br/>
|-
| Drive Motor Controllers
| (Drive Motor Controller Name)
|-
| Weapon Motor
| Turnigy 2836 Brushless 450 Size Heli Motor 3700KV
|-
| Weapon Motor Controllers
| HobbyKing 30A BlueSeries Brushless Speed Controller
|-
| Receiver
| <span style="line-height: 20.7999992370605px;">Hobby King 2.4Ghz Receiver 6Ch V2</span><br/>
|-
| Remote Control
| <span style="line-height: 20.7999992370605px;">Hobby King 2.4Ghz 6Ch Tx and Rx V2</span><br/>
|-
| Battery
| (Battery Name)
|-
| (OTHER:)
| <br/>
|}

==== Problems ====

*HDPE walls bowed during assembly, causing parts to rub
*Not enough room for weapon between inner plates
*Center of mass was too far forward, leading to low traction for wheels
*Nut bar assembly took up too much space

==== Good aspects ====

*(List of good aspects, 1 per bullet point)

==== Changes/Improvements ====

*HDPE-Aluminum combination walls
*No Nut bar assembly

== See also ==
<ul style="line-height: 20.7999992370605px;">
<li>[(link to other bot made this year) (Name of other bot made this year)]</li>
</ul>

== Notes: ==

<span style="line-height: 20.7999992370605px">(random joke, optional)</span>

<span style="line-height: 20.7999992370605px">(Naming inspiration, optional)</span>

<span style="line-height: 20.7999992370605px">(Names of original builders)</span>

About Trello

2018-06-14T01:25:46Z

Ndaugherty6:

[[Category:How to Guides]]

Trello is a project managment tool, which allows you to keep track of tasks, see what tasks others are working on, and have a general overview of all tasks.

How to use Trello:

#Sign up for a Trello account here: [https://trello.com/signup https://trello.com/signup]
##You may create a new Trello account or use your Google account for logging in.
#Ask your PM to add you to your subteam's Trello board. They will need the email you used to sign up or your gmail address if you signed in with Google.
#For detailed instructions, follow Trello's getting started guides:
#* [https://trello.com/guide/board_basics.html Board Basics]
#* [https://trello.com/guide Guide]

General Tips:

#When you start a large project, it's usually best to have a Trello card for it. Create this Trello card in the subteam board it applies to, and under the correct category within that board.
#Add members who are working with you on this project to the card.
#Add labels that apply to the card's contents.
#If a card has multiple parts to it, you can create a checklist for each subtask, and check them off to show progress.
#Add a due date to the card. For events, this is the start time of the event.
#When you have completed the task, archive the Trello card.

Google Meet

2018-06-14T01:25:33Z

Ndaugherty6:

[[Category:How to Guides]]
[[Category:Information Technology]]

Google Meet is a more business-oriented edition of Hangouts available to G Suite customers, including RoboJackets. We use it for larger remote meetings, including Core meetings during the summer. '''Note that you will need a [[G Suite Accounts | RoboJackets G Suite account]] to set up a meeting.'''

==Comparison to Hangouts==
*Google Meet supports up to 25 participants compared to 10 for Hangouts.
*Users without a RoboJackets G Suite account must be explicitly invited to the meeting in advance, or ask to join and then be approved by someone with a G Suite account. With Hangouts, anyone can join using the link.
*Any participant can mute any other participant by clicking the microphone icon next to their avatar.
*Users may join via phone using the dial-in number and PIN provided.

==How to schedule a meeting in advance==
#Visit [https://calendar.robojackets.org calendar.robojackets.org] and create an event.
#In the '''Video call''' section, click "Add video call".
#Add guests using the right sidebar. Note that you should only add Gmail addresses, otherwise they won't be able to join directly.
#Click Save.
Guests will be able to view the meeting the day of at [https://meet.google.com meet.google.com]. They'll also be to join the meeting using the direct URL or meeting code without approval.

==How to start an impromptu meeting==
Visit [https://meet.google.com meet.google.com] and click "Start a new meeting". You can then distribute the link to participants. Note that unless they have a G Suite account, you will have to manually approve them as they join - you'll hear a ding and [[:File:Google_Meet_confirmation_prompt.png|a notification box]] will appear.

Google Meet

2018-06-14T01:24:14Z

Ndaugherty6:

Google Meet is a more business-oriented edition of Hangouts available to G Suite customers, including RoboJackets. We use it for larger remote meetings, including Core meetings during the summer. '''Note that you will need a [[G Suite Accounts | RoboJackets G Suite account]] to set up a meeting.'''

==Comparison to Hangouts==
*Google Meet supports up to 25 participants compared to 10 for Hangouts.
*Users without a RoboJackets G Suite account must be explicitly invited to the meeting in advance, or ask to join and then be approved by someone with a G Suite account. With Hangouts, anyone can join using the link.
*Any participant can mute any other participant by clicking the microphone icon next to their avatar.
*Users may join via phone using the dial-in number and PIN provided.

==How to schedule a meeting in advance==
#Visit [https://calendar.robojackets.org calendar.robojackets.org] and create an event.
#In the '''Video call''' section, click "Add video call".
#Add guests using the right sidebar. Note that you should only add Gmail addresses, otherwise they won't be able to join directly.
#Click Save.
Guests will be able to view the meeting the day of at [https://meet.google.com meet.google.com]. They'll also be to join the meeting using the direct URL or meeting code without approval.

==How to start an impromptu meeting==
Visit [https://meet.google.com meet.google.com] and click "Start a new meeting". You can then distribute the link to participants. Note that unless they have a G Suite account, you will have to manually approve them as they join - you'll hear a ding and [[:File:Google_Meet_confirmation_prompt.png|a notification box]] will appear.

[[Category:How to Guides]]
[[Category:Information Technology]]