Issue with compass QMC5883 #9967
Open
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
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.
About two months ago, I noticed incorrect QMC5883 compass readings on our drone when I was designing a custom autopilot for it. I started looking for the problem. I found only two issues with this compass in your repository: #9101 and #9091. But it a liitle other. I had to dig deeper. I found the documentation for the QMC5883 and started checking to see if the registers in the QMC5883 were programmed correctly, which is how I found the bug in the driver. For the insurance I checked a correctlly programming this driver in the repository of the Betaflight. So you can to verify as same.