Open
Conversation
Was using LONG_RANGE, which measures 2m but at 33ms HIGH_SPEED measures 1.2m, with slightly reduced accuracy, but at 20ms
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.
Was using LONG_RANGE, which measures 2m but at 33ms
HIGH_SPEED measures 1.2m, with slightly reduced accuracy, but at 20ms
This isn't related to the bus speed problems. This is just making the laser read as fast as it can; so we can get as many readings as possible during the speed run; this change gives us approximately 50 readings per second per device instead of 30.
The trade-off is a couple of percentage points of accuracy, but that should be acceptable. We can always play around with it if not.