correcting vspeed defaults in presets #2533
Merged
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.
User description
With 9.0 the default presets have been missed updating for the vspeed controller values. Since the firmware defaults also have not been updated, a fresh plane setup or a setup with unchanged vspeed PIDFF controller values (not in diff) will have a 5x higher d value than recommended. This still results in dolphining on some platforms.
Updating the presets for the maintenance release that is planned.
PR Type
Bug fix
Description
Corrected VSpeed PIDFF controller default parameters for firmware 9.0
Removed outdated pre-9.0 vertical speed control values
Added proper altitude control response and feedforward settings
Updated parameters for FW-WT and other fixed-wing platforms
Diagram Walkthrough
File Walkthrough
defaults_dialog_entries.js
Update VSpeed PIDFF defaults to firmware 9.0js/defaults_dialog_entries.js
nav_fw_pos_z_p,nav_fw_pos_z_i, andnav_fw_pos_z_dparameters from FW-WT and other presets
setprefix:nav_fw_pos_z_p,nav_fw_pos_z_i,nav_fw_pos_z_d, andnav_fw_pos_z_FFnav_fw_alt_control_responseparameter set to 45 for altitudecontrol
multiple fixed-wing presets