You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 24, 2023. It is now read-only.
Problem
When running autonomous code, the robot does not drive the correct distance, even though the code used to work, and no changes have been made that should have caused this.
To Reproduce
Steps to reproduce the behavior:
Run EdgarProCompetition
Select an autonomous routine
Begin the autonomous period
Robot will fail to drive the correct distance
Expected behavior
The robot should complete the autonomous routine with no error.
Sugested fix
Recalibrate driveIN, as the error is most likely caused by a mechanical issue rather than a software issue.
The text was updated successfully, but these errors were encountered:
driveIN had been modified to allow for the motor waitForCompletion to be set to false. This change somehow broke the code. This feature was unused, so it has been removed, and modified auton routines have been returned to their original state.
driveIN modifications were not responsible for the break, driveIN was improperly calibrated (1 rev = 5.625 in, now 1 rev = 5 in). All autonomous routines are functional again.
Problem
When running autonomous code, the robot does not drive the correct distance, even though the code used to work, and no changes have been made that should have caused this.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The robot should complete the autonomous routine with no error.
Sugested fix
Recalibrate driveIN, as the error is most likely caused by a mechanical issue rather than a software issue.
The text was updated successfully, but these errors were encountered: