View Single Post
  #1   Spotlight this post!  
Unread 28-08-2016, 23:16
GeeTwo's Avatar
GeeTwo GeeTwo is offline
Technical Director
AKA: Gus Michel II
FRC #3946 (Tiger Robotics)
Team Role: Mentor
 
Join Date: Jan 2014
Rookie Year: 2013
Location: Slidell, LA
Posts: 3,570
GeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond repute
Re: Build season week 1

I realized that it is not clear from my earlier post, but our week 1 prototyping was primarily for the purpose of determining the "difficulty" of various manipulator approaches. Of course, we always want to remember the key points were from these efforts!

As I read through the responses, I realize that someone should more clearly state that the design process should generally run:
  1. Understand the rules (requirements)
  2. Plan your strategy (that is: which requirements/rules/scoring opportunities take priority)
  3. Prepare two or more designs
  4. Evaluate designs against your strategy and priorities; pick a design.
  5. As problems emerge, evaluate proposed design changes against your strategy and real-world findings
Most teams should probably be in step 3-5 overall at the end of the first week; we have been both significantly ahead of and significantly behind this in various years. We currently strive to be at step 5 for the drive system and step 3 or 4 for manipulators by the end of week 1.
__________________

If you can't find time to do it right, how are you going to find time to do it over?
If you don't pass it on, it never happened.
Robots are great, but inspiration is the reason we're here.
Friends don't let friends use master links.
Reply With Quote