Go to Post Real coaches dont use "strategy assistants" during matches. - Rick [more]
Home
Go Back   Chief Delphi > Technical > Technical Discussion
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #32   Spotlight this post!  
Unread 22-10-2010, 17:31
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,120
Ether has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond repute
Re: Chainless Mecanum Drive

Quote:
Originally Posted by Ether View Post
Frankly, I don't see where nonadrive is simpler
Just to be clear: For a fair comparison of the code required, you have to compare apples to apples. Mecanum requires no special operator intervention or programming to actuate raising or lowering of wheels. To be functionally similar to this for comparison, nonadrive requires extra operator input(s) and extra code to respond to those extra operator input(s) to raise and lower the traction wheels and control whether or not to power the center wheel. To be functionally equivalent (same driver interface and same robot behavior), nonadrive requires extra logic to react to the normal joystick axis driver commands and decide automatically when to raise or lower the traction wheels (for example, when strafing or tight turning is commanded).

This is not an argument that mecanum is "better". Just a comparison of the code involved. The code for either is fairly straightforward.

It would be interesting to hear from teams that have fielded successful nonadrive robots. Did you add extra input(s) and associated code for the driver to manually raise and lower the traction wheels, or did you add logic to process the "normal" driver commands and let the robot automatically handle this decision in order to keep the driver interface simpler, or did you design a "hybrid" compromise with manual operator input(s) plus some automatic behavior?





Last edited by Ether : 22-10-2010 at 17:49.
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
crab drive vs. mecanum drive system superbotman Technical Discussion 33 06-01-2010 03:09
Mecanum Drive Train Sam2197 Technical Discussion 25 16-11-2008 20:51
mecanum drive system Charger_07 Technical Discussion 5 23-01-2007 19:20
pic: Jester Drive:Mecanum Wheel Drive Train Ken Delaney 357 Technical Discussion 64 29-03-2006 22:16


All times are GMT -5. The time now is 23:30.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi