Strategic Design Workflows in Onshape Presentation

I was recently inspired by 8033’s heavily convoluted design process in 2023, along with some recent offseason posts by phenomenal teams talking about their design process, especially this post from BREAD 5940, to go down a major rabbit hole.

I wanted to answer the question: Can any team guarantee, through a robust workflow, with no experience of FRC game metas, that they will end up with a strategic robot that can play the game well?

There are many great posts and presentations about game analysis, strategic design and building a robot that is robust and minimizes failure points. Some of my favorites are @Michael_Corsetto’s original strategic design presentation (rollers are king) and @Karthik’s classic FRC presentations (don’t miss them at champs!).

But, I think there has been a shortage of information about the specific workflow that you can follow to “check all those boxes”. It’s really hard to give such a presentation since there have been so many different ways that teams go about designing and building a robot. But given the recent uptick in teams using Onshape due to the discontinuation of GrabCAD, and the more systematic process that Onshape encourages, I thought there might be more space for a more detailed workflow presentation now.

The fruits of my efforts is this slide deck, which I’ve titled “Meta-Strategic Design Workflows in OnShape”. The term “meta-strategic design” refers to the strategy and methods surrounding wider robot architecture - E.G. before the subsystem brainstorming stage.

Some of you might know that I gave an early version of this as presentation at WRRF a couple weeks back, and it went pretty decently. That was kind of like a beta, and since then I’ve added several new slides and a ton of new content to make it more useful. In my original talk, I didn’t take enough time to explain what Masterketches at their core really are and how to do them step-by-step. So I think there’s space for an updated series of videos or presentation using this newer deck. If I decide to make a new video or present somewhere with it I’ll send it here.

There are many, many elements here that are super debatable, but it’s gotten to the point where I’d like to share it with the community and see how it’s received. Tons of people in the FRC community are far more knowledgable than me (I’m just a student on 8033), and I’m sure theres ton’s to add. Please give feedback so I can improve it!!

As a final note, HUGE thanks to 5940, 973, 5460, 3512, 6657, and others for visuals and resources that I used here. Not only have your rescources allowed me to make this presentation, but they have seriously fundamentally changed how I see FRC, and I really appreciate all the knowledge you are sharing. If any of ya’ll would prefer me to remove your images / CAD, shoot me a DM and I’ll do it ASAP.

Anyways, here it is. Let me know what ya’ll think.

P.S. if anyone does the hands on portion on their own (slide 22) let me know how it goes!

36 Likes

Can confirm this is really cool

11 Likes

One of my favorite presentations when i had to kinda learn more Strategic Design was the Spartan Series video with Adam heard (https://www.youtube.com/watch?v=JyPHwNx_KXM&ab_channel=smanrobotics)

If you go through the slideshow, you’ll find some really nice materail including a rubric-esque thing that you can use to grade your architectures

image

I kind of broke down the presentation in different questions/biggest takeaways that I’ve sent to my team(still watch the video its a very good video):

  • Integration: How hard is it to integrate your architecture? (your entire robot should not look like a gearbox)
  • Invention: If you need to invent something over the course of build season, maybe you should step away from that idea.
  • Tactical Features: How you achieve your goals. (generally skip these) We saw this in 2019 through 5026 double robot climb, as its a feature that allows us to help our alliance.
  • DOFs: If your robot has a lot of degrees of freedom, that introduces a lot of failure points.
  • Coordinate motion and sequencing(handoff system): Do the actuations have to happen in an order(good example 5026 in 2023. If you need to hit a very specific angle to score, there are so many confounding variables that can mess this up(backlash, motorwear,bad design for control…etc).
  • Mechanism types: High force mechanisms like climbs, lifts, launcher, winches can be tough. Launchers and winches shift under higher load which can cause a lot of problems at competition.
  • Tuning: How easy it is to adjust your system. Having to rely on things like a practice field or swapping parts out means that maybe its not as simple as you want.
  • COTS Usage: Using COTS when possible(Rev ion set) will help us fabricate our robot very quickly, as well as implementation with other parts.

the biggest thing i think teams struggled with was actually working through architectures quickly, and i think next season we’ll that change with addition of KrayonCad.

4 Likes

@AdamHeard’s presentations are great and yeah, those are all great points, along the thread of Mike’s talk. I missed the shoutout for sure :slight_smile:

I’m curious how Adam feels about how to run those first several days in build season aside from those strategic design decisions re sketching, blocking, etc. I’m pretty sure 581 is still on Solidworks so stuff like KrayonCAD isn’t quite as easy to navigate but they still aced the architecture in 23 so I’m sure they’ve got an awesome workflow.

1 Like

Not from 581, but I do know that their off-season robot was done in onshape and the cad link for their 2023 robot is an onshape link, so I’m pretty sure they use Onshape, or at least are switching to it for 2024.

3 Likes

:laughing: I was thinking of 599

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.