FRC 6328 Mechanical Advantage 2025 Build Thread

Welcome to the 6328 Mechanical Advantage #openalliance build thread for 2025! We’re looking forward to this season and we’re ready to step up our Open Alliance game!

This year, we’re excited to compete at Week 1, GSD, and Week 4, UNH in the NE District. As has been the case for the past few years, we are aiming to build a reliable, relatively simple, robot that leans into our strengths in software to hopefully perform at a good level throughout the season.

This year, we’re hoping to do weekly longer form posts, as well as short, picture and video based posts as cool and interesting things come up. If you have any feedback or questions about anything please reach out to us in the thread.

Team Links:

Dave

158 Likes

We’re celebrating the launch of our 2025 build thread with a special surprise! Keep an eye on the Littleton Robotics YouTube channel for the next few days to see what we have in store…

49 Likes

Do you mean like short form video or shorter posts? Either would be great

2 Likes

image

:point_up_2:me smashing the subscribe button

70 Likes

Yes

Merry Christmas everyone!

29 Likes

This Build thread and a few other notable ones are such a great service to the FRC Community. I hope FIRST one day will start recognizing teams for their outreach at the World Championship.

35 Likes

6328, best known for two things, their incredible open alliance threads and their unwillingness to lose an offseason event.

Oh I hear they have ̶A̶ ̶g̶r̶e̶a̶t̶ ̶h̶e̶a̶d̶ ̶c̶o̶a̶c̶h̶ a great coaching TEAM and an einsteins streak as well :open_mouth: Can’t wait to follow along this season!

14 Likes

Appreciate the kind words but we don’t have a head coach! 6328 has a core group of mentors that all contribute in their own ways.

We’re very fortunate that we have a roster of mentors; software, hardware, business, awards, strategy, electrical/controls, manufacturing and otherwise that all own and are working to build a great program for the kids! I can’t wait to tell you all more about it soon!

26 Likes

Indeed, our team will be following them and every other Open Alliance team as well!

What you guys have helped to create as a founding member is uniquely valuable to the community, I wish I had found out about it sooner!

7 Likes

Love this blog and love this team. I hope we get to compete with you at DCMPs again this year.

2 Likes

Our 2025 GitHub repository is now live!

We’re trialing a new approach to open source software this year, so you may notice that the repository looks a little different than previous years. We feel that it is critical for our students to be able to discuss tasks, write code, and receive feedback in a familiar and comfortable environment within our team. We also want to maximize the community benefit of having our code publicly accessible for reference and inspiration. This year, we decided to reevaluate our approach to open source code in order to better achieve both of these objectives.

The key change is that we’ve transitioned our primary workspace for robot code to a private GitHub repository. The repository linked above is a public copy of our robot code, which will be automatically updated every day with the latest stable code from our development repo. This repository does not include usernames, issues, or pull requests, but you can still follow along with our development and changes throughout the season. We hope that this can serve as an example for how open source robot code can benefit both students and the wider FRC community. All of the GitHub workflows required for this setup are included in the public repository.

We’re happy to answer any questions about our approach to robot code development, and are excited to share the software work that our students will be starting very soon!

44 Likes

Why did you feel the need to set up this pipeline instead of working on the public repo?

1 Like

We feel that it is critical for our students to be able to discuss tasks, write code, and receive feedback in a familiar and comfortable environment within our team. We also want to maximize the community benefit of having our code publicly accessible for reference and inspiration. This year, we decided to reevaluate our approach to open source code in order to better achieve both of these objectives.

28 Likes

I’ll rephrase: what specific downsides did you notice when working directly on the public repo? Was there negative feedback on that from team members?

3 Likes

Will issues be copied as well? Seeing the in season management is pretty cool.

2025 Kickoff Resources

Last year I shared our materials we put together for approaching kickoff, something that has been evolving each year to try and balance productive discussion with engaging our whole team throughout the process.

This year we had a meeting with some of our experienced students and mentors to talk about where we want to either tweak things or make large changes to our process. The “standout” topics that informed our changes are:

  1. We want to make the weekend more engaging to a wide variety of students. This means adding in some more tactile elements (hand written notes, encouragement of using whiteboards and scratch paper) and breaking up the monotony with a fun but productive activity on Sunday morning.
  2. We had many examples on our worksheet that were from before our current generation of students.

You may note that the slideshow is very similar and the worksheet got the most visible changes. We will be piloting this for the first time ourselves on Saturday. I hope these can serve as a useful jumping off point for any other teams and as always we are happy to answer any questions!

2025 Kickoff Slides

2025 Kickoff Worksheet

23 Likes

Kickoff Weekend: :fish::coral:

Team 6328 had a great start to the season this weekend, with our team’s discussion circling around understanding the game, high level strategy, and design plans.

Saturday:

Our day started with reviewing good strategies for reviewing the game manual and some key things to keep in mind when brainstorming. Then, after watching the stream, the team broke up into groups to review the rules and fill out our very own rules test.

|624x372.99999999999994

Rules Test:

This year, we created our very own rules test for our students. Before the stream, a group of student leads brainstormed what was important to know about any FRC game and created a preliminary list of questions. After the stream, we regrouped and created more game-specific questions, categorizing them and compiling them in a google form which all of our students and mentors then filled out. We aimed to make the questions and answers relatively clear to understand, simple to answer, and relevant to students’ understanding of the game. With our own rules test, we found that we were able to quiz our students on the most important information while also focusing on learning the rules instead of punishing students for incorrect answers. Everyone was able to understand that game in a complete way in a relaxed environment.

After the rules test, groups began to fill out our 2025 Kickoff Worksheet. (Blank copy). This year, we aimed to make kickoff more engaging for our students: we provided more choice in format and more open-ended questions. We found that groups benefitted from being able to choose between working online and on paper, and both options were equally popular. With more brainstorming opportunities, groups came up with unique ideas and strategies which we then collected in a single team worksheet for the team to reference.

Sunday:

We started the day off with a round of “humans play the game” with a makeshift field. This was a first for us, and we had a lot of fun while also learning more about the game.

Next, we had a whole team discussion and brainstormed an exhaustive list of tasks that a robot could do in the game (we think of these as the “what”s). We then had a team presentation about team strategy and various role complexities to better understand our goals. We discussed various roles we could play in the game, our capability in reliably executing roles of increasing complexity, and their respective point values during a match to help guide us through the build season.





Keeping these in mind, we ranked our tasks to create a robot priority list to help us think about the “hows” of completing our goals. We sorted these into “Needs”, “Wants”, and “Nice to Haves”. While this is not a perfect system, it proved to be a simple way to categorize and rank robot tasks. With some elements of the game being more nuanced and there being less of a consensus among team members, we “starred” some tasks to indicate that they could be placed either a category higher or lower.

After this, the team divided into groups one last time to brainstorm robot and subsystem designs. We had many great ideas and will soon be deciding on which prototypes we want to build. Many groups took inspiration from 118’s 2018 robot, thinking of a similar intake and handoff mechanism to an arm that can work with both CORAL and ALGAE, much like our 2023 robot’s claw, which was able to manipulate both cubes and cones. Below are some student sketches of possible designs!


We will be starting to prototype this week; stay tuned for updates!

pufferfish

-Lesia

63 Likes

Is there a reason that you are not going to focus on scoring L4?

4 Likes

i think they are going to, they are saying that its not maximum priorety tho

3 Likes

This was a heavily talked about trade-off the team is considering this year; we’re currently creating a more in-depth analysis of the specific trade-offs of complexity vs theoretical robot performance ceiling to ensure that our final decision will fall in line with our team’s resources. Once we finish that up this week, we’ll share a post with the analysis!

19 Likes