Fix for stuck in place rovers #119
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rovers would get stuck in the ROTATE state of the statemachine inside DriveController.cpp . The values being passed out of the fastPID method were too low (varied from 40 all the way to 0 or 1). The net result was the rover would send these through ROSAdapter into sendDriveCommand resulting in constant power to motors but the rover wouldn't move. The fix was to set a hard min value for rover motor speeds coming out of fastPID inside the ROTATE state. Currently set to 80 and seems to run ok. Needs testing. Made changes to PID.cpp and ROSAdapter.cpp with cleaning up and commenting all 3 files and moving some braces for readability while debugging problem. Currently left debugging cout statements in code for future hardware testing. Will remove once testing is complete before pull request is accepted.
Actual fix located in DriveController.cpp on lines 139-171
Fixes issue #91