Open
Conversation
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.
The calibration script now produces a nice input/output graph and optionally exports the data to a CSV file.
With averaging, the process takes about 45 minutes and produces a curve like this:
(Note that the script was killed early at the ~90% mark.)
Calibration noise is reduced by averaging many measurements, and this value is configurable. I suspect replacing the 3D printed coupling with a flexible coupling should reduce the noise further and reduce the amount of averaging we need to collect a datapoint.
For reference, a ~20min calibration (with fewer averages) looks like this: