View Single Post
  #1   Spotlight this post!  
Unread 17-02-2011, 21:36
Joe Ross's Avatar Unsung FIRST Hero
Joe Ross Joe Ross is offline
Registered User
FRC #0330 (Beachbots)
Team Role: Engineer
 
Join Date: Jun 2001
Rookie Year: 1997
Location: Los Angeles, CA
Posts: 8,579
Joe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond repute
Re: Jaguar Motor Control

Quote:
Originally Posted by oceanblack View Post
I have a few questions about Jaguar Motor Control using Labview. We have the default sample modified and up and running and the robot is moving great. We have 4 motor controllers opened using the [DRIVE] Open 4 Motor box. However, we have a bit of slack on one chain and I was wondering if it was possible to offset the amount of information is sent to some of the motors (so like multiply it by 0.9 to make the one side move a bit slower)

How do I modify values sent to Arcade Drive for individual motors?. So far example, I have x * 0.9 sent to the left motors, and x sent to the right motors.
Slack in the chain won't cause a side to travel slower, unless you have so much slack that it's skipping teeth. If that's the case, you really need to fix the mechanical problem.

Quote:
Originally Posted by oceanblack View Post
The other issue is we are using Jaguar motor controllers to control the movement of the arm. However, each motor controller is controlling a single motor. In labview, I noticed the open function requires 2 motors, or does it? Maybe someone can get me some help. But I'm trying to send individual values to each motor controller and I'm wondering if I have to supply 2 motors or can I just use one...
For a mechanism other then a drive train, use the MotorControl VIs rather then RobotDrive.
Reply With Quote