Skip to content
Brand Logo

ModalAI Forum
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.

3,275Members
5,164Topics
26,145Posts
Browse

Categories

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

    2k 12k
    2k Topics
    12k Posts
    L
    Hi @Alex-Kushleyev, I wanted to follow up on this as we are currently in a critical phase of our commercial pilot deployment, and having the Starling 2 grounded is severely impacting our timeline. Given the voxl-imu-server logs and the pictures provided, is there any specific software workaround, service configuration, or hardware adjustment we can try to restore the IMU functionality? If you determine that the board requires factory repair or replacement, please let us know how we can expedite the RMA process to get operational again as soon as possible. Thank you for your support, Luis

  • Commonly asked questions we get from the community

    68 297
    68 Topics
    297 Posts
    Eric KatzfeyE
    @JB1 Our voxl-remote-id software with WiFi dongle is intended only for reference and is not meant to be a commercially ready system for our customers who need a remote id solution for their VOXL2 based drone products. Integration, testing, validation, and FAA registration with desired hardware is up to the end user. At a minimum the manufacturer id would need to be changed from ModalAI's id to your companies issued manufacturer id.

  • Questions by Product

    Product related questions and answers

    2k 12k
    2k Topics
    12k Posts
    S
    I am using a starling2 max with a voxl 2. I am using wifi for telemetry and successfully uploaded a waypoint mission in QGroundControl. When I try to execute the mission, the drone arms but never takes off. Below is the voxl-version and voxl-inspect-services output: voxl-version: system-image: 1.8.04-M0054-14.1a-perf kernel: #1 SMP PREEMPT Mon Mar 24 22:31:58 UTC 2025 4.19.125 ──────────────────────────────────────────────────────────────────────────────── hw platform: M0054 mach.var: 1.0.1 SKU: MRB-D0012-4-V2-C29-T7-M28-X0 ──────────────────────────────────────────────────────────────────────────────── voxl-suite: 1.5.0 ──────────────────────────────────────────────────────────────────────────────── Packages: Repo: http://voxl-packages.modalai.com/ ./dists/qrb5165/sdk-1.5/binary-arm64/ Last Updated: 2026-06-18 19:39:25 List: libfc-sensor 1.0.7 libmodal-cv 0.5.18 libmodal-exposure 0.1.4 libmodal-journal 0.2.6 libmodal-json 0.4.7 libmodal-pipe 2.13.2 libqrb5165-io 0.5.0 libvoxl-cci-direct 0.3.3 libvoxl-cutils 0.1.5 modalai-slpi 1.2.0 mv-voxl 0.1-r0 qrb5165-bind 0.1-r0 qrb5165-dfs-server 0.2.0 qrb5165-imu-server 1.1.3 qrb5165-mini-tof-server 0.2.2 qrb5165-rangefinder-server 0.1.5 qrb5165-slpi-test-sig 01-r0 qrb5165-system-tweaks 0.3.6 qrb5165-tflite 2.8.0-2 voxl-bind-spektrum 0.1.1 voxl-camera-calibration 0.6.0 voxl-camera-server 2.2.4 voxl-ceres-solver 2:1.14.0-10 voxl-configurator 1.0.2 voxl-cpu-monitor 0.6.0 voxl-docker-support 1.3.1 voxl-elrs 0.4.7 voxl-esc 1.5.4 voxl-feature-tracker 0.5.2 voxl-flow-server 0.3.6 voxl-gphoto2-server 0.0.10 voxl-joystick-server 0.0.6 voxl-jpeg-turbo 2.1.3-7 voxl-lepton-server 1.3.3 voxl-lepton-tracker 0.0.4 voxl-libgphoto2 0.0.4 voxl-libuvc 1.0.7 voxl-logger 0.5.3 voxl-mavcam-manager 0.6.0 voxl-mavlink 0.1.5 voxl-mavlink-server 1.4.9 voxl-microdds-agent 3.0.0-0 voxl-modem 1.1.8 voxl-mongoose 7.7.0-2 voxl-mpa-to-ros 0.3.9 voxl-mpa-to-ros2 0.0.7 voxl-mpa-tools 1.4.0 voxl-open-vins 0.4.19 voxl-open-vins-server 0.3.12 voxl-opencv 4.5.5-3 voxl-osd 0.1.8 voxl-portal 0.7.11 voxl-px4 1.14.0-2.0.105 voxl-px4-params 0.7.5 voxl-qvio-server 1.2.0 voxl-remote-id 0.0.9 voxl-reset-slpi 0.0.1 voxl-ros2-foxy 0.0.1 voxl-state-estimator 0.0.5 voxl-streamer 0.7.5 voxl-suite 1.5.0 voxl-tag-detector 0.0.5 voxl-tflite-server 0.4.1 voxl-utils 1.4.8 voxl-uvc-server 0.1.7 voxl-vision-hub 1.8.23 voxl-vtx 1.4.7 voxl-wavemux 0.0.1 voxl2-io 0.0.3 voxl2-system-image 1.8.04-r0 voxl2-wlan 1.0-r0 ──────────────────────────────────────────────────────────────────────────────── voxl-inspect-services : Scanning services... Service Name | Enabled | Running | CPU Usage ─────────────────────────────────────────────────────────────────── docker-autorun | Enabled | Not Running | modallink-relink | Disabled | Not Running | voxl-camera-server | Enabled | Running | 80.7% voxl-cpu-monitor | Enabled | Running | 0.0% voxl-dfs-server | Disabled | Not Running | voxl-elrs-startup | Disabled | Not Running | voxl-feature-tracker | Disabled | Not Running | voxl-flow-server | Disabled | Not Running | voxl-imu-server | Enabled | Running | 3.5% voxl-joystick-server | Disabled | Not Running | voxl-lepton-server | Disabled | Not Running | voxl-lepton-tracker | Disabled | Not Running | voxl-logger | Disabled | Not Running | voxl-mavcam-manager | Enabled | Running | 0.0% voxl-mavlink-server | Enabled | Running | 3.5% voxl-microdds-agent | Enabled | Running | voxl-mini-tof-server | Disabled | Not Running | voxl-modem-doodle | Disabled | Not Running | voxl-modem | Disabled | Not Running | voxl-mpa-ros2 | Disabled | Not Running | voxl-open-vins-server | Disabled | Not Running | voxl-osd | Disabled | Not Running | 1.8% voxl-portal | Enabled | Running | 24.6% voxl-px4 | Enabled | Running | voxl-qvio-server | Disabled | Not Running | 0.0% voxl-rangefinder-server | Enabled | Running | voxl-remote-id | Disabled | Not Running | voxl-seek-server | Disabled | Not Running | voxl-softap | Disabled | Not Running | voxl-state-estimator | Disabled | Not Running | voxl-static-ip | Disabled | Not Running | 1.8% voxl-streamer | Enabled | Running | voxl-tag-detector | Disabled | Not Running | voxl-tflite-server | Disabled | Not Running | voxl-time-sync | Disabled | Not Running | voxl-uvc-server | Disabled | Not Running | 0.0% voxl-vision-hub | Enabled | Running | voxl-vrx | Disabled | Not Running | voxl-vtx | Disabled | Not Running | voxl-wait-for-fs | Enabled | Completed | I have 3 logs from recent flights: https://logs.px4.io/plot_app?log=ef58c5c5-b105-41e0-bd12-202e5ff7f206 https://logs.px4.io/plot_app?log=e6654338-39fb-4429-b242-224fa468a522 https://logs.px4.io/plot_app?log=e6654338-39fb-4429-b242-224fa468a522 The following image shows the intended waypoint mission. https://drive.google.com/file/d/1FKFF4qVOXKiCqwCgiltWpe0bm_KrqHKj/view?usp=sharing Please let me know if there is any advice about how I can get it to correctly execute the waypoint mission.

  • Questions about developing software on the products

    501 2k
    501 Topics
    2k Posts
    R
    Hi, I was doing already autonomous mission again and again succefully with two drones. later I also encountered few crashes some of them prety harsh. but I was able to recover. also sufered from px4-param being deleted/corrupted. Now I test everyting and I cannot get the first drones to work with my code. when I switch to offbaord it immidiatly lands: VOXL-FC] heartbeat: armed=0 mode=OFFBOARD [VOXL-SVC] authority revoked (pilot takeover / link loss) — standing down (no re-request). [VOXL-SVC] WAIT_VIO: VIO velocity unstable (VIO backend converging) (65 s) [VOXL-SVC] WAIT_VIO: VIO pose stale (70 s) [VOXL-SVC] WAIT_VIO: VIO pose stale (75 s) with a new drone out of the box it works great. I suspect it has something to do with with overwritten params that I am not aware of. tried pulling the params from the good drone by px4-param show -a and compare them. without a good conclusion. my second guess is that somehow the cameras or other elements are oscilating and make the vio speed estimation not good and that is why these two drone fail to start the mission. can you help with a step by step procedure to eliminate the prorblem. I have tested the services, the cameras and it all looks fine. BR, Roy

  • Please request review from ModalAI before building your drone or custom add-on PCB

    15 43
    15 Topics
    43 Posts
    Alex KushleyevA
    Hi @Eyal , I just did a quick test and I am getting 2.0ms ping time when voxl2 cpu is in perf mode, and about 2.5ms when in auto mode. VOXL2 is idle. the NCM networking feature works concurrently with ADB, which is great and we also have some scripts to set up NAT if you need your voxl2 to actually use the Linux host as a "router" to access outside world. that is easy to set up as well (requires some routing changes on the linux host). In terms of real-time streaming, it is definitely adequate for image / video streaming to a Linux host. In fact, this option is my personal favorite way of connecting to Voxl2 while developing / testing cameras and viewing multiple streams in voxl-portal. Voxl-portal uses jpeg compression, which is a lot less efficient than h264/h265 and with the NCM connection, i don't have any issues (compared to adb port forwarding, which also allows voxl-portal to work, but is about 10x slower and uses a lot more CPU, you get frame drops in voxl-portal if required bandwidth is higher than 30-50Mbps or so). I am mainly using the USB-NCM feature for development purposes (as opposed to on a flying drone), but i have not found any limitations, at least for the bench testing use case. In terms of CPU load affecting the speed, i just ran a test stress -c 8 which loads up all 8 cores to 100% and the ping times did not change in perf mode (2.0ms) and in auto mode, the ping times reduced from 2.5ms to 2.0ms because the cpu cores are actually running at faster speeds. I am guessing that all the USB stuff is happening in the kernel at a higher priority, so it's not affected by the user applications (unless the cpu overheats, i supposed). GPU / DSP loads should not have any effect on this, since they are separate hardware. I also did another test - stream 4 video streams to voxl-portal (live view), which added up to about 100Mbps of network traffic and ping time stayed between 1.5-3.0ms (sometimes lower than 2.0ms). I have not observed any stability issues related to NCM being active for long periods of time (days). Make sure you are using a high quality USB-C cable (nothing fancy). Alex