Reducing the speed of motors

[Rangel(kf7fdb)]

Hello, my team has just got one of our robot chassis built. I then ran tank drive code on the robot and one thing we noticed is that it drove fast. Real Real fast. So what we want to do is cut the speed of the robot in half. How would you give less signal to the pwms.

[Vikesrock]

If you just want to cut the whole range in half, simply multiply the joystick inputs by .5 before passing them to whichever drive VI you are using.

[Mark McLeod]

Increase the size of your wheel sprockets...

[Ether]

Hello, my team has just got one of our robot chassis built. I then ran tank drive code on the robot and one thing we noticed is that it drove fast. Real Real fast. So what we want to do is cut the speed of the robot in half. How would you give less signal to the pwms.

What you really should do is change the overall gear ratio on your robot so that when you are commanding full voltage to the motors, you get the vehicle top speed you want.

You can do this by increasing the size of the wheel sprockets (as Mark suggested - if you are using drive chains), or by using smaller diameter wheels, or by using a Toughbox gearbox (12.75:1 gearing) instead of the CIMpleBox (4.67:1 gearing) supplied in the KoP.

If you reduce the speed by simply scaling down your joystick outputs in software, you'll wind up with a robot with low acceleration and without much pushing force.

[Rangel(kf7fdb)]

If you just want to cut the whole range in half, simply multiply the joystick inputs by .5 before passing them to whichever drive VI you are using.

Thanks. I guess I forgot to mention that we wanted to go that fast but not all the time. Now we can choose how fast to go.:D

[PAR_WIG1350]

reducing the voltage?

No, that would mean less power. Technically, this never happens anyway, but i don't think we need to get into that.

Increase the size of your wheel sprockets...

Yes, this allows you to leave the code alone and still get full power. To cut the speed in half (approximately), the wheel sprockets should be about twice the size. As a bonus, you also get more torque.

EDIT:

Thanks. I guess I forgot to mention that we wanted to go that fast but not all the time. Now we can choose how fast to go.:D

OOPS, I missed that. In that case, forget what I said.

[Vikesrock]

Thanks. I guess I forgot to mention that we wanted to go that fast but not all the time. Now we can choose how fast to go.:D

Ok, so what it sounds like you want to do is use a mapping function to give you more control on the low end with the same maximum signal. This thread (http://www.chiefdelphi.com/forums/showthread.php?t=88065&highlight=joystick+mapping) talks about various mapping functions, x^3 or variants of it is a common choice.