Topics created by m1baldwin

@Adrian-Hidalgo Appreciate the response, thank you!

I had the same issue. Updating the voxl_mpa_to_ros package resolved it for me: opkg update opkg install voxl-nodes

We have not done a direct comparison. In general though, all of those systems typically achieve 1-1.5% drift over distance which is something we see pretty consistently with the qvio-server

Our software found on Gitlab is only licensed to run on ModalAI hardware. It is difficult for us to support hardware we did not build and do not have traceability on build quality and test.

That is correct. They are the same binaries with target-specific integration software around them.

The VOXL platforms are all open, with the code available at https://code.modalai.com . This enables our customers to modify however they see fit. The qvio server that ships takes ~33% of one CPU core (out of 4 cores). So it might not be a worthwhile exercise to move that to the could. If you were processing a much larger state estimate, like a full keyframe SLAM, then that processing could be done on a server. It might be hard to close the control loops in flight if you are trying to fly with it. As an outer loop though, it should work fine.

Thanks @modaltb , I appreciate your feedback. I think the usb-to-ethernet can make sense at least for proof-of-concept. @Chad-Sweet Yes, I am aware there is already a companion computer on the VOXL Cam. In my current work, I've already got an autonomy stack implemented on-top of a custom px4 drone platform with the upboard as the companion. My first interest is to add the VOXL Cam purely as a "tracking module" to replace something like the intel t265, and integrate the odometry out of it into my existing software. This would give me a way to evaluate the VOXL Cam in the use-cases I am exploring with a drone/autonomy configuration that is known to work. From there, depending on how well it works, I might consider replacing the upboard with the VOXL Cam, but that would not be the first thing I would do, as I would have quite a bit of software to re-work/port edit: It's good the VOXL can already run ros; I figure I could use voxl_mpa_to_ros to pass the VIO data over ROS from the VOXL to the Upboard in this PoC just to get started easily.