Open
Conversation
Member
|
BH sensor reads 2 bytes, so even if it will read random values, it will still return number in a valid 0..65535 range. Then it can be adjusted based on some BH configuration parameters, so actual value may be in different range, but it should never produce out of range values like "3 579 139 328 lx". Please try to look for the root cause of such report. |
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
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.
What does this PR change?
BH1750 is 16 bit sensor, max value is 65 535. PR adds limit for this max value to avoid out-of-range values when I2C communication produce incorrect values.
Affected area
Notes
Optional.
Checklist