Posts made by Moderator

@Mouhamed-Ndoye Hi Mouhamed, the motor size is dictated by the ESC and not the flight controller. For that size drone, you likely need ESCs larger than we offer. In that case, you should use a flight controller that works with ESCs spec'd for your platform. VOXL 2 would be a companion computer in that case https://docs.modalai.com/voxl2-external-flight-controller/

@olearypa Hi, we asked around. It seems like it should work as is, but we have not confirmed or tried it

@Peter-Milani Hi Peter, it's not possible for us to answer comprehensively about NDAA compliance. We can answer country of origin questions though.

Our M0107, M0161, M0166 for instance are built by ModalAI in the USA
M0149 is built by a partner in Taiwan

@Pete Starling 2 Max is probably easier to configure for this. You could mount the Doodle radio on the bottom. The M0151 is a good expansion board for this.

@JoeAR_21 to correct VIO drift, voxl-vision-hub can correct using an AprilTag without any ROS involvement. If you just need to send the data to ROS for another purpose, you should extend voxl-mpa-to-ros to support tag detections

Source: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros/-/tree/master/catkin_ws/src/src/interfaces?ref_type=heads

We love incorporating merge requests if you do end up with something useful!

The Starling 2 and Starling 2 Max will be supported for the foreseeable future. The Sentinel is less popular, so it is likely to be deprecated in 2025 but is currently marked as "Active Production" on its website

Dash speed, or burst speed, is the airframes capability when full throttle is applied for a short period of time. Batteries are typically able to discharge more current when first applied, but not for a sustained period of time.

@anghung said in How to use the USB Type-C interface on the board's ADB shell as a regular USB interface?:

he USB Type-C interface on the board's ADB shell as a regula

That is a USB OTG interface which will negotiate automatically with its peer device

@Jetson-Nano The M0173 kits include the IR filter on all sensors.

@Chase-Riley the recommended approach is to use J18 ESC port directly: https://docs.modalai.com/voxl2-external-flight-controller/#voxl-2-connecting-an-external-flight-controller

You can reach out at https://modalai.com/contact and we will work with getting you enabled

@vamsi manual mode will have drift, are you sure there is really an issue? Manual mode has no position control

@arcj can you share your working tflite configuration with M0014 and the configuration that is not working with M0025?

@Viktor-Gal have you read through the troubleshooting VIO documentation? https://docs.modalai.com/flying-with-vio/#troubleshooting-vio

@LucaVertiq Hi, sorry you're running into issues. You should probably try the unbricking process https://docs.modalai.com/voxl2-unbricking/

@Wesley-Gunawan did voxl-inspect-cam show anything while voxl-camera-server was running? it looks like you restarted voxl-camera-server while voxl-inspect-cam was running.

I think the proper steps are:

1. update config (done)
2. reboot VOXL 2
3. run voxl-inspect-cam -a

there is still a lot of churn on the APIs, etc. which makes it difficult to document and support comprehensively

@Wesley-Gunawan Can you please set and run inspect-cam again?

"en_preview": true,

"en_snapshot": false,

@Wesley-Gunawan that looks like it's running properly. Can you open another terminal and run voxl-inspect-cam -a ?

@Wesley-Gunawan It looks like you are using a C08 config. https://docs.modalai.com/voxl2-camera-configs/#c8---hires-only

Have you tried voxl-configure-cameras 8 ?

voxl-camera-server documentation for troubleshooting recommends running voxl-camera-server -d0. Can you try that and paste the output?

@Bilal-Hussain Hi Bilal, USB is a wired protocol, typically limited to a few meters. The range you would achieve would be dictated by the radio, and not the USB interface