The Trobots 5013 are happy to announce that we will be participating in the Open Alliance for the 2023 FRC season Charged Up.
We believe the open alliance will provide us with the following benefits
- Commitment device to produce better documentation and keep our CAD up to date.
- Peer review. Sometimes we have bad ideas, the faster we realize it the better.
- Visibility. We want to get our name out and get known better outside of our region.
It doesn’t come without a cost of increased time commitment to keep everything updated though.
Since Champs we have done a few things:
We are switching to OnShape to allow for easier usage from any machine and easier sharing. So we had a few training sessions where students worked on designing a robot cart. We did not get around to finalizing any of the designs or building but the practice was good none the less. Link to our OnShape Team
We also developed a Lego robotics camp curriculum for a Girl Scout camp. The camp went well and the girls really enjoyed seeing the competition robot shoot the big tennis balls.
We attended Cowtown Throw Down. An offseason event in Lees Summit. It is a great event and the competition was fierce. Since we didn’t have any trained climbers and we really like our swerve modules we chose not to exercise our famous climber.
We ended up as captains of the #3 alliance and chose 1939,1764, and 1763 as our alliance partners and went to the semifinals. Incidentally at Heartland 1764 was our first pick and at Central Mo 1939 was our first pick. So we were getting the band back together.
Next year our biggest goal for our robot is reliability. Last year through regionals and champs we suffered from electrical unreliability. At Cowtown we had no electrical issues. The difference? Solder. on all of our 22-24 AWG connections we went from Wago connecters to solder and it served us well. The only issues our robot had were a cracked polycarb intake plate and a broken belt. Both of which we had spares for and both of which were non crippling damage for the match.
Over the summer we did fix a code issue with our autonomous routine that had plagued us. Our robot didn’t make it the distance we intended. We had used PathPlanner. The problem we had was the constraint declaration for our controller had declared the max speed as the robots theoretical (not practical) max speed and not the max speed of the leg of the routine. This led us to no be able to travel the whole distance of the leg. We now know better.
Our github for those who are interested.
We look forward to learning from and sharing with the rest of the wonderful open alliance teams.