View Single Post
  #8   Spotlight this post!  
Unread 02-09-2016, 23:16
SoftwareBug2.0's Avatar
SoftwareBug2.0 SoftwareBug2.0 is offline
Registered User
AKA: Eric
FRC #1425 (Error Code Xero)
Team Role: Mentor
 
Join Date: Aug 2004
Rookie Year: 2004
Location: Tigard, Oregon
Posts: 486
SoftwareBug2.0 has a brilliant futureSoftwareBug2.0 has a brilliant futureSoftwareBug2.0 has a brilliant futureSoftwareBug2.0 has a brilliant futureSoftwareBug2.0 has a brilliant futureSoftwareBug2.0 has a brilliant futureSoftwareBug2.0 has a brilliant futureSoftwareBug2.0 has a brilliant futureSoftwareBug2.0 has a brilliant futureSoftwareBug2.0 has a brilliant futureSoftwareBug2.0 has a brilliant future
Re: System Design Requirements

1) Minimize cockpit workload.

Time spent fumbling with controls is time not used to pay attention to what's happening on the field. And if there are fewer steps to be done there are fewer steps to do wrong. On our robot this year it was possible to do a scoring cycle with the gunner only pressing a control twice: once to enable the intake and once to fire.

2) Tolerate failure.

Whether it's wear, a design flaw, or an opposing robot reaching in and riping out wires, failures will happen. We broke several chains in our drive train this year but due to the design none of the breaks did more than unpower one of our eight wheels. Similarly, all the automated functions on our robot could be overridden by the operator, allowing them to adapt to unforeseen circumstances.
Reply With Quote