FTC Teams Drive Train Process

This post is being provided to provide an overview of the process used by the drive train sub-teams of FTC 329: Chicago Squires and FTC 2813: Teen Girl Squad.

Each subteam discussed several options for the drive train, each choosing the approach they preferred.  See team specific posts for their decision process and progress.

Building Process

Validate components

1. Build prototype chassis to become familiar with Tetrix components
   
2. FTC 329 mounted 2 motors for indirect drive
   
3. FTC 2813 mounted 4 motors for direct drive
   
4. Simulate game play by moving prototype chassis and drive train over various surfaces and down mock-up of ramp
   
5. Connect to control systems to test drivability of prototype
   
6. Analyze prototype for potential issues (movement restrictions, ease of maintenance, etc)
   
7. Analyze 329 prototype (2 wheel indirect drive) and 2813 prototype (4 wheel direct drive) for drivability and compliance with team's design goal(s)
   

Design & Build Drive Train

1. Identify design goals
   
2. Determine final geometry for chassis design with manipulator sub-team
   
3. Determine drive train configuration
   
4. Generate shopping lists for any additional parts needed
   
5. Identify any fabrication needs for custom parts (using aluminum and/or polycarbonate)
   
6. Decide on chassis design with integration and manipulator sub-teams
   
7. Rebuild chassis and drive train to reflect team's decisions
   
8. Connect to control system to test drivability
   

Quality Assurance

1. Validate designed drive train agains design goals and competition constraints
   
2. Test, Analyze, Re-design or tune design as needed until final product meets design criteria
   
3. Self-inspect using inspection checklist; making corrections as needed until "inspection ready"
   

Documentation

1. Fully document the "as built" design with annotated drawings (label all control points!)
   
2. Glue in team journal and add to team competition binder 
   
3. Create 3 copies of BOM, one for team journal, one for team binder, and one for judges
   

Prepare for Competition

1. Create drive train toolkit (maintenance tools, pre-match check list, drive train binder or folder, completed self-inspection checklist)
   
2. Go through pre-match checklist to ensure mechanical stability of drive train
   

We are now competition ready!

FTC 2813 - Teen Girl Squad Overview

This blog is being provided to provide an online home for tracking the progress of the Teen Girl Squad FTC team, a subset of the Chicago Knights Robotics Team. 

Team Members:

Chassity B, Emmanuel Christian School, Chicago

Capri Hawkins, Bronzeville Scholastic Institute, Chicago

Remel H, Emmanuel Christian School, Chicago

Porscha M, Lindblom Math & Science Academy, Chicago

Lydia M, Lindblom Math & Science Academy, Chicago

Monica M, Walter Payton College Prep

Jazmyn T, Lindblom Math & Science Academy, Chicago

Team Leader: Jackie Moore, Agape Werks

Team Sponsor(s): Agape Werks, Chicago Knights

FTC LabView Programming

This post is being provided as an overview and to track the programming progress of the FTC teams using the LabView software.

Software Validation

1. Install LabView Software
   
2. Install FTC Update
   
3. Verify initial software install with Sample VI
   

Learn TeleOperated Coding

1. Install 2 Joystick Sample VI
   
2. Validate and understand supplied blocks
   
3. Create custom version for testing modifications
   
4. Validate and document modifications
   
5. Install 4 Joystick Sample VI
   
6. Validate
   
7. Create Custom version for testing modifications

Learn Sensor Coding

1. Install Sensor Sample VI
2. Validate and understand supplied blocks
3. Create custom version for testing modifications
4. Validate and document modifications
5. Install Encoder Sample VI
6. Validate and understand supplied blocks
7. Create custom version for testing modifications
8. Validate and document modifications

Learn FTC Competition Template

1. Install FTC Template VI
   
2. Use simple pre-validated VIs to test and understand case controls (eg play sound 1 if autonomous, else sound 2)
3. Replace "sound 2" with 4 Joystice VI (either sample or fully validated custom version)
   
4. Validate above modified VI
   
5. Replace "sound 1" with simple "move forward VI"
   
6. Validate above modified VI
   
7. Competition FTC Template Validation Complete
   

Create custom solutions for your team

Teleoperated

1. Determine desired movements for drive train
   
2. Create TeleOperated VI and validate
   
3. Determine desired movements for manipulator
   
4. Update TeleOperated VI and validate
   

Autonomous

1. Create flow chart of desired autonomous movements
   
2. Create Autonomous VI(s) shell(s)
   
3. Add and validate blocks one LUW at a time until done
   

Final Competition Preparation Steps

1. Validate code one more time.
2. Save VI with meaningful name including team number (eg FTC1739_FaceOff)
   
3. Save all relevant VIs in team specific folder on master desktop (eg folder name: FTC1739_Package.081213
   
4. Create zip file and distribute to all of programming team
   
5. Place zip file on the team USB drive
   
6. Document code within LabView
   
7. Upload validated code from NXT to team USB drive for backup (cannot be modified)
   
8. Print copy for team's journal (glue it on one of the journal pages) and copy for team competition binder
   
9. Create a matrix of all inputs/outputs, put in team journal & in team competiton binder
10. Prepare programming toolkit (USB drive, programming notebook/folder, USB cord, etc)

We are now competition ready!