ll40ls: Increase the number of samples used for every measurement #9247
Conversation
This file contains 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
…k for LitarLite Signed-off-by: CarlOlsson <carlolsson.co@gmail.com>
CarlOlsson
force-pushed
the
pr-ll40ls_corr_peak
branch
from
5312bbf
to
724de10
Compare
Signed-off-by: CarlOlsson <carlolsson.co@gmail.com>
CarlOlsson
force-pushed
the
pr-ll40ls_corr_peak
branch
from
724de10
to
3080c3b
Compare
|
What is the readout rate with this PR? |
|
We flew it last week with 50 Hz, seems to work fine, don't know the maximum rate |
LorenzMeier
approved these changes
Apr 19, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Increase the number of samples the sensor use to find a correlation peak and report a measurement. Benefit is increased range and more robust measurement, downside is if you want to read out the sensor at a very high rate, but for the majority of applications I don't think that is a problem.
This has only been bench tested so far