FRC Team 3735 VorTX 2024 Build Thread | Open Alliance

2024 Open Alliance Build Thread

Welcome to FRC Team 3735, VorTX’s 2024 Season Build Thread! This will be our 14th Season in the FIRST Robotics Competition, and we are excited to share our team’s progress.

About Us

We are a student-led team with team membership tallying over 75 students from all five Klein ISD high schools. Established in 2011 as “Klein Bots”, we re-branded to “VorTX” in the offseason of 2016 and have continued our success winning multiple awards including Chairmans, Entrepreneurship, Quality, Sustainability, multiple offseason wins, and have competed at World Championships in 2015 - 2017. We also have many experienced Coaches (KISD staff), Industry Mentors (mostly team alumni), and previous year’s Alumni advising and administrating the team.

The Build Thread

We expect that build thread posts will be updated multiple times per week throughout the season, approximately every other day. Leading up to Kickoff, we will share bi-weekly Saturday updates from our off-season developments before the build season commences. A formal design review process is being practiced this off-season and further implemented this coming year which will complement quality content shared on this build thread. We look forward to sharing our journey from both Robot and Business perspectives and receiving constructive feedback from the FRC community. If you have questions, please reach out to us here on Chief Delphi and the Open Alliance Discord.

Happy Kickoff, and best of luck to all teams!

Team Links

GitHub
OnShape
The Blue Alliance
Website
Instagram
YouTube


Posted By: Lewis Longbottom - Mechanical Engineer & FRC 3735 Lead Mentor
2014-2015 Alumni
Alumni Mentor 2016-2019
Industry Mentor 2020-Present


8 Likes

10/13/23 Off-Season Update:

To conclude the 2023 Season, VorTX celebrated with our annual Banquet. We recognized our successes, notably our Sustainability Award from the Waco FiT District Event, and our graduating Seniors.

Despite an overall good season, the team was unable to qualify for state championships. We’ve identified many actionable improvements which we expect will improve our performance in the coming season. One positive takeaway was that we implemented an important process we expect will play an important role in the team’s future success: Retrospectives. We initially used the format for post-competition, but it has since been used after any major activity the team embarks on. The goal is to identify 3 things and break them down;

  1. What went well?
  2. What did not go well?
  3. What can we do better next time?

The order is important for morale purposes and to encourage discussion, a common management tool for meetings - start on a positive, get to the point, and end on a positive. To quote from the sustainability award requirements, This is how our team celebrates success and documents lessons learned to prevent repeating mistakes. It’s a simple matter of continuous improvement that allows all members of the team to provide feedback and have input on the future direction of the team. What’s important is feeding the lessons learned back into the next event, which we will do with pre-competition meetings to discuss all points and have them covered.

2023 Waco Week 1 Retrospective
2023 Space City Week 5 Retrospective
2023 Season Retrospective
2023 The Remix Retrospective

Our first task after the banquet was confirming new leadership for the off-season into the build and competition seasons. This year, the team decided to formalize the leadership selection process, which previously was decided by departing or remaining students. In the new process, we formed a Leadership Committee composed of team members who met the letterman requirements and/or demonstrated leadership capabilities over the previous season. Any decisions made by students on the team will now be made based on the decision of the leadership committee and not any one student. We identified responsibilities of the Leadership Committee which is mostly setting a good example for others. Following the formation of the Leadership Committee, Mentors sought nominations for Team Captain, Robot Lead, and Business Lead positions. Position responsibilities were listed in detail and are to be assessed during the nomination process by the committee members. Nominees for these three positions were then interviewed by Mentors and Coaches who then make a unanimous decision on each position, and confirm the individuals to the Leadership Committee. This process took approximately 1 month from forming the process to the announcement.

With the Team Captain, Robot Lead, and Business Lead known to the team, the next most important task was Recruiting New Members. The team organized and scheduled “Demos” at the district’s high schools, which involved the 2022 Robot, posters, awards, a presentation, and a QR code sign-up link for the team. Through several successful demos, the team had many new members sign up for the team. We then organized Parent & Student Informational Meetings where we introduced the team (and its leads and mentors) , played the FIRST FRC videos, presented what we do, and outlined expectations and cost. After the meeting, we distributed Parent permission and student sign-up forms (if they hadn’t already been completed), and chatted to people. This was an important activity because feedback from our previous year was that some new students and parents did not know who the leads were and what the real expectations were which led to some misunderstandings. We received great feedback from parents from this meeting and everyone is seemingly on the same page, we also have an excellent accounting of everyone on the team and their status. To date, the team has 85 sign-ups, with over half being from new members.

With all the new members joining, we must have a very organized team in terms of not only the shop but also task management. Mentors set up a Trello account and created boards for the off-season and build season. There, they set up lists where the students created cards and managed the work. Trello (available in limited form for free) utilizes a web-based Kanban style of lists and cards to track the progress of tasks and we highly recommend it to teams looking for productivity and transparency improvement. Off-season lists were structured as Backlog (to-do), In-Progress, High Priority, Blocked, Needs Mentor Review, Sent Back, and Done. Build Season lists are set up as Drivetrain, Intake, Sub-Systems, Electrical, Programming, Business, Kickoff, General (to-do), In Progress, Done, and Blocked. There are a lot of lists to organize all the build season tasks, so we’ve yet to see how well this works in practice.

In June of 2023, we once again collaborated with Team 1477 Texas Torque in hosting our annual Robotics Summer Camp. We lead youth through fun and engaging STEM related activities in small groups to learn critical thinking and cooperation skills. The camp was hosted over the course of four days with different challenges to start each day. Following the day’s challenges, the groups worked on their Lego robots, which were completed on the final day of camp. We also collaborated with one of our sponsors during the offseason in order to spread awareness for STEM in the community. We were invited by Campus Kids; a leading sponsor for the team, to give robot demos and introduce our team to elementary school students at 4 different schools. These two important events strengthened our bond with Campus Kids, and furthered our mission to “provide youth with the skills needed for future careers in the fields of STEAM” and to “spread the principles of FIRST everywhere we go.”

2023 Summer Camp Pictures

|288x192.72911392405064

In September we competed at “The Remix” offseason competition hosted by our local friends, Team 1477 Texas Torque. Our goal at this competition was primarily to get our new members competition experience. We considered making changes to the robot to make it more competitive, but due to lack of meeting time during the summer, we were not able to make significant changes, and by the time school started, we decided to focus more on training instead of changing the robot. Our drive team was all seniors last year so we also wanted to get some of the returning members practice driving. We also tried to get all of the new members in the pit at some point during the competition. One of the goals for next year is to have better defined competition roles. In the past we relied too heavily on a few people to both drive the robot, fix things in the pit, and sometimes play a part in our pick list and other things, so we wanted to help everyone get an idea of what role they think would fit them best. Our team spirit has also improved significantly over the past few competitions, making the stands a more fun place to be, which has unexpectedly improved our scouting quality as well. Overall we accomplished our goals and then some, being the 3rd robot on the 3rd alliance and winning the event with our alliance partners, 624, 8515, and 8879. We write more about our experience in the retrospective above. A big thank you goes out to our winning alliance partners; 624 Cryptonite, 8515 Photon, 8879 REDBird Robotics. The Remix is a fantastic event where our new members were able to run the pit, turn the robot around successfully every match and execute our strategy well.

image

Remix Off-Season Competition Pictures

|317x237.730223815201

One of the most important tasks this off-season was generating a thorough and quality Training Plan. ~50% of this training is created and presented by mentors and ~50% by student leads. There are 16 sections or modules that we expect students to attend by MS Teams or in-person meetings depending on the training. We will update this table with links once the presentations are polished up.

0) Introduction to VorTX 1) General Shop Safety and Hazard Awareness 2) VorTX Sub-System Overview 3) Hand and Power Tool Training 4) Designing Robots for FRC
5) OnShape CAD Training 6) Prototyping in FRC 7) Robot Sub-Systems in FRC 8) Mechanical Components in FRC 9) Gear Reduction, Motor Selection and Pneumatics Design
10) Control Systems and Programming in FRC 11) Manufacturing in FRC 12) Electrical in FRC 13) Design Reviews in FRC 14) Work Breakdown Structure
15) Kickoff Preparation 16) Competition Preparation

We’ve also introduced a new style of training, where students are free to choose what subteams they would like to be trained in. This year, we held 3 block training sessions with options for Tool, Electrical, Programming, CAD, and Business training, allowing members to learn what they want to learn instead of being forced into learning what they don’t.

Shop Organization has become an important priority to the team this offseason, as we’ve accumulated so many parts over 13 seasons and it’s getting difficult to manage. Nuts and bolts, planetary gearboxes, gears, sprockets, and chains - you name it, it was everywhere (in the wrong place) and was the most inefficient part of our build process last year. We have to fix bad habits of not cleaning up small parts, chips, and tools. A new concept introduced this year was a mandated 15-minute cleaning period at the end of every meeting, in hopes to combat this issue. We are still in this process but are making good progress although it is still making tool training difficult. One step we took was to re-organize the layout of the shop. We now have all power tooling along one side of the shop, allowing for a safer and open space to assemble the robot. New workbenches have been designed and are in the process of being built. We went for a simple construction design allowing us to link workbenches together for a larger workspace if needed.

Shop Reorganization Picture

image

New Tooling and Equipment purchases were made this off-season. We made an off-season buy list and assessed the quality and purpose of our tools. We considered a new pricey horizontal bandsaw but opted for a lower-cost chop saw from Evolution for tubing. In the past we had used a miter saw with a metal cutting blade, but this did not have good clamping abilities and presented safety concerns with the high blade speed. We then started using a Harbor Freight horizontal bandsaw which lasted a few seasons but proved to be losing its way in the prior season. We hope the chop saw yields good results. We also have kept our small vertically mounted bandsaw from prior seasons for smaller cuts, as it’s still in good condition, but we’ll be replacing the stand, since it’s pretty beat up from years of use and travel to competition and back… Next up is the CNC router, we purchased a decent-sized machine years ago and it still works well, but it often has leveling issues and is tricky to manipulate. This year, with the passing of the school bond, Klein ISD invested in a larger 4ftx4ft CNC router for the team that has a nice control system for easier setup. We are looking forward to setting it up in the newly organized shop space. Also received earlier from the bond was the Markforged 3D printer, which makes amazing parts quickly. Lastly, we replaced a lot of hand tools, drill bits, new annular cutter, belt sander, hex keys, digital calipers, electric rivet gun (game changer), tool chest (absolute beast), and many other things. Let’s just say we have Christmas about every month. We are very fortunate to have great sponsors, the support of Klein ISD, and our grant awards.

One of the projects some team members are working on is a new Robot Cart. It’s difficult to tell when the current cart entered service, probably around 2016 or 2017 with many modifications over the years, but it’s time for an upgrade. The team began by deciding on a list of requirements to guide the re-design. This is ongoing work, and we look forward to sharing the design for feedback before we start the build. A Battery Cart is also in the works and will be shared later.

To wrap up this update, we expect to continue the training plan through November and finish shop organization. We have plans to decommission the 2022 robot into a practice swerve drive base and document the technical issues with the robot to feedback points to the design review checklist. We will confirm the remaining leads before kickoff (sub-systems, awards, outreach, finance). We will finish the design of the Robot and Battery Carts ready for fabrication. Lastly, our final job is closing out the many smaller tasks in Trello, and getting our pre-season buy list purchased so we are ready for kickoff and build season.


Posted By: Lewis Longbottom - Mechanical Engineer & FRC 3735 Lead Mentor
2014-2015 Alumni
Alumni Mentor 2016-2019
Industry Mentor 2020-Present


5 Likes

what are your plans on using the rev vortexes

2 Likes

Looks like a phenomenal product with an even more phenomenal name! Hopefully REV sponsors us this year purely for the product🔌

3 Likes

While we are still in a joking mood can we please center the triangle in your pfp? It’s getting to me :smile:

image

Also there something weird going on with your website?

1 Like

Thats dark mode for you, I will try fix tomorrow for the sake of team illuminati. The website is being finished up by a developer we are working with. We also have a backup site thats 90% there so maybe we launch that soon in a post update.

gotcha :eye:

10/27/23 Off-Season Update:

Over the past two weeks, VorTX has been hard at work finalizing our training process and finishing development of our curriculum, as well as sneaking in some work on some interesting off-season projects. We also managed to finalize two more leads, our Outreach/Media Lead and our Awards Lead, so we are almost done with that process!

Two weeks ago, we shared our Training Plan on this thread, but we’d like to go more in depth on how exactly we have been running our training. As we mentioned last week, we have 16 modules for general team training. These are lessons presented by our team’s mentors once every week at our Friday meetings. To supplement that training, we also developed specific subteam training. These specialized trainings have been running alongside these general team trainings in 2 week cycles (we just finished our second cycle today) where students are allowed to choose their training of choice.

Here is the progression in each of our pathways:

Week # Tools Electrical Programming Business
1 Part Creation Introduction to electrical components Basic Java introduction Sponsorship Training
2 Assembly Creation Hands on wiring with past robots Advanced Java functions Awards Training
3 Git / Robot Code Outreach Training
4 Subsystem Architecture and control loops Media Training

These 2-week cycles previously mentioned are available for students. We will run these cycles three times, so they are allowed to choose 3 out of these 4 options. Weeks 1 and 2 are the first two weeks of a training, and the ones required to participate in that activity during the build season. Weeks 3 and 4, however, are for students who do not want to participate in as many different disciplines and would prefer to further their knowledge in one specific discipline. That means that after the first cycles (9/29 and 10/6), we’ve been running cycles of both Weeks 1-2 and Weeks 3-4 in our programming and business training.

Our CAD training required substantially more time than our other 4 training sessions, so we have decided to move it to a specific Wednesday meeting dedicated to CAD training. So far we have run a couple of these meetings and they are going great. For those wondering, our curriculum for CAD is as follows:

image

After this 5 week progression, we plan to host a Saturday meeting where each CAD student is provided a basic paper sketch, and is expected to turn it into a CAD model in a day.

As of last Saturday (10/21), we held our first Admin Sync Meeting. In these meetings, the team’s mentors, coaches, and team leads get together to discuss team finances, future events, and project plans. At this meeting we received exciting news that our new, large-frame CNC router will be arriving in the next month.

We are planning a new event for this upcoming season. Many teams produce a robot reveal video prior to competitions. We have failed to do that for the past few years, so we would like to make up for that by turning our robot reveal this year into something much more grand than the typical robot reveal. We’ll be hosting a Robot Showcase Event on March 2nd, 2024, a week before our first competition in Plano, Texas. At this event, we will invite nearby teams, our sponsors, school district representatives and all interested members of the community to watch our robot reveal premiere live, discuss with our team members, and see our robot in action for the first time ever! More details will be provided once we come to some conclusions about how the event will work, so stay tuned.

One project we mentioned last week was our team’s new Robot Cart. We have made limited progress in the past two weeks, but we have developed some conceptual designs now and plan to deliver a finalized design in our next update in two weeks.

Our other improvement project was the development of a new Battery Cart, which we have decided on requirements for. Due to issues with space in the pit we have often encountered in the past, we plan to integrate our new battery cart with a storage system for our DeWalt boxes this year. Tackling both these issues at once is a fantastic idea. We plan to have some CAD on this by the next update.

To sum up today’s update, we continued work on training, held an Admin Sync Meeting, developed plans for an exciting new Robot Showcase Event, and made some progress on our off-season projects.


Written By: Andrew Heiman - 2023 FRC 3735 Team Captain


4 Likes

11/11/23 Off-Season Update:

In the past month, we’ve been hard at work on the business side of our team, so this post will be more focused on the business progress.

The largest change we’ve made this year was that we began our work during the off-season, instead of beginning business work during build season. Our major focus the past few weeks has been Awards, mainly the Executive Summaries for the FIRST Impact Award. We’ve implemented a new strategy to properly write these executive summaries, and that is the sending out of our new team questionnaire. This questionnaire includes many important questions that the executive summaries ask for answers to, and it was sent to all prior team members and mentors to get an unbiased and purely factual understanding of our team’s accomplishments and goals. We’re also building up a steady supply of Team Media during our offseason meetings in preparation for award presentations.

Over the offseason, we’ve also been hard at work retaining Sponsorships and reaching out to new sponsors. All is going well, and we’d love to thank all our sponsors for continuously supporting us over the years. We’re working on some sponsor-specific gifts for our longest-lasting sponsors, with a unique plaque and presentation that we’ll show off along with what we’ve done over the last year at their facilities.

Our team has also been working hard on some new outreach opportunities. Next week, on Saturday (November 18th) we’re scheduled to work with Project CURE to package medicine to send to developing countries. As a team, we’d love to involve ourselves with CURE even more and we’re in the process of planning more outreach opportunities soon in the future.

We’ve also been working hard on getting some Grants submitted, which we’ve finally concluded as of last week. As of now, we’ve been awarded two grants, the Rockwell Automation Grant and the Texas Workforce Commission Grant. Thank you, Rockwell and the Texas Workforce Commission! Our final update from the business side is that our Team Website is ready to publish, and we are working on pushing it out to the domain soon!

Today, we finished the last day of our cyclical Training Plan, so here’s a retrospective of how training went this year.

2023 Offseason Training Retrospective

From here, we plan to continue with our general full-team training as led by the mentors, and we plan to delve into more projects and training for students to demonstrate and practice their skills hands-on. Some of these projects would be an in-depth analysis of our 2023 competition robot, as we scrap it to the drivetrain level and convert it into a prototyping platform, which will involve some rewiring of the robot. In addition, we’re pushing our work on the robot cart and battery cart to a full team endeavor, hoping that the experience in design/manufacturing for these projects can teach the necessary skills we’ll need during build/competition season.

Overall, the Robot Cart progress has been slow but it will be speeding up over the coming weeks as we have more people dedicated to the task as it is becoming a higher priority. A few minor CAD additions were made over the last two weeks, but the cart is still not ready for fabrication as we had hoped. As can be seen below, we have adopted extruded T-slot extrusion as the construction method allowing for adjustability season to season. This allows the robot supports to be moved depending on the robots design. This also allowed us to use a majority of the extrusion material that had been taking up space in the shop being unused on the robot. We expect plates to be machined out with our team branding elements and hopefully powered coated. Side plates will likely include the logos of our sponsors.

Initial Robot Cart CAD

image

We’ve also made steady progress towards our Battery Cart. Our two main ideas were to repurpose a Husky workbench into a battery cart by drilling in specific holes for wires to pass throughout or to create a tall standalone battery cart that can hold 10 batteries and 3 battery chargers. Work has been slow over the past two weeks but the plan is to speed through design before next Friday to make sure we can have enough projects to work on after our training concludes.

:us: VorTX would like to thank all of our Veterans for serving our country and may we honor your service each and every day. :us:


Written By: Andrew Heiman - 2023 FRC 3735 Team Captain.


1 Like

12/2/23 Off-Season Update:

On November 11, we held our Second Admin Sync Meeting. We confirmed the Due Payment System; through SchoolCashOnline, will be ready to accept payments before the season starts by installments or lump-sum amounts. We’ve also set a goal to have our Team T-shirts and polos arrive for new/returning members before Kickoff. They are now expected to arrive before the end of our Christmas break, allowing us to distribute them at Kickoff.

A small task we’ve been working on in the background, has been our ongoing attempt for our mentors to receive Workshop Access and the ability to open shop for the team. Currently, our Klein ISD coaches are the only ones with access to the shop, but due to how often we’ll be meeting in season it would be ideal for our mentors to have access as well.

We’ve also been reaching out to our long-term Sponsors to secure funding for the 2024 Season. We have worked over the past few weeks to create presentations and gifts for our sustaining sponsors, in hopes of growing our relationship with them and thanking them for years of support. We’re starting fabrication of a sponsor’s plaque that will be presented in the coming weeks. We’ve also been communicating with other sponsors on more sponsor-related events, such as a possible summer camp in collaboration with a sponsor. We received awesome news that Raytheon Technologies will be joining us as a sponsor for the 2024 season after receiving a grant, THANK YOU RTX! The team has done excellent work reaching out to family and friends, new businesses, sustaining sponsors and now Fortune 500 corporations.

Our New CNC has been confirmed to have been shipped, so we expect a busy couple of weeks to have it assembled and running before the season starts.

Another task we’ve begun work on, has been to fulfill our desire for more Shop Space. Currently, our shop is filled with tools, machines, and robots to the point where we have to move everything outside before we can begin meetings. We hope to alleviate this struggle. We’ve talked with the school principal from Klein High School (where our shop is located). He’s currently trying to see what will work and has provided us with a few options that we have to discuss the pros and cons of. We’re also still working on confirmation for the location for our Kickoff (1/6) and Robot Showcase (3/2) events (as well as finalizing plans for them).

As of December 1st, we have four New Workbenches in the shop, built by our team’s mentors. These are 2ft by 4ft each and have latches on the sides to be able to link together allowing for a configurable workspace. They were also designed to be short enough to allow all members to work on the robot. They have a floor base so we can store items in the bottom such as mobile tool boxes and organizers.

Workbench's Connected

Workbench with Test Drivebase

At our last meeting, we dismantled our 2023 competition robot, in hopes of documenting its shortcomings. This documentation came out subpar, and we hope to improve on it soon. We also plan to turn this dismantled robot into a test drivebase. The Robot Cart has begun fabrication with cutting the extrusion to size and assembly will begin next week. Though we thoroughly thought out the requirements and had good references, admittedly the design process was rushed. But knowing it is a simple frame where the sizing has been well considered, we don’t expect many issues.


Written By: Andrew Heiman - 2023 FRC 3735 Team Captain


2 Likes

12/18/23 Off-Season Update:

Due to our first semester at school ending, we could only slot one team meeting over the past two weeks. However, that doesn’t mean we didn’t make any progress aside from that meeting!

Right after we posted our last OA update, we received our New CNC! Over the past week, our team’s mentors have been working on assembling the machine before we bring it to the shop. Which will happen the Friday before Kickoff.

MillRight CNC Power Route Plus XL w/Touchscreen + 1.5kW Spindle

We also got in contact with a few of our past mechanical-based Sponsors to meet them face-to-face and receive a tour of their facility. We also provided presentations to them detailing what we requested of them and outlining the FRC build and competition seasons. We plan to reach out to more sponsors soon. Thank you Champion Fiberglass and iSolids for supporting us over the years!

We also made a bit more progress in the workshop over the last few weeks. We continued our Shop Cleaning and will continue with it until we are in a fully usable state by Kickoff. While that was happening, some of our team was hard at work on our two big projects as of now, the robot cart and robot disassembly projects. Robot Cart assembly began last week, and it should be all done right before Kickoff, leaving us a fully dedicated team to focus on our 2024 robot. Our Robot Dissasembly team has continued their work on the drivetrain and has replaced the front two small bars with one large bar, making a completely square and easy-to-test Swerve drivebase.

We’re also finishing up purchasing all of our Robot Buy List parts and tools to go into the build season. On the topic of build season, we’ve also finally finalized our location and begun scheduling our Kickoff plans. It will be held at our district’s multipurpose center from 9:30 AM to 6:30 PM where we plan to get all preliminary strategy ideas determined for our 2024 season.

Happy Kickoff to all FRC Teams!


Written By: Andrew Heiman - 2023 FRC 3735 Team Captain


1 Like

1/5/23 Kickoff Update:

VorTX is ready and excited for kickoff! Our New CNC is now completely assembled and running. We have a few minor tasks remaining to surface the spoilboard with the new tooling and perform a test cut but we are really happy with how it came together. We made one small mod so far to add pressurized air from a small air compressor and tank, and we plan on adding a dust boot to contain the mess. It conveniently fit in our large closet to keep the noise down and space available. For Robot Cart progress, again, no updates over the winter break, but our drivetrain team will likely have time after completion before the competition to finish assembly.

|335x447.5268022181146

For our kickoff preparation, we would like to share our Pre-Stream Slides with everyone in hopes it helps provide a reference kickoff schedule, a framework for discussion and also how we plan out the build season. We will have a Gantt chart soon once we baseline sub-systems. The next post will have slide summaries of kickoff.

Our plan after broadcast is to split into 5 or 6 groups each led by 1 mentor or alum each and read assigned sections of the arena, game play, game rules, robot rules and human rules, and robot construction rules- specifically only non-evergreen rules. ~15 mins per section(s) and a 5 minute summary presentation to the team. Assigned sections will be grouped in order to finish this in 1 hour, we are expecting four “read in detail” sections and the largest section split between two groups. Mentors will scan to check if the structure of the manual had changed since the prior year and highlight this to the team if other sections need attention. After a 30 min break for lunch, we will return as a group to discuss how to play the game - reread the game overview, how to score, how to rank, what you can and can’t do. We will then split back into the same groups to develop priority lists and perform cost-benefit analysis of the game, and brainstorm strategies. Groups will then present their strategies and field a few questions. The team will then split back into groups to analyze all the strategies and make adjustments to priority lists. After a 15 min break we will regroup for team discussion for final priority list, and make the overall strategy determination based on resources.





















Posted By: Lewis Longbottom - Mechanical Engineer & FRC 3735 Lead Mentor
2014-2015 Alumni
Alumni Mentor 2016-2019
Industry Mentor 2020-Present


3 Likes

1/7/23 Kickoff Update:

Kickoff went very smoothly and we stuck almost exactly to our schedule. All conversations were on topic and the team worked very efficiently to first summarize game manual sections and present to the rest of the team. Given that the vast majority of the team was brand new to the team this year, they did exceptionally well taking in the process of thinking strategically and developing group priority lists. One thing we do want to work on for next year is standardizing a format for groups to develop strategies. Every team tackled strategies and cost-benefit analysis differently which resulted in difficult assessments to obtain ranking points, though explanations were given well.

The team focused heavily on the ranking point tasks of high cycles to obtain the Melody ranking point (scoring 18 or 15 with Co-Op bonus) and the Trap scoring, and climb to obtain the Ensemble ranking point. We believe that being able to climb and score the Trap consistently would not only benefit us with the potential for a ranking point (with a partner) but also contribute significant points for elimination matches should we make it.

With either one of these ranking points, we assume the match would also likely be a win, though it’s possible in matches, just outscoring alone wins the 2 ranking points for the match. Strategically designing for the two other ranking points at a minimum ties the match on ranking points. Scoring in the Speaker has a 2:1 point ratio and it could be argued cycle times could be similar to scoring in the Amp (but are they?). Distance traveled and congestion in scoring at the speaker could throw this in favor of the Amp. However, with the Speaker being “amped”, to 2.5X, the point value is now 5 points a shot (how many shots can you get?). Versus 1 point scoring at the Amp, and no amping of the Amp. Both Amp and Speaker scoring require the same amount of cycles to obtain the Melody ranking point. We believe with both alliances scoring 1 Note (ring) in the Amp in the first 45 seconds, providing the Co-op bonus and lowering the Note quantity scored threshold to 15 from 18, will be advantageous to both alliances as it makes the Melody ranking point more feasible during the match (for both alliances, especially lower scoring alliances). The Co-op bonus has the further advantage of a ranking point tie-breaker. For cycle times, it has been suggested within the team but not formally discussed or agreed upon, that a best-case cycle would be 15-18 seconds respectively to the Amp/Speaker from the Source (HP station). Therefore, we project our contribution to be 6-7 with a stretch to 8 cycles at best with 20 seconds to spare for last Climb and or Trap. 8 scored Notes are not enough to reach the 18 or 15 required for the ranking point, but there are two other alliance partners. Evaluating scoring for everybot and kitbot is a good go-by for an average alliance partner. Those cycles could be estimated to be 3-4 for a Tank drive or better for a swerve on an active field. So on average, we could expect to see 7+4+4 = 15 which would make Melody only possible with Co-op. With a higher scoring alliance, 7+7+4 = 18 would score Melody RP without Co-op bonus. If we underestimate the average cycle of 4 but overestimate our cycle time by 1 each, it evens out. We are counting on the higher-performing robot to pull through for the alliance. In summary, we would need to design for 6 or better Notes scored to rank well, our functionalities and resource allocation need to reflect that.

The team is still in debate about whether or not to go for the Trap. “IT’S A TRAP!! - or is it? Understanding how and how fast we can score Trap right now is difficult to determine hence why the team is at odds over how exactly you can do it and how it influences Amp and Speaker. We would rather not miss the 5 Trap points or more and Ensemble RP. It may end up being that we Amp and Trap score the whole match, to Amp the speaker for others and keep the Melody ranking point in sight. However, if the better Speaker scoring robot is equally as fast as us at scoring, we would have to Amp score almost the entirety of the match to keep the clock running.

Today’s kickoff also focused the team more on complexity and resources. Again, with a team of 75%+ rookies, where do we draw the line between scoring in the Amp, scoring in the Trap, and scoring in the Speaker, and floor pickup vs human player pickup. One functionality debate right now is whether we have a mechanism that scores all three, but what about the integration difficulty of that? We do not want to get tied up designing and integrating a whole complex part of the robot distracting us from being able to get driving and practicing shooting and amping, this could be the ultimate decision maker on whether or not to Trap score.

We are settled as a team on human player loading at a minimum but are at odds over floor pickup. Ground pickup requires more design time, iteration and optimization, and more difficult integration. We have used ground pickup in the past with varying results. It’s also something else to break on the robot, which usually does, if not designed robustly and tested thoroughly. On the flip side, this is a cycle game, buzzer beating may be a reality, and being able to pickup that dropped Note (or shuttled note?) may be a big capability to support an alliance. We believe cycles across the field will be more reliable and consistent from a design and operation standpoint, hence human player pickup is default.

Until Monday we are undetermined on Trap/Amp/Speaker/Floor Pickup (shocker!), in the meantime, we will be sketching in 2D CAD to determine the geometry and feasibility of a combined system that can score all three. Then we will make a final complexity determination and decide by Monday.

1 Like

1/8/23 Day 1 Update:

The team met for the first season meeting today and spent the first few hours discussing concept ideas between students. Once Mentors arrived we started finalizing the Overall Priority List. It changed quite drastically since kickoff. After more consideration, we determined the Trap to be too complex and draw of resources to consider being a top design priority. We also changed our mind on intake to prioritize floor pickup over source pickup, due to the fact that we want to become a high scoring robot and the best way to do that is have the multi-piece auton, reduce cycle times, and be able to pickup rebounds. We also moved Speaker ahead of Amp because we believe an ideal elims alliance will have 3 speaker robots, but only needs 2 amp robots. Climb middle remains a top five priority but was moved lower due to the fact that our top priority aside from floor intake is scoring in both Amp and Speaker. This lowered human player intake further. HP intake is not something we won’t think about, but we believe a ground pickup could also double for HP station pickup on the floor or at the source. Climb to the side is the last design priority but still on our to-do list to be considered in its design. Trap is a TRAP!

Here’s some concepts discussed following strategy today. The first is standard kitbot style shooter with under bumper intake and a hood for Amp scoring.

The second is also a kitbot shooter but with outtake wheels to score Amp downward (might be intake too?).

The third below is a kitbot style shooter but with a human player intake structure over the top to channel straight from HP station to drop down into Amp. Interesting simple design, but might not clear the stage.

The last student design here is having the Note sit flat in the robot, and be rotated up by a kitbot style shooter and has a deflecting wheel to drive down into the Amp.

The last two are mentor ideas, the first has actuating intake for ground pickup, up position for HP intake, all the way back to feed the shooter. The shooter in default inline position is Speaker and down position is Amp (two position cylinder!). The other picture is from FRC 33 Killer Bees 2013 design, which takes inspiration of parallel intake and shooting. The mentor idea was that if the back was high enough, it could core the amp, but the downside is clearing the stage. As an alternative a hood was proposed to deflect the Note downwards into the Amp.

We have asked students to continue research another day and to start sketching concepts in CAD to clear the stage and produce initial testing geometry to build prototypes.

We also have the Amp built by our awseome parent volunteers! The back was added but no pictured.

2 Likes

1/10/23 Day 2 Update:

On Tuesday we had our first off-day Teams call, where we checked out OA posts and watched Ri3D videos together. What stood out the most was the Quokkas Ri3D design that met all of our objectives and ideal level of complexity. It was pretty similar to the FRC 33 2013 design we originally took inspiration from with a parallel intake/shooter, but instead, a pass through design with intake and shooter on opposing ends. We believe this opposing end design is more effective at cycles, reducing turning time during the match and potential instability of turning while driving fast across the field. We had a really positive experience with pass-through in 2018 Power Up. The team’s view is that we focus on optimizing this design for our priority list which ranks Speaker higher than Amp. To do this, we want to avoid adjusting the arm angle to score Speaker the majority of the time from the intake position; if possible, the whole time. We believe this will introduce more cycle time efficiency and reliability, scoring from the Subwoofer. The arm will rotate upwards and shoot the Note DOWN into the Amp. We believe shooting downwards is the intended direction to score the note reliably.

During today’s in-person meeting we further explored the geometry of the pass through on an arm concept. There is a lot of geometry to control and understanding what first optimizes our priority list is important, but at the same time making educated assumptions to start a design. We want the arm to stay in a static position from intaking to score Speaker, but also score Amp reliably. We also want to understand the other Speaker scoring positions and position the intake/scoring mechanism accordingly. We also want to understand the affect of compression. We expect a mix of research and data from rookie teams building test platforms will better iterate the design. We also recognize there is an element of risk driving around the field with the intake past the bumpers. We also know we want to be able to drive under the stage as if it wasn’t there which is an important packaging constraint.

The team will now form a more detailed list of design requirements list and push the CAD geometry further along to start extruding solids.

The drivetrain team has begun assembling new SDS MK4i modules, and un-inverting them! Then we will test driving over notes. We also have a practice drivebase with MK4i that will be tested driving over notes. After evaluating we will decide on which setup to go with. We believe the more ground clearance the better.

3 Likes

1/12/23 Day 2 Update:

On Thursday we had a Teams call where we determined the Needs, Wants, and Nice to Have features of the robot in the Priority list. Then as part of our design process we determined the Functional and Performance requirements of the respective sub-systems where shall and want statements were generated for each. Design requirements will be determined after the Conceptual Design Review milestone. We assessed concepts generated early by our team and better proven concepts by Ri3D teams. We did not list all Ri3D teams, but credit goes out to all teams who built robots and inspired us along the way. We then built a quick table to compare different robot concepts and their systems and applied very general assessments to each.

Today we completed functional requirements for intake and decided on a plan of action to move from conceptual to preliminary design.

Below are a few slides extracted from our Conceptual Design Review that we will cover tomorrow morning. The Robot Lead will make the concept selection known to the team, explain the reasons and areas for improvement. The scoring and intake sub-system teams will be combined, then the Intake lead will become the combined intake/scoring sub-system lead, and the scoring lead will become the lead for the arm sub-system.

Also today, was a lot of action in the shop on the organization front. We have a new back to back and end shelf arrangement that neatly ties three space consuming and used shelves together. Many parts were put back in their intended location and workspaces were cleaned in anticipation of prototype test rig builds by rookies and mentors. Due to our decision making happening sooner than expected (or rather on time), we are expecting to be ready to approve the drivetrain frame for manufacture by Wednesday next week, and perhaps the arm preliminary arm mounting frame. MK4i! Modules are nearing completion and need motors to be installed now.

Another progress item is the test drivebase that electrical is building up. It looked complete today and I don’t have pictures yet, but everything that’s supposed to be there, looked like it was there. The drivebase size on the test platform is 30”x30” which is also our go-by perimeter on the 2024 bot, so we could end up having a B bot to enhance drive practice while building a competition bot - not something we have planned.

The team met at Tumble22 for dinner today and we had a great gathering, eating out after meetings is something we decided would be a great improvement to team culture and we are happy the team embraces it. An update will be posted tomorrow where we should have more to share on the design side.

3 Likes

1/13/23 Day 4 Update:

Today we started the meeting with a Conceptual Design Review presented by the Robot Lead. We read through the functional and performance requirements to all present then reviewed concepts and explained the concept selection decision to proceed with the Quokkas style robot. We then followed by splitting into sub-system groups and simultaneously continued work on all fronts. The Intake team was tasked with reading in depth through the Quokkas thread on CD and published materials to understand challenges and detail decision choice decisions. Then the task was replicating the geometry for the intake/scoring assembly in order to make it configurable for us. The goal is to build the assembly as soon as possible, integrate in the CAD assembly, then determine any final adjustments to dimensions to support our packaging and optimal shooting angles. Then practice, A LOT, and improve further. If we have an awesome Auton, it could well be the most important ability of the robot.

One improvement we want to make is to the speed of the arm, for faster auton, cycle time, and intake protection when traversing the field. We believe with Neos, 52T x 12T, 25:1 or 36:1 MaxPlanetary we can reduce the gear ratio from 250:1 to 143-156:1 to obtain a stall load of 175-251 lbs vs. 217 lbs with MiniCIMs. The Arm time to 90 degrees would be 0.32-0.45s vs. 0.71s.

There was minimal CAD done today, but over the weekend and with Monday (MLK) being a holiday, we expect to be further along with 3D. We did start a Work Breakdown Structure which we will use to track progress and assign resources.


image

1 Like

1/15/23 Day 5 Update:

Just a quick update for today. We added the arm mechanism to the robot assembly today and had a Teams call to discuss what we want to change before we get too far along. The swerve modules are making the space availability quite an issue to mount the scoring mechanism. Therefore we will now adjust the design to mount the arm mechanism frame above the swerve modules out to the side. We also decided to check if we can mount the MaxPlanetary through the tube instead of under it.

The climb subsystem is continuing to look at options and we will reserve space to adjust for the center of gravity.

The drivetrain team is now working to add some extra support for the frame in the middle of each side as we suspect some high speed collisions this year and we don’t want to bend a frame. They will also work with the Electrical team to land the battery and control system components to finalize the bellypan, hopefully by Wednesday when we can start fabrication of the drivetrain.

1 Like

Any concerns or tips for keeping that chain center to center across the two different tubes? I have only ever done chain c-c on one tube in a single machine operation.

I’m not sure I quite understood the question? The chain is not across two tubes. Our chain is not perfect yet and we are changing the position of the drive.

1 Like