Mecanum Single Joystick Control not working

[pastelpony]

For some reason, it seems as the inputs in the default mecanum code are inverted for some people, including myself. I'm not sure if this occurs for everyone, but just try to play with your joystick inputs and inversions. I personally had to edit the default code to get the wheels to spin the right way. You probably don't have to.

[Ether]

Originally Posted by pastelpony

just try to play with your joystick inputs

If by "play with your joystick inputs" you mean "wire the joystick values to the wrong inputs on the robot drive vi", that should never be necessary... and it makes your code confusing and difficult for others to help you.

I personally had to edit the default code to get the wheels to spin the right way. You probably don't have to.

If by "edit the default code" you mean "edit the inverse kinematic computation", that should never be necessary...and it makes your code confusing and difficult for others to help you.

[pastelpony]

Originally Posted by Ether

If by "play with your joystick inputs" you mean "wire the joystick values to the wrong inputs on the robot drive vi", that should never be necessary... and it makes your code confusing and difficult for others to help you.



If by "edit the default code" you mean "edit the inverse kinematic computation", that should never be necessary...and it makes your code confusing and difficult for others to help you.

Correct me if I'm wrong, but I've been reading that the default mecanum code in the WPI library actually takes the incorrect inputs by default. I'm not sure if thats true for everyone, but it was only with that advice I recieved on this forum concerning possible incorrect code that we were able to get mecanum working. And this was after countless tests, wire swaps, and inversions.

[pastelpony]

[quote=pastelpony;1438465]Good point. Thanks.

[Ether]

Originally Posted by pastelpony

Correct me if I'm wrong, but I've been reading that the default mecanum code in the WPI library actually takes the incorrect inputs by default.

Would you please post a link to where you've been reading that?

I don't have access to LabVIEW to inspect its code, but here's the inverse kinematics code taken straight from 2015 WPILib RobotDrive.Java:

wheelSpeeds[MotorType.kFrontLeft_val] = xIn + yIn + rotation;
   
wheelSpeeds[MotorType.kFrontRight_val] = -xIn + yIn - rotation;
      
wheelSpeeds[MotorType.kRearLeft_val] = -xIn + yIn + rotation;
      
wheelSpeeds[MotorType.kRearRight_val] = xIn + yIn - rotation;

I'm not a Java guru, but it looks correct to me.

[pastelpony]

Originally Posted by Ether

Would you please post a link to where you've been reading that?

I don't have access to LabVIEW to inspect its code, but here's the inverse kinematics code taken straight from 2015 WPILib RobotDrive.Java:

wheelSpeeds[MotorType.kFrontLeft_val] = xIn + yIn + rotation;
   
wheelSpeeds[MotorType.kFrontRight_val] = -xIn + yIn - rotation;
      
wheelSpeeds[MotorType.kRearLeft_val] = -xIn + yIn + rotation;
      
wheelSpeeds[MotorType.kRearRight_val] = xIn + yIn - rotation;

I'm not a Java guru, but it looks correct to me.

I'm not quite sure how credible this is, but it sure did help me.

[Greg McKaskle]

I compared the LV code to the attached Java, and they are the same.

The LV code first does a gyro transformation in case you have one and want to use field coordinates.

The code then uses the same expressions on the same inputs with the same output names. The code then normalizes the motor outputs.

If you have an issue with the code, can you be more specific about what was wrong with it?

Greg McKaskle