View Single Post
  #2   Spotlight this post!  
Unread 16-01-2008, 21:50
artdutra04's Avatar
artdutra04 artdutra04 is offline
VEX Robotics Engineer
AKA: Arthur Dutra IV; NERD #18
FRC #0148 (Robowranglers)
Team Role: Engineer
 
Join Date: Mar 2005
Rookie Year: 2002
Location: Greenville, TX
Posts: 3,078
artdutra04 has a reputation beyond reputeartdutra04 has a reputation beyond reputeartdutra04 has a reputation beyond reputeartdutra04 has a reputation beyond reputeartdutra04 has a reputation beyond reputeartdutra04 has a reputation beyond reputeartdutra04 has a reputation beyond reputeartdutra04 has a reputation beyond reputeartdutra04 has a reputation beyond reputeartdutra04 has a reputation beyond reputeartdutra04 has a reputation beyond repute
Re: easyC vs Hardcoding

Last year, Team 228 used WPILib, which is the back-end behind EasyC to do all of our programming for our FRC robot. While we used MPLAB as the primary editor to write our code, you can also use the built-in text editor in EasyC PRO or use Eclipse.

What we really loved about it is the speed at which you can write code, and how quickly we could get very sophisticated code running on our robot. We had closed loop feedback for everything on our robot, with PID control on our elevator and wrist. We used an accelerometer, two gyros, two encoders, and an IR range sensor.

Here's a video of our "drive-by" autonomous from last year:

http://youtube.com/watch?v=KR6daSCFjSM


I support EasyC and WPILib, because I would much rather see teams tackling more advanced control applications (like closed-loop (sensor) feedback), rather than "just getting their robot to work".

But of course, if you are familiar with programming in C, and you can write everything you need there, then by all means, go ahead and "hardcode" everything.
__________________
Art Dutra IV
Robotics Engineer, VEX Robotics, Inc., a subsidiary of Innovation First International (IFI)
Robowranglers Team 148 | GUS Robotics Team 228 (Alumni) | Rho Beta Epsilon (Alumni) | @arthurdutra

世上无难事,只怕有心人.