@Vinny said: M0041에 대한 자세한 설명(장치 및 I2C 주소 포함)은 다음 링크에서 확인할 수 있습니다: We have confirmed that the M0041 uses the INA231. We would like to use the INA260 in place of the INA231. Could you please confirm whether the INA260 can be used with the M0041 and the existing VOXL 2 software? If so, what hardware and software changes would be required, including any modifications to the current sensor driver or configuration?

@Vinny said: J3는 3번 핀과 5번 핀(GPIO_23 RXD, GPIO_22 TXD)을 통해 UART7만 제공하며, 해당 장치는 /dev/ttyHS1로 열거됩니다. UART13은 J3가 아닌 고속 B2B 포트인 J5에 있습니다. J3 및 J5의 전체 핀 구성은 다음 링크를 참조 하십시오. https://docs.modalai.com/voxl2-connectors/ We would like to use UART7 on J3 and UART13 on J5 to communicate with an STM32F103. Are these UART interfaces enabled by default, or is any additional hardware or software configuration required?

On the Wi-Fi questions: The -M36 option ships with an Alfa Network AWUS036EACS (802.11ac AC600, dual band 2.4/5 GHz, Realtek chipset, made in Taiwan). It is listed on the Starling 2 Max datasheet. Yes, you can use a different USB adapter, as long as the VOXL 2 kernel has a driver for its chipset. You cannot install arbitrary vendor drivers without rebuilding kernel modules, so pick an adapter based on one of the Realtek chipsets we support: RTL8812AU or RTL8821CU / RTL8811CU. The adapters we have tested are listed on the VOXL 2 WiFi Setup page. If you find a Japan-certified (Giteki) adapter with one of those chipsets, it should work with voxl-wifi in both Station and SoftAP mode. If you cannot find a certified adapter with a supported chipset, another option is a USB-to-Ethernet adapter on VOXL 2 connected to a small Japan-certified Wi-Fi bridge or travel router on the drone. VOXL 2 only sees Ethernet, so there are no driver constraints. In SoftAP mode the default hostapd country code is US. For use in Japan, set country_code=JP in /data/misc/wifi/hostapd.conf after running voxl-wifi so the radio uses Japanese channel and power rules.

@qqa , we have document how to achieve folder-level encryption on VOXL2 here : https://docs.modalai.com/enabling-file-encryption/ . Please let us know if you have any other questions.

Sorry @senja for the delays, this post did not get flagged for me. Yes, they install on different sides of the VOXL 2 board as shown here: https://docs.modalai.com/voxl2-connectors/#connector-callouts [image: 1792693889198-9a619597-c0ad-460a-b43a-c0689c8a0aab-image.jpeg] https://docs.modalai.com/M0226/#overview [image: 1792693659205-3064b401-56ca-4e7d-973c-0fe9c3ebe5cc-image.jpeg] https://docs.modalai.com/m0062-datasheet/#connector-callouts [image: 1792693766032-bc42a15b-8021-47f4-a9b6-534603ed8399-image.jpeg]

Thanks Tom and Eric, finally resolved this, it ended up being a power supply issue. The unit we used to typically run it on the bench seemingly browned out somewhere in the flashing procedure.

Files promised below voxl-mapper-packages.zip

Hello. Can a Starling 2 drone autonomously fly while flying over the pipe inside a sewer? The drone must fly autonomously in a dark place to inspect cracks or internal conditions while flying along the water pipe. I'm not sure if this feature can run on Starling, so I'm asking for help!

Hello everyone, I am looking for some expert advice on a VOXL 2 companion computer setup for a long-range platform. I have two main integration challenges: Challenge A: VIO at Higher Altitudes To solve the motion blur and pixel density issues at higher altitudes, I am planning a 6-camera configuration. I want to use 4 downward-facing sensors (2 daylight + 2 IR) equipped with narrow-angle lenses, alongside 2 standard wide-angle sensors (front and rear). Could you advise on the best supported sensors (e.g., IMX series) for this? Has anyone successfully tuned the voxl-qvio-server for narrow-angle lenses, and what were the altitude limits you achieved? Challenge B: LAN Integration & WireGuard The payload data flow will be: External RTSP Camera -> Ethernet -> VOXL 2 (WireGuard encryption) -> Ethernet -> Digital RX. Because VOXL 2 lacks multiple LAN ports, I will need a miniature industrial Ethernet switch. Does ModalAI have any tested hardware recommendations for this? Furthermore, what is the best practice for routing this VPN traffic through the VOXL 2 Ubuntu environment without bottlenecking the CPU? We are currently evaluating the VOXL 2 for a broader fleet deployment and want to ensure the ecosystem can support this custom optics requirement. Any feedback on off-the-shelf solutions or standard configurations for this use case would be greatly appreciated. Thank you!

Vinny and Tom, thank you so much!! Final Follow up questions below and I should be good Can a userspace service drive GPIO_46 as a plain output while the kernel SPI driver holds it as CS1 for /dev/spidev14.1, or do we need to remove that chip select from the device tree? What state are GPIO_46 and the level shifter in from power-on until the SPI driver loads? On the ESC cables: Does MCBL-00015-2 replace the kit's UART cable? It's listed as straight-through 1:1, but the M0138 data sheet says to leave J1 pin 1 (3.3 V reference out) unconnected, and our notes show VOXL 2 J18 pin 1 also carries 3.3 V. Is the 1:1 cable fine on the M0138, or should pin 1 be left open? Can the 150 mm -2 version be ordered for a production build? Is there a 150 mm version of the kit's VOXL 2 power cable? Is a stable SDK planned that includes voxl-px4 1.18.0-1.0.12 or newer?