Running two commands at once, but both commands use the same motors.

[jreneew2]

Originally Posted by Ether

Three things:

1) I assume you have a mecanum drivetrain? (there is no "h" in "mecanum")

2) If you want to drive in a straight line in any particular direction, and simultaneously rotate the bot to a desired angle, you can do that using mecanumDrive_Cartesian. Feed your gyro to the gyroAngle parameter; supply the x and y components of the desired straight-line field-centric motion to the x and y parameters; and feed the output of a closed-loop controller to the rotation parameter. The input to the controller will be your desired angle (setpoint) and your gyro reading (process variable).

and finally, and perhaps most importantly:

3) Mechanical workmanship is of paramount importance. Make sure your drivetrain is built and aligned correctly before attempting #2 above. If you're not sure what "built and aligned correctly" means in the context of mecanum drive, I encourage you to ask before proceeding.

1) Yeah we have a mecanum drive train. The reason i said that with an 'h' is because in our code we have Robot::driveBaseSub->MechDrive(XAxis, YAxis, RotateAxis, IMU_Yaw); I should probably change that soon...

2) Yeah, OK. I was thinking about it in a more complicated way i guess. I just really tried to copy-paste from our original rotate to angle command into the drive command and it didn't go so well. I will have to try that. Also, by closed loop, you mean PID? We have not implemented a PID loop into the robot yet, but plan on doing so once we have the basics down. Right now, if the robot overshoots the 0 degrees it rotates to, it just turns in the opposite direction with a slower speed. We have a tolerance of about 2 degrees on it right now which seems good for what we need.

3) Yeah, I get what you mean. We have field-centric drive working on a robot we used last year and then just stripped down to the bare minimum for what we need. The wheels are not perfectly aligned just from usage over the season and unseen measurement error by us. I will fix this issue soon.

Thanks a bunch!
- Drew (Team 2053 Programmer)

[Ether]

Originally Posted by jreneew2

by closed loop, you mean PID?

It doesn't have to be PID. It can be any form of closed loop control that does what you want.

Right now, if the robot overshoots the 0 degrees it rotates to, it just turns in the opposite direction with a slower speed... seems good for what we need.

That's a closed-loop controller. You could use that if you're happy with it.