2026 REBUILT

We had an exciting Week 6 at the FIRST California Northern State Championship at the Cow Palace. Competing against 60 of the top teams in Northern California, our robot demonstrated consistent and reliable performance throughout qualifications. We finished with a 9–3 record, ranking 7th overall, and proved we could contribute effectively across a wide range of matches, from high scoring offensive games to tighter, defense-heavy matchups. Between East Bay District and DCMP, we had very limited turnaround time, so our focus was on preparation rather than major redesigns. Instead of introducing new mechanisms, we prioritized manufacturing critical spares and reinforcing key components to ensure we could handle the demands of a high level event. This allowed us to stay consistent and avoid major issues during competition. Our robot’s reliability and adaptability were key to our success. With strong match-to-match consistency, we were able to contribute points and support our alliance members in every match. The work we put into preparation paid off, as we maintained smooth operation throughout the event demonstrating Valence as reliable and robust, ranking 7th at the end of the qual matches. As Alliance 5 Captains, we selected 971 as our first pick and 3256 as our second pick. Our alliance worked well together, combining [...]

During Week 5 we competed at the East Bay District where we finished in 2nd place finalists. Our robot performed reliably throughout the event, and we’re proud of the consistency and progress we’ve achieved this season. We were honored to be selected for Alliance Captain 1 Team 3256 WarriorBorgs, alongside Team 10339 BrainShift, and are grateful for the opportunity to compete with such great alliance members.  We had great interactions with the judges at the event who were impressed by our intentional robot design & material choices, our upside-down brainpan design, and neatly labelled wiring. They awarded our team the Industrial Design Award. We were able to achieve a point total of 62 at East Bay, giving us a total of 107 points which qualified us for the first ever Nor Cal District Championships (DCMP). With DCMP being the following week, we knew that we could improve our robot with some additional software optimizations and some new auto routines. We also want to ensure our drive team maximizes their time on the practice field, focusing on timing during active and inactive periods of play. Thank you to Berkelium and all the FIRST volunteers for organizing and supporting such a great event. We’re incredibly [...]

We had a successful Week 2 Silicon Valley District event. Our robot was reliable, robust, and capable of handling heavy defense, and our shoot-on-the-move (SOTM) capabilities helped us rank 4th after quals. As Alliance Captain 3, we selected Teams 5026 Iron Panthers, 1351 TKO, and 5499 Bearium, and we thank them for being great partners in the playoffs. We were honored to receive the Quality Award sponsored by Apple. Thank you to Team 100 Wildhats for hosting and to all the FIRST volunteers who helped support the event. We are proud of the team’s performance and progress this season, and look forward to competing in the Week 5 East Bay District event.  With the next competition being at Berkeley in Week 5, we had a lot to work on. We decided to fix the damage to Valance and give our team driver some driver practice to improve his skills. After his practice, we decided to improve our Autos and implement new code into the robot, like a turret hood-down feature for under the trench, and we also reworked our intake kicker bar so that it intakes quicker and that there is a lower likelihood of jamming it on a ball. We also chose to look for a new [...]

Spartan (971) Week 0 Scrimmage Arriving at the 971 Week 0 Scrimmage event site, we safely offloaded the pitcases and robot from the trailer, and unpacked our pit cases in our designated pit location near the field. The team worked well getting everything set up, including configuring our RADIO so we could move to field calibration. We also had a few of our team members help out by volunteering at the event, covering field resets, refereeing, and clean-up at the conclusion of the event. The Spartan Week 0 event was incredibly successful for the team, resulting in many learnings from working in the pits with new students, how the robot operated on the field in an Alliance with 5 other robots on the field, and potential match strategies. The team used these learnings to inform what to focus on as we prepare the robot and spares for the  Week 2 Silicon Valley District event. The robot performed well and exceeded our expectations for a week 0 scrimmage. From a mechanical design standpoint, the robot was thoroughly battle-tested during matches. It absorbed several hard impacts with both field elements and other robots, demonstrating that the team has built an incredibly reliable and robust robot. Members of the drive team [...]

Week 0 Scrimmage Preparations: As we continued to work towards the Spartan Week 0 event, we finalized the list of our competition members in both the pit team and strategy. We made some final touches and adjustments to have a competitive robot to field at the event. The week leading up to the event, we allowed the software team to make some major improvements to the robots functions while our new driver and drive coach got prepared. Intake / Store Testing: Throughout the preparations for week zero we made minor tweaks to the intake and store subsystem, our testing revealed some performance issues which need to be fixed. We found that many of the balls would shoot out of the top of the hopper rather than going into the dye rotor (spindexer), so we added a net to the extending portion of the hopper.  Shooter Testing: Over the past two weeks of FRC, our team has had several successes and roadblocks. Our turret now aims exceptionally well using a phase shift combined with the robot velocity. It’s been smoothed with a linear filter for limiting jitter. Our shooter and hood are currently operating well, and have a strong outtake speed, looking forward to seeing how it works at [...]

Convergence: Build Week 5 & 6, which spans work days 21 to 30 for our team, is the time of convergence. The drivetrain and Control System Board (CSB) were completed by Work Day 12. The software groups worked on code to validate what would be required for each of their respective subsystems. The various CAD groups turned prototypes into real subsystems, going through many preliminary design reviews (PDRs), iterations, and then final critical design reviews (CDRs). The Spindexer (dye-rotor), floor, and racetrack required some extra time to finalize their designs. During this time, the manufacturing group started to manufacture subsystems that cleared their CDR phase, our 3D printers have been working overtime as well. Subsystems assembly teams have been very busy. Our three robot driver candidates continued to practice with our prior-season robots to become familiar with optimal drive paths within the Alliance and Neutral zones, traversing the bump, and going under the trench. Intake and Store: Assembly work was completed on the intake and store. The Control Systems team completed all the wiring. We moved the robot to the field to validate the end to end operation by running several tests. Our robot driver was able to test acquisition of game pieces running at various speeds while the intake and store hardware [...]

Prototyping Climb Decision: Telescoping arm - After weight and packaging considerations by the team at large, we made a DVC decision to redistribute the workforce of the windmill climb to the telescoping climb. The windmill design added extra structure and instability, which increased weight and made integration more difficult. The telescoping climb offered a more compact and straightforward solution that fit better with the rest of the robot. Refocusing the workforce allowed the team to improve reliability and spend more time testing and refining the final climb system.   Intake & Store: This week, we have been finalizing the wire management of the intake motor, as well as the mounting for the back wall of the hopper. We decided to use 3M Dual Lock to attach the back wall to the side walls, so it’s easier to access the battery and service other mechanisms above the drivetrain. We also decided to bend the back wall around our climb rather than go around it to make it easier to attach and detach. Spindexer: The CAD and design of the dye rotor were adjusted throughout the week. We were able to make a lot of progress CAD-wise, and we began manufacturing the hex shaft and [...]

At the start of build week three, our Decision Voting Committee (DVC) made some important decisions regarding what mechanism had conceptually demonstrated the ability from a hardware and software point of view to support our functional requirements & strategy, and what mechanism would be given an additional week of prototyping time. Our Intake and Store, Spindexer, and Turreted Shooter were approved for our competition robot. Our two climb prototypes were given another week to finalize their prototypes. Intake & Store: Over the past week, our team has been completing the intake CAD. We decided to do a linear intake with an extendable hopper on top of it, so it can store more balls. For this design, we made the hopper extend horizontally while the intaking mechanism extends at an angle, allowing us to have a higher capacity while still fitting under the trench, even when the intake is stowed. We are now finalizing our mounting system, which will allow our manufacturing team to get to work. Spindexer: With the decision to move forward with the spindexer our cadders started working on the CAD for a more complete design based off of our prototype to be integrated with other subsystems. We are taking inspiration from the 111 [...]

Build Week 2 was a hive of activity with 5 groups focused on prototyping, while a sixth group worked on our Alpha Bot. A final group of students focused on delivering a competition drivetrain (DT) and control system board (CSB) by Work Day 12.  We mounted a turret onto a spare drivetrain with a hoodless shooter. Using two cameras, vision allowed us to calculate the turret’s position in order to score in the hub. We successfully compensated for robot movement by providing shooting on the move (SOTM) and intend to further tune it, then experiment with a real hood. We tested a design for linear climb using three sets of hooks, which let us get an L1 climb, but for L2 and L3, we encountered some issues with the hooks not reaching and the tilt of the robot. Our hooks are spring-loaded, which allows them to go from below the rung. We are pivoting the design to a fast L1 climb, as L3 will likely not be point efficient. We tested our prototype v2 of the windmill climb, and with some human assistance, we got an L1, L2, and almost an L3. We had some issues with the auxiliary arm getting caught on the [...]

On kickoff day, our team immediately dissected every aspect of the new 2026 FRC game, “Rebuilt.” We constantly reviewed the field layout and put ourselves in the minds of the game designers to reverse-engineer strategy. Our team reviewed the manual for hours, and we broke out into groups to discuss our thoughts on certain rules. Coordinating as a team again, we compiled our thoughts about the manual and then quizzed ourselves to truly master the game. With the game’s dimensions, regulations, and facets in mind, we started to strategize using previous lessons from our mentors’ presentations. We organized our functional requirements into four categories: shall have, expected, could have, and shan't have. Once we finalized our robot’s functional requirements and expectations, we tackled our strategy for the game. This consisted of numerous pitches from our breakout group expressing what they thought was the best strategy for this game. We discussed whether we should utilize the trench by making our robot short, the possibility of stealing the fuel from the opponents, the benefits and downsides to using the human player, and how high we would want to climb the ladder. Once we started our prototyping days, it was clear what we would want to see on a robot. [...]