-
Notifications
You must be signed in to change notification settings - Fork 3
Add offsets, example, fix acceleration. #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# SPDX-FileCopyrightText: 2022 Kattni Rembor for Adafruit Industries | ||
# SPDX-License-Identifier: MIT | ||
|
||
import time | ||
import board | ||
import adafruit_adxl37x | ||
|
||
i2c = board.STEMMA_I2C() # uses board.SCL and board.SDA | ||
accelerometer = adafruit_adxl37x.ADXL375(i2c) | ||
|
||
accelerometer.offset = 0, 0, 0 | ||
|
||
print("Hold accelerometer flat to set offsets to 0, 0, and -1g...") | ||
time.sleep(1) | ||
x = accelerometer.raw_x | ||
y = accelerometer.raw_y | ||
z = accelerometer.raw_z | ||
print("Raw x: ", x) | ||
print("Raw y: ", y) | ||
print("Raw z: ", z) | ||
|
||
accelerometer.offset = ( | ||
round(-x / 4), | ||
round(-y / 4), | ||
round(-(z - 20) / 4), # Z should be '20' at 1g (49mg per bit) | ||
) | ||
print("Calibrated offsets: ", accelerometer.offset) | ||
|
||
while True: | ||
print("%f %f %f m/s^2" % accelerometer.acceleration) | ||
time.sleep(0.2) |
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm torn for what to do here. As is, it technically works, so the correct typing should be
-> None
. Is the intention to allow for silently ignoring the lack of implementation, as opposed to raisingNotImplementedError
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tekktrik You're the expert here! I'll defer to you on this one. It throws the
NotImplementedError
when attempting to use it, because you can't set the range on this chip.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm.... if you want the behavior to be that it throws
NotImplementedError
on both getting and setting, then I'd say it's fine to leave the typing as is because there's never really going to be a case where someone is expecting to getint
and actually gets anything at all, so the potentially future-safe implementation of returningint
seems fine. If you want the get functionality ofrange
to not fail but also not give anything useful, I would probably type this as returningNone
. Either implementation works so up to you!There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can leave it as it is for now then, and if it comes up in the future as an issue, we'll look at updating it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So is the decision to raise
Not ImplementatedError
from this property getter as well?