Topics created by Daniel Rincon

Hi @Alex-Kushleyev ! Thank you very much for responding. Here is a diagram of how we use the cameras. Almost everything comes from the factory. I made some optimizations, such as ensuring that our mission manager does not consume or open a video consumption channel, but only consumes data, which has improved things, but I have not been able to significantly improve consumption and temperature issues. Sometimes the open vins reaches over 100% consumption and dies in the process (state -1), which is extremely risky for autonomous operation. I also noticed that it has a certain delay, which can lead to erroneous coordinates or erratic movements. I saw that you recommend a fan. Which one would you recommend? Do you sell them?
I look forward to your comments and possible help, thank you very much.

diagrama.png

Solved using SDK 1.4

@Daniel-Rincon have you looked through the troubleshooting guide? https://docs.modalai.com/flying-with-vio/#troubleshooting-vio

Usually looking at the ovins-overlay in voxl-portal offers good insight

The common issues are vibration is too high, the extrinsics are incorrect or there are not enough features to track in the environment

@Daniel-Rincon Yes, please start a new post for the VIO question

@Daniel-Rincon I'm hoping you are still around as we might be having a similar issue. When you say documentation, do you mean these: https://gitlab.com/voxl-public/support/voxl-train-yolov8

What specific helpers did you add with what model conversions? (Reference: I also have a custom yolov8 model trained for an output of two classes.)

@Daniel-Rincon The front and downward facing "tracking" cameras are used for VIO. The frontward and downward facing"hires" cameras are recommended for doing any sort of CV work.

We don't supply a "shell" for the drone but have had customers do similar work