Skip to content
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

Report NONE for baro and mag MSP requests if not USE_ed. #8135

Merged
merged 1 commit into from May 1, 2019

Conversation

Projects
None yet
2 participants
@jflyper
Copy link
Contributor

commented Apr 30, 2019

It was erroneously introduced by #8121.

Responding with zero (BARO_DEFAULT and MAG_DEFAULT) will cause configurator to display these sensors enabled, and since write (set) side is ignored, they can never be displayed as disabled.

Report BARO_NONE and MAG_NONE for baro and mag MSP requests
Responding with zero (BARO_DEFAULT and MAG_DEFAULT) will cause
configurator to display these sensors enabled, and since write (set)
side is ignored, they can never be displayed as disabled.

@mikeller mikeller added this to the 4.0.1 milestone May 1, 2019

@mikeller mikeller added the RN: BUGFIX label May 1, 2019

@mikeller mikeller merged commit bcac7f2 into betaflight:master May 1, 2019

1 check passed

Travis CI - Pull Request Build Passed
Details

mikeller added a commit that referenced this pull request May 1, 2019

Report NONE for baro and mag MSP requests if not USE_ed. (#8135)
Report NONE for baro and mag MSP requests if not USE_ed.

@jflyper jflyper deleted the jflyper:bfdev-fix-sticky-mag-and-baro branch May 2, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.