@zachary-lowell-0 That worked perfectly, thanks!

Hi @K.Stute, IMX377 never became a supported sensor on VOXL 2, and the M0026 IMX377 module is end of life. What is on the board today: The system image ships a sensor module driver for IMX377, but only for camera slot 3 (J7 upper, which is M0084 JU): /usr/share/modalai/chi-cdk/imx377/com.qti.sensormodule.imx377_3.bin voxl-camera-server has no imx377 sensor type, and none of the standard camera configs use it, so voxl-configure-cameras can't set it up. The sensor types the server accepts are listed in common_defs.h. If you want to experiment anyway: copy that bin into /usr/lib/camera, plug the camera into J7 upper, check dmesg for imx377 probe succeeded, then start from an IMX214 hires config on slot 3 and change the resolutions to match the IMX377. That is untested on VOXL 2 and we can't support it. For a 4K hires camera on VOXL 2 we recommend the IMX412 (M0107 or M0161). It has drivers for several slots and is used in the standard camera configs. See VOXL 2 Image Sensors and VOXL 2 Camera Configs.

Hi @chris-pagnotta , yes it will work using M0181 adapter (provided in the kit) connected to VOXL2 J8. Please let me know if you need more details. Alex

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

Hi @vinny Thank you for sending the Starling 2 Max STEP file, it's very helpful: the propellers are included, and the frame lines up exactly with the V3 model's coordinates. The export is a single flattened body with no part names, so I can't identify individual components. I have a few questions about the ToF sensor in particular. Configuration: Can you confirm this file is the V4 frame with the C29 sensor package? ToF position: Where is the ToF sensor in this model? A centre point and the direction of the optical axis would be enough, in the file's own coordinates (X right, Y up, Z forward, mm). Comparing it with the V3/C28 model, my best guess is the front-left of the nose, standing upright, around X −13 / Y 10 / Z 63 mm. Is that right? Which ToF parts: Which ToF module and adapter board does C29 use? I tried virtually fitting your public M0178_STARLING_TOF_ADAPTER_REVA and MCAM-00005-TOF-A65 3D models into the nose of this STEP file (software shape-matching, no physical hardware), and neither matches exactly. Is there a different part number, or is the ToF shown in simplified form in this export? Orientation and field of view: An earlier forum post said the C29 ToF is mounted "vertically". Does that mean the 106° side of its 106° × 86° view is vertical, so the horizontal view is 86°? Named-parts version: If possible, could you share the same model as a multi-part STEP with component names, or a dimensioned drawing of the C29 nose showing the ToF, tracking-camera and hi-res-camera positions? I need this to check that a removable payload mount and propeller bumpers stay out of the ToF and tracking-camera views. Thanks again.