Skip to content
VOXL® Developer Community

Build smaller, smarter, safer drones.

Ask the ModalAI engineering team, search thousands of solved threads, and share what you're flying — direct from the people who build VOXL.

3283Members
5167Topics
26160Posts
Browse

Categories

  • Note sure where to post? Ask questions here for direct access to the ModalAI engineering team

    2k 12k
    2k Topics
    12k Posts
    Eric KatzfeyE
    Yes, use the normal RC port. But cannot use an SBUS receiver with that port.
  • Commonly asked questions we get from the community

    69 298
    69 Topics
    298 Posts
    Adnaan YunusA
    Hi, I have a voxl 2 starling drone and I am running the camera stream using hireses_front_small_encoded inside adb shell via voxl-camera-server -d 0. Its crashing after 5-7 minutes, not sure what it is wanted to send here for inquiry purposes. Hardware Here is the hardware specs: ──────────────────────────────────────────────────────────────────────────────── system-image: 1.8.06-M0054-14.1a-perf kernel: #1 SMP PREEMPT Wed Oct 22 04:13:18 UTC 2025 4.19.125 ──────────────────────────────────────────────────────────────────────────────── hw platform: M0054 mach.var: 1.0.1 SKU: MRB-D0012-4-V2-C28-T8-M0-X0 ──────────────────────────────────────────────────────────────────────────────── voxl-suite: 1.6.3 ──────────────────────────────────────────────────────────────────────────────── current IP: 192.168.30.103 (wlan0) ──────────────────────────────────────────────────────────────────────────────── Logs Here is the error breakdown: VERBOSE: finished sending request for frame 17621 for camera tracking_front VERBOSE: returning from SendOneCaptureRequest for frame 17622 for camera tracking_front VERBOSE: setting hal3 exposure for tracking_front 6175533 461 VERBOSE: Received result from HAl3 for frame number 17564 VERBOSE: added request for preview stream VERBOSE: Sending request for frame 17622 for camera tracking_front for 1 streams ERROR: Received Fatal error from camera: tracking_front ERROR: Sending request 17622, ErrorCode: -ENODEV ERROR: Received "Result" error from camera: tracking_front, frame number 17607 VERBOSE: Received result from HAl3 for frame number 17607 VERBOSE: Received 1 buffers from camera tracking_front, partial result:0 VERBOSE: Received output buffer 17607 from camera tracking_front WARNING: Thread: tracking_front result thread Received ESTOP VERBOSE: Buffer arrive before meta frame 17607 VERBOSE: Received result from HAl3 for frame number 17608 VERBOSE: Received 1 buffers from camera tracking_front, partial result:0 VERBOSE: Received output buffer 17608 from camera tracking_front VERBOSE: Buffer arrive before meta frame 17608 VERBOSE: VERBOSE: Exposure: 26132338 VERBOSE: Readout Time: 22874342 VERBOSE: Received result from HAl3 for frame number 16321 VERBOSE: Received 0 buffers from camera hires_down, partial result:2 VERBOSE: Received metadata for frame 16321 from camera hires_down VERBOSE: Timestamp: 1013675034124 VERBOSE: Gain: 1004 VERBOSE: Exposure: 33233328 VERBOSE: Readout Time: 22874342 VERBOSE: Received result from HAl3 for frame number 17564 VERBOSE: Received 0 buffers from camera tracking_down, partial result:2 VERBOSE: Received metadata for frame 17564 from camera tracking_down VERBOSE: Timestamp: 1013725406646 VERBOSE: Gain: 637 VERBOSE: Exposure: 6971563 VERBOSE: Readout Time: 16122531 VERBOSE: Received result from HAl3 for frame number 16353 VERBOSE: Received 1 buffers from camera hires_front, partial result:0 VERBOSE: Received output buffer 16353 from camera hires_front VERBOSE: Received result from HAl3 for frame number 16321 VERBOSE: Received 1 buffers from camera hires_down, partial result:0 VERBOSE: Received output buffer 16321 from camera hires_down VERBOSE: Received result from HAl3 for frame number 17564 VERBOSE: Received 1 buffers from camera tracking_down, partial result:0 VERBOSE: Received output buffer 17564 from camera tracking_down VERBOSE: Received result from HAl3 for frame number 16354 VERBOSE: Received 0 buffers from camera hires_front, partial result:2 VERBOSE: Received metadata for frame 16354 from camera hires_front VERBOSE: Timestamp: 1013707432602 VERBOSE: Gain: 497 VERBOSE: Exposure: 22541986 VERBOSE: Readout Time: 22874342 VERBOSE: Received result from HAl3 for frame number 16322 VERBOSE: Received 0 buffers from camera hires_down, partial result:2 VERBOSE: Received metadata for frame 16322 from camera hires_down VERBOSE: Timestamp: 1013703705218 VERBOSE: Gain: 1004 VERBOSE: Exposure: 33233328 VERBOSE: Readout Time: 22874342 VERBOSE: Received result from HAl3 for frame number 17565 VERBOSE: Received 0 buffers from camera tracking_down, partial result:2 VERBOSE: Received metadata for frame 17565 from camera tracking_down VERBOSE: Timestamp: 1013758701129 VERBOSE: Gain: 635 VERBOSE: Exposure: 6960569 VERBOSE: Readout Time: 16122531 VERBOSE: Received result from HAl3 for frame number 16354 VERBOSE: Received 1 buffers from camera hires_front, partial result:0 VERBOSE: Received output buffer 16354 from camera hires_front VERBOSE: Received result from HAl3 for frame number 17565 VERBOSE: Received 1 buffers from camera tracking_down, partial result:0 VERBOSE: Received output buffer 17565 from camera tracking_down VERBOSE: Received result from HAl3 for frame number 16322 VERBOSE: Received 1 buffers from camera hires_down, partial result:0 VERBOSE: Received output buffer 16322 from camera hires_down VERBOSE: Received result from HAl3 for frame number 16323 VERBOSE: Received 0 buffers from camera hires_down, partial result:2 VERBOSE: Received metadata for frame 16323 from camera hires_down VERBOSE: Timestamp: 1013737159124 VERBOSE: Gain: 1004 VERBOSE: Exposure: 33233328 VERBOSE: Readout Time: 22874342 VERBOSE: Received result from HAl3 for frame number 16323 VERBOSE: Received 1 buffers from camera hires_down, partial result:0 VERBOSE: Received output buffer 16323 from camera hires_down ------ voxl-camera-server: Camera server is now stopping DEBUG: Stopping Camera: tracking_front DEBUG: ------ Last frame encoded: -1 DEBUG: OMX_EventCmdComplete DEBUG: OMX_EventCmdComplete DEBUG: Encoder moved to Idle State DEBUG: Deleting buffers for tracking_front preview stream DEBUG: OMX_EventCmdComplete DEBUG: Deleting buffers for tracking_front small video stream DEBUG: Deleting buffers for tracking_front large video stream DEBUG: Deleting buffers for tracking_front snapshot stream DEBUG: Deleting buffers for tracking_front misp stream DEBUG: Done closing device for camera tracking_front DEBUG: Done calling stop for camera tracking_front Stats For Camera tracking_front: Received Frame Count: 17622 Request Error Count: 55 Buffer Error Count: 31 Result Error Count: 32 DEBUG: Deleting Camera: tracking_front DEBUG: Stopped Camera: tracking_front DEBUG: Stopping Camera: hires_front DEBUG: ------ Last frame encoded: 16348 DEBUG: OMX_EventCmdComplete DEBUG: OMX_EventCmdComplete Segmentation fault: Fault thread: VideoEncCallBac(tid: 10824) Segmentation fault voxl2:/data/px4/log$ voxl2:/data/px4/log$ ERBOSE: finished sending request for frame 17621 for camera tracking_front bash: ERBOSE:: command not found front:/data/px4/log$ VERBOSE: returning from SendOneCaptureRequest for frame 17622 for camera tracking_f bash: VERBOSE:: command not found voxl2:/data/px4/log$ VERBOSE: setting hal3 exposure
  • Questions by Product

    Product related questions and answers

    2k 12k
    2k Topics
    12k Posts
    Alex KushleyevA
    @mrawding , I am sorry, but it looks like we are not going to be officially supporting Ubuntu2.0 Kernel on VOXL2, as we are working on enabling next gen hardware.. We did start the effort but it is not going to be finished for the general availability for VOXL2. Alex
  • 502 Topics
    2k Posts
    Eric KatzfeyE
    And the latest build of our fork with this fix is here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.146-202607161052_arm64.deb
  • Please request review from ModalAI before building your drone or custom add-on PCB

    16 45
    16 Topics
    45 Posts
    E
    Hey @alex-kushleyev, good to know it holds up like that under load, and thanks again for the reply. Two things I'm trying to pin down on the Mini: Power. Can a USB port on the VOXL Mini actually supply around 2-2.5 W, and can it do that on one port while a small USB camera runs on the other? Or should I plan to power those externally? Extra camera slot. From the D0013-V2 CAD the imager board looks like 5 DF56 coax connectors with 4 used (EO + dual AR0144 + Boson+), and the Lepton is on the M0187 SPI adapter so it's off the CSI bus. Is that spare coax connector wired to a usable CSI lane, and would voxl-camera-server take a 5th sensor (an M0161) there without a custom config? Thanks, Eyal