We are using the Bots Unlimited wifi board attached directly to our voxl2 board. It seems like the wifi driver will sometimes randomly crash with this message being repeated in dmesg: "Block woal_cfg80211_scan in abnormal driver state". When this happens the drone can no longer connect to wifi. We couldn't find any way in software to reboot the wifi board. To get it working again we have to power cycle the drone. Is there a fix for this?

Starling 2 Max is designed for 4S batteries only (two 2S Li-Ion battery packs, which are connected in series inside the vehicle). The Mini ESC, which also acts as a power source for VOXL2 inside the Starling 2 Max, is rated at least for 4S input (depending on the version of the ESC). There are several versions of the Mini ESC to provide the users some flexibility, in particular the voltage of the VOXL2 regulator (5V for VOXL2 and 3.8V for VOXL2 Mini). Since Starling2 Max uses a VOXL2, the ESC part number will be either M0129-5 or M0129-65. An updated (6S) version of the Mini ESC was released after the release of Starling 2 Max (new ESC part numbers: M0129-63, M0129-65). This ESC update extended the supported voltage for the ESC (not for Starling 2 Max) from 4S to 6S. The 4S version of the ESC has been phased out because the 6S version outperforms the original version even at 4S voltages (due to better Mosfets), so the 6S version is an improvement over the original 4S version of the ESC, while being fully backwards compatible. Using the 6S-rated ESC in the 4S-rated Starling 2 Max is completely safe. If you use the Mini ESC outside of the Starling 2 Max, you need to verify the part number / sticker on the ESC before plugging in 6S battery (M0129-63, M0129-65 only) The ESC variants and part numbers are documented here : https://docs.modalai.com/voxl-mini-esc-datasheet/ Alex

Please reach out here: https://www.modalai.com/pages/blue-uas-cleared-fpv-customer-intake-form

Hi ModalAI Team, I am attempting to set up a clean voxl-cross build environment on my host system using the repository at voxl-docker/voxl-cross. When running ./build-cross-docker.sh, the script halts missing the target rootfs archives: 1.8.06-M0054-14.1a-perf-20260203-rootfs.tar.gz 2.0.1-perf-20260122-rootfs.tar.gz qcs6490-ubun24-rootfs-0.0.6-20260311-040328.tar.gz When checking FileCloud (modalai.filecloudonline.com), my user account only sees the RB5 Flight with VOXL SDK Platform Releases directory (rb5_platform_*.tar.gz), and the Docker Images/Flat Builds subfolders do not contain these sysroot tarballs or the pre-built voxl-cross_V2.7.tgz container archive. Could you please provide direct download links for the missing rootfs archives, or grant access to the voxl-cross build assets directory on FileCloud? Host Environment: Ubuntu 22.04 / Docker Engine Target Hardware: VOXL 2 / QRB5165 Thanks!

Hello ModalAI team, I am part of a university student research team exploring the development of custom flexible circuit boards based on the VOXL ESC Mini and VOXL 2 Mini. We understand that the complete electrical schematics and design files for these products are not publicly available. Are there any options that would allow our team to move forward with this research, such as additional technical documentation, design files available under an NDA, a university research agreement, or direct engineering support? We would be happy to provide more information about our project, university affiliation, and intended use if needed.