-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
send velocity setpoint to enable proper takeoff/land #12009
Conversation
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, since it's only sending out points at a different point in the code.
@@ -86,6 +86,8 @@ bool FlightTaskAutoMapper::update() | |||
_generateVelocitySetpoints(); | |||
} | |||
|
|||
_obstacle_avoidance.updateAvoidanceDesiredSetpoints(_position_setpoint, _velocity_setpoint); |
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.
Is it necessary/desired to publish these all the time even if there is no obstacle avoidance enabled or present?
Could it be conditioned by COM_OBS_AVOID
either here or inside the updateAvoidanceDesiredSetpoints()
function?
handling is enabled
During takeoff you're always in the condition within xy acceptance radius and more than altitude radius away from the takeoff waypoint
@MaEtUgR do you mind reviewing again. There are a few changes:
|
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.
I don't see it breaking anything.
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.
hotfixes look ok
Send velocity and position setpoints from AutoMapper to enable proper landing. Before this PR, the avoidance only knew about the position waypoint but due to the drift in the local frame that waypoint could have been reached while still being in air.
Needs MAVROS PR mavlink/mavros#1233 otherwise it isn't possible to send to the companion computer vectors containing NAN.