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

Support odometry velocity in body and local frame [REOPENED] #14703

Merged
merged 7 commits into from
May 13, 2020

Conversation

kamilritz
Copy link
Contributor

At the moment we expect the external vision's velocity to be expressed in world/local frame. This PR allows for the vision velocity also being expressed in body frame. For this a field is added to the vehicle_odometry message that stores the frame in which the velocity is expressed;

Related ECL PR: PX4/PX4-ECL#708
Solving issue: #13935

FYI @TSC21 @jkflying

TSC21
TSC21 previously approved these changes Apr 20, 2020
Copy link
Member

@TSC21 TSC21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we put this under test in CI? Parallel to the existing one I mean. It will need some minor work on the Gazebo side so to send the velocity in the body or local frames (two different models I would say).

Copy link
Contributor

@jkflying jkflying left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some small things, and of course the ECL PR needs to be merged and updated.

Thanks for the great cleanup here!

@kamilritz
Copy link
Contributor Author

@jkflying Great, now it is not fitting on fmuv2 anymore.

@kamilritz kamilritz requested a review from jkflying May 5, 2020 17:05
@TSC21
Copy link
Member

TSC21 commented May 5, 2020

@kamilritz it would probably look ugly, but you could limit the frame support per target using a preprocessor directive. Which we already have for v2 btw

@kamilritz
Copy link
Contributor Author

SITL tests are failing recently often. I have a suspicion that this is related to the offboard 'takeoof and land' test case starting sometimes without having proper position information, since ekf is always reporting local_position valid for the first few seconds. Will fix this soon.
I just ran the mavsdk tests locally for the PR and those tests are passing:
Screenshot from 2020-05-13 08-34-19

@kamilritz
Copy link
Contributor Author

Lets get this merged, change requests are addressed

@kamilritz kamilritz force-pushed the vision_velocity branch 4 times, most recently from 28e33b8 to 6e75d74 Compare May 13, 2020 07:45
@bresch bresch requested a review from TSC21 May 13, 2020 09:03
@bresch bresch dismissed jkflying’s stale review May 13, 2020 09:04

Comments addressed

Copy link
Member

@TSC21 TSC21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks @kamilritz!

@bresch
Copy link
Member

bresch commented May 13, 2020

Unrelated SITL failure, let's merge that.

@bresch bresch merged commit 3897030 into master May 13, 2020
@bresch bresch deleted the vision_velocity branch May 13, 2020 10:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants