-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Fixed wing altitude control fixes #10541
Fixed wing altitude control fixes #10541
Conversation
@breadoven how much of it is a reflect of bad mechanical setup and how much of it is inav being too aggressive on the defaults? |
The altitude control method changed from position to velocity so it's not unexpected that the PIDs might need tweaking from the current values. Others testing 8.0 have had similar pitch instability issues. The basic default for P is 40 but the Configurator defaults are 25 for a wing with a tail and 35 for a wing without a tail so both lower than 40 and in fact 30 is between these values. I guess the Configurator default settings should also be adjusted, certainly for flying wing at least, I'm sure there shouldn't be a problem for planes with a tail using the current value. |
@breadoven The configurator defaults are probably what most users will encounter first. Unfortunatelly, this would also be brough over in a diff. So we would need to both change the values in the configurator for those and mention in the release notes that users may want to lower vertical P and increase nav_fw_alt_control_response. Do you have suggested values for wing without a tail? Another option is to apply this pr and mention it in configurator, but change the profile values after 8.0 is out and we get more feedback on the effect of these changes. |
@mmosca if we control velocity now and not position, I think between Elevator and Delta mix setups there should be no relevant difference anymore. IMHO we can just remove these entries from the presets. I am just not sure about the diff transfer of the old values in this case. Should we rename to prevent it or leave it in release notes that 80% don't read? |
If the default profile values work, I don't think we need to rename it. The values are close to the defaults for wing with tail anyway.Mentioning it in the release notes and announcements should be enough. |
I think we should just apply this PR and mention the change in altitude control in the release notes, specifically that the PID settings for And probably best to remove the Configurator profile settings and only reapply them if need be when more feedback is available. I'd have thought it makes sense they should be different simply because flying wings seem to have a noticeably more sluggish pitch response than planes with a tail. Having said that the conventional motor glider I have uses a |
Think I'm going to merge this since it seems it should prevent the pitch instability issue. If there are further problems they'll just have to be dealt with with additional changes. |
do you need any other changes, or should I cut rc4 this weekend? |
No more changes required. If this doesn't fix the issue then you would have to look at something more drastic but I think with the correct settings it should be possible to tune out any pitch instability. |
Is there a chance to test the RC4 this weekend? |
It is out. The latest nightly also includes this changes. |
Sorry, I didn't notice. |
Should reduce the possibility for pitch instability issues such as #10536. Also increases default value of
nav_fw_alt_control_response
setting, which testing shows can be set higher for improved response, and adds setting to inflight adjustments.nav_fw_pos_z_d affect reduced by changing PID adjustment factor from 100 to 300.
nav_fw_pos_z_ff setting added with default of 10.
Tested on HITL as far as it can be but also via flight testing which tends to indicate lower PID P and D settings reduce the potential for pitch instability providing a safer starting point for further tuning.