From 03459ecc49884ff8dd7ea517ecada907d85d55c5 Mon Sep 17 00:00:00 2001
From: TommasoBendinelli <43389342+TommasoBendinelli@users.noreply.github.com>
Date: Thu, 29 Aug 2019 13:18:21 +0200
Subject: [PATCH] Point out important detail regarding odometer states

I lost some time realizing it, so it is better to write it in the documentation.
---
 docs/reading.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/reading.rst b/docs/reading.rst
index cacd8c9..9a5005d 100644
--- a/docs/reading.rst
+++ b/docs/reading.rst
@@ -25,6 +25,7 @@ Odometery
 * ROS Message Type: ``nav_msgs/Odometry``
 
 The driver integerates visual-inertial velocity estimates reported by Bebop's firmware to calculate the odometery. This message contains both the position and velocity of the Bebop in an ENU aligned odometery frame also named as ``odom``. This frame name is configurable (see :ref:`sec-params`) The cooridnate frame convention complies with ROS REP 103 (:ref:`sec-coords`). Please not that since odometery is calculated from Bebop States (see :ref:`sec-states`), the update rate is limited to **5 Hz**.
+Also note that only the orientation states (yaw, pitch and roll) are only available as soon as the driver is launched. The other states in odometry will be equal to 0 until the takeoff command.
 
 .. _sec-gps: