As of right now, when you call the MoveDistance command it will move the robot to a specified encoder position rather than a specified distance. This means if you ran the MoveDistance command twice with the same value, it would move to that position the first time and then make no further change. The expected outcome would be for the robot to move that distance twice. The easiest solution to this problem would be to zero the encoders of the drivetrain on command initialization.
StephenDay1
commented
4 years ago
As of right now, when you call the MoveDistance command it will move the robot to a specified encoder position rather than a specified distance. This means if you ran the MoveDistance command twice with the same value, it would move to that position the first time and then make no further change. The expected outcome would be for the robot to move that distance twice. The easiest solution to this problem would be to zero the encoders of the drivetrain on command initialization.