Mag current/throttle compensation #14457
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
|
Documentation has started as well: PX4/PX4-user_guide#692 |
|
This solves the effect of the current generated by the thrust change on the geomagnetic sensor due to the improper layout of the circuit board.Right？ 😃 |
RomanBapst
reviewed
Mar 24, 2020
RomanBapst
previously approved these changes
Mar 24, 2020
baumanta
force-pushed
the
mag_comp_upstream
branch
from
d8b41ae
to
f6496ff
Compare
RomanBapst
previously approved these changes
Mar 24, 2020
1 task
bkueng
approved these changes
Mar 25, 2020
Closed
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.
New feature to compensate compass for current/throttle:
Parameters for each axis have to be identified offline using the provided python script. If there is no current reading available, there is the option to compensate for thrust, only advisable if the relationship is linear for the given setup (In my tests I've observed that for some setups the relationship is linear and it works well, for others it is not).
Offline parameter identification:
Log from drone with parameters for current compensation applied:
https://logs.px4.io/plot_app?log=cf3ca047-ea1b-43c0-b8dd-a425bea539d4