1
Phoenix 4533
2
Table of Contents
Page Number | Design Process Steps |
3-7 | Define the Problem |
8-11 | Research |
12-17 | Brainstorm & Conceptualize |
18-27 | CAD and Prototype |
28-35 | Improve, Select, and Finalize |
36-37 | Final Build Season Solution |
38-46 | Analyze and Improve after Anderson |
47-48 | Final Post-Anderson Solution |
49-58 | Analyze and Improve after Charleston |
59-60 | Final Post-Charleston Solution |
Define the Problem
3
4
Define the Problem : Kickoff
Robot restrictions
Best/quickest way to score points?
Best way to earn ranking points/coopertition points?
Best way to make our team attractive during alliance picks?
Recommendations:
5
Award | Awarded For… | # of Points |
Winning Point | Winning | 2 |
Melody | at Least 18 Amp+Speaker points | 1 |
Melody (coopertition) | at Least 15 Amp+Speaker points | 1 |
Ensemble | At least 10 stage Points and 2 robots onstage | 1 |
Coopertition | Both Teams must press the coopertition button after scoring I note | 1 |
Location | Auto Points | Teleop Points |
Leave | 2 | |
Amp Note | 2 | 1 |
Speaker Note | 5 | 2 |
Amplified Speaker Note | | 5 |
Stage Park | | 1 |
Onstage | | 3 |
Onstage Spotlit | | 4 |
Harmony | | 2 |
Note in Trap (one per trap) | | 5 |
Define the Problem : Kickoff
We created a chart with the points and awards available for different requirements. This is helpful as it is easier to look at all the information in one spot.
6
Whole Team Debate
Recommendations:
Define the Problem : Kickoff
7
Week | 2024: Crescendo Build Season Agenda | |
Jan 6-13 | Define the Problem, Brainstorm & Research, CAD & Prototype Prototype Presentations Saturday morning | |
Jan 15-20 | Build and Code first iteration of Chassis | |
Jan 22-27 | Build and Code first iteration/ Test and Improve Chassis | |
Jan 29 - Feb 3 | Test and Improve Shooter, Floor pickup, Amp, Climber | |
Feb 5-10 | Test and Improve all | |
Feb 12-17 | Test and Improve all | |
Feb 19-24 | Test and Improve all | |
Feb 26 - Mar 2 | Final Iteration & Drive Practice | |
March 4-9 | Drive Practice - Load In - Anderson (March 7-9) | |
Define the Problem : GANTT Chart
6
Research
8
9
Research: Field Elements
Speaker & Subwoofer
6’6” off the ground
2 AprilTags, 1 centered and one offset
The subwoofer lights show the amplification countdown
Stage: ^^^Different chain heights diagram ^^^
Lowest possible point is 28.5 inches off the floor
10
Research: Field Elements
Amp
11
Research: Field Setup and Scoring
We used 4481’s Unofficial Cheat sheet to help us understand the best way to score match points and ranking points in the qualification matches. This helped us to visualize the Crescendo field and the placement of notes on the field.
This helped drive our team’s decision to focus on scoring in the Speaker and Amp and climbing on the Stage, and to ignore the Trap.
Brainstorm and Conceptualize
12
13
Brainstorm & Conceptualize: Chassis
Ideas & Sketches for Chassis: Morgan and Aiden
14
Brainstorm & Conceptualize: Intake and Shooter
Intake and Shooter Ideas & Design Drawings - Made by Evan, Alex, and Luke
We came up with the idea to intake under the bumper because it would intake all in one fluid motion and less prone to damage.
15
Brainstorm & Conceptualize: Intake and Shooter
Intake and Shooter ideas & sketches -
Made by Evan, Alex, and Luke
16
Brainstorm & Conceptualize: Amp Flipper
Amp Flipper Ideas & Drawings -
Made by Duru, Nirval, and Chloe
17
Brainstorm & Conceptualize: Climber
Ideas/sketches by Connor and Maria
CAD and Prototype
18
19
CAD and Prototype: Chassis
CAD of Chassis by Morgan, Aiden and Charlie
20
CAD and Prototype: Intake and Shooter
CAD and Prototype of Intake and Shooter - Made by Evan and Luke
21
CAD and Prototype: Intake and Shooter
CAD and Prototype of Intake and Shooter - Made by Evan and Luke
22
CAD and Prototype: Intake and Shooter
CAD and Prototype of Intake and Shooter - Made by Evan and Luke
23
Amp Flipper CAD drawings, prototypes and final iteration - Made by Duru, Nirval, and Chloe
CAD and Prototype: Amp Flipper
24
Amp Flipper CAD drawings, prototypes and final iteration - Made by Duru, Nirval, and Chloe. It was Chloe’s first time actually doing CAD on the bot, and any CAD at all! Learned a lot about Onshape’s platform.
CAD and Prototype: Amp Flipper
25
CAD and Prototype: Climber
Hook Design Drawings, CADs, and prototypes - Made by Connor and Maria
26
CAD and Prototype: Climber Hooks
Prototypes and Final Hook Design - Made by Connor and Maria
27
CAD and Prototype: Climber
Climber sub-assembly
Custom modifications designed, CAD-ed, and built by Connor and Maria
Improve, Select, and Finalize
28
29
Improve, Select, and Finalize: Chassis
Swerve chassis built by Morgan, Charlie, and Aiden
30
Improve, Select, and Finalize: Chassis
Swerve drive code by Alex.
Don’t ask Alex about PID values.
Just don’t. ;-)
Swerve chassis CAD and Build - Morgan, Aiden and Charlie
31
Test and Improve: Intake and Shooter
Shooter tests run by Evan, Luke, and Drake (code).
32
Improve, Select, and Finalize: Intake and Shooter
Intake and Shooter built by Evan, Luke, and Ace
←Evan and Ace with GAME FACES ON.
Evan and Ace losing it and laughing. :) →
33
Improve, Select, and Finalize: Amp Flipper
Amp Flipper - Made by Duru, Nirval, and Chloe
Duru pointed out that a separate Amp sub-assembly could still score if something happened to our Intake, Lift, and/or Shooter.
34
Improve, Select, and Finalize: Climber
Climber first iteration:
Build led by Connor and Maria
35
Improve, Select, and Finalize: Climber
CAD and Custom Parts - Made by Evan, Connor, Morgan, Finn, Duru, and Luke
Final
Build Season Solution
36
37
Final Build Season Solution
←Amp Flipper Design and CAD by Duru, Nirval, Chloe & Finn
Intake, Lift and Shooter Design and CAD by Evan, Luke & Finn →
←Climber Design and CAD by Connor, Maria, and Finn
Code written by Alex, Drake, Ace, and Robert
^ Chassis Design and CAD by Morgan, Aiden, & Finn
Analyze and Improve
(After PCH Anderson District Event)
38
39
Analyze and Improve: Shooter
At our first event in Anderson, SC, our Note shooter was occasionally shooting low. We originally had high-speed wheels on one side and low-speed on the other.
We decided to add power to the shooter to help it shoot more consistently.
We upgraded to high speed wheels on BOTH sides. Both sets of wheels got their own high-speed motor without a gear-reduction.
Modifications led by Evan and Luke.
Before:
After:
40
Analyze and Improve: Vision Code
Drake made a Note- detection helper to allow the robot code to easily aim and trigger our intake, reducing our cycle time from pick-up to shoot.
Note Detection
Code
41
Analyze and Improve: Amp Flipper
At Anderson our Source Human Player could not send Notes into our Amp Flipper if Bot-hoven was not perfectly lined up.
In addition to writing vision code to use April tags to line the robot up (see next page), we CAD-ed up ‘cups’ that widened the “catch” opening of our Amp Flipper.
Before
After
Aiden, Duru, and Nirval modified our Amp-Flipper
42
Analyze and Improve: Vision Code
After Anderson Drake improved our vision code so that it would check on camera status to more easily diagnose problems with the cameras.
This made the system more reliable and robust while improving position accuracy.
AprilTag code
43
Analyze and Improve: Climber
At our first event at Anderson, SC we had some trouble with our climber jamming. This was caused when we went under the Stage and/or chain and hit it with our climber hooks.
Due to this issue we CAD designed a new hook to be shorter to prevent this issue and improve the reliability of our climber.
CAD design modification by Connor.
Before:
After:
44
Analyze and Improve: Climber
Our climber towers leaned outwards like a “V” when we climbed.
Temporary fix → Crossed yellow Kevlar cords anchoring climb towers to chassis
Final fix →
Crossed metal rods with turnbuckles anchor the climber towers to the chassis to prevent the cimbers from leaning out, modification led by Evan
45
Analyze and Improve: Auto Code
← At Anderson, our Auto could only ‘leave’ for 2 points.
It became really clear that getting a lot of points during Auto helped win matches.
Alex used Pathfinder to develop one- and two-note autos.
←Shoot and leave auto for 7 points.
46
Analyze and Improve: Auto Code
Two note auto and leave for twelve points
Final
Post-Anderson Solution
47
48
Final Post-Anderson Solution
Analyze and Improve
(After PCH Charleston District Event)
49
50
Analyze and Improve: Rear Camera Mount
We were concerned with the rear camera being shaky due to the movement of the amp flipper and impacts with other bots and field elements.
Evan had the idea to add rubber bands in between the bracket and the metal extrusion to absorb vibrations, and Evan and Drake installed them.
After:
Before:
51
Analyze and Improve: Amp Flipper
Notes sometimes bounced out of our amp flipper at the Anderson and North Charleston events. This lost us time as we do not have floor pickup for the amp flipper. We simply took out some of the churros to lower the momentum of the note if it bounces around.
Before: Churros all around
After: 2 churros removed from each side
Duru, Chloe, and Maria modified our Amp-Flipper
52
Analyze & Improve: Intake
Our intake was good at both Anderson and North Charleston but we wanted to make floor pickup even quicker to shorten our cycle time.
Due to this we added another roller to the intake which is closer to the front of the robot and can catch notes even if they are against walls.
Before:
After:
53
Analyze & Improve: Intake
Evan worked to design, CAD, and attach another roller and the motor which powers it. He also connected this new roller with chain so that the code would not need to be changed.
Before:
After:
54
After the North Charleston Event Alex and Drake worked to update our autonomous to score 3 notes and get leave giving a total of 17 points.
Analyze and Improve: Auto Code-3 note
This involved adding a limelight and figuring out angles.
55
Analyze and Improve: Auto Code-4 note
After the North Charleston Event Alex and Drake worked to update our autonomous to score 3 notes. � Then after we were able to get a 3 note autonomous Alex and Drake began work on a 4 note autonomous which could score us 22 points
56
Analyze and Improve: Note Detection
Before
At first we temporarily mounted the limelight with a zip tie.
Of course. :)
We were using a camera for note detection, but Limelights use less power and are much faster.
So we decided to switch out our camera for a limelight.
57
Analyze and Improve: Note Detection
After
Permanent mounting for limelight
Evan CAD-ed up a custom mount that fit over the 1-inch structural tube.
Drake adjusted the vision code for the limelight.
58
Analyze and Improve: Checking & Testing
Mr. John, Gabe (4533 alumnus!), Alex, Mr. Kevin, and Nyire check the swerve modules. Mr. Ed supervises.
Duru flexing–
she’s driving with the controller behind her back while testing auto-floor note pickup!
Final
Post-Charleston Solution
59
60
Final Post-Charleston Solution
Bot-Hoven, all ready for the
Peachtree District Championship!