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

Bug in odometry/tf position fixed: z-coordinate was only integer values #155

Closed
alexjung opened this issue Aug 6, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@alexjung
Copy link

commented Aug 6, 2015

I recorded some data flying an AR.Drone 2.0 and was wondering why the z-coordinate of odometry and tf was only jumping between 0, 1, 2 and so on.
I checked ARDroneDriver::PublishOdometry in ardrone_driver.cpp and fixed line 702 from
odo_msg.pose.pose.position.z = navdata_raw.navdata_demo.altitude / 1000;
to
odo_msg.pose.pose.position.z = navdata_raw.navdata_demo.altitude / 1000.0;

Now I receive continuous values on odometry/tf for the z-coordinate.

Maybe you want to include the change in the git hub version of the driver.

@mani-monaj

This comment has been minimized.

Copy link
Member

commented Aug 7, 2015

Good catch. I set it to be fixed in the next release.

@mani-monaj mani-monaj added this to the 1.4.1 milestone Aug 7, 2015

@mani-monaj mani-monaj added the bug label Aug 7, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.