What do you think is a more efficient way to drive your robot?

Our team did the same thing last year and it is a really great way to make it a lot easier on the driver like this game to make the base a little less sensitive so that it is easier to stack cups, make it easier to get in the right position to pick up cubes, etc.

Long story short: easy way to make the game less stressful and difficult.

@shota_irl Sure! I realized after posting that I had oversimplified the actual functions that I used. Since it seems like a lot of people found it useful, so I’ll explain it in greater detail :smile:

Traditionally, you just set the motor equal to the the joystick’s value. This is represented by the dashed red equation y = x (see graph below). In order to get a curve with the following characteristics:

You can use the equation with the form:

10%20AM
In this equation n >= 1, x = unmodified joystick output, and y = requested motor speed. The graph below demonstrates the output of various values of n.

As you can see when n = 1 (blue), it actually results in the traditional output. Also note that they all intersect the points (0, 0) and (127, 127). Please be aware that if you choose an even value for n, the output will be positive even when you push the joystick backwards! You can solve this by multiplying the sign of the raw joystick value and the output of your function. When n is an odd number, the direction of the output will work as expected. Remember there is no correct value of n, and it’s up to the driver’s preferences.

@Gameoa Yes technically you are correct, but each of the functions have a specific constant that they need to be divided by, as you can see from my equation.

Oh yes, forgot to mention that part

It’s also important that for teams with v5, the denominator becomes 100^(n-1)

I’ve used tank drives with H drives in IQ. Just used the buttons to move the H-Drive.

That works too, but then you have less control and a few less buttons to use for other stuff, which for some robots can be important, like for example last season my team used every single button on the controller.

We use mtr.move(n) in Pros which takes a number [-127, 127] and applies voltage to the motor. We found voltage control to be much smoother than velocity control during operator control for the drive.