FRC Deep Dive - 254 Cheesy Poofs - Inside Look/AMA - Giveaways

254 almost always makes robots that are perfect for the game(or at least have a base for the perfect robot to iterate later- 2019 for example), do you have a special method for analyzing the game or do you just go off of experience?


From when future drivers walk in the door to when they are driving on einstein, what is the process like to choose them and train them? I’m mostly interested in your off season drive practice system, and how you train against defense.


How do you take on teaching the students about advanced control subjects, such as non-linear feedback and the ramsete controller?


How do you plan your wire/tubes so well? I don’t see any tubes for the pistons on the wrist for Lockdown.

How do you guys build your bumpers? How do you mount them in particular? (Pins???)

1 Like

254 Bumpers

1 Like

How did you machine and attach (looks like weld?) the linkages at the end of the arm? Also, are there any significant printed parts worth pointing out in detail?

1.How do you guys disguise or hide your wires?
2. How do you acquire some high tier sponsors? do you make your robot so light?

1 Like

I asked this question once a while back. The answer I got? Velocity.

That’s just… playing with physics…

That’s a clown question - there’s only one valid flavor of caprisun.


As building such a sophisticated robot must take a lot of effort and time, how did you arrange your build season so that you were able to build and test your robot in time? Besides, may you share your experience about how to design the parts for an excellent robot? (e.g. using stimulation to ensure that a conponent can work properly, perhaps?)

What does the learning curve look like in the 2017-2019 era vs earlier periods of poof awesomeness?

i.e. Is there freshman/sophmores in key positions? Or does that almost always fall on seniors? Is all this handled on a case-by-case basis?

There is defiantly merits to having a very experienced student in the same position for 3+ years, conversely there is an argument for a junior/senior with greater competition experience to pass the baton down the chain.

1 Like

254, please elaborate further however you see fit. For example,

  • Were there driver behaviors involved to avoid getting stuck, groomed through practice?
  • Was there a minimum speed the drive train was allowed to move?
  • Were there skid plates, like 2012? Does powder coat count as a “skid plate” ?
  • Is it worth the risk to attempt this for teams who only have access to the team version of a field?
  • Was a brain pan really all it took?
  • etc

Thank you for all the questions! Please post any more you may have by end of day. It will be more difficult to catch ones tomorrow as we prepare for the show but you can always ask live on air at

What kind of 254 giveaways are you interested in???

  • What do you do during your offseason?
  • How does your design process work? What steps do you take to go from a set of requirements (as seen in the table in your Tech Binder) to a mechanism? I ask primarily because your team always seems to come up with the “obvious once you see it” design that is, by the end of the season, the most effective system on the field.
  • How does your code development/testing/integration process work?
  • How do you CAD multiple mechanisms in parallel while avoiding geometry conflictions?
  • How do you pass experience and knowledge from one generation of students to the next?
  • How do you select a drive team?
  • How do you maintain team morale throughout the full year, as well as during the difficult build season?

definitely hats or sweatshirts

how do you guys approach teaching students the build side of FRC weather it be new team members or team members who are looking to learn something new.

Hey, would that new guy that’s joining the 254 keep of record of the surprises / differences he sees in how they function so that he could come here and give us some feedback on what they do that’s unusual? A set of ‘fresh eyes’ often identifies many things that 254 team members may consider every-day.