CentrifugeBuild update
Rip centrifuge 2026-2026 May big colson live ever onRip centrifuge 2026-2026

FIRST Robotics Team 4322 – Venturing Crew 1701
CentrifugeRip centrifuge 2026-2026
And finally, everyone else who I didn’t mention here and probably should’ve, which also includes many of the people who helped make the “build blog” what it is today. Thank you for your hard work and support that helped make this thread possible.
To give a bit of a preview of what we’re lining up for 2027, the team’s currently undergoing a whole bunch of internal overhaul, which I’m excited to document our journey through in the hopes that it helps others. It may mean that the posting schedule will not be super frequent as I devote energy into this all-hands-on-deck project. We still plan on running a 2027 “Open Alliance” build thread.
One of the primary pressing issues is that the team’s kinda broke at the moment, so that’s a high priority to navigate. We are, uh, very open to donations and sponsorships…[1]
If one were to donate to the City of Orange Public Library Foundation with “Robotics” as the memo line… ↩︎
I got more. CD wouldn’t let me post 'em all at once.
I am so tired of rebuilt and was happy to take a break from drive coaching a few matches at Beach Blitz… Looking forward to Biocore though
Centrifuge15 photosWell, this is it. The last Rebuilt event.
The event itself was pretty stacked. We had high hopes for our performance for this event coming out of Tidal and with a new robot upgrade, but the qualification schedule and matches made it relatively apparent relatively quickly that even getting to finals here was a bit of a long shot. Other teams (in particular 5199, shout out to them) were out-shining what we had and we were just finally running up against every single fundamental limitation of robot design decisions made in January.
But we still gave it a good shake, and managed to:
After Tidal, @Alon22 of 7415 and his brother Lior offered to drop by after their FTC meet on the Saturday morning to help out. To even do some…live-action roleplay, if you will.
He drive coached several of our matches, helped a lot with pre-match strategy, and helped out during alliance selection strategy along with half of 7415 who also showed up for the Sunday to help out generally as well. (We had a 7415 kid as our HP during elims.) It was a really fun extension of what we had started at Tidal.
In exchange, I’m ostensibly going to help out quite a bit with awards for his FTC teams, and possibly other tips like “don’t rebuild 3 weeks before regionals.” Because, that’s like, the one thing I, @guineawheek, am qualified in FIRST to actually talk about off the cuff. I barely know anything about FRC by comparison. But I can tell you how to make a very good FTC presentation script, pit judging setup, and portfolio.
I do find it as much fun and as energizing as Alon seems to find drive coaching, though, so don’t get me wrong, this is very much a win-win.
I can’t wait to work again with Alon for 2027 Port Hueneme, along with @Eeshwar, who is as far as I can tell the most excited person on Earth to be attending Port Hueneme next year.
Seriously, he’s obsessed with that venue, despite having never seen it before.

I tell this story to illustrate the truth of the statement I heard long ago in the Army: Plans are worthless, but planning is everything.
—Dwight D. Eisenhower
Using an internal tool made by a datacenter somewhere, and with the additional input of @Alon22, we mapped out possible alliance selection scenarios after the first day based on projected ranks from Match13. We used them to essentially map out things like:
Being a low-ranked captain meant that we would have solid picks all the way through.
Who did you bribe to let you assemble this alliance?!
—Friends of the team
(no, not the buggy FTC scoring website; please use ftcscout.org instead)
A bunch of key matches flipped in ways that ended up diverging our predicted alliance selection from reality. 294 didn’t attempt a burn at all; rather reaching straight for 11722 EIA as a trench dumper pick. In part due to them having some mechanical difficulties during the event, we ended up with the opportunity to pick 3476 Code Orange.
Which, despite our heavy use of their practice space, we had strangely never had the opportunity to play on the same alliance with this season, even in quals. And now we did…as the team picking them. The idea was that despite them running new drivers and having mechanical issues, they had a high ceiling.
We also nabbed 2659 on the way back, for reasons discussed previously. Their efforts, after all, were critical in them taking a match off of Tide 6995. There was some debate about them versus 599, but A7 had made that decision for us by nabbing 599 themselves. For our backup pick, we managed to snag 399 because they were:
Jeremy ended up quite involved in our pre-match strategy conversations. He even ended up behind the glass during Match 10. I’m probably not doing justice to him, because I’m not really involved in fine match strategy; I mostly just help map out picklists.
You might notice RoboWarriors isn’t Orange. They applied orange tape to their robot to attempt to solve this problem.
It is kinda funny to look at our elims matches and see this massive blob of orange behind the glass along with a kid in a 7415 shirt and a kid in a 4414 shirt (who is on 7415.)
In the end, we were out in 3, with losses being annoyingly avoidable. But at the end of the day, these sorta things happen; after all, our alliance selection strategy had some risk to it and sometimes the risk doesn’t pay out. That’s just how it is sometimes, and Beach Blitz is a strong event where every alliance is a serious contender. Our opponents did a pretty good job.
And I’d like to emphasize that our alliance partners were wonderful to work with and I think for their first event ever Code Orange’s new drivers did a pretty great job. Offseasons are precisely the place to try 'em out; heck, we were running a different driver from the one we had at Champs because Mr. Showed-Up-To-Driver-Practice-In-His-Prom-Suit was off at college to do new and cool things.
Ultimately we were mostly happy that Centrifuge’s last FRC match ever was spent doing the scoring, passing, and stealing it was designed to do from start to finish.
Beats Midtide going out in 2 last year with its intake finally fully giving out ![]()
I’m just sick of this game, man —@Indiebot
And yeah. That’s our last Rebuilt event, ever. This also marks the last real update of our 2026 build thread as well, because, well, everything from here on out is really 2027 season-facing.[1]
It’s been an adventure writing this thread that was never really supposed to exist in the first place. But I’m glad I did, and I hope you are too. I’d like to thank everyone who reads this thing, has commented on it, referenced it for their own benefit, or has otherwise engaged with it. I’m going to follow up this post with a bunch of acknowledgements, but CD doesn’t let me ping a cajillion people at once.
Thank you for reading.
I do owe the public a post about how we landed on Siraya 64D TPU for our stub rollers but I forgot to write it before writing this. So I guess you’ll have to wait for next thread. ↩︎
While we were paying the jam fix tax now, a large part of it was due to the aging nature of all the fuel this late in the season. We had instances of balls doubling up in the tunnel and the spindexer path just due to that. Even if we truely fixed jamming before offseason we probably would have had to do more because of the fuel.
Centrifuge13 photosWe added a proper expanding hopper for our 2026 robot’s sixth and final event, Beach Blitz.
Inseason, we had consciously made the decision to ditch our original expanding hopper concept in favor of a net.
As the hopper didn’t deploy reliably and was really wobbly, it was just way too much of a design problem to worry about when we had other big ongoing issues such as turret azimuth wiring and indexer jams. Going for a net meant that our robot was limited to 30-40 balls of held fuel, but in exchange meant the rest of the robot worked and it was one less problem to worry about.
And this ended up being a mostly fine tradeoff. In Galileo, we won an elims match in part because our opponents’ robot had a hopper/intake jam and we didn’t have hopper to jam against. But it also meant our scoring ceiling was a lower than teams with larger capacities and we’d struggle more in matches where there just wasn’t a ton of balls in our alliance zone.
And it was with this background that on the car trip back from Tidal Tumble, our students decided “well, what if the robot had a hopper for its last ever event?”
And so it happened, on a two week timeline. The CAD was driven by a student who had not CADded major mechanisms for the robot before, but had been involved in the Tide clone attempt. The process ended up being, in my view, a representative simulation of executing a real in-season upgrade, and it turned out phenomenally.
The hopper had a bunch of general leading requirements.
At the suggestion of some 4201 design students, our hopper had a 2910-style “triangle” with a locking pin. The geometry had a bunch of key advantages over our original design:
As is probably fairly obvious from looking at it, the hopper sits low enough over the intake that it would be exceedingly difficult for the hopper to jump over onto the intake. It could not physically flex upwards enough to do this given the slider configuration.
A previous failure mode with the alpha intake/hopper combo was balls getting sucked down the front; we addressed this in the first revs of our comp intake with stand-offs over the top roller, but here we also specifically designed balls to be able to get sucked through the intake again and deposit properly back in the hopper when the intake was raised.
Watch the video on YouTubeHaving a big old net on top was still pretty critical for capacity reasons. Apparently this whole thing made our absolute capacity go from ~45 balls to ~60-70 balls. The bigger increase, however, was the number of balls you could comfortably hold while still going under trench or just in general, going from closer to 20-30 to ~40-50, which did have some positive impacts on performance ceiling.
It turns out, however, that routinely shoving ~40-50 balls into a machine that was rarely filled past ~35 to avoid jamming does, in fact, make it jam a lot. Up until now, we didn’t really care because it was a compromise we made to focus on making the rest of the machine work good. But now we had to finally deal with it.
We ended up (re?)discovering all sorts of ways to twiddle and jam the ballpath.
This process ended up being long, frustrating, exhausting, and burnout inducing. Debates on how to properly measure throughput or characterize ball physics were discussed at length to the point of religious belief. Point is, if you made me personally build another spindexer there’d probably be some counter-rotating coaxial upper cone involved somehow.
We did not fix every jam, but we were able to reduce their overall rate significantly. In a sense, we ended up paying a tax that other teams already paid earlier in the year, but didn’t due to tradeoffs with in-season strategy.
The timeline and execution of the hopper ended up being similar to an in-season upgrade. It was conceptualized, designed, and manufactured in about a week, and took another few days for integration to get shaken out.
All things considered, the hopper turned out really well. The hopper and intake itself performed exemplary, and survived getting smashed all the time into the field and into other robots. Pretty much all major issues were second-order effects from a strategy of holding more balls.
In Beach Blitz quals, the intake only failed to deploy during auto once, and that was due to it getting snagged on a lowered turret guard that was twiddled to avoid another type of jam and not directly caused by the hopper whatsoever. While it would’ve been kinda funny, we never found ourselves hopperless.
Special thanks to 5199 for letting them use their machine shop on short and late notice.
Beached Blitz. Battery Beached. Battery Blitz? Beach Batteries? Brownout Blitz?
Ignore the intake being larger than reality, okay? ↩︎
This one is pretty good to
This was genuinely one of the hardest pick calls we have ever had to make
We were going back and forth basically right up to the wire. The other options had gotten better day 2 and not seeing 7415 score their last match was a bummer. The actual final call was not made until about 2 min before we started alliance selection. I never want to have to go through something that stressful again ![]()
After this show of hands I called @Alon22 and said “My students are a bunch of degenerate gamblers and we want to first pick you” and I think that really set the tone for the rest of the event ![]()
I think the students were sad they couldn’t go to the casino next door /s
We are Clockwork, FRC Team 4322, Venturing Crew 1701, centered in the city of Orange, CA. We first started as a small team in 2011, but have now grown like oranges to influence our community.
Meetings, virtual sessions, local events, and competition dates, merged from the team's calendars and The Blue Alliance.
FRC 4322 Clockwork
Saturday, January 9, 2027 · (noon Eastern)
The 2027 game, BIOCORE™ presented by Haas, is revealed in FIRST’s kickoff broadcast.
Part of the FIRST® CANOPY™ season.
Powered by The Blue Alliance
Your color theme, Weather sky and team colors follow you to every device you sign in on. Your location is never synced.
Off by default. Turn this on to see a short list of changes when you visit after an update (until you choose "Don't show me again" for that update). Either way, What's new is always in your notifications.
Off opens The Blue Alliance's normal site. Saved in this browser.