Best posts made by Chad Sweet

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

You can set the resolution of the preview stream in /etc/modalai/voxl-camera-server.conf

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?

@Jgaucin you can use voxl-portal to view the output of all of the image sensors on the drone. The Sentinel has forward and rearward stereo depth pre-calibrated and tested in the factory

https://docs.modalai.com/voxl-portal-cameras/

this might also be useful
https://docs.modalai.com/calibrate-cameras/

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

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

For VIO use voxl-inspect-qvio

For GPS use voxl-inspect-gps

The source code for those is here

It is not something we have direct support for since the flight controller is built in.

Here is how you connect VOXL to an external flight controller: https://docs.modalai.com/how-to-connect-voxl-to-pixhawk/

The normal UART is not exposed on VOXL Flight, so you would have to modify the code on VOXL to use a different UART

https://docs.modalai.com/voxl-datasheets-connectors/

Why use Docker for this? voxl-logger is setup to do this for you already

posted a few basics in the docs https://docs.modalai.com/voxl-tflite-server/

You can see exactly where the image comes in her: https://gitlab.com/voxl-public/modal-pipe-architecture/voxl-tflite-server/-/blob/master/server/threads.cpp#L105

Have you looked at the video tutorial here? https://docs.modalai.com/configure-extrinsics/

You will need to change the code in voxl-vision-px4 to use a different UART. I don't think betaflight supports mavlink though as a control mechanism. What are you hoping to connect between VOXL and betaflight?

Please review the External UDP Mavlink Connection documentation

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/

We have not had a problem shipping directly to Australia.