Easing into top speed

[MaxMax161]

I think that doing a PID or something more advanced like that would be the best solution to the problem long term however that requires time to write, robot time to debug, and all of that fun stuff.

I personally think that your best solution would be to proportionally decrees the sensitivity of the joysticks (just multiply the value that comes out by something less then 1) unless a button is pressed, in which case they have full sensitivity.

This is easy to program and gives your drivers something to help them drive the robot well. At this point in the season there isn't a lot of time to learn and implement anything complicated so I'd go with something simple and then put it on the drivers to learn how to drive better using any tools you can give them.

[RoboMaster]

I really like the divide by 2 and disable with a button method, it's simple, easy to tell your drivers, and works quite well. You can also pick any other number than 2 if you want, like 3.

Some teams, like us, have cubed the joystick values (that is, x^3). This allows you to have slow speeds the majority of the time (that still increase), but also allows you to have that last bit of full speed. Squaring works, too, but cubing seems to be better and more defined. Visualize it with this graph. Plus, you don't have to press a button to disable it for full speed. Sometimes, that's one more button to memorize and drivers get turned off by that and don't use it.
To program this in LabVIEW: squaring is as simple as inserting a Square node in the wire. Cubing is more tricky, I would suggest using a Compound Arithmetic Function set to multiplication and the same joystick value wired to 3 inputs. Or you can use a fancy expression node, but don't forget to use ** instead of ^

[Ether]

Originally Posted by RoboMaster

Some teams, like us, have cubed the joystick values (that is, x^3). This allows you to have slow speeds the majority of the time (that still increase), but also allows you to have that last bit of full speed.

This might be of interest:

http://www.chiefdelphi.com/media/papers/2421

[Clayton Yocom]

I have a VI we built this year that does exactly this, I'll post it Tuesday when I can get back at the latest build of our code. It makes a joystick value "trickle" up or down (two different VIs). If you haven't acquired anything better I hope this will work with as little tweaking as possible

[Clayton Yocom]

Here is that file I was talking about, its a day late sorry :/

Leme know if this looks like what you need.