View Single Post
  #14   Spotlight this post!  
Unread 16-01-2011, 22:00
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,040
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: Mecanum Advice Request

Quote:
Originally Posted by BigJ
If you have an algorithm that translates in every direction the same, you will get about 71% ( sqrt(2)) of full power from your motors when going forward with no other modifications. 1675 usually includes a "beast mode" for going stright forward/back with 100% power.
Quote:
Originally Posted by Jogo View Post
Can you further explain this? Why would you only get 71% when going forward?
If you use the provided library functions (such as LabVIEW Holonomic vi), you don't have to worry about this and there is no need for a "beast mode", because the normalization is performed on the wheel speeds after the inverse kinematic calculations are performed, not on the joystick commands. You get the full range of motor command to the wheels in all directions.


Now, don't confuse this with the pushing force of a mecanum, which is a separate issue. In a traction-limited situation, mecanum has less pushing force than a standard-wheel vehicle using the same tread material, because the floor reaction force (for a given forward force) is higher on a mecanum wheel so it loses traction more easily.



Last edited by Ether : 16-01-2011 at 22:06.
Reply With Quote