View Single Post
  #7   Spotlight this post!  
Unread 19-01-2011, 01:12
davidthefat davidthefat is offline
Alumni
AKA: David Yoon
FRC #0589 (Falkons)
Team Role: Alumni
 
Join Date: Jan 2011
Rookie Year: 2010
Location: California
Posts: 792
davidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud of
Re: Programming full "holonomic" for mecanums

Quote:
Originally Posted by Dfontana View Post
Correct me if I'm wrong, but shouldn't this already be fully implemented in an encapsulated method (likely Holonomic Drive)? This is the case with LabView, and has been since about midway through the 2010 season.

All you should have to do is feed in the x, y, and z-axis of your joystick as parameters to the Holonomic Drive method.

I haven't personally seen the Java WPI so I can't say for sure. Check?
Now what is the fun in that?

I can argue that making the function yourself is 10x better. First, you learn how it works; its not a black box to you. Second, you have FULL control over the code. Now this year, our code is getting ramped up; it has actual structure Last year I just did spaghetti code, because of my laziness. You really can't have structure with a black box in the middle of it.

There is no challenge when using the driver class; its like putting together a kitbot. Sure it works and its easy, but where is the accomplishment in that?
__________________
Do not say what can or cannot be done, but, instead, say what must be done for the task at hand must be accomplished.