Dreadnought never got to compete at a regional, but we are (as long as the school allows) going to pursue attending California offseasons this Fall. We are still deciding whether or not to release the build blog, but we will eventually be releasing the 2020 Code when it is ready.
Myself and other students/mentors from the team are also happy to answer any questions you have about the robot and these past two seasons, but I advise anyone to skim through the Technical Binder before asking a question.
We do not upload / directly share CAD files, but I can pull up screenshots if needed to clarify confusions.
Mind sharing a CAD screenshot of the linkage for the chock and the actuation of the ramp in the back of the serializer? These renders look dope, but it’s a bit hard to make out some of the smaller details from the pdf.
Are you guys using some sort of traction control code? I remember doing the math for 4 falcons and something like 13ft/s would already get you wheel spin.
How much did you struggle with getting the balls to settle into the serializer? We also did top load for 2020 and realized one of the biggest struggles was to quickly get balls from
Intake to there and settled.
You guys also show a picture pointed towards goal where you have what looks to be two balls still pinched by intake and some balls in serializer too. Anything special in programming sequence to stops jams and/or get fast feeding in that scenario?
Any video of how that bar off back of intake works for feeding/intaking?
I sort of remember you talking about solving controls problems in hardware instead of software in one of your Citrus Circuits Fall Workshops, but I’ve never been able to find the specific one again since watching it originally. Wish I could, it was really well done IIRC.
In your strategy decisions, you say that you decided a buddy climb mechanism would be beneficial, but you don’t have any mention of it elsewhere. Did y’all choose to not go through with a buddy climb, or was it something that you planned to implement later?
Great job on the documentation, btw! Super helpful and easy to follow!
Seconding getting more details and/or any available CAD screenshots of the buddy climb. A quick motor count leaves a single remaining PDP slot that could have been allocated to the mechanism, and a on the drivetrain page of the technical binder we can see two pancake cylinders, presumably for deploying it:
Since their 2020 FRC Season page has their weight listed at the 125 lbs limit, I assume they just didn’t have the weight for it.
On a different note, and since I wasn’t able to type all of this out earlier since I was in class, thanks for doing this Q&A. Your technical binder threads are probably my favorite threads aside from the 254 Robot thread, less so because of the binder itself (although it is certainly a great resource) but more as a result of the information that can be garnered from your responses about the reasoning behind design choices and the specific detail from your CAD screenshots. Just a lot of great stuff in general, and a pleasure to read through after the fact.
We ran about 21 FPS free speed a few years ago, had a ton of fun with it, But also found it a bit uncontrollable. Can you go into more detail about gearing that high, and how you address controllability issues?
Allows the operator to select between the outer port and the inner port
This is such an underrated, under-discussed bullet point, and I’m really looking forward to the public code release! Just attempting to figure out if the robot could hit the inner goal exposed my programming team to a number of things like strategic CAD sketches, multilateration and imaginary point projections.
Great work as always! I love the details that y’all put into these tech binders. I’m curious about how the shooter hood articulates, the back of the shooter seems to be obstructed in the pictures.
It looks like it’s just a printed Markforged Onyx sector gear, integrated directly into the back of the hood. 2910 used a similar hood design in 2021, think it might have been based off of 254’s, but I can’t remember my source on that.
Looks like those pancake cylinders are in the bumper zone, and the drivetrain has a matching set of holes on the front rail. Some kind of quick-change bumper mounting scheme?
Considering the contents of this post, I personally doubt it.
^ Circa October, 2020
Also, you can see the 3/8”-16 thumb screws in one shot of their 2020 Season Recap (pictured and linked to above), in roughly the same position as the outermost set of holes in the back rail of their drivetrain pictured in my original screenshot of the binder. (IMO the cost-benefit analysis for that doesn’t really work out either [costs: weight, complexity, use of a manifold slot, loss of robustness; benefits: slightly faster, easier bumper attachment?])
CHOCK
The Chock was a late addition that helps the Serializer. While intaking, the Serializer is contantly running counter-clockwise (when viewer from above). As the first few balls come in, they will get swept around and back to be under the shooter, making space in the front half of the serializer for the next 2-3 balls to fall in. When we are ready to shoot, the chock gets lifted and the serializer spins up while the shooter spins up.
The Chock itself is just a fixed plate and a moving plate. A cylinder pulls the moving plate down. Pivot is a shoulder bolt and a bushing.
“Skatepark Ramp”
Normally while the Serializer is spinning, the balls barely contact the 2 Feeder rollers. When we want to shoot, we needed some way to slightly elevate the balls above the normal serializer floor they were rolling on, so they would contact the Feeder and get taken up into the Shooter.
The Skatepart Ramp is our nickname for this little pancake cylinder that just pushes up a flap of 1/16" polycarb to create a little ramp that guides the balls up to the Feeder. Nothing more than a cylinder whose rod pushes directly on a piece of polycarb is thin and fixed on one end.
