Skip to content
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

moveByVelocityZ in body frame #3476

Closed
meurissemax opened this issue Mar 16, 2021 · 0 comments · Fixed by #3475
Closed

moveByVelocityZ in body frame #3476

meurissemax opened this issue Mar 16, 2021 · 0 comments · Fixed by #3475

Comments

@meurissemax
Copy link
Contributor

meurissemax commented Mar 16, 2021

What feature are you suggesting?

Overview:

I experienced a small problem with function moveByVelocityBodyFrame (when used to move in X-Y plane): multiple calls, separated by a small amount of time (for example, the time to process and analyze an image) leads the UAV to move downwards gradually.

A small video illustrating this problem is available here: https://youtu.be/iiWdGzhMKqA

The use of moveByVelocityZ solved this problem, but unfortunately its associated moveByVelocityZBodyFrame does not exist, so I propose to add it.

Smaller Details:

The implementation would be (almost) exactly the same as the moveByVelocityBodyFrame added in #3169.

Usage: moveByVelocityZBodyFrameAsync(vx, vy, z, duration, drivetrain (optional), yaw_mode (optional), vehicle_name (optional)).

Nature of Request:

  • Addition

Why would this feature be useful?

To be consistent in the methods proposed in the API for moving using velocity.

Indeed, the function moveByVelocity has its associated moveByVelocityBodyFrame. It is not the case for the function moveByVelocityZ.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants