Attempt to improve odometry using Opticalflow(&rangefinder)
-
Hey @Eric-Katzfey, @James-Strawson @Tom-Kaufmann,
I've been using Starling for quite a while. Congratulations on a great product.
One of the things I noticed was that when using voxl-mapper for a significant time (like 15mins), the accumulated drift becomes a serious issue. I want to try and reduce the accumulated drift.An option to solve this issue is to use an OpticalFlow/Rangefinder with an external FC. I have completed this setup successfully. I can use my MAV in position mode with the fused odometry without issues. VOA works as well.
I know from the docs and GitLab that voxl-mapper takes 2 inputs whub_body_wrt_fixed and tof. Is there a way to pass the fused odometry instead of whub_body_wrt_fixed? [ I want the mapper to use this data instead of whub_body_wrt_fixed]. The message type of the fused odometry is nav_msgs/Odometry.
- Will I need to modify the voxl-mavlink-server to achieve this?
- How do I get the mapper to use the fused odometry data?
- How do I synchronize these new position estimates and the pointcloud?
I'm currently working on this project. So any suggestions or ideas will be instantly implemented, tested and reported back. i hope to hear from you.
Thank you
-
Hey @Eric-Katzfey, @James-Strawson @Tom-Kaufmann,
I've been using Starling for quite a while. Congratulations on a great product.
One of the things I noticed was that when using voxl-mapper for a significant time (like 15mins), the accumulated drift becomes a serious issue. I want to try and reduce the accumulated drift.An option to solve this issue is to use an OpticalFlow/Rangefinder with an external FC. I have completed this setup successfully. I can use my MAV in position mode with the fused odometry without issues. VOA works as well.
I know from the docs and GitLab that voxl-mapper takes 2 inputs whub_body_wrt_fixed and tof. Is there a way to pass the fused odometry instead of whub_body_wrt_fixed? [ I want the mapper to use this data instead of whub_body_wrt_fixed]. The message type of the fused odometry is nav_msgs/Odometry.
- Will I need to modify the voxl-mavlink-server to achieve this?
- How do I get the mapper to use the fused odometry data?
- How do I synchronize these new position estimates and the pointcloud?
I'm currently working on this project. So any suggestions or ideas will be instantly implemented, tested and reported back. i hope to hear from you.
Thank you
@Chad-Sweet, @James-Strawson, @tom any updates?
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