Mismatching measures between VIO and Mavor local pose
-
Hello to every one.
I am struggling with something related to the Visual Inertial Odometry of my voxl2 board and mavros. I am not able to understand if it is working correctly or not. Basically this is the behavior I am not understanding correctly.
I am using the tracking camera to estimate the position and the orientation of my uav. The resulting pose seems correct and the quality is good as well. I start also mavros, since I want to integrate my application with the ROS framework.
I am comparing the value present in the /qvio/pose topic and the one in the /mavros/local_position/pose that should be the estimated position from the uav point of view.
Results:
-
Orientation: I am mainly considering the YAW. The Yaw tracks the IMU data directly, without taking into account the value generated from the /qvio/pose. There is an offset due to the initial rotation of the uav, and the rotation is inverted by sign
-
Position: there is an offset. No very huge but the position seems to be filter with other things
I was wondering if these things are correct, and why
Regards.
-
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login