@Aaky , the mixer should never output a value lower than mixer min (while armed).

@tom That worked! thanks for the help

@Paola-Lim You will need to follow directions from this page : https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release Tom suggested getting the SDK 1.1.3, so per instructions you should go to https://developer.modalai.com, log in, then click on Protected Downloads -> VOXL2 Platform Releases and download VOXL2 SDK 1.1.3 and follow the rest of instructions from "flashing voxl sdk" page Alex

@JoeC Sure. There is a configuration script at /etc/modalai/voxl-px4.conf that has some high level configuration values that affect how the startup script executes. The actual startup script now resides in /usr/bin. It is /usr/bin/voxl-px4-start. This is actually called from the higher level script /usr/bin/voxl-px4.

Hi @majjam I'm glad Alex is helping you. Nothing should ever be "searing hot" in our platforms. If it is, it may be that you have a 5V supply connected to the 3.3V supply of the MCU by an errant connection using one of the connectors, and over time the MCU will fail (likely very promptly). Please double check your wiring and connections to all peripherals and connectors using this page as a guide: https://docs.modalai.com/voxl2-io-datasheet/#connector-callouts Be sure you do not connect any 5V supply to the 3.3V pins. Thanks!

Hi @Jskim We are happy to report our testing was successful. I have documented the process where you can modify MCBL-00022-2 and add the series caps for your self to unblock your USB 3 speeds: https://docs.modalai.com/cable-userguides/#how-to-modify-mcbl-00022-2-for-use-with-voxl-2-mini-usb-3-speeds Hope this helps!! Let us know how your testing progresses.

@Moderator Thank you for the response. I did come across this product of yours here: https://www.modalai.com/products/mdk-m0135?_pos=1&_sid=e4d19a51b&_ss=r that should work great after looking through some of your user guides and technical documentation.

@Jeremy-Frederick No, it should not ever crash in mid flight! Can you provide the console output (journalctl -b -u voxl-px4), px4 log, and dmesg output from one of these in flight crashes so we can try to figure out what is going on?

@Denver-Hopkins We had other projects come up. But this is starting to creep to the top of our list. If you would like to fast track it, feel free to email me at andrew.wilkins@ascendengineer.com

@Moderator Got it. I have mailed already to contact@modalai.com . Please expedite my request and let me know.

@afdrus Sounds good, let me know if I can help in any way!

Hi @wy Yes. You will need to use these hardware adapters as shown here though to mate to our Framos adapters (MDK-M0061): https://docs.modalai.com/voxl2-mini-image-sensors/#hardware-information Keep in mind, VOXL 2 Mini is just a reduced CSI port version of VOXL 2. We even retain the same hardware notations of "J6" and "J7" that align the same electrically and functionally with "J6" and "J7" of VOXL 2. Hope this helps!

@Paola-Lim Hey @Paola-Lim ! Check out our guide on setting up Wi-Fi here. Let me know if you have any questions! Thomas Patton

@John-Nomikos i see, yes, most likely due to: /lib/systemd/system/multi-user.target.wants/adbd.service That re-enables it after reboot.. Anyway, it looks like you found a workaround. Alternatively you could potentially remove that dependency from multi-user.target.wants/ but i have not tested that

@Paola-Lim The board can either be in "adb mode" or "fastboot mode". To go from adb to fastboot you can use adb reboot bootloader and to go from fastboot to adb you can use fastboot reboot

@Darshit-Desai We do not have a ready to fly reference yet. VOXL 2 Mini and the VOXL ESC Mini both support the industry standard 30.5mm mounting hole pattern, so you should be able to find a frame to fly.