FRC2023-2024: Crescendo: Difference between revisions
		
		
		
		
		
		Jump to navigation
		Jump to search
		
				
		
		
	
| No edit summary | No edit summary | ||
| (8 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
| * [[Media:Frc2023-2024GameManual.pdf|Game Manual]] | * [[Media:Frc2023-2024GameManual.pdf|Game Manual]] | ||
| * [https://github.com/trc492/Frc2024Crescendo Code Repository] | * [https://github.com/trc492/Frc2024Crescendo Code Repository] | ||
| * [[Media:Frc2023-2024ImpactAward.pdf|Impact Award Essay]] | |||
| * [[Media:Frc2023-2024_DCMPAwardsFlyers.pdf|Flyers]] | * [[Media:Frc2023-2024_DCMPAwardsFlyers.pdf|Flyers]] | ||
| == Season Videos == | |||
| === Impact Award Video Submission === | |||
| <youtube>yo399jWPOkc</youtube> | <youtube>yo399jWPOkc</youtube> | ||
| ==  | === Pit Interview === | ||
| <youtube>62sKZA0hP38&list=PLwES-SbpsnxwdIUbTTTtnTQixvvBjSe_w&index=40</youtube> | |||
| <youtube> | |||
| === What  | == Season Recap == | ||
| === What Went Well? === | |||
| * Better team spirit  | |||
| ** We had signs, cheers, stickers/buttons/pokemon cards | |||
| ** Better social media presence  | |||
| * We had a strong summer (good training with lots of kids)  | |||
| * Our participation in 2 off-season competitions gave lots of members good drive practice  | |||
| * We were able to kick off quickly into prototyping phase  | |||
| * Good mechanism ideas  | |||
| ** Implementation of amp thing went well  | |||
| ** Our ability to do redesign is very good | |||
| * Our auto-assists were very organized  | |||
| * We had good cross sub-team communication  | |||
| * We finished a lot of our priorities list  | |||
| * Match strategy went well  | |||
| * Good setup for how we were going to play each match  | |||
| * Better alliances this year | |||
| * Pit scouting setup was effective and detailed  | |||
| * We had ASB window fundraising this year  | |||
| * We applied for Impact Award which we haven’t done in a long time  | |||
| * Handles for the robot were nice  | |||
| * Rounded corners were helpful before robot inspection | |||
| * Open alliance was used more this year  | |||
| === What Did Not Go Well? === | |||
| === Mechanical === | |||
| {| class="wikitable" style="margin:left" | |||
| |- | |||
| ! style="text-align:left;"| Problems | |||
| ! style="text-align:left;"| Solutions | |||
| |- | |||
| | '''Battery issues:''' Our battery got unplugged twice when we got hit. || Protect the battery from strenuous movement against hard hit. | |||
| |- | |||
| | '''Wires are too taut:''' Wires or connectors may pull out or break when robot got hit hard. | |||
| | | |||
| * Leave enough slack when wiring and strain relief the wire at the connectors. | |||
| * Secure connectors by screwing them down or hot gluing them. | |||
| |- | |||
| | '''Wiring maintainability:''' Connectors access may be blocked by fixtures. || Carefully plan the placement of the component and orientation so that the connectors are easily accessible. | |||
| |- | |||
| | '''Shooter Tilter is fragile:''' Shooter Tilter is often damaged when hit. | |||
| | | |||
| * Design a mechanism such that it is protected by the perimeter and within the robot bumpers. | |||
| * It's okay for a mechanism to extend outside the perimeter but ''Turtle Mode'' should bring it back inside the protective perimeter. | |||
| |- | |||
| | '''Shooter Tilter maintainability:''' Tilter was designed such that it's not easy to maintain. If the pulley breaks or skipped a tooth, it is not easy to fix. || Components should be design with maintainability in mind. | |||
| |- | |||
| | '''Radio/Ethernet Switch is not accessible:''' Radio/Ethernet switch block are placed and wired such that it's not easy to fix their wiring. || If it is unavoidable that a component is placed in a hard to access location, it should be designed so that it can be "taken out" easily to fix the wiring and put back. | |||
| |} | |||
Latest revision as of 21:10, 28 April 2024
Game Resources
Season Videos
Impact Award Video Submission
Pit Interview
Season Recap
What Went Well?
- Better team spirit
- We had signs, cheers, stickers/buttons/pokemon cards
- Better social media presence
 
- We had a strong summer (good training with lots of kids)
- Our participation in 2 off-season competitions gave lots of members good drive practice
- We were able to kick off quickly into prototyping phase
- Good mechanism ideas
- Implementation of amp thing went well
- Our ability to do redesign is very good
 
- Our auto-assists were very organized
- We had good cross sub-team communication
- We finished a lot of our priorities list
- Match strategy went well
- Good setup for how we were going to play each match
- Better alliances this year
- Pit scouting setup was effective and detailed
- We had ASB window fundraising this year
- We applied for Impact Award which we haven’t done in a long time
- Handles for the robot were nice
- Rounded corners were helpful before robot inspection
- Open alliance was used more this year
What Did Not Go Well?
Mechanical
| Problems | Solutions | 
|---|---|
| Battery issues: Our battery got unplugged twice when we got hit. | Protect the battery from strenuous movement against hard hit. | 
| Wires are too taut: Wires or connectors may pull out or break when robot got hit hard. | 
 | 
| Wiring maintainability: Connectors access may be blocked by fixtures. | Carefully plan the placement of the component and orientation so that the connectors are easily accessible. | 
| Shooter Tilter is fragile: Shooter Tilter is often damaged when hit. | 
 | 
| Shooter Tilter maintainability: Tilter was designed such that it's not easy to maintain. If the pulley breaks or skipped a tooth, it is not easy to fix. | Components should be design with maintainability in mind. | 
| Radio/Ethernet Switch is not accessible: Radio/Ethernet switch block are placed and wired such that it's not easy to fix their wiring. | If it is unavoidable that a component is placed in a hard to access location, it should be designed so that it can be "taken out" easily to fix the wiring and put back. |