I'm confused by all of the new data. Can you summarize? You have tested with 2 different USB cameras: Lepton and c270. You have tested with 3 viewers: QGC, VLC, and ffplay. You have tested with 2 applications: voxl-uvc-server and voxl-streamer. Only one network connection: Microhard. Can you also try a MIPI camera instead of a USB camera? Then can you create a matrix saying which ones worked and which ones didn't?

Hardware: VOXL2, M0154 (2023 revision), SKU TF-M0054-4-V1-C11 Software: voxl-suite 1.6.5, system-image 1.8.08-M0054-14.1a-perf, kernel 4.19.125 Camera: FLIR Boson (FLIR vendor ID 09cb), connected via UVC/USB2 directly to VOXL2's internal USB2 host port (not via M0153 MIPI adapter) Comparison unit: an older VOXL2 M0054 (2021) with the same setup DOES NOT show this problem. SYMPTOM Board hard-freezes (not a clean reboot) within ~30-100s of the camera actively streaming, when the camera is connected directly to the internal USB2 port (no hub in between). Freeze is total: kernel logging, journald, and an independent on-device background process (unrelated to camera/USB) all stop simultaneously with zero warning in dmesg/journal beforehand. No panic, no watchdog trace, no lockup/stall message — just silence. The board does not self-recover; only a manual power cycle brings it back. Confirmed via app-level logs too: buffered log writes already visible on a live tail -f are lost from disk after recovery, showing the whole system (including the kernel's own writeback) stopped instantly with no chance to flush. Observed at the moment of freeze: power LED stays solid on; camera's own LED goes dark — suggesting the camera's specific USB port power rail is what actually loses power, not the whole board. This problem happens repeatedly on two different M0154 boards, but does not happen on M0054 boards. REPRODUCTION Connect Boson camera directly to VOXL2 internal USB2 port (no hub). Stream from the camera (e.g. continuous V4L2 capture). With no USB-C cable to a host connected: board freezes within roughly 30-100 seconds, unrecoverable without power cycle. With USB-C cable connected then disconnected mid-stream: also reproduces (sometimes as a clean PMIC SMPL/UVLO reset with automatic reboot, sometimes as the hard freeze above — inconsistent). WORKAROUND FOUND Placing a plain bus-powered USB2 hub (Genesys Logic 4-port, 05e3:0610) between the camera and the internal port fixes it completely — board survives indefinitely, with or without a USB-C cable connected. This points to the internal USB2 rail feeding that port not having enough local current/transient capability for the Boson's direct USB draw; the hub's own local bulk capacitance/current-limited power switch appears to absorb what the internal rail can't. ANOTHER WORKAROUND Connect any device to the USB-C output - it can be a laptop, a USB storage device or even a USB hub with nothing connected to it. In such a case, there will be no resets. ADDITIONAL NOTES No working hardware watchdog was found on this unit: /dev/watchdog does not exist, and msm_watchdog logs "wdog absent resource not present" at boot — so any future hang, from this or any other cause, also won't self-recover. Docs note M0154 is the revision where the USB-C port's host-mode support was brought to parity with VOXL2 Mini (M0054 didn't support USB-C host the same way) — asking in case that host-mode rework touched this same internal USB2 power path. Separately, after extended testing, this unit's USB-C debug port has stopped enumerating on a host entirely (no lsusb/adb activity at all, even after full power cycle) — possibly unrelated connector/PHY damage from repeated stress, flagging in case it's relevant to the same root cause. QUESTION: Is there a known current/power budget limitation on VOXL2's internal USB2 port when powering the Boson directly (vs. via the M0153 MIPI adapter path), and did anything on that specific power rail change between M0054 and M0154?

Hi @tom, That's exactly what I was looking for, 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.

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