Open
Conversation
Made calibration routine more robust so it would run without problems on both the Teensy 3.1 and the Pro Mini
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Made calibration routine more robust so it would run without problems on both the Teensy 3.1 and the Pro Mini.
I've had trouble with code compatibility between the Teensy 3.1 and the Pro Mini having to do with my sometimes sloppy treatment of integer types. I made the calibration routine more robust in this regard and it nows gives the same calibration results for both processors.
I hope my constant fiddling with this library is not causing you trouble!