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: support send_extended_sys_state #19137
Conversation
c351242
to
5c686ef
Compare
Seems to work, tested both SLT and tailsitters using:
|
{ | ||
if (quadplane.in_vtol_mode()) { | ||
QuadPlane::position_control_state state = quadplane.poscontrol.get_state(); | ||
if ((state == QuadPlane::position_control_state::QPOS_AIRBRAKE) || (state == QuadPlane::position_control_state::QPOS_POSITION1)) { |
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.
might want to limit this to only be QPOS_AIRBRAKE
we can sometimes spend a while repositioning in QPOS_POSITION1
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.
So much nicer than my effort :-)
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 would be nice to have the autotest too!
#endif | ||
}; | ||
|
||
MAV_LANDED_STATE GCS_MAVLINK_Plane::landed_state() const |
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.
we could work the takeoff and landing state later
The original PR from @peterbarker did have some auto tests. I guess they should still work..... |
yep, that is why I asked ! specially when the vtol transition seems tricky |
Rework of #10698 now we have separate translation logic.