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.

3461Members
5012Topics
25859Posts
Browse

Categories

  • Not sure where your question goes? Ask here. ModalAI engineers and the community answer questions about any VOXL product.

    2k 11k
    2k Topics
    11k Posts
    VinnyV
    Hi, Yes, each column is one channel. The full pinout is now in the VOXL 2 IO datasheet, under J1. For the M0022 Rev A: Rows The row nearest the 10-pin J1 connector (silkscreen S) carries the PWM signals. The middle row is not connected. The row at the far board edge (silkscreen G) is ground. Columns The silkscreen numbers the columns 1 to 8. With the silkscreen readable and J1 toward you, column 1 is on the left, at the same end as J1 pin 1. Column n carries PWM channel n from VOXL 2 IO J1: Column S row Middle row G row VOXL 2 IO J1 pin 1 PWM CH1 Not connected GND 2 2 PWM CH2 Not connected GND 3 3 PWM CH3 Not connected GND 4 4 PWM CH4 Not connected GND 5 5 PWM CH5 Not connected GND 6 6 PWM CH6 Not connected GND 7 7 PWM CH7 Not connected GND 8 8 PWM CH8 Not connected GND 9 Power and ground All eight G-row pins are tied together and to J1 pin 10 (GND). There is no power rail on the header. VOXL 2 IO J1 pin 1 (5P0V_BOOST) reaches the M0022 connector but is not connected on the board, and the middle row is not connected to anything. Power your ESCs or servos from their own supply. 5P0V_BOOST is a low-power reference only and must not power ESCs or servos: VOXL 2 IO datasheet, J1.
  • VOXL 2, VOXL 2 Mini and VOXL 2 IO: bring-up, connectors, power, cameras, system image and SDK installs on the current compute platform.

    669 4k
    669 Topics
    4k Posts
    Hector NevarezH
    Hi Ilan, Secure boot isn't something we've validated on VOXL 2 ourselves. To answer your questions, we did a one-off test: we re-signed the images from our flatbuild with a throwaway test key and checked that SecTools could sign and validate them. We haven't flashed re-signed images, booted them, or fused a board. Please treat the below as what we believe the path is, not a tested procedure. One caution before you blow any fuses: QFPROM fuses are one-time and can't be undone. A wrong key hash, OEM ID or Model ID, or any image in the boot chain signed with the wrong key, could permanently brick the board. We'd recommend flashing your signed images on an unfused board first and making sure everything boots and runs, then fusing a board for real. Unsigned boot images for the current VOXL 2 system image (XBL, TZ, devcfg, AOP, DSP and modem firmware, ABL), or a build path that produces them. You'll need to go to downloads.modalai.com to get the flatbuild for M0054-1. It's under downloads/Flat Builds/M0054(154)-1.zip. It has the boot images (XBL, TZ, devcfg, AOP, ABL), the DSP firmware (inside NON-HLOS.bin), and the firehose programmer. These images aren't unsigned. They're signed with Qualcomm's default SecTools test key, with OEM ID and Model ID set to 0x0000. We believe you can re-sign them with your own key rather than starting from unsigned images. In our test, SecTools replaced only the signature and the code stayed the same. A few images (TZ, QUP firmware, and part of XBL) also carry a Qualcomm production signature, and SecTools kept it when we re-signed. The OEM ID and Model ID used on VOXL 2, and any sec.dat or fuse settings you use or recommend. We don't sign the images with our own key. The flatbuild carries Qualcomm's default test signature with OEM ID and Model ID at 0x0000. We don't ship a sec.dat and don't blow any secure boot fuses, so we don't believe there's anything from our side you'd need to match. Whatever OEM ID and Model ID you choose should match between your fuse settings and the images you sign. A firehose programmer we can sign with our key, so fused units can still be flashed over EDL. Does the VOXL 2 flash flow (QDL, fastboot) work with a signed firehose? The firehose programmer is in the flatbuild as ufs/prog_firehose_ddr.elf, and we were able to re-sign it the same way as the other images. We haven't tested our flash flow on a fused board, so we can't say yet whether QDL or fastboot work there. Make sure you have a working signed firehose before you fuse, since that's likely your only way to recover a board over EDL. Are any QFPROM fuses blown on shipped units? No, we don't blow QFPROM fuses on shipped units. Does the current system image use ICE inline encryption (FBE) for /data? If yes, where are the keys held (TEE, RPMB)? No. /data isn't encrypted; it's a plain ext4 partition. The kernel has inline encryption support built in, but our image doesn't set it up, so there's no key storage to describe on our side. Does ABL support verified boot (AVB) for the kernel and root filesystem? Not at the moment. ABL has support for verified boot and dm-verity, but both are turned off in our build. The boot image has no AVB footer and the vbmeta partitions are empty, so ABL boots the kernel without checking it. Turning it on would mean rebuilding ABL with verified boot enabled and signing the boot image with your key. dm-verity also needs a read-only root filesystem, and VOXL 2's rootfs is read-write today, so that part would be a bigger change. Any known issues or guidance for secure boot on VOXL 2. The main one we expect is that PX4 on the DSP will likely stop working. VOXL 2 generates a per-device test signature at first boot so PX4 and our sensor code can run on the sensors DSP (SLPI). We don't expect test signatures to be accepted on a fused board, so those DSP libraries would need production signing before PX4 will load. Depending on the method, that may need a rebuilt SLPI firmware from our side, so please let us know before you fuse if you need PX4 running. Let me know if you have additional questions thanks!
  • Starling 2, Starling 2 Max, Sentinel, Seeker, m500, RB5, the PX4 Autonomy Developer Kit and Stinger FPV: flying, tuning, repairs and spare parts.

    649 3k
    649 Topics
    3k Posts
    VinnyV
    Hi @mmirtaba, Sorry for the slow reply. Disconnecting the USB-C cable and the batteries right away was the right call. Please do not power the drone again, from the batteries or from USB. Open an RMA here and reference order 8701: https://www.modalai.com/pages/rma Every Starling 2 Max is flight tested before it ships. So we can start looking into it before the unit arrives, please reply here with: Photos of the drone, including any part that looks discolored or damaged Where the heat and the smell seemed to come from, if you noticed Which port on the drone the USB-C cable was plugged into, and what it connected to on the desktop (a USB-C port, or a USB-A port through an adapter) Which operating system the desktop runs, and what "searching for the required drivers" involved (for example a Windows pop-up, Device Manager, or downloading something) Roughly how long the drone was running on batteries before you plugged in the USB-C cable Roughly how long after plugging in the cable you noticed the smell
  • Flight Core, Flight Core v2, Flight Core ArduPilot, the original VOXL, VOXL Flight, VOXL Flight Deck, VOXL-CAM and the older dev kits.

    433 2k
    433 Topics
    2k Posts
    Alex KushleyevA
    @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.
  • ESCs, image sensors, ToF and tracking cameras, Microhard and cellular modems, power modules, GPS and other add-on boards.

    414 2k
    414 Topics
    2k Posts
    Alex KushleyevA
    @juancho248 Sorry for the delay, please see the answers below: @juancho248 said: Which Starling 2 Max configuration provides the most suitable high-resolution RGB cameras for our application? All versions of Starling 2 Max come with dual IMX412 cameras (one front-facing, one down-facing). @juancho248 said: Is the C29 configuration currently supported, and what are its camera and depth-sensing capabilities? yes, c29 is supported. Note that TOF (depth sensor) does not work outdoors due to sunlight @juancho248 said: Can the RGB cameras be configured for downward-facing image acquisition? The rear IMX412 is already down-facing. The front camera is forward-facing, so you would need to make modification to make it down-facing @juancho248 said: Can the platform capture full-resolution still images programmatically, rather than only video frames? Yes, you can capture full resolution images, including RAW10 , which can be processed offline for best results. Processed YUV also supported. @juancho248 said: What camera controls are available through the SDK, including exposure, gain, image format, resolution, and capture timing? exposure, gain can be changed in real time. resolution can only be changed before camera server is started, but we support multiple streams with multiple resolutions (so you could have one full resolution stream for sparse captures and lower resolution for video feed). SW zoom is also available for processed images (YUV and video). @juancho248 said: Can captured images be associated with timestamps and available vehicle pose or localization metadata? yes, each image has metadata, including timestamp, exposure, gain. The timestamp is using linux monotonic time, which can be correlated with other data sources that are logged with same time source. @juancho248 said: What onboard storage options and image-transfer interfaces are supported? built-in storage (EMMC 120GB split into two partitions, typically at least 80-90GB free on a fresh system install - dont remember the exact number). you could support USB-based storage as well. Transfer images can be done using the USB / ADB interfrace. The adb itself is slow (<5MB/s) but a usb-ethernet can be enabled on the same USB connection, that is typically ~35MB/s transfers. If you use wifi on the drone, that is also an option. wifi speed depends on typical factors. @juancho248 said: Can images be stored locally during a mission and transferred after landing without requiring continuous Internet connectivity? Yes, as long as you don't run out of local storage. Note that RAW10 images from IMX412 at full resolution (4040x3040) are about 15MB each. YUV of the same resolution are 18MB each. You can also compress them to JPG on voxl2. Please let us know if you have any other questions of if I missed anything. Alex
  • voxl-sdk releases, MPA services, camera and video pipelines, Remote ID, and building and deploying your own software on VOXL.

    392 2k
    392 Topics
    2k Posts
    S
    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.
  • GPS-denied navigation with VIO, AprilTag relocalization, mapping and path planning, and obstacle avoidance.

    114 486
    114 Topics
    486 Posts
    Anthony KangA
    Files promised below voxl-mapper-packages.zip
  • Answers to the questions we get most often, written by ModalAI.

    64 293
    64 Topics
    293 Posts
    J
    Probably not fully out of the box. Starling 2 can support GPS-denied flight using VIO and onboard compute, but a sewer pipe adds low light, few visual features, tight clearance, and unreliable communications. Autonomous inspection would likely need a tuned SLAM/localization setup, obstacle sensing matched to the pipe profile, lighting, and a fail-safe flight plan. Test incrementally in a mock tunnel first. Check with ModalAI about the stock flight stack’s sensor and autonomy limits for your exact configuration.
  • Have an idea for our products or software you would like to see implemented? Tell us here.

    25 88
    25 Topics
    88 Posts
    Serhii RovnyiS
    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!
  • Ask ModalAI to review your PCB, connector choices or system architecture before you build, and find 3D models of our products.

    55 168
    55 Topics
    168 Posts
    Alex KushleyevA
    Hello @elvis-bicharri , Please take a look at the updated Starling 2 Max C29 V4 model : https://storage.googleapis.com/modalai_public/modal_drawings/MRB/D0012-Starling-2-Max-C29-V4-20261112.STEP You should be able to see all the sub assemblies and parts labeled now. Also, the model size (MB) is reduced. Please let us know if you need anything else. [image: 1794462369745-68e2b39c-c885-4c17-aa24-ed28cb1c7da5-image-resized.jpeg]