-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[WIP] Fixed-wing performance model docs #2842
Conversation
@github-actions Could you please post a couple more times, I don't understand yet. |
9610535
to
3233be6
Compare
Sarcasm @RomanBapst ? FW_S_CEILING is not in https://docs.px4.io/main/en/advanced_config/parameter_reference.html but your doc links to that. Probably because PR not yet merged? And you need to add this to SUMMARY.md. It will whinge on every commit until those are fixed. |
@@ -1,6 +1,6 @@ | |||
# PX4-Autopilot Main Release Notes | |||
|
|||
This contains changes to PX4 since the last major release (v1.14). | |||
This contains changes to PX4 since the last major release (v1.14). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RomanBapst When you're done, can you add a release note in this doc for the change following the pattern in https://docs.px4.io/main/en/releases/1.14.html
I'm trying to make sure that we don't have to come back and think about what we did and why when we get to the release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RomanBapst ^^^^
62bec52
to
13cd0e6
Compare
1d3c1d2
to
8dac417
Compare
@RomanBapst Let me know when this is ready for review (I see corresponding PR went in). |
8dac417
to
95ed5ca
Compare
95ed5ca
to
db72892
Compare
Signed-off-by: RomanBapst <[email protected]>
Signed-off-by: RomanBapst <[email protected]>
Signed-off-by: RomanBapst <[email protected]>
Signed-off-by: RomanBapst <[email protected]>
Signed-off-by: RomanBapst <[email protected]>
Signed-off-by: RomanBapst <[email protected]>
Signed-off-by: RomanBapst <[email protected]>
Signed-off-by: RomanBapst <[email protected]>
af5e291
to
49200ef
Compare
Co-authored-by: Hamish Willee <[email protected]>
Signed-off-by: RomanBapst <[email protected]>
@hamishwillee I am not sure what the issue with the formula rendering is. They render fine in vscode, but that might not say anything. I might also need to start using chatGPT... |
Formulas fixed - the markers can't have whitespace. See commit |
@RomanBapst OK, fixed rendering and subedit. You should have another look and add info in a release note if this is a new feature (?). If it is docs on older features, from what version is this all true? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe you could split the docs a bit more into sections that explain what PX4 is doing in the background (the parts with the formulas basically), and what the user has to do to enable the auto adaptions (set the WEIGHT_GROSS, set the CEILING, ..anything else if I forgot about it).
|
||
rearranging this equation for airspeed gives: | ||
|
||
$$V = \\sqrt{\\frac{2mg}{\\rho c_A F}}$$ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
$$V = \\sqrt{\\frac{2mg}{\\rho c_A F}}$$ | |
$$V = \sqrt{\frac{2mg}{\rho c_A F}}$$ |
@RomanBapst @sfuhrer I'm away for two weeks, so won't be commenting on this further for a bit.
I agree with this - the 80% of users just need to know what you set, while the rest are interested in what PX4 does. You've somewhat done this by having the top section of weight compensation "this is what you do" and then the subsections "this is how things are scaled", but it isn't obvious when you're reading the docs. In the compensating for air density section you've mixed what the user has to do and what PX4 does in each of the subsections. So as @sfuhrer indicates I'd have a top section covering everything that the user actually does - such as set Then all the rest on what PX4 does could be in its own section PX4 Scaling Algorithms. The notation bit would go under there too. Further, consider this section: If you read this out of context looks like this is something you have to do "Scale the Maximum Climb Rate" and "The maximum climb rate ( Hope that makes sense. I can help with this in two weeks if it isn't clear. |
…eds to tune and the theory behind the various compensations Signed-off-by: RomanBapst <[email protected]>
Signed-off-by: RomanBapst <[email protected]>
@hamishwillee @sfuhrer I tried to restructure the text according to your input, please let me know what you think. |
No flaws found |
|
||
### Effect of Density on Trim Throttle | ||
|
||
TODO: Add derivation here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ETA? I.e. is it worth merging the rest first and doing this as a post process?
@sfuhrer @RomanBapst I just pressed the wrong button and merged this rather than updated :-(. Let's build on the docs now published. I did a subedit to my taste in #3029 - I think the new structure is better but this can be made a bit tidier. @RomanBapst We may need answers/fixes from these (I'll merge my fixup PR but questions are against it):
|
This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there: https://discuss.px4.io/t/px4-v1-15-public-changes-what-needs-docs/39850/7 |
Docs for
Added PerformanceModel for fixed wing PX4-Autopilot#22091
mention that some compensations apply only for propellers (e..g maximum climbrate would be different for jet engine)
document procedure when user does initial tuning in conditions very different from sea level standard atmospheric conditions