Welcome to our thread!
2025 Links
4192 is excited to join the openalliance for the 2025 Season! We’ll be competing week 2 at Plano and week 4 at Fort Worth.
4192 is excited to join the openalliance for the 2025 Season! We’ll be competing week 2 at Plano and week 4 at Fort Worth.
We finished the season ranked 39th in FiT District (3 DCMP playoff wins away from Champs).
I’d also like to congratulate our own FTC team 12791 for winning the FTC Inspire Award and representing team USA at FIRST Global!
At NTX, we ran our 2024 robot unmodified from the 2024 season. We had several issues and mostly played defense as a result.
Thanks to 3676 Redshift Robotics and 6369 Mercenary Robotics for inviting us to your alliance!
We had a blast at NTX, thanks to all the volunteers and teams who made the event possible!
We disassembled our 2024 intake after NTX. We kept our shooter/elevator together for reference/part storage for 2025, but our intake is back in the cabinets.
To practice rapid prototyping, we built an UTB intake, and it mostly worked!
We used both 1/5” plywood and 1/8” hardwood with success.
Prototyping went well, but we made a few mistakes.
We disassembled our drivetrain and inspected the damage from 2024.
The damage wasn’t too bad this year: our drivetrain tube did bend at the bumper mounts, but the damage was contained to a small area.
Overall, while we’re happy with our current levels of damage, we’ll make a few improvements for reefscape:
Underrated meme
Based on the leaked reefscape manual, we designed our 2025 drivetrain. For 2025 we’re planning a 28”x28” chassis.
The bumpers are composite parts, so hiding them when looking “behind the bumper” should be easy.
Thanks to onshape, drivetrains are easy to cad, so having a configurable drivetrain ready before the season doesn’t cost much time. More importantly, the drivetrain can be a reference for good practices and file organization.
I’ve made a lot of spreadsheets/docs for FRC over the years, here are some that you may find useful!
This sheet, developed by teams 353 and 358, has helped us a ton with submitting grants/sponsorships (and my college apps lol). This is the same as the original, but with more formulas (google sheets is the only programming language I know).
Because the shared sheet is not actively updated, the dates/requirements may be off. I also removed some that were not relevant to us, but adding new grants/sponsorships is not too difficult. Make sure to check with the original and update any incorrect ones (:
Thanks 353 and 358 for the awesome resource!
This is just data from reca.lc in a spreadsheet comparing different COTS Swerve ratios. The scores are arbitrary and don’t work. The spreadsheet assumes a 118 lb robot (our 2024 weight) with 15 lb of auxiliary weight. I’ve used this sheet to compare ratio choices between teams and motors (L4+ Vortex on a 40lb robot is the future).
This is a document showing the progression of our DunkTank robot REBOUND’s version history. It creates some pretty cool graphs, and highlights “trends” (procrastination) in our design process. I’m definitely making one for our 2025 season bot; we’re at version 30 or so already (:
Here’s our prescouting before Amarillo. We used QRScout for data collection, but quickly realized quantitative data was mostly useless (vibes>data). The cool thing about this is the “PlanoData” Sheet, where I calculated that, through match 27, the alliance who collected the most midline notes won 89% of the time. Interestingly, we were on the only alliance in this dataset to win a match with only 1 midline note (statbotics gave us an 8% chance of victory before the match). We had a wild numerical season: statbotics went 4-8 at our first event, 10-2 at our second (with a streak of 10 matches) and 12-0 at dcmp (22 correct qualification match streak).
For our first pick at Amarillo, we basically just used vibes (the data on teams was too close to determine the “correct” pick). Afterwards, I wanted to see how we could avoid making the same mistake in the future. Here are some of my findings:
Ultimately, we switched to Lovat for dcmp, which helped us improve for playoffs/alliance selection.
I created this spreadsheet to find the “easiest” event for us in 2025. It’s not particularly useful, but it does provide some interesting insights. Rank (opr) and Trev Rank are both for 4192 (where our opr ranks, and where I rank us. If I remade this today, the trevrank would be <7 for all events)
This is how we cook up our open alliance posts. Google’s headers automatically copy into markdown, so no extra work is needed. There is also a (not well hidden) easter egg in the document (:
I hope some of these turn out to be useful! I love making spreadsheets, these are some of my favorites.
I would love to see more about the graph/how it works.
Looks awesome, love the excel work (and may need to steal some inspiration for upgrading the grant database.)
The process is pretty smooth.
There are a lot more days in the season that I would’ve thought (especially when you start CAD 2 months early), so later on I’ll update it with a weekly option as well (the chart can become messy).
To save the graph, you can use sheets’ “download image” option, which lets you save as a png or svg.
Happy kickoff! Over the coming days, we’ll post our strategy, would’ves, should’ves, could’ves list, and a few other things.
Good luck in REEFSCAPE!
i’ve got a lot of thoughts.
Today we met at our library to discuss our team goals, watch the reveal, read the manual, and consider effective strategies.
We created a needs/don’ts list, but we misread the manual and didn’t realize that the alga goes to the opposing human player, not your own. So, we’ll reconsider our list of objectives.
rank | Needs | Don’ts | tbd |
---|---|---|---|
1 | auto leave | opposing side auto leave | preload coral score |
2 | alga only | coral | |
3 | alga ground intake | deep climb | |
4 | alga auto intake | ||
5 | park (june) | ||
6 | shallow climb |
Our analysis of this game found a couple of things.
With an alga-centric robot seeming unlikely for us this year, we’ll start planning which field objects we’re constructing for 2025. The reef is necessary, but the coral dropper and barge are questionable for us (we’d rather prototype climb on an actual field). As of now, the processor seems unlikely.
I’ve done some krayoncad, expect that & some sketches later tonight. I wanted (anti-3DM) to do a 1 dof robot before game reveal, but that seems unlikely given the performance boosts of a second dof.
“Just watch ri3d bro”
2dof (without ground intake).
Pros
Cons
“He made me experience high tide!”
This design uses an elevator & wrist to score in all four levels. Similar to 3847/4414 in 2023, it could be another option.
Pros
Cons
I don’t know why but the correlevator really looks like it should be a double pendulum to me
(Alt: my Reefscape hot takes)
Level 3 coral requires algae removal (2 algae per coral). In order to score level 3 coral, we’d need to consistently be able to both
These two tasks could require a lot of prototyping, which may be different from the final field.
Shallow climb is worth 6 points, requiring another shallow climb & a park to reach the barge rp. 6 points is also most likely inconsequential for playoffs (a park is more efficient), so it may be worthwhile to go deep or go home.
Dual-caged deep climb may also be a trap. While climbing on two cages does seem easier, cage alignment may be difficult to consistently climb (without swinging). Prototyping and testing this system would also be a challenge.
Is prototyping & testing a climb really worth it? If deep-climbing is common at our two district events, it may be worthwhile to just park instead of designing a deep-climber. Potential designs right now (arm latch + drivetrain rotation, dual telescope climber for two cages) may be too slow to comfortably run in playoffs, and the traffic near the barge during playoff match end could take more time.
I’m curious to hear other opinions on potential Reefscape traps.
We added a fixed roller claw to the double-jointed arm concept, and the geometry seems to fit. This robot is able to accomplish most reef tasks (except for L1 and L4 scoring). The ball can only remove the algae between levels 2 and 3, and seems to be capable of scoring into the processor (with assistance from coral intake).
If we chose this archetype, we won’t pursue level 4, as we’d need either
neither of which are a good idea for this game.
This elevator only uses 1 DoF to score in l2, l3, and l4 on the reef with human station intake. However, compared to the 2DoF arm, the elevator is still more complicated.
We won’t meet in person until Tuesday (expect a mega post that evening or Wednesday), so for now we are planning out our next few weeks.
Here are the field elements we’re looking to construct:
Barge doesn’t seem too useful yet; we’ll probably wait to see what other teams come up with for climbing.
We’ll start designing prototypes soon, here are some things we’re wanting to test out:
(Cranberry Alarm end-effector prototype)
We’ll be looking to intake coral from the station and potentially ground, so there’s a few things we need to test out. The cranberry alarm end effector seems to work with our design, and may be able to remove algae from the reef.
(our double-jointed arm design with a fixed algae reef intake.)
We’ll mostly be moving algae from the reef, so the testing is focused on finding ways to package an algae intake.
(our 2024 climb used passive hooks with surgical tubing to return to position)
To determine whether a shallow or deep climb is more valuable, we’ll need to test different latching methods.
4% of build season gone, 96% left to remove!
Last night, we developed a mastersketch for the coralarm concept. It should be capable of scoring into L2 and L3, while also removing algae from the reef.
The arm uses the same position for L3 and L2 scoring, allowing us to rapidly switch.
This design seems to be pretty competitive. It also saves room for a potential ground intake later in the season, if ground intakes are needed.
Here are the main problems with this robot: