Detect accelerometer vibration #3210
Merged
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
|
Perliminary tests indicate that vibration levels of > 200-300 cause accelerometer to go crazy. Another metric to consider when tuning. |
digitalentity
force-pushed
the
de_acc_vibre
branch
from
22a7c3e
to
c74905c
Compare
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.
First step towards fixing #486
Introduce
debug_mode = VIBEto log a few things:[0] = raw accelerometer vibration level (X axis, forward)
[1] = raw accelerometer vibration level (Y axis, right)
[2] = raw accelerometer vibration level (Z axis, up)
[3] = number of clipped acceleration readings (exceeding 7.9G)
Testing needed to figure out acceptable levels of vibration on XYZ axis