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

Convert body-fixed IMU data to Inertial frame for Pose messages #193

Closed
mhkabir opened this issue Jan 24, 2015 · 8 comments
Closed

Convert body-fixed IMU data to Inertial frame for Pose messages #193

mhkabir opened this issue Jan 24, 2015 · 8 comments

Comments

@mhkabir
Copy link
Member

mhkabir commented Jan 24, 2015

No description provided.

@LorenzMeier
Copy link
Member

@vooon @mhkabir Are you using this message yet? http://mavlink.org/messages/common#LOCAL_POSITION_NED_COV

I'm wondering if we should stick acceleration in earth frame into it as well, and cut the covariance to the upper triangular. That would end up being 36 floats (9+8+7+..+1), which is still manageable (144 bytes).

@TSC21
Copy link
Member

TSC21 commented Apr 9, 2015

@LorenzMeier that was an open issue (#94). From what I know, it's still not in use.
Seems a good add though, since it manages with position estimate uncertainty.

@mhkabir
Copy link
Member Author

mhkabir commented Apr 9, 2015

No we aren't. No covariance from the PX4 estimation yet.

@mhkabir
Copy link
Member Author

mhkabir commented Apr 9, 2015

And this issue is separate, I think. The thing here, the ROS Pose message expects attitude in the inertial frame. My flight visualiser thus was getting the track inverted.
The IMU message expects it in body frame.

@TSC21
Copy link
Member

TSC21 commented Apr 9, 2015

@mhkabir from what I remember in my thesis I had to invert the yaw axis so to sync both frames, as I was getting an invertion on map VS vehicle, on Rviz.

@mhkabir
Copy link
Member Author

mhkabir commented Apr 9, 2015

Yeah. As I said. It expects Pose has attitude in inertial frame.

@TSC21
Copy link
Member

TSC21 commented Apr 9, 2015

Yeah #195 seems to solve it then :)

@mhkabir
Copy link
Member Author

mhkabir commented Apr 9, 2015

It would. If it worked. Which it doesn't. Using tf won't work here.

@mhkabir mhkabir closed this as completed Jun 28, 2015
nmichael pushed a commit to rislab/mavros that referenced this issue Mar 19, 2016
common.xml: Added GPS_RTK and GPS2_RTK
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants