View Single Post
  #5   Spotlight this post!  
Unread 17-08-2013, 14:19
evanperryg's Avatar
evanperryg evanperryg is offline
IT'S THE BUMP N' DUMP
AKA: Evan Grove
FRC #4536 (The Minutebots)
Team Role: Mentor
 
Join Date: Apr 2013
Rookie Year: 2011
Location: Minneapolis, MN
Posts: 656
evanperryg has a reputation beyond reputeevanperryg has a reputation beyond reputeevanperryg has a reputation beyond reputeevanperryg has a reputation beyond reputeevanperryg has a reputation beyond reputeevanperryg has a reputation beyond reputeevanperryg has a reputation beyond reputeevanperryg has a reputation beyond reputeevanperryg has a reputation beyond reputeevanperryg has a reputation beyond reputeevanperryg has a reputation beyond repute
Re: Choose your own control-system adventure

Arranged them in order of importance

10) Radio connection reliability: I will be honest, it makes me furious when a robot loses connection mid-match, especially when the refs ignore it.
6) Code download time: Again, this makes me mad. Either the event needs to compensate for poor upload times or the poor upload times need to be fixed. It is not the fault of the team that code takes 20 minutes to upload.
9) Software reliability: Even if it isn't the fastest, or the most efficient, it should work as intended at least 98% of the time.
4) IO capabilities: More IOs make for more options for robot design. I have a feeling that in 5 years, FIRST will have outgrown 10 PWMs. As it is, my team was planning on using all 10 this year(ended up using 8)
8) Durability: It should be solid. I'm not saying every electrical component should be in a huge enclosure, but a control system shouldn't be/feel flimsy.
5) Radio bandwidth: We maxed out at 6fps@160x90 on our camera. Bad, but few teams actually end up effectively using their camera, anyway.
1) Processing speed: It should be responsive. I'm not saying we need some kind of quad-core, dual FPGA thing but we shouldn't be trying to use an Arduino, either.
13) Compactness: Tiny=better. Trying to cram a cRio and sidecar into the amount of available space on my team's bot this year was a nightmare.
11) Boot time: If you can get it under 20 seconds, great. But, what is more important is performance after the boot sequence is over. Anything over a minute, though, is a problem.
2) Code space: Has anyone ever actually run out of code space on the cRio? The amount we have now is fine.
12) Price: As long as we still get one free one from FIRST, there is any huge concern over controller cost.
3) User-available RAM: We've got plenty right now, but more is always nice.
7) Clean programming interface: I prefer text-based coding to gui, so I don't particularly care about this one.

tl,dr: Vex does everything right that the cRio does wrong, and the cRio does everything right that Vex does wrong.
__________________
FRCDesigns Contributor | "There is only one corner of the universe you can be certain of improving, and that's your own self." -Aldous Huxley
2012-2016 | FRC Team 2338: Gear it Forward
2013
Wisconsin Regional Winner 2014 Midwest Regional Finalist 2015 Midwest Regional Chairman's Award, Finalist, Archimedes Division Champion, IRI Semifinalist 2016 Midwest Regional Chairman's Award, Finalist, Archimedes Division Gracious Professionalism Award, R2OC Winner
2015 | FTC Team 10266: Mach Speed
2015
Highland Park Qualifier Winner, Motivate Award
2017-???? | FRC Team 4536: The Minutebots

Thanks to the alliances and friends I've made along the way: 33 74 107 111 167 171 234 548 1023 1089 1323 1625 1675 1732 1756 2064 2077 2122 2202 2358 2451 2512 2826 3936 3996 4039 4085 4241 5006 5401 5568 5847 5934
Reply With Quote