FRC2023-2024: Crescendo - Revision history

Mikets at 04:10, 29 April 2024

2024-04-29T04:10:34Z

← Older revision		Revision as of 21:10, 28 April 2024
Line 37:		Line 37:
	=== What Did Not Go Well? ===		=== What Did Not Go Well? ===
	=== Mechanical ===		=== Mechanical ===
	* '''Battery issues:''' Our battery got unplugged twice when we got hit.		{\| class="wikitable" style="margin:left"
	** 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.		! style="text-align:left;"\| Problems
	** Leave enough slack when wiring and strain relief the wire at the connectors.		! style="text-align:left;"\| Solutions
	** Secure connectors by screwing them down or hot gluing them.		\|-
	* '''Wiring maintainability:''' Connectors access may be blocked by fixtures.		\| '''Battery issues:''' Our battery got unplugged twice when we got hit. \|\| Protect the battery from strenuous movement against hard hit.
	** 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.		\| '''Wires are too taut:''' Wires or connectors may pull out or break when robot got hit hard.
	** 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.		* Leave enough slack when wiring and strain relief the wire at the connectors.
	* '''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.		* Secure connectors by screwing them down or hot gluing them.
	** 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.		\| '''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.
	** 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.		\|-
			\| '''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.
			\|}

Mikets at 03:39, 29 April 2024

2024-04-29T03:39:04Z

← Older revision		Revision as of 20:39, 28 April 2024
Line 51:		Line 51:
	* '''Radio/Ethernet Switch is not accessible:''' Radio/Ethernet switch block are placed and wired such that it's not easy to fix their wiring.		* '''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.		** 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.

	~~{\| class="wikitable" style="margin:left"~~
	~~\|+ Caption text~~
	\|-
	~~! Problems !! Possible Solutions~~
	\|-
	\|
	\|-
	~~\| Wiring issues~~
	\|-
	~~\| Example \|\| Example \|\| Example~~
	\|}
	~~Problems: Possible Solutions:~~


	~~Wiring issues~~
	~~Too tight (not enough strain relief in cables)~~
	~~Connectors could’ve been secured better~~
	~~Some wires were hard to access~~
	~~Wrist~~
	~~Wrist was hard to access and maintain~~
	~~Radio~~
	~~Radio was also difficult to access~~






	~~We could limit the exposure~~
	~~Design a mechanism such that it is protected by the perimeter and within the robot bumpers~~
	~~Turtle mode should be completely within the perimeter~~





	~~Software~~
	~~Problems: Possible Solutions~~








	~~Strategy/Scouting~~

	~~Drive team~~
	~~Guarantee full commitment from drive team~~

	~~Outreach/Awards/Media~~
	~~More spirit this year!! W media team~~
	~~Better social media presence~~


	~~Team Leadership + advice for next year’s leaders~~
	~~Find key programmers?~~
	~~Emails weren’t being received by members~~
	~~Too many communication channels~~
	~~Connect email to discord~~
	~~People aren’t following up with small action items~~
	~~CEO delegates tasks to leadership team~~
	~~Have a running to-do list with status column (full leadership team has access to it)~~
	~~Sub-team communication~~
	~~Hard to startup a team~~

Mikets: /* Season Recap */

2024-04-29T03:38:18Z

Season Recap

@@ Line 15: / Line 15: @@
 === What Went Well? ===
 * Better team spirit
 * We had a strong summer (good training with lots of kids)
 * We were able to kick off quickly into prototyping phase
-=== What Did Not Go Well? ===

Mikets at 00:29, 29 April 2024

2024-04-29T00:29:10Z

← Older revision		Revision as of 17:29, 28 April 2024
Line 12:		Line 12:
	<youtube>62sKZA0hP38&list=PLwES-SbpsnxwdIUbTTTtnTQixvvBjSe_w&index=40</youtube>		<youtube>62sKZA0hP38&list=PLwES-SbpsnxwdIUbTTTtnTQixvvBjSe_w&index=40</youtube>

	== ~~Lessons Learned~~ ==		== Season Recap ==
			=== What Went Well? ===
			* Better team spirit
			* We had a strong summer (good training with lots of kids)
			* We were able to kick off quickly into prototyping phase

	~~=== What Works Well? ===~~

	=== What ~~Needs Improvement~~? ===		=== What Did Not Go Well? ===

Mikets: /* Impact Award Video */

2024-04-26T20:44:11Z

Impact Award Video

← Older revision		Revision as of 13:44, 26 April 2024
Line 6:		Line 6:

	== Season Videos ==		== Season Videos ==
	=== Impact Award Video ===		=== Impact Award Video Submission ===
	<youtube>yo399jWPOkc</youtube>		<youtube>yo399jWPOkc</youtube>

	=== Pit Interview ===		=== Pit Interview ===
	<youtube>62sKZA0hP38&list=PLwES-SbpsnxwdIUbTTTtnTQixvvBjSe_w&index=40</youtube>		<youtube>62sKZA0hP38&list=PLwES-SbpsnxwdIUbTTTtnTQixvvBjSe_w&index=40</youtube>

Mikets: Replaced content with "== Game Resources == * Game Manual * [https://github.com/trc492/Frc2024Crescendo Code Repository] * Impact Award Essay * Flyers == Season Videos == === Impact Award Video === yo399jWPOkc === Pit Interview === 62sKZA0hP38&list=PLwES-SbpsnxwdIUbTTTtnTQixvvBjSe_w&index=40 == Lessons Learned == === What Works Well..."

2024-04-26T20:41:21Z

Replaced content with "== Game Resources == * Game Manual * [https://github.com/trc492/Frc2024Crescendo Code Repository] * Impact Award Essay * Flyers == Season Videos == === Impact Award Video === <youtube>yo399jWPOkc</youtube> === Pit Interview === <youtube>62sKZA0hP38&list=PLwES-SbpsnxwdIUbTTTtnTQixvvBjSe_w&index=40</youtube> == Lessons Learned == === What Works Well..."

← Older revision		Revision as of 13:41, 26 April 2024
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]]
	* Pit Interview
	~~<youtube>62sKZA0hP38&list=PLwES-SbpsnxwdIUbTTTtnTQixvvBjSe_w&index=40</youtube>~~

	~~== Impact Award Submission ==~~
	Throughout the last 3 years, Titan Robotics Club has been defining impact for everyone in a multitude of different ways. At TRC, we make an impact for our own members. Many of our members at TRC have learned many different skills which they now use in their everyday lives. For example, at TRC we taught our members how to use tools safely and effectively. We also taught our members how to go through the engineering design process for creating a robot by extensively planning, adjusting, and assembling. Our students carry these skills with them throughout their careers in STEM going into Engineering and computer science courses. TRC has also created a massive impact on its members with skills which aren’t just related to STEM. For example, our members have learned how to write emails and grants. Most importantly though, our members have learned teamwork and leadership by participating in our club and working together on a set goal. These skills are important for the success of all our members. Some of our most successful students have attended a wide range of schools all around the US including UW, NYU, ASU, and more! Titan Robotics Club does not just impact our own members, we have impacted our local community as well. Throughout the past 3 years, our club has been attending many different events right in Washington. For example, Titan Robotics Club for the past 10 years has been supporting school fairs and science related events where we showcased the capabilities of STEM, and the opportunities and values FIRST has to offer for students and adults. Within the last 3 years, we’ve impacted over 3,500 students locally through captivating robots. Titan Robotics Club has also hosted several workshops in Washington. These FLL workshops allow us to spread the message of FIRST by providing a hands-on experience where kids and adults will learn the process of teamwork and working together to solve challenges. Titan Robotics Club has also made an Impact for other FIRST robotics teams, spreading FIRST values of teamwork and gracious professionalism. TRC is a member of the Bellevue Alliance, which is an Alliance of all the FRC teams in Bellevue Washington consisting of 948, 949, 1899, 2412, and 9036. However, for the past few years all the teams in the Bellevue area have lacked the shop space necessary to build a full field. Through corporate sponsorship, Titan Robotics acquired a large warehouse with enough space for a full field, we shared that resource with other teams allowing them to practice, test, and adjust their robot on a full-size field. We also assisted the other teams on the Bellevue Alliance to advocate for a location where they could build their own full-size field. When they were successful in getting a location from our school district, even though TRC already owns a full-size field, we assisted in the process of constructing the field parts and elements showing the FIRST values of collaboration and gracious professionalism. Because of the aftermath of COVID when one of our fellow BA teams was under threat of shutting down, Titan Robotics created an impact by assisting them with space, tools, and other essential resources to ensure the team would stay open to continue to provide a space for their members to spread the FIRST ideas. We here at Titan Robotics are always willing to assist our fellow teams when in need because that’s the proper way to spread FIRST ideals. We’ve impacted over 200 other FIRST students and mentors by assisting them with needs which are difficult to obtain. Titan Robotics Club hasn’t just helped around here in Washington, we’ve made our impact globally by hosting webinars which can be viewed from all over the world. These Webinars help people learn about STEM related opportunities once they reach college. Our webinars assist students from all over the world by giving them an understanding into a technical field and the challenges faced, while also providing an open space for questions from our curious listeners. We’ve been doing our webinars for the past few years. We've affected over 100 students from around the world in just the past 3 years by giving them a look into STEM fields where they can explore the opportunities STEM has to offer. Titan robotics club has been a gateway for students all around the world to understand FIRST and STEM and the opportunities offered with them. We define impact because we’ve been doing this for so long, and consistently every year since our teams founding back in 2001. We’ve been doing this for 20 years and our impact has helped small town members of FIRST, young kids, and even a global audience become interested in STEM.

			== Season Videos ==
			=== Impact Award Video ===
	<youtube>yo399jWPOkc</youtube>		<youtube>yo399jWPOkc</youtube>
			=== Pit Interview ===
	== ~~Season Videos~~ ==		<youtube>62sKZA0hP38&list=PLwES-SbpsnxwdIUbTTTtnTQixvvBjSe_w&index=40</youtube>

	== Lessons Learned ==		== Lessons Learned ==

Mikets: /* Season Videos */

2024-04-26T09:52:12Z

Season Videos

← Older revision		Revision as of 02:52, 26 April 2024
Line 12:		Line 12:

	== Season Videos ==		== Season Videos ==
	~~=== PNW DCMP Recap ===~~
	~~<youtube>RyM__JFJ7Hk</youtube>~~

	== Lessons Learned ==		== Lessons Learned ==

Mikets: /* Season Videos */

2024-04-26T08:19:37Z

Season Videos

← Older revision		Revision as of 01:19, 26 April 2024
Line 12:		Line 12:

	== Season Videos ==		== Season Videos ==
	PNW DCMP Recap		=== PNW DCMP Recap ===

	<youtube>RyM__JFJ7Hk</youtube>		<youtube>RyM__JFJ7Hk</youtube>

Mikets: /* Season Videos */

2024-04-26T08:18:48Z

Season Videos

← Older revision		Revision as of 01:18, 26 April 2024
Line 13:		Line 13:
	== Season Videos ==		== Season Videos ==
	PNW DCMP Recap		PNW DCMP Recap

	<youtube>RyM__JFJ7Hk</youtube>		<youtube>RyM__JFJ7Hk</youtube>

Mikets at 08:18, 26 April 2024

2024-04-26T08:18:26Z

← Older revision		Revision as of 01:18, 26 April 2024
Line 10:		Line 10:

	<youtube>yo399jWPOkc</youtube>		<youtube>yo399jWPOkc</youtube>

			== Season Videos ==
			PNW DCMP Recap
			<youtube>RyM__JFJ7Hk</youtube>

	== Lessons Learned ==		== Lessons Learned ==