We used the tools discussed in Part 1 – Game Theory to determine our strategy and define our Robot Requirements in Part 2 – Robot Requirements which allowed us to prototype our Design Elements in Part 3 – Design Elements for this season’s game (and game manual). Now we are ready to build a robot.
Robot Reveal
We are proud to present “untitled robot” for your educational pleasure:
Below you can find our Ri3D Robot Technical Overview discussion:
Deep Dive Technical Resources
TECHNICAL LINKS: Build Thread (ChiefDelphi) | CAD (Onshape) | Code (GitHub) | Tech Binder (gDoc)
Lessons Learned and Next Steps
You can find our Ri3D Robot Lessons Learned and recommended next steps in the video below:
One thing to keep in mind when using an approach like this is to never close your mind off to eccentric and novel ideas. Ideas like this are what make FIRST worth doing. A novel concept like this allows you to view the technical challenges in a whole new light, and when contemplating ways to accomplish something so outlandish, you might just stumble across real practical solutions for problems you are having with your current design.
Just remember our motto, and the second letter in FIRST:
LEARN.CREATE.INSPIRE.
Summary
Hopefully these articles can help new teams, teams in transition, or teams that are just looking for a new and improved way to approach robot design to learn and apply an analytical requirements based approach this season.
stay denk friends
If you want to learn more about this process, check out our presentation from the 2017 Purdue FIRST Forums on Robot Requirements!
If you have any questions, feel free to reach out to us on Facebook or e-mail us at denkbots(at)gmail(dot)com!
As always, feel free to join the conversation on our Facebook or Bluesky with your questions, thoughts, and feedback on these articles!
Before you go, check out our reveal short with a little ditty from Indianapolis Jazz Master Wes Montgomery!