The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
The coordinate frames for ardrone_autonomy are given in the documentation and conform to the conventions given in REP-103.
As for how the odometry is calculated, again, from the documentation:
Odometry data
New in version 1.4.
The driver calculates and publishes Odometry data by integrating velocity estimates reported by the drone (which is based on optical flow). The data is published as
nav_msgs/Odometrymessages toardrone/odometrytopic. The corresponding TF transform is also published as odom -> base transformation.
So, basically the odometry is calculated using dead reckoning. It's noisy because that's just the nature of dead reckoning.
| | 2 | No.2 Revision |
The coordinate frames for ardrone_autonomy are given in the documentation and conform to the conventions given in REP-103.
As for how the odometry is calculated, again, from the documentation:
Odometry data
New in version 1.4.
The driver calculates and publishes Odometry data by integrating velocity estimates reported by the drone (which is based on optical flow). The data is published as
nav_msgs/Odometrymessages toardrone/odometrytopic. The corresponding TF transform is also published as odom -> base transformation.
So, basically the odometry is calculated using dead reckoning. It's noisy because that's just the nature of dead reckoning.
Update:
You can add a tf frame and visualize that in RViz. Please refer to the tf tutorials
| | 3 | No.3 Revision |
The coordinate frames for ardrone_autonomy are given in the documentation and conform to the conventions given in REP-103.
As for how the odometry is calculated, again, from the documentation:
Odometry data
New in version 1.4.
The driver calculates and publishes Odometry data by integrating velocity estimates reported by the drone (which is based on optical flow). The data is published as
nav_msgs/Odometrymessages toardrone/odometrytopic. The corresponding TF transform is also published as odom -> base transformation.
So, basically the odometry is calculated using dead reckoning. It's noisy because that's just the nature of dead reckoning.
Update:
You can add a tf frame and visualize that in RViz. Please refer to the tf tutorials
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
