RoadRunner Calibration for FTC Robotics Teams

The RoadRunner motion planning library for First Technology Challenge (FTC) Robotics teams is a game changer for rapidly creating highly accurate complex autonomous routines that can easily self-correct themselves when the unexpected happens.
Huge thanks to rr.brott for maintaining the documentation for RoadRunner that this guide is based on.
FTC Team 21225 - Shear Force created this video to help explain how to work your way through the Tuning Process which is key to calibrating the library to work optimally for your specific robot.
Installation Instructions here:
rr.brott.dev/d...
Quick-Start GitHub page here:
github.com/acm...
Tuning Guide documented here:
rr.brott.dev/d...
Bonus: once you've gotten your robot properly calibrated, you should install the MeepMeep visualizer tool located here:
github.com/acm...

[@markdaniels1673]

Is there any way we can communicate? I have a few questions.

[@jaiminishah6824]

I am using mecanum wheel with drive encoder. During tuning process , forwardpushtest, I get ticks travel negative and even my angularramptest I get negative graph. Can you help me what should I do to get positive ticks traveled?

[@shearforceftc]

Maybe reverse the directions of your encoders (make sure the DeadWheelDirectionDebugger test is working in the right direction) because it sounds like the encoders are set in the same directions just backwards from the front of the robot?

[@jaiminishah6824]

Which odometery pods are using? Can you send me link to purchase the pod which can retract , most latest odometery pod?

[@shearforceftc]

@@jaiminishah6824 we are using the ones from Opti. They can be retracted, but we aren't using that this year since there are no obstacles to drive over this year. optii.com.au/collections/odometry

[@3805나장호]

When using these deadwheels, do I need to set it up with configure robot and then run it? Every time I run deadwheel direction debugger, I get an error message and it says that it can only be run when using deadwheels.

[@shearforceftc]

You have to configure your motors and your deadwheels in configure robot, but you also should have made some code changes that tells it that you are using Mecanum and deadwheels. Verify that In the TuningOpModes file, you set the DRIVE_CLASS variable to the drive class you’re using. public static final Class DRIVE_CLASS = MecanumDrive.class; Also verify in the Mecanum class, On line: 240 that you changed this line: localizer = new DriveLocalizer(); To: localizer = new ThreeDeadWheelLocalizer(hardwareMap, MecanumDrive.PARAMS.inPerTick);

[@ziezster8470]

@@shearforceftc for me it says it required 3 parameters instead of 2 when I use the threedeadwheel localizer