-
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
Support odometry velocity in body and local frame [REOPENED] #14703
Conversation
6c05221
to
958918c
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.
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).
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.
Just some small things, and of course the ECL PR needs to be merged and updated.
Thanks for the great cleanup here!
@jkflying Great, now it is not fitting on fmuv2 anymore. |
@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 |
296322f
to
2a6fdd9
Compare
91ea750
to
af0bf24
Compare
Lets get this merged, change requests are addressed |
28e33b8
to
6e75d74
Compare
6e75d74
to
4683fd3
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.
LGTM! Thanks @kamilritz!
Unrelated SITL failure, let's merge that. |
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