-
Notifications
You must be signed in to change notification settings - Fork 17.2k
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
Plane: Add VTOL descent rate, convert existing rate to climb rate only #16927
Conversation
@@ -39,14 +39,24 @@ const AP_Param::GroupInfo QuadPlane::var_info[] = { | |||
AP_SUBGROUPPTR(pos_control, "P", 17, QuadPlane, AC_PosControl), | |||
|
|||
// @Param: VELZ_MAX |
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.
It is safe to just change it to VELZ_MAX_UP
, not sure if its better to or not tho
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.
wanted to allow people who have changed the value from defualt to still use it when copying params back into a new firmware load... or a new board....thought changing the param name would prevent that
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.
discuss at devcall
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.
If one is down, the other should be up, otherwise it's just confusing, IMO.
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.
could parameter conversion somehow be used to convert Q_VELZ_MAX, someone tries to set that from an old param file into UP and DN of that value, allowing old param files to work with the new code that changes VELX_MAX to MX_UP?
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.
Nope. We don't have any parameter change hooks to do something like that. If we did we'd already have done a lot more sanity checking on some params when people try to set them.
3b51226
to
97f8ba0
Compare
84c1569
to
28a5393
Compare
Would be nice to see an autotest for this. |
This is absolutely useful, after all it has already been present in the Copter for years. |
4a450ba
to
e73d835
Compare
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.
Looks fine to me - but the name question needs to be settled.
82ba4ae
to
22b8502
Compare
Co-authored-by: Reko Merio K9260@student.jamk.fi Co-authored-by: Peter Barker <pb-gh@barker.dropbear.id.au>
I think to be consistent with Copter it would be good to call the parameters PILOT_SPEED_UP and PILOT_SPEED_DN |
Merged, thanks @Hwurzburg |
Co-authored-by: Reko Meriö K9260@student.jamk.fi
designate existing pilot climb rate for ascent only
add pilot descent rate max param