Hi. Is there support for connecting the Boson SX8 or Viento HD10 to the VOXL 2 through a MIPI connection?

As far as I know no one has ever tried this. I don't think HITL is supported by ardupilot (was in the past) but there may be some sort of Simulation on Hardware (SoH) that you could try to get running on VOXL2. I'm guessing it wouldn't be easy.

@alex-kushleyev Thanks for the response! A control model is a simple MLP (multi-layer perceptron) Input observation space: PX4 odometry topics, ToF depth/Depth estimation model, object detections. Output action space: PX4 offboard commands ( position and yaw for now, but we might extend to velocity/Collective thrust and body rates)

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

@MattK This is a generalized question but did your Starling Max 2 come with a ToF?

Hi ModalAI team, I’m developing a sub-250 g UAV and am trying to determine the lightest practical VOXL 2 / VOXL 2 Mini camera and sensor architecture for the aircraft. The target payload functions are: Daylight RGB video / imaging FLIR Boson+ 320 thermal video Camera input required for reliable VIO / navigation Lowest possible total camera, adapter, cabling, and interposer mass I am specifically trying to avoid carrying unnecessary stereo, ToF, or additional cameras if they are not required. Could you recommend the exact minimum hardware stack you would use for this application? In particular: For reliable VIO, can we use a single tracking camera, or is a stereo pair required/recommended? Which current ModalAI tracking camera/module would give the lowest installed mass? For RGB imaging, what is the lightest currently supported color camera/module that can provide useful daylight video? For a Boson+ 320, is the current recommended connection still: Boson → M0201 → coax → M0181 → VOXL 2 J8? Can the Boson, RGB camera, and minimum VIO camera configuration operate simultaneously on one VOXL 2 / VOXL 2 Mini? If yes, could you provide the exact ModalAI part numbers/interposers/cables required and, if available, approximate individual masses? Is there a supported camera configuration close to this, or would it require a custom voxl-camera-server configuration? The aircraft has a very tight mass budget, so I am trying to establish the absolute minimum viable sensor stack rather than starting from one of the larger development-kit camera configurations. Thanks, Yisrael

Please update your VINS to our master branch here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-open-vins-server For epoch-synced cams, tracking AR0144, please use: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-open-vins-server/-/tree/synced-timestamp?ref_type=heads

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 @dakota_ltu Under an NDA we could consider the ESC. However, even under NDA, we cannot share the VOXL 2 Schematics unless the recipient is also a Qualcomm licensee with their own NDA with Qualcomm. If that is still a path with value to you, please use this form: https://www.modalai.com/pages/contact-us