Updating crossfire telemtry and use fonction prom position #3
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
Quick-Flash
added a commit
that referenced
this pull request
Jan 2, 2021
* feat(mixer_smoothing): smoothing out the motor output calculation removing the harsh motorMix constraining. Also introduced thrust linearization and 'AirMode 2.0' * feat: QuickFlash's predictive AirMode, porting from another impl (#3) * min/max fix, thanks to borisbstyle * predictiveAirMode activation logic refactor * applyAirMode become applyMixerClipAdjustment * refactoring and simplification * rolling back some useless changes * cleared out thrust linearization formula and fixed the linear throttle (there was a division by 100 too much) * removed unnecessary sign management * removed unnecessary change * fix * fixes, removed throttle linearization for the moment * moved PID scaling * removed DEBUG_WRONG_PIDSUM_SIGN * thrust linearization formula changed (actual matematical inverse) and reintroduced thruttle linearization * removed duplicated code * mixer_impl * mixing yaw separately * fixes and temporarily put mixerImpl on OSD * mix & roll/pitch mix rate * norm fix * wip * fixes * final, maybe... * cleanup * unlinear throttle fix * removing avg controller's caused thrust/motor * backup * two pass mixer. Version 1.0.0 * two level thrust linearization * code cleaning * TL from idle level and TPA disabled when TL is enabled * fix SPA and motorOutputIdleLevel * changed desmos link for TL graphs * fix: applying AirMode level (so AirMode OFF) given throttleMotor, so that with boht linear_throttle ON and OFF the transition is the same * removed mixer impl from OSD and another code cleaning * mixerInitProfile called into pidInitConfig * rewording * fix: fixed thrust-linearization disabling. Code cleaning * 65 default value for linear_thrust_low_output * little code simplification * 3d mode fix and cleanup Co-authored-by: nerdCopter <56646290+nerdCopter@users.noreply.github.com> Co-authored-by: Quick-Flash <46289813+Quick-Flash@users.noreply.github.com>
raemin
pushed a commit
to raemin/EmuFlight
that referenced
this pull request
May 9, 2021
* feat(mixer_smoothing): smoothing out the motor output calculation removing the harsh motorMix constraining. Also introduced thrust linearization and 'AirMode 2.0' * feat: QuickFlash's predictive AirMode, porting from another impl (emuflight#3) * min/max fix, thanks to borisbstyle * predictiveAirMode activation logic refactor * applyAirMode become applyMixerClipAdjustment * refactoring and simplification * rolling back some useless changes * cleared out thrust linearization formula and fixed the linear throttle (there was a division by 100 too much) * removed unnecessary sign management * removed unnecessary change * fix * fixes, removed throttle linearization for the moment * moved PID scaling * removed DEBUG_WRONG_PIDSUM_SIGN * thrust linearization formula changed (actual matematical inverse) and reintroduced thruttle linearization * removed duplicated code * mixer_impl * mixing yaw separately * fixes and temporarily put mixerImpl on OSD * mix & roll/pitch mix rate * norm fix * wip * fixes * final, maybe... * cleanup * unlinear throttle fix * removing avg controller's caused thrust/motor * backup * two pass mixer. Version 1.0.0 * two level thrust linearization * code cleaning * TL from idle level and TPA disabled when TL is enabled * fix SPA and motorOutputIdleLevel * changed desmos link for TL graphs * fix: applying AirMode level (so AirMode OFF) given throttleMotor, so that with boht linear_throttle ON and OFF the transition is the same * removed mixer impl from OSD and another code cleaning * mixerInitProfile called into pidInitConfig * rewording * fix: fixed thrust-linearization disabling. Code cleaning * 65 default value for linear_thrust_low_output * little code simplification * 3d mode fix and cleanup Co-authored-by: nerdCopter <56646290+nerdCopter@users.noreply.github.com> Co-authored-by: Quick-Flash <46289813+Quick-Flash@users.noreply.github.com>
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.
Important: Feature freeze / release candidate phase for Betaflight 3.5
From 22/07/2018 until the release of Betaflight 3.5.0 (scheduled for 05/08/2018), the project is in a 'feature freeze / release candidate' phase. This means:
Pull requests can still be submitted as normal. Comments / discussions will probably be slower than normal due to shifted priorities;
If your pull request is a fix for an existing bug, or an update for a single target that has a low risk of side effect for other targets, it will be reviewed, and if accepted merged into
masterfor the 3.5 release;All other pull requests will be scheduled for 4.0, and discussed / reviewed / merged into
masterafter 3.5.0 has been released. Please keep in mind that this potentially means that you will have to rebase your changes if they are broken by bugfixes made for 3.5.Important considerations when opening a pull request:
Pull requests will only be accepted if they are opened against the
masterbranch. Pull requests opened against other branches without prior consent from the maintainers will be closed;Please follow the coding style guidlines: https://github.com/cleanflight/cleanflight/blob/master/docs/development/CodingStyle.md
Keep your pull requests as small and concise as possible. One pull request should only ever add / update one feature. If the change that you are proposing has a wider scope, consider splitting it over multiple pull requests. In particular, pull requests that combine changes to features and one or more new targets are not acceptable.
Ideally, a pull request should contain only one commit, with a descriptive message. If your changes use more than one commit, rebase / squash them into one commit before submitting a pull request. If you need to amend your pull request, make sure that the additional commit has a descriptive message, or - even better - use
git commit --amendto amend your original commit.All pull requests are reviewed. Be ready to receive constructive criticism, and to learn and improve your coding style. Also, be ready to clarify anything that isn't already sufficiently explained in the code and text of the pull request, and to defend your ideas.
If your pull request is a fix for one or more issues that are open in GitHub, add a comment to your pull request, and add the issue numbers of the issues that are fixed in the form
Fixes #<issue number>. This will cause the issues to be closed when the pull request is merged;Remove this Text :).