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

THR_MDL_FAC parameter unclear #13105

Closed
hamishwillee opened this issue Oct 7, 2019 · 0 comments · Fixed by #13129
Closed

THR_MDL_FAC parameter unclear #13105

hamishwillee opened this issue Oct 7, 2019 · 0 comments · Fixed by #13129

Comments

@hamishwillee
Copy link
Contributor

hamishwillee commented Oct 7, 2019

Documentation for THR_MDL_FAC is unclear.

The equation in description refers to PWM, but it is not clear this is a normalised value. It should be renamed to something like out_normalized.

From Lasse Fröhner

Maybe also thrust could be renamed to thrust_normalized or something similar.

The question originated here: https://discuss.px4.io/t/thrust-curve-compensation-through-thr-mdl-fac/13207

Finwood added a commit to Finwood/PX4 that referenced this issue Oct 8, 2019
The documentation of the thrust model parameter `THR_MDL_FAC` did not
mention both thrust and "PWM" being relative values. Also the use of the
term PWM could be misleading, since the model is applicable to CAN ESCs
as well.

This commit rephrases the user documentation string and a few source
code comments, but no logic changes are made.

Closes PX4#13105
bkueng pushed a commit that referenced this issue Oct 9, 2019
The documentation of the thrust model parameter `THR_MDL_FAC` did not
mention both thrust and "PWM" being relative values. Also the use of the
term PWM could be misleading, since the model is applicable to CAN ESCs
as well.

This commit rephrases the user documentation string and a few source
code comments, but no logic changes are made.

Closes #13105
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants