Lots of new features added to this driver #4
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.
I have implemented and tested many of the more advanced features provided by this device. Probably need someone at Core to review, I am happy to write up some documentation about best practise that I have found in using these new methods.
The main additions are:
These methods require some helper functions, which are included, but would NOT normally be considered part of the user API. For internal consumption only!
In my bench tests (and in the wild) I found increasing the timing budget from the default (about 95 miliseconds) to 200, or 300 ms, provided dramatic reduction in the standard deviation of measurements, across all three distance modes. Sometimes even 400ms worked well, but the improvement over and above say 300ms is not great... at the expense of slowing down the rate of measurements returned.
Hope you like it! It has transformed a kinda inaccurate device into one that in most cases consistently measures to within a millimeter or 2...
Regards, T.