Can you share a picture of your setup? Is the Quectel RM502Q-AE installed?

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

Thanks for posting the ssl fix. We're looking into this. We don't typically use rosdep for anything. Is there something specific you need to get working?

A more traditional ROS experience is easy to achieve running Ubuntu in a Docker on VOXL : https://docs.modalai.com/docker-on-voxl/

Your understanding is correct, ModalAI's supported configurations are a result of Qualcomm limitations

It would have shipped with everything tested and working. What do you mean by "passed the wizard"?

The system was tested in VIO mode for 20 minutes before shipping. All drones are very sensitive to frame modifications, so this needs to be done carefully

• Were you able to fly successfully before frame modifications?
• How well does it fly manually? Have you looked at the logs in manual.mode for vibration?
• Can you please share a log of the VIO output?
• If you reset all of the software, you may need to recalibrate the cameras
• It looks like there are loose parts hanging off of the drone. VIO is VERY sensitive to vibration. Can you revert your frame modifications and try again?

You should be able to use the open source PX4 avoidance, but it may require a bit of an atypical architecture. When trying to use big ROS projects we recommended running Ubuntu on VOXL in Docker

The base Yocto layer should be ROS core and expose the VIO and depth from stereo modules:

• voxl-cam-ros
• snap_vio
• depth-from-stereo

Then the Ubuntu OS in the Docker should subscribe to the appropriate hardware layer topics to execute the PX4 Autonomy

We should have this better documented, but keep asking on this thread and we'll try to get you going. Shouldn't be any major blockers, but a few tweaks are probably necessary.

Are you flipping the fastboot switch back? Your symptom is consistent with leaving the fastboot switch engaged instead of setting it back to normal after a few seconds

Might be worth watching the tutorial here if you're unsure

We do not have a thermal option available today, though the Flir Boson and Lepton have been integrated by customers in the past using USB

Stereo cameras need to be co-planar and mounted rigidly. Then they need to be calibrated. Otherwise you should be able to mount wherever convenient

You can see an example of how to write telemetry on top of a video frame here
https://gitlab.com/voxl-public/modal-pipe-architecture/voxl-qvio-server/-/blob/master/server/main.cpp#L715

@Suvasis-M https://docs.modalai.com/voxl2-mini-external-flight-controller/

See topic: https://forum.modalai.com/topic/3640/ardupilot-on-voxl2

Hi Erik, thanks for pointing that out. It was a mistake, it has now been fixed as there are no CH-201 sensors

@MattK The VOXL SDK is common between VOXL CAM, VOXL 1 and VOXL 2, so the same messages will be sent in the same manner between VOXL and the flight controller over mavlink

@tpavlic here is the documented method for connecting Graupner

https://docs.modalai.com/flight-core-connections/#graupner-receiver-optional

@Jyotish-Kumar Mythic discontinued this product a while ago. It is not available or supported

We have not had a problem shipping directly to Australia.

@bensusana which version of px4 are you running? PX4 changed the px4io protocol in 1.14 and that board will no longer work correctly. You should connect your csrf receiver directly to VOXL 2 if using PX4 1.14

@relevinsky it looks like you have corrupted flash

@tiralonghipol yes, the ToF is rotated per the extrinsics. You will need to modify your urdf to match