Hi John, No worries, also apologies for the delayed response. I should have asked for the SDK version you are on since we started packaging a voxl-sparrow-utils package that has that mlanutl bin that was missing in a later SDK version, I included the deb in the installer which should hopefully install correctly. Here is the new one to try with the README.MD with the instructions: https://drive.google.com/drive/folders/1SBCSf8_EZkkYV3GnvDhC2poD7ckjDLWq?usp=sharing , Thanks! Luke

@Alex-Kushleyev Hi Alex. Thanks for following up on this topic. I will update this thread with details. Thanks!

Around January 2026, I purchased a GPS-denied Development Drone with Battery Pack and Controller / Dual 4K & Dual Tracking (without ToF)/WiFi and Ghost Atto 2.4GHz(D0012). When I tried to remove the BOTS WiFi module that came with it and install the included VOXL 2 Ethernet and USB Hub Add-on(M0062), the antenna attached to the cover interferes and I am unable to install it. Has anyone experienced a similar situation? Also, if anyone knows a solution method, please let me know. Thank you.

@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.

Hardware: (board / drone / SKU, serial # if you have it) M0138 Software version: (paste the output of voxl-version) Python codes Configuration / services: (paste the output of voxl-inspect-services) Doesn't respond to USB uart What happened: I was connecting the M0138 to a 24V power supply for bench test. It turned on the led in the bootup sequence but afterwards stopped completely responding. I tried plugging it in and out but wouldn't start up again. Then I tried touching the components and the Vreg Inductor seems to be getting very hot, all other components seem fine. Is there a way to repair it? How would I do that? The purchase was made few months back and I don't want the ESC to scrap and want to make some use out of it. Thanks Logs / pictures: (attach files; PX4 logs -> https://logs.px4.io)

Hello @ישראל-בן-שלמה , Please see some options below and the recommendations at the end. For reliable VIO, we recommend dual tracking cameras. The tracking cameras are very light, so the extra 3 grams will give you lots of safety margin AR0144 is probably the best option since this is what we use. 2.2g with 80mm coax cable OV7251 camera (M0014) is probably the smallest (it is lower resolution also 640x480 vs 1280x800 for AR0144). ov7251 is EOL but it looks like we have some in stock. the weight of M0014 module is 0.5g (with the flex cable). However, to connect it to VOXL2 / mini, you would need an interposer like M0076 (0.6g) ( or M0135 (1.0g) IMX214 (M0025 module, https://docs.modalai.com/M0025/ ) may be the lightest 4K camera we have (0.7g with flex cable), but it is very old and sensor + lens quality is very far from our newer (and heavier) IMX412- and IMX664-based camera modules. Flir Boson 320 is a bit heavy too. The one i have with lens is about 23g. Most of the weight is the lens, i think. for connecting Boson to a Voxl2 Mini, you should use M0194 ( https://www.modalai.com/products/m0194 ) Boson → M0201 → coax → M0194 → VOXL 2 Mini J6 or J7? you can plug in another camera into M0194, such as AR0144 (coax version) or the IMX412 (coax version) The best option in terms of support (no EOL components) and hardware quality, would probably be: VOXL2 Mini (11g) M0195 (5.0g) -- see C43 configuration : https://docs.modalai.com/M0195/ Boson + M0201 + coax -> plugs directly into M0195. weight of M0201 + 80mm coax is 1.7g + 0.7g = 2.4g. Need to add weight of Boson! one or two AR0144 (M0166) -- 2.2g with 80mm cable (each) hires camera (IMX412) M0161 : 8.5g with 800mm coax cable Minimal Config VOXL2 Mini (11g) M0194 plugged into J7 (1.4g) + 80mm coax (0.7g) + M0201 (1.7g) + weight of Boson M0166 AR0144 (2.2g with 80mm coax) plugged into M0194 M0076 (0.6g) plugged into VOXL2 mini J6 M0025 IMX214 camera (0.7g) plugged into M0076 ** note that this is mixing the coax and non-coax cameras, but i think this should work. we would need to give this a quick test to make sure. Alex

Is there a log lin pipe field or debug flag that shows whether the throttle is currently engaged? Currently if you wish to have more robust logging you can run the commands via command line with the -d flag and check the output - you can also write some burner scripts capable of subscribing to the MPA itself and outputting what you need - lastly you can use voxl-logger which is capable or recording the data coming off the raw pipes. Was the throttle behaviour changed after 0.6.1? If a newer voxl-open-vins-server fixes it, which SDK version should we move to? you should be pulling the most recent instance of it - you can either build it from source from gitlabl OR you can run apt-get upgrade and that will auto pull the most recent deb's from our server. Given it is intermittent, is it safe to treat "dt == 33.3 ms" as a pre-flight check, or is there a more reliable condition we should test before an autonomous flight? I am a bit unsure what you mean treating this as a pre flight check - either openvins is feeding odometry and local setpoint positional data to px4 or it is not - if it IS even if its running slower that 33.3ms, then I would argue you are fine to fly. Thanks! Zach

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!

Hi, This post is quite old now, so going to mark it as resolved. If it is not, please start a new topic in the correct category for your needs. Thanks!