View Single Post
  #1   Spotlight this post!  
Unread 15-08-2013, 23:10
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
Choose your own control-system adventure

Here's a list of possible things one might want in a robot control system:

1) Processing speed
2) Code space
3) User-available RAM
4) IO capabilities
5) Radio bandwidth
6) Code download time
7) Clean programming interface
8) Durability
9) Software reliability
10) Radio connection reliability
11) Boot time
12) Price
13) Compactness

If you were designing a new robot controller for FIRST what would you prioritize?

(I've been inspired by the thread about the new control system and seeing the "FIRST team survival excercise" thread. )

Last edited by SoftwareBug2.0 : 15-08-2013 at 23:11. Reason: Forgot a word
Reply With Quote