Skip to content Link Search Menu Expand Document
ModalAI DOCS
Store

SDK 1.8.X Release Notes

Available now at https://downloads.modalai.com

SDK 1.8.1 is the current release for VOXL 2, VOXL 2 Mini, VRX and QCS6490. See Which SDK Should I Flash? for the SDK each product ships with.

Table of contents

  1. Overview
  2. SDK 1.8.1 System Images
  3. SDK 1.8.1 MD5 Hashes
  4. SDK 1.8.1 Package List
  5. SDK 1.8.1 Full Changelog (from SDK 1.8.0)
  6. SDK 1.8.1 Pre-release Builds
  7. SDK 1.8.0 Support Matrix
  8. SDK 1.8.0 System Images
  9. SDK 1.8.0 MD5 Hashes
  10. SDK 1.8.0 Package List
  11. SDK 1.8.0 Full Changelog (from SDK 1.6.8)

Overview

SDK 1.8.1

Released November 18, 2026

  • voxl-camera-server 2.2.47: IMX664 ClearHDR (on by default for imx664-fpv), highlight auto exposure as the default on IMX412 and IMX664, a new voxl-boson-config tool, and an opt-in camera-core backend (use_camera_core) in place of CamX.
  • voxl-vtx 3.19 and voxl-osd 1.8: VRX pilot view recording and re-streaming (video and OSD), frequency hopping with adaptive frequency hopping (AFH) that moves the hop set off jammed or busy channels, 5/10 MHz bandwidth on M0185, a radio menu in the VTX and VRX OSD menus, a VRX video loss mode (raw or freeze), a Nyctis video profile, and CoT AR waypoints. With several VRXs, one controls the link and the others observe.
  • IP radios: on Silvus and DTC links voxl-vtx runs adaptive link on the radio’s own link quality, and the OSD menu sets frequency, bandwidth and TX power. voxl-vision-hub 1.10.4 adds opt-in RC over IP (en_rc_active).
  • voxl-osd 1.8: a channel list grouped by band, a redesigned flight-mode menu with custom flight mode names, and a PX4 logging row.
  • voxl-lepton-server 1.5: M0197 support, faster boot and resync, CRC checks, and a new lepton0_grey pipe with stripe correction and denoise.
  • voxl-elrs 1.3: a “Reset to defaults” command, receiver updates over adb, a Windows build of the frontend, and ELRS 3.5.3.37 and 4.1.0.15 firmware.
  • voxl-configurator 1.1.57: hardware sub-revision B for Seeker V6 on QCS6490 (M0197 mounted rolled 180 degrees).
  • voxl-px4 and voxl-fpv-px4: Teseo LIV3 and LIV4 GPS support, an ESC actuator function fix, and ESC debug packet logging.
  • voxl-microdds-agent 3.0.2: upstream Micro XRCE-DDS Agent 3.0.2 and qcs6490 support.
  • modalai-adsp 1.0.14: USB-C connector temperature reset and shutdown thresholds.
  • voxl-tflite-server 0.5.2: a YOLOv8n person and vehicle detection model.
  • System images: VOXL 2 and VOXL 2 Mini 1.8.12, VRX 2.0.2-perf-20261117, QCS6490 v0.3.8.

SDK 1.8.0

Released October 12, 2026

  • PX4 moves from 1.14 to 1.18: voxl-px4 and voxl-fpv-px4 are rebased on upstream PX4 release/1.18.
  • PX4 sensor and thermal calibration files are now stored in /data/modalai/px4 instead of /data/px4/param.
  • voxl-open-vins-server 0.7.8: asynchronous multi-camera VIO, ceres-free initialization, and in-process targetless calibration (--calibrate), with a VINS Calibration page in voxl-portal.
  • voxl-vtx 3.3 and voxl-osd 1.2: Qt-based OSD rendering over DRM/KMS, adaptive link, an RF occupancy scanner and AR waypoints. voxl-vtx requires voxl-osd 1.2.0 or newer on the drone, so run SDK 1.8.0 on both the drone and the VRX.
  • voxl-camera-server 2.2.43: an imx664-or-imx412 sensor type that detects which hires sensor is fitted, and nyctis640 support.
  • voxl-elrs 1.2: faster parameter enumeration, M0220 firmware updates over SMP, and presets matched by parameter name.
  • voxl-configurator 1.1.54: hardware sub-revision SKUs (for example V6A).
  • libmodal-pipe 2.15 adds px4_vehicle_attitude_t and vtx_state_t pipe interfaces.
  • New packages: voxl-wireguard, voxl-quectel-cm, voxl-aprilgrid-camera-calibration, voxl-bf-osd-font, voxl-portal-web-libs and libvoxl-qt.

Upgrading a Seeker from SDK 1.6.3 or older: since voxl-elrs 1.1.2 (SDK 1.6.4), voxl-configure-mpa applies the Seeker sUPI GPIO preset on D0019 and D0020, which turns on Requires Arm for receiver Pin 2 and Pin 3. Those pins then hold their failsafe until the receiver itself is armed with voxl-elrs, whether or not the vehicle is armed. See Requires Arm.

SDK 1.8.1 System Images

See the system image release notes for VOXL 2 and VOXL 2 Mini and the VRX.

PlatformSystem image
VOXL 21.8.12
VOXL 2 Mini1.8.12
VRX (ubun2.0-multi)2.0.2-perf-20261117
QCS6490v0.3.8

SDK 1.8.1 MD5 Hashes

SDKHash
ubun2.0-multi_SDK_1.8.1.tar.gzb625bdec1550180957f59951bd583df7
voxl2-mini_SDK_1.8.1.tar.gzfab0c00aaf8ca61b984f6ffc40fee5fe
voxl2_SDK_1.8.1.tar.gz7ec6b93ba033c46399d3eadf4aeb2702
qcs6490_SDK_1.8.1.tar.gz0ef4d7b5bc184432a92c9021ca69b064

SDK 1.8.1 Package List

Release date: November 18, 2026

Meta-package: voxl-suite sdk-1.8.1 tag on GitLab, the exact package set pinned for this release.

Package changes from SDK 1.8.0 to SDK 1.8.1. Packages not listed are unchanged from SDK 1.8.0.

SDK 1.8.1 Full Changelog (from SDK 1.8.0)

libvoxl-cci-direct v0.4.1 → v0.5.0 3 changesSource CHANGELOG Diff
  • add voxl_cci_init_with_camera_hal() to start a minimal camera HAL so cameras are powered on and reachable over CCI, works on qrb5165 and qcs6490
  • add voxl-cci-uart tool
  • fix Semgrep findings in build and packaging scripts
libvoxl-codec v0.1.5 → v0.1.7 3 changesSource CHANGELOG Diff
  • [Codec2] Output through callbacks, return input buffers, runtime bitrate/framerate/GOP
  • [V4L2] Lower the encoder minimum resolution to 96x96 and reject out of range sizes at configure time instead of a bare -EINVAL at STREAMON
  • Add voxl-encoder-generate-video tool to encode a synthetic stream with no camera, with selectable test patterns
modalai-adsp v1.0.10 → v1.0.14 4 changes
  • Only toggle data lines on CDP ports when the HIGH-Z is enabled
  • Add extra protection to prevent a crash during UART reconfigurations
  • Raise USB-C connector RST/SHDN thresholds to 95/100 C
  • Add USB-C Connector shutdown / reset temp configs
modalai-adsp-vrx v1.0.0 → v1.0.2 3 changes
  • Set the usbc connector temp thresholds to 115/120
  • Only toggle data lines on CDP ports when the HIGH-Z is enabled
  • Add USB-C Connector shutdown / reset temp configs
modalai-slpi v1.2.4 → v1.2.5 1 change
  • Add extra protection to prevent a crash during UART reconfigurations
qrb5165-rangefinder-server v0.1.7 → v0.2.0 8 changesSource CHANGELOG Diff
  • create the control pipe before touching the bus so pause works from startup
  • retry sensor init and restart the sensors after read errors instead of exiting, systemd restarts did I2C traffic that couldn’t be paused
  • add io_expander_reset_pin and io_expander_reset_addr to reset a locked up sensor through its XSHUT line, set for the M0187 TOF in the M0173 arrangement
  • skip the reset when the io expander isn’t there, the M0157 breakout has the TOF but no expander
  • set the VL53L1X intermeasurement period to the timing budget, it was a fixed 30ms which ST doesn’t allow below the budget
  • add pause, pause_10s and unpause control pipe commands to stop i2c traffic
  • line buffer stdout so the journal gets log lines live
  • migrate to cross 4
voxl-camera-calibration v0.6.3 → v0.6.4 1 changeSource CHANGELOG Diff
  • use shifted targets for D0020/D0019 V6 front tracking cam to avoid gimbal occlusion
voxl-camera-server v2.2.43 → v2.2.47 25 changesSource CHANGELOG Diff
  • camera-core backend: ClearHDR exposures fused in MISP at the rate its clients read, with its tone mapping, HDR auto exposure and AWB
  • camera-core backend: support the Boson and Nyctis 640 thermal cameras (RAW only)
  • camera-core backend: every camera needs its slot in camera-setup.json, cameras are no longer discovered
  • camera-core backend: a camera that fails to start no longer shifts the ids of later cameras
  • add an opt-in camera-core backend (use_camera_core, default off) in place of CamX
  • imx664 ClearHDR (en_hdr), processed on the GPU with tone mapping, AWB on the merged image, EIS support and a debug log; on by default for imx664-fpv
  • add imx664_v2 sensor drivers (normal and ClearHDR modes) for qrb5165 and qcs6490, installed by voxl-configure-cameras for all imx664 configs and the imx664 / imx412 slot probe
  • imx412 zzHDR and DOL-HDR (experimental): merge and tone mapping, runtime exposure ratio, optional denoise, flickering light correction
  • add highlight auto exposure (ae_mode highlight) with exposure / gain split; ae_mode auto runs it on imx412 / imx664 with misp and is the default for those sensors (imx412 was isp)
  • HDR and highlight AE: ae_desired_msv sets the output brightness, raised digital gain limits in dark scenes, sensor specific gain limits
  • normal debayer: luminance gamma (gamma_mode) as the new default, AWB ignores clipped pixels
  • remove the 0.0625 Y offset from the RGB to YUV conversion
  • qcs6490: raw frame stride adjustment and ClearHDR Bayer texture access on the GPU instead of a CPU copy
  • publish camera capabilities, ClearHDR gain_info and per-pipe gamma in the pipe info json, written from a separate thread; periodic updates behind en_pipe_info_updates (default off)
  • set the CPU affinity and RT priority before the camera module is loaded so the CAMX threads inherit them
  • load opencv_<camera>_intrinsics.yml first, then <camera>_intrinsics.yml
  • a negative max_request_queue_depth is replaced by 0 (not limited) with a warning
  • voxl-configure-cameras copies the platform’s default tuning file for every camera config, fix the qcs6490 default tuning file name, add latest default tuning files
  • m0197: add C46/C47 configs, rotate tracking_front instead of tracking_down on C46/C47
  • camera configs 48 and 63 are the Nyctis versions of 47 and 62, with rev A and M0197 variants
  • remove the defaults for system images 1.6.4 and older (IMX214DefaultsOld, IMX412DefaultsOld)
  • add a script to generate all default camera server configs, add hdr-dark-capture.sh
  • add boson v2 sensormodules with updated sensor timing (including readout time), voxl-configure-cameras uses them
  • fix 14 bit boson processing publishing the raw frame from the previous iteration
  • add voxl-boson-config tool
voxl-configurator v1.1.54 → v1.1.57 10 changesSource CHANGELOG Diff
  • voxl-check-calibration no longer requires the per-unit lepton intrinsics, voxl-lepton-tracker uses the generic lepton intrinsics
  • modem 37 is the M0236 (was mislabeled M0198)
  • D0020 XSL (extras SL) loads the 3115 900kv ESC tune via voxl-esc setup_d0020_xsl_3115
  • Seeker camera menus: C48 (D0020 V6) and C63 (D0008 V6) are the Nyctis versions of C47 and C62
  • require baro temp cal on all qrb5165 (M0054/M0154) V6 seekers, not just D0020-4
  • voxl-configure-mpa loads every PX4 params helper (ghost, steam deck, pwm via elrs, msp_dp_osd, indoor_vio_missing_gps, zero_rf_missions, voxl2_io, test team tweaks) from the v1.18 params tree instead of v1.14
  • D0019 and D0020 V6 use the D0008_FPV_V6 extrinsics like D0008 V6, all V6 seekers share the chassis (was D0008_FPV_V5)
  • hardware sub-revision B for D0008, D0019 and D0020 V6 on M0197 (board code 9): the M0197 is mounted rolled 180 degrees vs V6 and V6A
  • voxl-configure-sku: the wizard offers B only on M0197, scripted -v 6B / -r B is rejected on other boards, families and versions
  • voxl-configure-mpa V6B: keeps the base camera config (no 62B), selects the shared rolled-board V6 extrinsics and warns when they are not installed, loads other_helpers/m0197_board_rotation.params after the platform params for SENS_BOARD_ROT 12 (needs voxl-px4-params 0.9.36 and the voxl-mpa-tools extrinsics)
voxl-cpu-monitor v0.7.7 → v0.7.8 8 changesSource CHANGELOG Diff
  • fix max cpu freq for small cores on qcs6490
  • disable systemd CPUAccounting which was disabling RT scheduling on ubun2.0 (gen1.5 vrx)
  • fix cpu frequency over-reporting when kernel throttles cpu before governor.
  • fix zombie processes being reported in top memory/cpu consumers after long uptimes
  • cpu_t_max in MPA topic now reports max temp instead of mean.
  • voxl-inspect-cpu computes its own mean from individual core temps now.
  • proper handling of old deprecated standby mode commands.
  • fix 1s delay coming out of pitmode on arm
voxl-elrs v1.2.3 → v1.3.30 78 changesSource CHANGELOG Diff
  • updating a Spire’s transmitter over adb works more than once a session: the reconnect after an update asked for a transmitter itself, so the Spire’s voxl-elrs opened its UART at the host’s receiver baud instead of the transmitter’s 921600. That garbled the port for voxl-rc-server too (its startup check failed every read for ~40 s, and stopping it for the next update waited that out), and the next update’s bootloader request went unanswered. The host now asks as the caller did on every connection, and the Spire keeps its transmitter’s baud whatever a host that lets it pick the role says
  • a port another process reads too (voxl-rc-server on a Spire’s transmitter UART) is no longer taken for unplugged when the other reader gets to the bytes first: a hang-up is told by the port itself (its ioctls fail with EIO), not by empty reads. The host also waits 2 s after an update before it reconnects, past voxl-rc-server’s startup check, which keeps a Spire on an older voxl-elrs from reading its port as unplugged then
  • over adb, an update shows its progress: the VOXL’s voxl-elrs reports the transfer and the services it stops and starts (voxl-rc-server on a Spire, voxl-px4 on a drone) while it runs, instead of the host showing “Enter the bootloader” until it is done. The VOXL needs this voxl-elrs for it; an older one updates as before
  • presets: the “Example configuration” preset is gone (it mapped channel 15 to all four output pins, and showed in the frontend’s preset list like a real one), and the Custom Domain preset says what it sets instead of “pass -T for the TX”, which neither the frontend nor a Spire needs
  • frontend: the Parameters page shows a device’s last parameter. It read the indexes below the count the device reports, but that count is the highest index, so “Reset to defaults” on 3.5.3.37 / 4.1.0.15 (and a receiver’s Bind State) was missing; libelrs’s sweep for parameters its folder walk misses had the same off-by-one
  • commands on a transmitter through EdgeTX serial passthrough (a Zorro Blue’s M0193) get their reply. The module only sends right after it receives a frame, so a command, sent once, timed out (“Command stopped: Connection timed out”, and Reset to defaults never asked to confirm). libelrs now pings a transmitter while it waits for a reply and re-sends a read only every 500 ms, which also stops a second read reply being taken for the next command’s
  • frontend: a finished command shows “Done” instead of “Command is active”, the page reads the parameters again, and the status line says what changed, e.g. “Unbind done: UID 44AD05BE674C -> 1A2B3C4D5E6F”
  • firmware catalog adds ELRS 3.5.3.37 and 4.1.0.15 (3.5.3.33 to 3.5.3.36 and 4.1.0.12 to 4.1.0.14 stay): the ModalAI receivers and transmitter get a “Reset to defaults” command, last in their parameters, that asks first (“Reset all but UID?”), puts every setting except the UID back to its default and reboots, so the link partner stays bound. A receiver’s reset turns its custom domain off, so it relinks only with a transmitter that has it off too, and a drone’s receiver loses its SKU presets until “Apply SKU defaults” or voxl-elrs configure. The CLI doesn’t run it, since it asks. 4.1.0.15’s transmitter Unbind runs on click like every other Unbind (it asked “Generate new UID?”), so voxl-elrs unbind works against it
  • frontend: Run on Unbind asks first, since the link drops until the devices are bound again; firmware that asks as well (a 4.1.0.14 or older transmitter) is answered from that dialog. After Reset to defaults the Parameters page says the device rebooted and reads every parameter again once it is back, instead of “Command stopped” and the old values
  • frontend: the presets move off the Parameters page into a Presets window opened from the page’s header, so the parameter list (Bind and Unbind first) stays as the firmware has it. The window puts the SKU defaults and the presets made for the SKU first and the rest under “Other presets”; the presets that make up the SKU defaults are named under them instead of listed again. Selecting a preset shows each setting it would change, now and after, before Apply. The separate “Reset to firmware defaults” button is gone: a firmware “Reset to defaults” command shows in the parameter list like any other command
  • libelrs: elrs_preview_preset_for_params() reports what one preset, or the SKU defaults, would change against parameters already read, without reading or writing the device
  • updating a drone’s receiver over adb (the frontend, or voxl-elrs -p adb:SERIAL) works: the VOXL’s voxl-elrs stops voxl-px4, updates the receiver over the SLPI UART and starts voxl-px4 again, as an update run on the VOXL does. It used to try the UART with voxl-px4 still holding it, fail with an I/O error and leave the session with no device. The host carries on with a fresh session after each update, since the DSP reset that restarts voxl-px4 cuts the old one off. The VOXL needs this voxl-elrs too
  • frontend: the Parameters page lists the presets that fit the connected device, each checked against it without writing (“Applied”, or how many settings it would change), with a Load button; over adb it shows the VOXL’s SKU and tags the presets for it, and “Apply SKU defaults” loads those as voxl-elrs configure does, without a firmware update; “Reset to firmware defaults” appears for firmware with a “Reset to defaults” command
  • libelrs: elrs_check_presets() and elrs_check_presets_for_params() check every preset against the device with one parameter read, elrs_apply_sku_defaults() applies a SKU’s merged presets, and log_get_level() reads the log level
  • firmware catalog adds ELRS 3.5.3.36 and 4.1.0.14 (3.5.3.33 to 3.5.3.35, 4.1.0.12 and 4.1.0.13 stay): a 3.5.3.36 receiver or transmitter whose settings reset to defaults gets a custom domain of 863-983 MHz with 80 channels, still disabled, as on 4.x and in the “Custom Domain” preset, instead of copying its regulatory domain (904-927 MHz, 40 channels); settings already stored keep their values, and it still links with 3.5.3.x on either end; 4.1.0.14 behaves as 4.1.0.13 (its parameters share those defaults with the configuration code)
  • Spire (MVX-S SKUs): voxl-elrs finds its M0193 transmitter from /data/modalai/sku.txt, so it needs no -p and no -T: MVX-S0001-7 is on /dev/ttyHS1 and MVX-S0001-9 on /dev/ttyHS6, and -p naming that UART implies -T; another MVX-S SKU asks for -p, and every other SKU (drones, with an M0193 receiver too) keeps the receiver path; ping shows the port it used
  • update and fw flash on a serial port stop the system services holding it (voxl-rc-server on a Spire) and start them again afterwards, and touch nothing when nothing else holds it; another kind of holder is named and the update refused
  • an update stops voxl-px4 only when it reaches the device through voxl-px4 (crsf_raw or the SLPI UART)
  • a second voxl-elrs on a serial port is turned away (“/dev/ttyHS6 is in use by voxl-elrs (pid N)”) instead of the two taking each other’s replies until both read the port as unplugged; voxl-rc-server, which only writes, still shares it
  • frontend over adb: a Spire’s voxl-elrs tells the frontend it has a transmitter, so the frontend talks to its M0193, updates it with the TX image and stops voxl-rc-server for the update; the port list names a Spire after its SKU, and the Update page notes that updating a transmitter drops its link. The Spire needs this voxl-elrs too: an older one is handled as before
  • param set takes an option’s text before reading a number as its index: param set “Max Power” 500 picks 500 instead of failing
  • an unplugged serial port reports -ENODEV on the first ping even when the ping’s write fails first, so the frontend disconnects at once instead of after three missed heartbeats (test_unplugged_port failed about one run in three)
  • frontend AppImage: the titlebar shows the desktop’s buttons (minimize and maximize on Ubuntu, where only close showed): desktop settings now come through the settings portal, since the bundled GSettings schemas lack distro defaults
  • frontend AppImage: GNOME’s dock shows the VOXL ELRS icon instead of a generic one; each launch registers ~/.local/share/applications/com.modalai.VoxlElrs.desktop and the icon, which also lists VOXL ELRS in the app grid, starts the AppImage last launched, and hides once that file is deleted
  • with voxl-px4 stopped, libelrs processes share the receiver through voxl-elrs-bridge instead of the first one to open qup7 keeping it until it exits (a voxl-portal page load locked voxl-elrs out that way): auto starts the bridge, which holds qup7 and serves the crsf_raw pipe as px4 does, and exits 30 s after its last client; voxl-px4’s drop-in stops the bridge before px4 starts and resets the DSP if libelrs used it, so px4 still comes up with crsf_rc
  • a process that auto connected to px4’s crsf_raw starts the bridge when px4 stops under it, so an open voxl-portal ELRS page reaches the receiver again about 6 s after px4 stops instead of failing until portal goes idle
  • -p qup7 and monitor name the process holding the UART when they can’t open it (“qup7 is held by pid 1234 (voxl-elrs bridge, voxl-elrs-bridge.service)”); update and fw flash stop the bridge and keep it from restarting until they finish
  • with px4 stopped and the bridge running, mpa:crsf_raw clients (voxl-mavlink-server, voxl-io-server) get RC from the receiver
  • an unplugged serial port is reported as such: once the reader sees the port go away (unplugged or powered off), requests return -ENODEV at once instead of waiting out their timeout
  • frontend: unplugging the connected device disconnects, as Disconnect does, with “Disconnected: the device was unplugged”, so the port list is free for the next device instead of staying locked at “Connection lost”; the Update page’s last result (“Firmware update complete”) clears on disconnect
  • frontend: the Update page offers upgrades on the installed major only, as voxl-elrs update does: ELRS 3.x and 4.x do not link with each other, so a transmitter on 3.5.3.35 no longer reads “Out of date” or lists 4.1.0.13 as an upgrade, and the update dialog on connect is gone; Show all versions lists every release, newest first, and installing another major warns that it won’t link with the other one
  • frontend: the connection status names the port as the port list does (Zorro Blue) instead of its /dev/serial/by-id path, the PWM page is hidden while a transmitter is connected, and the update progress shows above the release list
  • firmware catalog drops ELRS 3.5.3.32 (3.5.3.33 to 3.5.3.35, 4.1.0.12 and 4.1.0.13 stay)
  • firmware catalog adds ELRS 3.5.3.35 (3.5.3.32 to 3.5.3.34 stay): the M0193 transmitter’s UID can be written, as on 4.1.0.13, as 12 hex digits that apply at once and are saved; receivers are unchanged from 3.5.3.34, and it still links with 3.5.3.x
  • frontend: the Parameters page (was Settings) edits a writable UID as hex, written on Enter or Apply instead of after each pause in typing, with a Bind phrase popover that shows the UID before writing it; a read-only UID is text to copy, and a device that keeps its old UID is reported
  • frontend: the port list names each device from its USB product string (Zorro Blue, VOXL 2, CH340 USB serial) with its device node and USB IDs underneath, lists radios and flight controllers first, keeps the selected port when it refreshes, selects the port last connected to at the next start, and sets the host mode for the device: EdgeTX, Betaflight or Direct
  • add voxl-elrs bind-state, which prints the receiver’s Bind State (Bound, Unbound or Binding): a receiver in bind mode sends no RC and no link statistics, the same as one whose transmitter is off; needs a receiver on ELRS 3.5.3.34 or 4.1.0.13, older firmware is reported as not having the parameter
  • firmware catalog adds ELRS 3.5.3.34 and 4.1.0.13 (3.5.3.32, 3.5.3.33 and 4.1.0.12 stay); receivers on both report a read-only Bind State parameter (Bound, Unbound or Binding): 3.5.3.34: settings changed from the Lua script no longer drop the link or desync hopping, M0193 transmitters no longer slip on rate changes or lose the receiver for ~3 s on a change into 50 Hz, telemetry ratio 1:2 works with M0184/M0193 receivers, and a UID written to a receiver applies without a reboot; it still links with 3.5.3.x on either end 4.1.0.13: M0193 transmitters in Gemini mode no longer hang after a telemetry ratio change or keep reporting a link while the receiver scans after an outage, and the transmitter UID can be edited from the Lua script
  • stock ExpressLRS firmware versions are read correctly: stock firmware packs only major.minor.patch into the device info firmware ID (3.3.0 is 0x00030300), which read as 0.3.3.0, so update found no 0.x firmware for a stock receiver, skipped the 3.x the catalog has and suggested --allow-major (4.x, which loses the link to a 3.x transmitter); ping also prints the decoded version
  • frontend for Windows: every release tag also builds voxl-elrs-<version>-windows-x86_64.zip (MinGW-w64 cross build on Fedora); serial devices appear as COM ports labelled with their USB product name, so a Zorro Blue still gets Recover Zorro TX; EdgeTX and Betaflight passthrough and XMODEM updates work, with the bundled firmware and HTTPS through a packaged CA bundle; no ADB backend (no VOXL connections) and no ESPTool
  • serial port I/O sits behind a platform layer: termios on Linux, as before, and overlapped COM port I/O on Windows; a write the port stops accepting now times out after 2 s instead of failing on the first EAGAIN
  • the AppImage and the Windows zip of a release tag are kept instead of expiring after a month, so download links stay valid
  • frontend: Recover Zorro TX, for a Zorro Blue whose internal M0193 TX was left with a half-written image by an interrupted update: after EdgeTX holds the TX in its bootloader (MDL held at power-on, needs EdgeTX with that bootloader hook), the button opens EdgeTX passthrough without identifying the TX and the Update page installs to MODALAI_M0193_TX; shown only for a Zorro Blue port
  • an update that loses its device (USB unplugged, handset powered off) ends at once with “No such device” instead of reading the hung-up port forever at full CPU, which also kept the frontend’s update lock; nor is a device that is gone retried
  • XMODEM uses CRC mode when the bootloader NAKs stray bytes before asking with ‘C’, instead of switching to checksum mode and having every block rejected (seen when a retried update found the bootloader already waiting)
  • update picks the transmitter image on a transmitter: without --target it treated every M0193 as a receiver, so -T update (or -E update) on an M0193 TX flashed the M0193 RX image; the role now comes from -T/-E as it does for fw flash
  • an explicit -b is kept when a TX target selects TX mode, so update --target MODALAI_M0193_TX -b 420000 --boot-baud 921600 can put the TX image back on an M0193 that runs RX firmware
  • firmware catalog adds ELRS 4.1.0.12 and drops 4.1.0.11 (3.5.3.32 and 3.5.3.33 stay): M0193 transmitters on 4.x ignored the reboot-to-bootloader command, so update and fw flash timed out on “bootloader prompt not detected” (“Connection timed out” in the frontend) and a 4.x transmitter could not be updated or downgraded; 4.1.0.12 transmitters take the command again; a transmitter still on 4.1.0.11 or older ignores it, so its first update to 4.1.0.12 takes SWD or the MSP UID-write reboot; receivers are unchanged and a 4.1.0.11 receiver updates in place (settings and binding kept)
  • the x86_64 AppImage of the frontend builds in CI again (it failed on the v1.2.3, sdk-1.8.0-2 and v1.3.9 tags): the AppImage runtime is pinned to a dated type2-runtime release instead of the “continuous” one, whose asset was replaced (404), and GTK 4.10.5 builds on GitLab’s shared runners, which answer close_range() with EPERM and made GLib’s spawn fail
  • add voxl-elrs pwm pin <pin> <us>…, which holds receiver pins at a raw pulse width (800-2200 us) until Ctrl-C or --for <seconds>, with or without an RC link the value bypasses the pin’s input channel, map and inversion, and other pins on the same channel don’t move; the pins are released on exit, and the receiver lets go of a pin 1 s after the last command; the receiver confirms every command, so firmware without it is reported as too old, pins that require arming are reported as holding their failsafe until ‘pwm arm’, and DShot, serial and I2C pins are refused; needs ELRS 3.5.3.33 or 4.1.0.10
  • firmware catalog adds ELRS 3.5.3.33 and 4.1.0.10 (3.5.3.32 and 4.1.0.9 stay): the pin output command behind pwm pin, M0184/M0193 On/Off pins switch again on 4.x, 10kHz Duty pins pulse on 3.x, and a pin switched from On/Off to a PWM rate pulses without a reboot
  • parameter writes read the value back up to three times, 100 ms apart, before failing, so configure through voxl-px4 no longer stops on “write verification failed” for a value that was written
  • firmware catalog is now ELRS 3.5.3.32 and 4.1.0.9 only (3.5.3.26-3.5.3.31 and 4.1.0.6-4.1.0.8 removed; ‘fw flash <file>’ still flashes an older image): M0184/M0193 receivers hold all four PWM pins low (No Pulses) until a preset or parameter configures them, instead of driving 1312 us (3.x) or 1824 us (4.x) from boot, which lit the Seeker light bars, updating a receiver to either version resets its settings and binding to defaults (configure reapplies the presets; bind again afterwards), and 3.5.3.32 receivers rescan rates after a disconnect instead of staying locked to their first rate
  • firmware catalog adds ELRS 4.1.0.8 (installed by update/configure only from 4.x, or with --allow-major): rate changes re-link in 0.1-1 s instead of 1-13 s, receivers rescan rates after a disconnect instead of staying locked to their first rate, and the M0193 transmitter resumes at once after a handset CRSF dropout
  • firmware updates recover instead of leaving the receiver or voxl-px4 broken: when the SLPI UART cannot be opened (DSP not ready yet: “Encountered error while initializing bus 17”), the command starts again in a fresh process, once a failed XMODEM transfer is retried twice; it leaves the receiver in its bootloader, which takes the next attempt after an update, voxl-px4 must recreate the crsf_raw pipe; if it does not, voxl-elrs resets the DSP and starts voxl-px4 again, and reports an error if that fails too
  • voxl-elrs records the version it flashed per target in /data/modalai/voxl-elrs/flashed; update --target on a device that does not answer stays on that major instead of falling back to 3.x
  • test hooks for the recovery paths: ELRS_TEST_FAIL_SLPI_OPEN=1 and ELRS_TEST_XMODEM_ABORT_AT=<blocks> (each fires once)
  • add voxl-elrs pwm write <channel> <value>…, which holds RC channels at a value until Ctrl-C or --for <seconds>, with or without an RC link the pins mapped to those channels follow through their maps; values are microseconds (880-2120) or percentages, e.g. pwm write 5 1900 --for 10 it resends the override every 100 ms because the receiver drops it after 1 s, and it goes through voxl-px4’s crsf_raw pipe, so voxl-px4 keeps running needs ModalAI receiver firmware (3.5.3.31 and 4.x take the override); an RC link that is up writes the same channels
  • update and configure stay on the major version the device runs: 3.x moves to the newest 3.x, never to 4.x, because a 4.x receiver does not link with a 3.x transmitter update --allow-major or configure --allow-major moves to a newer major; allow_major_update=true in /etc/modalai/voxl-elrs.conf allows it for every update a device already on 4.x keeps getting 4.x updates, and update says when a newer major is available and how to move to it
  • update says which version the device runs when there is nothing to do, and whether that is the newest local firmware or newer than anything in the catalog
  • fw flash writes ESP receivers at 921600 over SLPI: esptool syncs at 115200 and switches once its stub runs, taking a BetaFPV Nano 900 RX from ~2.5 min to ~45 s needs voxl-esptool 0.2.3, now the recommended version, which returns to 115200 before starting the new firmware
  • esptool progress shows live during fw flash instead of arriving all at once when it finishes
  • the “Received N bytes of data from SLPI while SLPI uart not in use” lines no longer flood the fw flash output
  • param list drops the banners and the root folder row, and ends with one line, e.g. “BFPV Nano 900RX: 16 parameters (hash 0x199e7187)”
  • group the commands under param, config, preset, pwm and fw; the old names still work as hidden aliases voxl-elrs help <command> or <command> --help explains a command, and typos get a suggestion
  • param get/set take a name or path, e.g. output-mapping/pin-1/map-mode, and param set takes selection options as text
  • config load and preset load print every change and take --dry-run; preset load takes several presets
  • presets are addressed by id (file name), name or path, and preset list shows which ones configure applies for the SKU
  • configure takes the SKU as an argument and --no-update replaces configure-sku
  • fw flash takes a catalog version, e.g. fw flash 3.5.3.30, or a file
  • exec <name> runs a receiver command parameter; an unknown command no longer enumerates the receiver before failing
  • tab completion comes from the binary and completes parameter paths, presets, firmware versions, targets and ports with nothing cached, the first Tab reads the parameter names through voxl-px4’s crsf_raw pipe
  • every command exits 0 or 1; failsafe exits 0, 1 in failsafe, 2 on error
  • merge the T7 and T8/T10 team race reset presets into reset_teamrace
  • log the per-command parameter count and serial open/close at DEBUG
  • add voxl-elrs monitor, which prints a timestamped line for each receiver reboot, RC gap and ping silence until Ctrl-C reboots come from the boot announcement ModalAI receivers send unprompted: 3.5.3.24+ on every receiver, 4.x on M0184/M0193 only it needs the receiver UART, so stop voxl-px4 first and run voxl-reset-slpi -t 8000 before starting it again
  • monitor --frames also logs the type, length and addresses of every frame received, RC and link statistics included
  • auto fails straight away when voxl-px4 runs with an RC mode other than CRSF_RAW, instead of timing out on the crsf_raw pipe
voxl-esc v1.6.5 → v1.6.6 1 changeSource CHANGELOG Diff
  • add d0020_xsl_3115 motor tune
voxl-esptool v0.2.2 → v0.2.3 3 changes
  • fail the SYNC wait after a few seconds when only non-bootloader data arrives (a receiver still running its firmware streams CRSF), instead of discarding it until the caller’s 300 s timeout
  • write to SLPI UARTs in 768-byte chunks instead of 64: each write is one DSP message and the DSP UART write blocks for about twice the transmit time, so a BetaFPV Nano 900 RX flash went from 105 s to 75 s at 115200 (12 s at 921600)
  • return the ESP8266 stub to 115200 before --after soft_reset runs the new firmware: after a write at a higher baud, ELRS 3.x hung with its LED dark until power-cycled
voxl-fpv-px4 v1.18.0-8.0.25 → v1.18.0-8.0.33 11 changes
  • Send correct OSD canvas size and blank empty warning line
  • Expose hover thrust estimate over DDS
  • Fixed leak of task descriptors in Qurt platform
  • Add logging of esc debug packets
  • Do not call voxl-reset-slpi after px4 reset on qcs6490 to avoid reset loop
  • Never block arming on magnetomoter failures
  • Stream STATUSTEXT on onboard links
  • Fixed missing actuator function assignment in voxl_esc driver
  • Updated GPS drivers for latest Teseo LIV4 support
  • Add cmdcounter and address fields back into the ESC log message
  • uxrce_dds_client: expose telemetry for DDS flight-control utilities
voxl-lepton-server v1.4.2 → v1.5.0 35 changesSource CHANGELOG Diff
  • M0197/M0255 support
  • faster bootup
  • faster resyncs
  • lepton model and lens data is now publishing in pipe info json
  • add CRC checks to data
  • SPI read rate fixed at 12MHz for robustness, spi_speed in the config is ignored unless force_spi_speed_override is true
  • remove cpu affinity lock to core 7
  • condense publishing to one thread instead of spawning threads each frame
  • max out priority for read thread to help timing
  • lower priority of publish thread to prevent treading on parsing thread
  • smoother frame timestamps: per-packet arrival time plus rc_math timestamp filter
  • thread-safe I2C, CCI commands can no longer interleave between threads
  • new --debug_raw option to hex dump raw SPI data
  • --debug_ffc now traces lepton FFC state
  • -d prints a 1Hz stats line, per-frame “publishing” prints moved to -v
  • one log line per dropped frame instead of a cascade of segment warnings
  • new lepton0_grey pipe with stripe and bar correction plus edge preserving denoise, color and h265 now built from it
  • smoothed outlier-rejecting AGC for 8-bit feeds (en_smooth_agc), snaps on FFC
  • configurable FFC frames to average, default 4
  • new dump_raw16 control command and --dump_raw16 option to save raw16 frames for analysis
  • optional histogram equalization (en_histeq, off by default)
  • lepton0_16raw is destriped by default (en_destripe_raw16), dumps stay unfiltered
  • NEON denoise and vectorized unpack, AGC, stripe and bar removal, -t prints per-stage publish timing
  • reliable VoSPI sync on first boot and after reboots, video output is restarted before each sync
  • full datasheet reset at every start on boards with a reset line (M0187, M0255), replaces the 1.4.2 skip on already booted leptons
  • resets and reboots now work on M0188/M0195, the CCI OEM reboot (M0157) no longer gives up on an expected I2C error
  • stay off I2C for 2.5s after any reset or reboot, I2C traffic while the lepton boots can hang it until a power cycle
  • turn the M0188/M0195 mux channel off while the lepton boots, keeps PX4 barometer traffic away from it
  • pause voxl-rangefinder-server through its control pipe while the lepton boots when it shares the lepton’s I2C bus, needs qrb5165-rangefinder-server 0.2.0
  • service starts after voxl-rangefinder-server
  • keep the lepton in reset with its clock off after the service stops
  • write the io expander pin directions again before every reset, warn if it lost power
  • detect M0157 with M0226 and exit as unsupported
  • --crystal_on/–crystal_off say when the clock comes from the carrier and can’t be switched
  • line buffered stdout so the journal gets log lines live
voxl-microdds-agent v3.0.0-0 → v3.0.2-0 6 changesSource CHANGELOG Diff
  • Upgrade Micro XRCE-DDS Agent to upstream v3.0.2, including the Fast DDS write return-code fix for batched XRCE packets.
  • Move from emulator docker to cross docker for both qrb5165 and qcs6490
  • Add qcs6490 support
  • Pin Fast CDR 2.2.8 and Fast DDS 3.6.2.0 to upstream commit hashes.
  • Always build and link the pinned DDS libraries for the agent package.
  • Apply the dependency patch to a generated source copy, keeping the submodule clean; require cleaning stale builds.
voxl-osd v1.2.1 → v1.8.0 13 changesSource CHANGELOG Diff
  • OSD Menu: add support in CHANNEL menu for starting, changing and stopping frequency hopping (mode, band, jamming avoidance, channel ticks)
  • OSD Menu: CHANNEL opens a channel list grouped by band
  • OSD Menu: hold the stick to autoscroll, PX4 LOGGING row with a confirm pop-up
  • ADVANCED > RADIO shows DRONE POWER and GCS POWER on Silvus links managed by voxl-vtx (ip_radio_stats silvus), each offering only the powers that radio supports
  • On DTC links managed by voxl-vtx (ip_radio_stats dtc), DRONE POWER and GCS POWER show FULL or dB below full power (the radios report no absolute power) and set the radios’ attenuation (set_ip_radio_atten / set_ip_radio_gcs_atten)
  • On Silvus and DTC links managed by voxl-vtx, the main menu CHANNEL row lists the frequencies every radio in the mesh supports and SAVE AND EXIT retunes them all together (set_ip_radio_freq)
  • On Silvus and DTC links managed by voxl-vtx, ADVANCED > RADIO BANDWIDTH shows the radios’ real width and offers only the widths every radio supports (set_ip_radio_bw); other IP radios still show N/A (IP)
  • Updated ar waypoints menu to support CoT Markers and clearing waypoints
  • Redesign the flight-mode menu with a scrollable picker and available external modes
  • Request the AVAILABLE_MODES data through mavlink onboard to get custom flight mode names
  • Show vtx hopping frequencies in OSD Menu
  • Update vtx_data to include camera_latency field
  • Add a radio menu to VTX and VRX OSD menus
voxl-portal v0.9.16 → v0.9.17 5 changesSource CHANGELOG Diff
  • camera server config editor page in camera multi-view, with a server log panel, load from a local file (open button or drag and drop), save locally, and raw text editing of broken json with the error highlighted
  • camera view: AE control buttons, HDR on / off button, save bayer frame button, HDR debug info, playback seek only in playback mode
  • multi-view: default downscale width 1280 px (was 320), config editor and server log split instead of overlaid
  • main menu always renders on top
  • fix DOM XSS in page rendering, guard string-keyed lookups against prototype keys, resolve semgrep and lint findings (Defect Dojo)
voxl-px4 v1.18.0-1.0.9 → v1.18.0-1.0.14 5 changesSource CHANGELOG Diff
  • Add logging of esc debug packets
  • Fixed missing actuator function assignment in voxl_esc driver
  • Bring the Teseo gps detection logic and BMM150 driver + board detection logic over from FPV build
  • Added cmdcount and address to ESC debug logging and enabled in default log profile
  • Moved to the ModalAI fork GPS drivers with latest Teseo support for LIV3 and LIV4
voxl-px4-params v0.9.35 → v0.9.39 5 changesSource CHANGELOG Diff
  • update RC timeout length for fpv drones
  • v1.18 fpv_helpers/enable_turtle_mode.params (all D0008 variants): VOXL_ESC_T_ON 9 -> 7, joystick turtle button on the Zorro’s ch10 like ELRS turtle mode (RC_MAP_AUX1 10); button 9 is a ch11 camera switch position, so switching cameras over IP (Silvus) turned turtle mode on
  • rename v1.18 fpv_helpers/seeker_v6b_m0197_board_rotation.params to other_helpers/m0197_board_rotation.params, voxl-configurator 1.1.55 loads the new name
  • m0197_board_rotation.params header describes the side roll (USB-C port moves to the other side of the drone) and that voxl-configurator loads it on Seeker V6B SKUs
  • v1.18 fpv_helpers/seeker_v6b_m0197_board_rotation.params: SENS_BOARD_ROT 12 for Seeker V6B (M0197 rolled 180 relative to V6), loaded by voxl-configurator 1.1.55 after the platform params
voxl-rc-server v0.0.10 → v0.0.11 2 changesSource CHANGELOG Diff
  • DTC and Silvus: ignore arm while the mode switch is in OFFBOARD (block_arm_in_offboard)
  • Zorro wheel (ch11) presets use 1000/1280/1440/1560/1720/2000, off the voxl-vtx stream switch bin edges, so 5 slots no longer skip cameras
voxl-tflite-server v0.5.1 → v0.5.2 3 changesSource CHANGELOG Diff
  • add yolov8n person/vehicle detection model
  • fix quit option in model selection menu
  • enable qcs6490 build
voxl-vision-hub v1.10.3 → v1.10.4 5 changesSource CHANGELOG Diff
  • joystick (MANUAL_CONTROL) RC channel emulation, enabled with en_joystick
  • consume rc_active pipe from voxl-mavlink-server, opt-in with en_rc_active (default off)
  • fall back to PX4 RC_CHANNELS when rc_active is stale
  • _ip suffix on factory_enable presets sets en_rc_active for RC over IP (DTC, Silvus)
  • VFC: don’t block shutdown while waiting for the flight mode configuration
voxl-vtx v3.3.4 → v3.19.2 72 changes
  • Fix low power on profile switch after disarming edge case
  • MAVLink telemetry: newest sample per sender, every event message, per-category TX bitrate lines
  • One VRX controls the link (adaptive link, IP fallback, hop set) and others observe
  • Observer can ask for control with a FUNC double tap or request_control, the controller gets a 10 s pop-up to accept
  • Hub: menu commands, VRX requests and RADIO settings now reach the drone through the spire
  • VRX: pilot view encoder and Qt OSD stop running when nobody is using them
  • VRX: more reliable delivery of CoT, AR clear and forwarded MAVLink to the drone
  • VRX: tx_power_dbm config key and improved back-channel TX power readout on gen 2
  • Adaptive frequency hopping (AFH): with jamming avoidance on, the link moves away from jammed or busy channels automatically
  • AFH: the OSD hop icon shows when jamming avoidance is working around a jammed or busy channel
  • AFH: with several VRXs, one controls the hop set and the others observe
  • Frequency hopping respects the FCC regulatory mode power limits
  • OSD menu: VTX publishes its usable channels, channel list in the OSD
  • OSD: live camera icon glow, LED icon casts a beam when active, zoom shown as a bar above the link bar, ALT/MGRS cards aligned with the link bar
  • Add new confirmation pop-up for the menu system, legend shows hold to autoscroll
  • IP radio link stats (ip_radio_stats dtc or silvus): adaptive link on Silvus and DTC radios
  • VRX OSD on an IP radio: the radio’s SNR, RSSI, noise, frequency, width, temperature and TX power
  • RC over IP: RC bar from the radio’s uplink SNR, or from video loss on links without radio stats (fiber)
  • Silvus and DTC frequency, bandwidth and drone/ground TX power settable from the VTX (set_ip_radio_* commands)
  • IP radio drone power follows the profile power; pit mode holds 25 mW until the first arm
  • IP radio presets: updated error correction defaults
  • IP-only links: UDP sends no longer block when the route to the VRX drops
  • voxl-configure-vtx --disable no longer errors on the VRX (M0205) or VOXL 2 Mini
  • Nyctis video profile; Nyctis gets Boson thermal status, pitch offset and invert
  • fix ai detection issue when detections from a single frame don’t have the same timestamp
  • CoT ar waypoint support
  • AR waypoints: support calibrated plumb-bob lenses alongside fisheye lenses
  • Fix bug when placing overridable OSD blocks by x/y bindings
  • Increase default AI detection quantity from 3 to 5
  • Update M0198 refrences to M0236
  • VRX: a latched static stream holds its session, so another VTX with the same key on the channel cannot take the picture over
  • VRX video_loss_mode: raw (default, both codecs decode frames with holes) or freeze (decode them but hold the last good frame until a clean I-frame, at most freeze_max_ms)
  • VRX OSD menu: VRX SETTINGS > DISPLAY > Video Loss switches Raw / Freeze live
  • voxl-inspect-vrx dmg column: decoder-flagged / loss-tainted / hidden frame counts
  • VRX menu RECORDING: video and flight log Off / On / Arm
  • Flight log: one CSV + ULog per device, named by flight id
  • Lepton overlays fall back to the generic lepton intrinsics when no per-unit cal is present
  • Adaptive link support for 10 MHz
  • VRX pilot view to ATAK: steady RTSP, OSD over MPEG-TS
  • VRX: recordings are pilot view (video + OSD), raw video as fallback
  • Gen1.5 VRX: pilot view recording and streaming support (needs libvoxl-codec 0.1.7)
  • Fix VRX crash when starting a recording on a read-only or pulled USB stick, and recordings after the first stopping right away
  • Add OSD toasts for USB recording failures (REC FAILED: USB ERROR, REC STOPPED: USB REMOVED, REC STOPPED: DISK FULL)
  • Gen1.5 VRX: fix display output after another application used the display
  • VRX pilot view: records and re-streams (RTSP/MPEG-TS) what the pilot sees (video + OSD) on vrx_pilot_encoded pipe, with or without a display
  • Take back interrupt signals from Qt for cleaner shutdown
  • OSD: weak-link edge glow, restyled AI detection boxes with fade and smooth tracking, OSD render rate increased to 60Hz
  • VRX width_scan param (default on) to turn off the stream-loss width scan
  • OSD: SNR shows – and the VTX bars are grey stubs while no video stream is arriving
  • Smoother channel-width changes; adaptive link can step down to 10 MHz with a VRX that supports 5/10 MHz
  • More accurate voxl-inspect-vrx
  • More robust in-process recovery when radios dropout
  • Fix Lepton decoding bug: Use CPU copy on QCS6490 when decoded frame stride does not match width
  • VRX switches between 5 and 10 MHz directly (needs the SDK 1.8.1 VRX system image)
  • Improved forward error correction defaults
  • voxl-inspect-vtx fec(ms) column now shows the error correction time per frame
  • Faster forward error correction encoding, lowering VTX CPU use
  • voxl-vtx and voxl-vrx flush stdout per line, so adaptive-link level changes reach the journal when they happen
  • Fix VTX latency readings on frames recovered by error correction
  • Initial working version of frequency hopping
  • Add OSD indication for frequency hopping
  • Add support for 5/10MHz bandwidth on M0185
  • Add camera_latency to vtx inspect tool
  • Add total_latency to vrx inspect tool
  • RC controls (rc_toggle stream switching, zoom_ch, invert_toggle, osd_rc_toggle and the ch7 LED status) read voxl-mavlink-server’s rc_active mux while it publishes, so a GCS joystick over IP drives them on the same channels as RF; setups without the mux keep using the autopilot’s RC_CHANNELS
  • remove the MANUAL_CONTROL joystick button settings (per-profile joystick_toggle, zoom_joystick_buttons, osd_joystick_toggle, led_joystick_button_off/ir), stale keys are dropped from voxl-vtx.conf; ch11 stream switching and ch12 zoom over IP need voxl-mavlink-server >= 1.4.23
  • ch7 LED status splits the channel into thirds (off below 1333 us, overt, IR above 1667 us) so a slightly off-center middle position no longer reads as IR
  • voxl-configure-vtx: rc_toggle defaults to 11 (the ch11 camera switch on the ModalAI TX presets), so radio presets (silvus, dtc, fiber, …) and plain factory setups switch cameras on ch11 like the seeker SKU setups; set -1 to disable.
  • Add a radio menu to VTX and VRX OSD menus
  • More reliable encrypted link start-up in weak signal
  • Fix lost packet counting
  • Update for new prod procedures

SDK 1.8.1 Pre-release Builds

SDK 1.8.1 went through ten pre-release builds, alpha0 to beta6. Each entry below lists what changed from the build before it, newest first. The final SDK 1.8.1 release has the same packages as 1.8.1-beta6.

SDK 1.8.1-beta6

Built November 17, 2026 · changes from SDK 1.8.1-beta5

voxl-vtx v3.19.1 → v3.19.2 1 change
  • Fix low power on profile switch after disarming edge case

SDK 1.8.1-beta5

Built November 17, 2026 · changes from SDK 1.8.1-beta4

  • System images: VOXL 2 and VOXL 2 Mini 1.8.12, VRX 2.0.2-perf-20261117, QCS6490 v0.3.8.
voxl-osd v1.6.0 → v1.8.0 3 changesSource CHANGELOG Diff
  • OSD Menu: add support in CHANNEL menu for starting, changing and stopping frequency hopping (mode, band, jamming avoidance, channel ticks)
  • OSD Menu: CHANNEL opens a channel list grouped by band
  • OSD Menu: hold the stick to autoscroll, PX4 LOGGING row with a confirm pop-up
voxl-tflite-server v0.5.1 → v0.5.2 3 changesSource CHANGELOG Diff
  • add yolov8n person/vehicle detection model
  • fix quit option in model selection menu
  • enable qcs6490 build
voxl-vtx v3.16.0 → v3.19.1 14 changes
  • MAVLink telemetry: newest sample per sender, every event message, per-category TX bitrate lines
  • One VRX controls the link (adaptive link, IP fallback, hop set) and others observe
  • Observer can ask for control with a FUNC double tap or request_control, the controller gets a 10 s pop-up to accept
  • Hub: menu commands, VRX requests and RADIO settings now reach the drone through the spire
  • VRX: pilot view encoder and Qt OSD stop running when nobody is using them
  • VRX: more reliable delivery of CoT, AR clear and forwarded MAVLink to the drone
  • VRX: tx_power_dbm config key and improved back-channel TX power readout on gen 2
  • Adaptive frequency hopping (AFH): with jamming avoidance on, the link moves away from jammed or busy channels automatically
  • AFH: the OSD hop icon shows when jamming avoidance is working around a jammed or busy channel
  • AFH: with several VRXs, one controls the hop set and the others observe
  • Frequency hopping respects the FCC regulatory mode power limits
  • OSD menu: VTX publishes its usable channels, channel list in the OSD
  • OSD: live camera icon glow, LED icon casts a beam when active, zoom shown as a bar above the link bar, ALT/MGRS cards aligned with the link bar
  • Add new confirmation pop-up for the menu system, legend shows hold to autoscroll

SDK 1.8.1-beta4

Built November 13, 2026 · changes from SDK 1.8.1-beta3

voxl-osd v1.3.2 → v1.6.0 7 changesSource CHANGELOG Diff
  • ADVANCED > RADIO shows DRONE POWER and GCS POWER on Silvus links managed by voxl-vtx (ip_radio_stats silvus), each offering only the powers that radio supports
  • On DTC links managed by voxl-vtx (ip_radio_stats dtc), DRONE POWER and GCS POWER show FULL or dB below full power (the radios report no absolute power) and set the radios’ attenuation (set_ip_radio_atten / set_ip_radio_gcs_atten)
  • On Silvus and DTC links managed by voxl-vtx, the main menu CHANNEL row lists the frequencies every radio in the mesh supports and SAVE AND EXIT retunes them all together (set_ip_radio_freq)
  • On Silvus and DTC links managed by voxl-vtx, ADVANCED > RADIO BANDWIDTH shows the radios’ real width and offers only the widths every radio supports (set_ip_radio_bw); other IP radios still show N/A (IP)
  • Updated ar waypoints menu to support CoT Markers and clearing waypoints
  • Redesign the flight-mode menu with a scrollable picker and available external modes
  • Request the AVAILABLE_MODES data through mavlink onboard to get custom flight mode names
voxl-px4-params v0.9.38 → v0.9.39 1 changeSource CHANGELOG Diff
  • update RC timeout length for fpv drones
voxl-rc-server v0.0.10 → v0.0.11 2 changesSource CHANGELOG Diff
  • DTC and Silvus: ignore arm while the mode switch is in OFFBOARD (block_arm_in_offboard)
  • Zorro wheel (ch11) presets use 1000/1280/1440/1560/1720/2000, off the voxl-vtx stream switch bin edges, so 5 slots no longer skip cameras
voxl-vision-hub v1.10.3 → v1.10.4 5 changesSource CHANGELOG Diff
  • joystick (MANUAL_CONTROL) RC channel emulation, enabled with en_joystick
  • consume rc_active pipe from voxl-mavlink-server, opt-in with en_rc_active (default off)
  • fall back to PX4 RC_CHANNELS when rc_active is stale
  • _ip suffix on factory_enable presets sets en_rc_active for RC over IP (DTC, Silvus)
  • VFC: don’t block shutdown while waiting for the flight mode configuration
voxl-vtx v3.15.1 → v3.16.0 7 changes
  • IP radio link stats (ip_radio_stats dtc or silvus): adaptive link on Silvus and DTC radios
  • VRX OSD on an IP radio: the radio’s SNR, RSSI, noise, frequency, width, temperature and TX power
  • RC over IP: RC bar from the radio’s uplink SNR, or from video loss on links without radio stats (fiber)
  • Silvus and DTC frequency, bandwidth and drone/ground TX power settable from the VTX (set_ip_radio_* commands)
  • IP radio drone power follows the profile power; pit mode holds 25 mW until the first arm
  • IP radio presets: updated error correction defaults
  • IP-only links: UDP sends no longer block when the route to the VRX drops

SDK 1.8.1-beta3

Built November 13, 2026 · changes from SDK 1.8.1-beta2

  • New package: libvoxl-camera-core v0.1.45.
libvoxl-cci-direct v0.4.1 → v0.5.0 3 changesSource CHANGELOG Diff
  • add voxl_cci_init_with_camera_hal() to start a minimal camera HAL so cameras are powered on and reachable over CCI, works on qrb5165 and qcs6490
  • add voxl-cci-uart tool
  • fix Semgrep findings in build and packaging scripts
voxl-camera-server v2.2.44 → v2.2.47 5 changesSource CHANGELOG Diff
  • camera-core backend: ClearHDR exposures fused in MISP at the rate its clients read, with its tone mapping, HDR auto exposure and AWB
  • camera-core backend: support the Boson and Nyctis 640 thermal cameras (RAW only)
  • camera-core backend: every camera needs its slot in camera-setup.json, cameras are no longer discovered
  • camera-core backend: a camera that fails to start no longer shifts the ids of later cameras
  • add an opt-in camera-core backend (use_camera_core, default off) in place of CamX
voxl-vtx v3.13.3 → v3.15.1 5 changes
  • voxl-configure-vtx --disable no longer errors on the VRX (M0205) or VOXL 2 Mini
  • Nyctis video profile; Nyctis gets Boson thermal status, pitch offset and invert
  • fix ai detection issue when detections from a single frame don’t have the same timestamp
  • CoT ar waypoint support
  • AR waypoints: support calibrated plumb-bob lenses alongside fisheye lenses

SDK 1.8.1-beta2

Built November 12, 2026 · changes from SDK 1.8.1-beta1

voxl-camera-calibration v0.6.3 → v0.6.4 1 changeSource CHANGELOG Diff
  • use shifted targets for D0020/D0019 V6 front tracking cam to avoid gimbal occlusion
voxl-fpv-px4 v1.18.0-8.0.29 → v1.18.0-8.0.33 4 changes
  • Send correct OSD canvas size and blank empty warning line
  • Expose hover thrust estimate over DDS
  • Fixed leak of task descriptors in Qurt platform
  • Add logging of esc debug packets
voxl-microdds-agent v3.0.0-0 → v3.0.2-0 6 changesSource CHANGELOG Diff
  • Upgrade Micro XRCE-DDS Agent to upstream v3.0.2, including the Fast DDS write return-code fix for batched XRCE packets.
  • Move from emulator docker to cross docker for both qrb5165 and qcs6490
  • Add qcs6490 support
  • Pin Fast CDR 2.2.8 and Fast DDS 3.6.2.0 to upstream commit hashes.
  • Always build and link the pinned DDS libraries for the agent package.
  • Apply the dependency patch to a generated source copy, keeping the submodule clean; require cleaning stale builds.
voxl-px4 v1.18.0-1.0.13 → v1.18.0-1.0.14 1 changeSource CHANGELOG Diff
  • Add logging of esc debug packets

SDK 1.8.1-beta1

Built November 10, 2026 · changes from SDK 1.8.1-alpha3

  • System images: VOXL 2 and VOXL 2 Mini 1.8.11, VRX 2.0.2-perf-20261110, QCS6490 v0.3.7.
voxl-vtx v3.11.0 → v3.13.3 7 changes
  • Fix bug when placing overridable OSD blocks by x/y bindings
  • Increase default AI detection quantity from 3 to 5
  • Update M0198 refrences to M0236
  • VRX: a latched static stream holds its session, so another VTX with the same key on the channel cannot take the picture over
  • VRX video_loss_mode: raw (default, both codecs decode frames with holes) or freeze (decode them but hold the last good frame until a clean I-frame, at most freeze_max_ms)
  • VRX OSD menu: VRX SETTINGS > DISPLAY > Video Loss switches Raw / Freeze live
  • voxl-inspect-vrx dmg column: decoder-flagged / loss-tainted / hidden frame counts

SDK 1.8.1-alpha3

Built November 9, 2026 · changes from SDK 1.8.1-alpha2

voxl-configurator v1.1.56 → v1.1.57 1 changeSource CHANGELOG Diff
  • voxl-check-calibration no longer requires the per-unit lepton intrinsics, voxl-lepton-tracker uses the generic lepton intrinsics
voxl-vtx v3.9.1 → v3.11.0 4 changes
  • VRX menu RECORDING: video and flight log Off / On / Arm
  • Flight log: one CSV + ULog per device, named by flight id
  • Lepton overlays fall back to the generic lepton intrinsics when no per-unit cal is present
  • Adaptive link support for 10 MHz

SDK 1.8.1-alpha2

Built November 6, 2026 · changes from SDK 1.8.1-alpha1

qrb5165-rangefinder-server v0.1.7 → v0.2.0 8 changesSource CHANGELOG Diff
  • create the control pipe before touching the bus so pause works from startup
  • retry sensor init and restart the sensors after read errors instead of exiting, systemd restarts did I2C traffic that couldn’t be paused
  • add io_expander_reset_pin and io_expander_reset_addr to reset a locked up sensor through its XSHUT line, set for the M0187 TOF in the M0173 arrangement
  • skip the reset when the io expander isn’t there, the M0157 breakout has the TOF but no expander
  • set the VL53L1X intermeasurement period to the timing budget, it was a fixed 30ms which ST doesn’t allow below the budget
  • add pause, pause_10s and unpause control pipe commands to stop i2c traffic
  • line buffer stdout so the journal gets log lines live
  • migrate to cross 4
voxl-lepton-server v1.4.2 → v1.5.0 35 changesSource CHANGELOG Diff
  • M0197/M0255 support
  • faster bootup
  • faster resyncs
  • lepton model and lens data is now publishing in pipe info json
  • add CRC checks to data
  • SPI read rate fixed at 12MHz for robustness, spi_speed in the config is ignored unless force_spi_speed_override is true
  • remove cpu affinity lock to core 7
  • condense publishing to one thread instead of spawning threads each frame
  • max out priority for read thread to help timing
  • lower priority of publish thread to prevent treading on parsing thread
  • smoother frame timestamps: per-packet arrival time plus rc_math timestamp filter
  • thread-safe I2C, CCI commands can no longer interleave between threads
  • new --debug_raw option to hex dump raw SPI data
  • --debug_ffc now traces lepton FFC state
  • -d prints a 1Hz stats line, per-frame “publishing” prints moved to -v
  • one log line per dropped frame instead of a cascade of segment warnings
  • new lepton0_grey pipe with stripe and bar correction plus edge preserving denoise, color and h265 now built from it
  • smoothed outlier-rejecting AGC for 8-bit feeds (en_smooth_agc), snaps on FFC
  • configurable FFC frames to average, default 4
  • new dump_raw16 control command and --dump_raw16 option to save raw16 frames for analysis
  • optional histogram equalization (en_histeq, off by default)
  • lepton0_16raw is destriped by default (en_destripe_raw16), dumps stay unfiltered
  • NEON denoise and vectorized unpack, AGC, stripe and bar removal, -t prints per-stage publish timing
  • reliable VoSPI sync on first boot and after reboots, video output is restarted before each sync
  • full datasheet reset at every start on boards with a reset line (M0187, M0255), replaces the 1.4.2 skip on already booted leptons
  • resets and reboots now work on M0188/M0195, the CCI OEM reboot (M0157) no longer gives up on an expected I2C error
  • stay off I2C for 2.5s after any reset or reboot, I2C traffic while the lepton boots can hang it until a power cycle
  • turn the M0188/M0195 mux channel off while the lepton boots, keeps PX4 barometer traffic away from it
  • pause voxl-rangefinder-server through its control pipe while the lepton boots when it shares the lepton’s I2C bus, needs qrb5165-rangefinder-server 0.2.0
  • service starts after voxl-rangefinder-server
  • keep the lepton in reset with its clock off after the service stops
  • write the io expander pin directions again before every reset, warn if it lost power
  • detect M0157 with M0226 and exit as unsupported
  • --crystal_on/–crystal_off say when the clock comes from the carrier and can’t be switched
  • line buffered stdout so the journal gets log lines live

SDK 1.8.1-alpha1

Built November 5, 2026 · changes from SDK 1.8.1-alpha0

  • System images: QCS6490 v0.3.6.
voxl-vtx v3.9.0 → v3.9.1 1 change
  • VRX pilot view to ATAK: steady RTSP, OSD over MPEG-TS

SDK 1.8.1-alpha0

Built November 5, 2026 · changes from SDK 1.8.0

  • System images: VOXL 2 and VOXL 2 Mini 1.8.10, VRX 2.0.2-perf-20261105, QCS6490 v0.3.5.
libvoxl-codec v0.1.5 → v0.1.7 3 changesSource CHANGELOG Diff
  • [Codec2] Output through callbacks, return input buffers, runtime bitrate/framerate/GOP
  • [V4L2] Lower the encoder minimum resolution to 96x96 and reject out of range sizes at configure time instead of a bare -EINVAL at STREAMON
  • Add voxl-encoder-generate-video tool to encode a synthetic stream with no camera, with selectable test patterns
modalai-adsp v1.0.10 → v1.0.14 4 changes
  • Only toggle data lines on CDP ports when the HIGH-Z is enabled
  • Add extra protection to prevent a crash during UART reconfigurations
  • Raise USB-C connector RST/SHDN thresholds to 95/100 C
  • Add USB-C Connector shutdown / reset temp configs
modalai-adsp-vrx v1.0.0 → v1.0.2 3 changes
  • Set the usbc connector temp thresholds to 115/120
  • Only toggle data lines on CDP ports when the HIGH-Z is enabled
  • Add USB-C Connector shutdown / reset temp configs
modalai-slpi v1.2.4 → v1.2.5 1 change
  • Add extra protection to prevent a crash during UART reconfigurations
voxl-camera-server v2.2.43 → v2.2.44 20 changesSource CHANGELOG Diff
  • imx664 ClearHDR (en_hdr), processed on the GPU with tone mapping, AWB on the merged image, EIS support and a debug log; on by default for imx664-fpv
  • add imx664_v2 sensor drivers (normal and ClearHDR modes) for qrb5165 and qcs6490, installed by voxl-configure-cameras for all imx664 configs and the imx664 / imx412 slot probe
  • imx412 zzHDR and DOL-HDR (experimental): merge and tone mapping, runtime exposure ratio, optional denoise, flickering light correction
  • add highlight auto exposure (ae_mode highlight) with exposure / gain split; ae_mode auto runs it on imx412 / imx664 with misp and is the default for those sensors (imx412 was isp)
  • HDR and highlight AE: ae_desired_msv sets the output brightness, raised digital gain limits in dark scenes, sensor specific gain limits
  • normal debayer: luminance gamma (gamma_mode) as the new default, AWB ignores clipped pixels
  • remove the 0.0625 Y offset from the RGB to YUV conversion
  • qcs6490: raw frame stride adjustment and ClearHDR Bayer texture access on the GPU instead of a CPU copy
  • publish camera capabilities, ClearHDR gain_info and per-pipe gamma in the pipe info json, written from a separate thread; periodic updates behind en_pipe_info_updates (default off)
  • set the CPU affinity and RT priority before the camera module is loaded so the CAMX threads inherit them
  • load opencv_<camera>_intrinsics.yml first, then <camera>_intrinsics.yml
  • a negative max_request_queue_depth is replaced by 0 (not limited) with a warning
  • voxl-configure-cameras copies the platform’s default tuning file for every camera config, fix the qcs6490 default tuning file name, add latest default tuning files
  • m0197: add C46/C47 configs, rotate tracking_front instead of tracking_down on C46/C47
  • camera configs 48 and 63 are the Nyctis versions of 47 and 62, with rev A and M0197 variants
  • remove the defaults for system images 1.6.4 and older (IMX214DefaultsOld, IMX412DefaultsOld)
  • add a script to generate all default camera server configs, add hdr-dark-capture.sh
  • add boson v2 sensormodules with updated sensor timing (including readout time), voxl-configure-cameras uses them
  • fix 14 bit boson processing publishing the raw frame from the previous iteration
  • add voxl-boson-config tool
voxl-configurator v1.1.54 → v1.1.56 9 changesSource CHANGELOG Diff
  • modem 37 is the M0236 (was mislabeled M0198)
  • D0020 XSL (extras SL) loads the 3115 900kv ESC tune via voxl-esc setup_d0020_xsl_3115
  • Seeker camera menus: C48 (D0020 V6) and C63 (D0008 V6) are the Nyctis versions of C47 and C62
  • require baro temp cal on all qrb5165 (M0054/M0154) V6 seekers, not just D0020-4
  • voxl-configure-mpa loads every PX4 params helper (ghost, steam deck, pwm via elrs, msp_dp_osd, indoor_vio_missing_gps, zero_rf_missions, voxl2_io, test team tweaks) from the v1.18 params tree instead of v1.14
  • D0019 and D0020 V6 use the D0008_FPV_V6 extrinsics like D0008 V6, all V6 seekers share the chassis (was D0008_FPV_V5)
  • hardware sub-revision B for D0008, D0019 and D0020 V6 on M0197 (board code 9): the M0197 is mounted rolled 180 degrees vs V6 and V6A
  • voxl-configure-sku: the wizard offers B only on M0197, scripted -v 6B / -r B is rejected on other boards, families and versions
  • voxl-configure-mpa V6B: keeps the base camera config (no 62B), selects the shared rolled-board V6 extrinsics and warns when they are not installed, loads other_helpers/m0197_board_rotation.params after the platform params for SENS_BOARD_ROT 12 (needs voxl-px4-params 0.9.36 and the voxl-mpa-tools extrinsics)
voxl-cpu-monitor v0.7.7 → v0.7.8 8 changesSource CHANGELOG Diff
  • fix max cpu freq for small cores on qcs6490
  • disable systemd CPUAccounting which was disabling RT scheduling on ubun2.0 (gen1.5 vrx)
  • fix cpu frequency over-reporting when kernel throttles cpu before governor.
  • fix zombie processes being reported in top memory/cpu consumers after long uptimes
  • cpu_t_max in MPA topic now reports max temp instead of mean.
  • voxl-inspect-cpu computes its own mean from individual core temps now.
  • proper handling of old deprecated standby mode commands.
  • fix 1s delay coming out of pitmode on arm
voxl-elrs v1.2.3 → v1.3.30 78 changesSource CHANGELOG Diff
  • updating a Spire’s transmitter over adb works more than once a session: the reconnect after an update asked for a transmitter itself, so the Spire’s voxl-elrs opened its UART at the host’s receiver baud instead of the transmitter’s 921600. That garbled the port for voxl-rc-server too (its startup check failed every read for ~40 s, and stopping it for the next update waited that out), and the next update’s bootloader request went unanswered. The host now asks as the caller did on every connection, and the Spire keeps its transmitter’s baud whatever a host that lets it pick the role says
  • a port another process reads too (voxl-rc-server on a Spire’s transmitter UART) is no longer taken for unplugged when the other reader gets to the bytes first: a hang-up is told by the port itself (its ioctls fail with EIO), not by empty reads. The host also waits 2 s after an update before it reconnects, past voxl-rc-server’s startup check, which keeps a Spire on an older voxl-elrs from reading its port as unplugged then
  • over adb, an update shows its progress: the VOXL’s voxl-elrs reports the transfer and the services it stops and starts (voxl-rc-server on a Spire, voxl-px4 on a drone) while it runs, instead of the host showing “Enter the bootloader” until it is done. The VOXL needs this voxl-elrs for it; an older one updates as before
  • presets: the “Example configuration” preset is gone (it mapped channel 15 to all four output pins, and showed in the frontend’s preset list like a real one), and the Custom Domain preset says what it sets instead of “pass -T for the TX”, which neither the frontend nor a Spire needs
  • frontend: the Parameters page shows a device’s last parameter. It read the indexes below the count the device reports, but that count is the highest index, so “Reset to defaults” on 3.5.3.37 / 4.1.0.15 (and a receiver’s Bind State) was missing; libelrs’s sweep for parameters its folder walk misses had the same off-by-one
  • commands on a transmitter through EdgeTX serial passthrough (a Zorro Blue’s M0193) get their reply. The module only sends right after it receives a frame, so a command, sent once, timed out (“Command stopped: Connection timed out”, and Reset to defaults never asked to confirm). libelrs now pings a transmitter while it waits for a reply and re-sends a read only every 500 ms, which also stops a second read reply being taken for the next command’s
  • frontend: a finished command shows “Done” instead of “Command is active”, the page reads the parameters again, and the status line says what changed, e.g. “Unbind done: UID 44AD05BE674C -> 1A2B3C4D5E6F”
  • firmware catalog adds ELRS 3.5.3.37 and 4.1.0.15 (3.5.3.33 to 3.5.3.36 and 4.1.0.12 to 4.1.0.14 stay): the ModalAI receivers and transmitter get a “Reset to defaults” command, last in their parameters, that asks first (“Reset all but UID?”), puts every setting except the UID back to its default and reboots, so the link partner stays bound. A receiver’s reset turns its custom domain off, so it relinks only with a transmitter that has it off too, and a drone’s receiver loses its SKU presets until “Apply SKU defaults” or voxl-elrs configure. The CLI doesn’t run it, since it asks. 4.1.0.15’s transmitter Unbind runs on click like every other Unbind (it asked “Generate new UID?”), so voxl-elrs unbind works against it
  • frontend: Run on Unbind asks first, since the link drops until the devices are bound again; firmware that asks as well (a 4.1.0.14 or older transmitter) is answered from that dialog. After Reset to defaults the Parameters page says the device rebooted and reads every parameter again once it is back, instead of “Command stopped” and the old values
  • frontend: the presets move off the Parameters page into a Presets window opened from the page’s header, so the parameter list (Bind and Unbind first) stays as the firmware has it. The window puts the SKU defaults and the presets made for the SKU first and the rest under “Other presets”; the presets that make up the SKU defaults are named under them instead of listed again. Selecting a preset shows each setting it would change, now and after, before Apply. The separate “Reset to firmware defaults” button is gone: a firmware “Reset to defaults” command shows in the parameter list like any other command
  • libelrs: elrs_preview_preset_for_params() reports what one preset, or the SKU defaults, would change against parameters already read, without reading or writing the device
  • updating a drone’s receiver over adb (the frontend, or voxl-elrs -p adb:SERIAL) works: the VOXL’s voxl-elrs stops voxl-px4, updates the receiver over the SLPI UART and starts voxl-px4 again, as an update run on the VOXL does. It used to try the UART with voxl-px4 still holding it, fail with an I/O error and leave the session with no device. The host carries on with a fresh session after each update, since the DSP reset that restarts voxl-px4 cuts the old one off. The VOXL needs this voxl-elrs too
  • frontend: the Parameters page lists the presets that fit the connected device, each checked against it without writing (“Applied”, or how many settings it would change), with a Load button; over adb it shows the VOXL’s SKU and tags the presets for it, and “Apply SKU defaults” loads those as voxl-elrs configure does, without a firmware update; “Reset to firmware defaults” appears for firmware with a “Reset to defaults” command
  • libelrs: elrs_check_presets() and elrs_check_presets_for_params() check every preset against the device with one parameter read, elrs_apply_sku_defaults() applies a SKU’s merged presets, and log_get_level() reads the log level
  • firmware catalog adds ELRS 3.5.3.36 and 4.1.0.14 (3.5.3.33 to 3.5.3.35, 4.1.0.12 and 4.1.0.13 stay): a 3.5.3.36 receiver or transmitter whose settings reset to defaults gets a custom domain of 863-983 MHz with 80 channels, still disabled, as on 4.x and in the “Custom Domain” preset, instead of copying its regulatory domain (904-927 MHz, 40 channels); settings already stored keep their values, and it still links with 3.5.3.x on either end; 4.1.0.14 behaves as 4.1.0.13 (its parameters share those defaults with the configuration code)
  • Spire (MVX-S SKUs): voxl-elrs finds its M0193 transmitter from /data/modalai/sku.txt, so it needs no -p and no -T: MVX-S0001-7 is on /dev/ttyHS1 and MVX-S0001-9 on /dev/ttyHS6, and -p naming that UART implies -T; another MVX-S SKU asks for -p, and every other SKU (drones, with an M0193 receiver too) keeps the receiver path; ping shows the port it used
  • update and fw flash on a serial port stop the system services holding it (voxl-rc-server on a Spire) and start them again afterwards, and touch nothing when nothing else holds it; another kind of holder is named and the update refused
  • an update stops voxl-px4 only when it reaches the device through voxl-px4 (crsf_raw or the SLPI UART)
  • a second voxl-elrs on a serial port is turned away (“/dev/ttyHS6 is in use by voxl-elrs (pid N)”) instead of the two taking each other’s replies until both read the port as unplugged; voxl-rc-server, which only writes, still shares it
  • frontend over adb: a Spire’s voxl-elrs tells the frontend it has a transmitter, so the frontend talks to its M0193, updates it with the TX image and stops voxl-rc-server for the update; the port list names a Spire after its SKU, and the Update page notes that updating a transmitter drops its link. The Spire needs this voxl-elrs too: an older one is handled as before
  • param set takes an option’s text before reading a number as its index: param set “Max Power” 500 picks 500 instead of failing
  • an unplugged serial port reports -ENODEV on the first ping even when the ping’s write fails first, so the frontend disconnects at once instead of after three missed heartbeats (test_unplugged_port failed about one run in three)
  • frontend AppImage: the titlebar shows the desktop’s buttons (minimize and maximize on Ubuntu, where only close showed): desktop settings now come through the settings portal, since the bundled GSettings schemas lack distro defaults
  • frontend AppImage: GNOME’s dock shows the VOXL ELRS icon instead of a generic one; each launch registers ~/.local/share/applications/com.modalai.VoxlElrs.desktop and the icon, which also lists VOXL ELRS in the app grid, starts the AppImage last launched, and hides once that file is deleted
  • with voxl-px4 stopped, libelrs processes share the receiver through voxl-elrs-bridge instead of the first one to open qup7 keeping it until it exits (a voxl-portal page load locked voxl-elrs out that way): auto starts the bridge, which holds qup7 and serves the crsf_raw pipe as px4 does, and exits 30 s after its last client; voxl-px4’s drop-in stops the bridge before px4 starts and resets the DSP if libelrs used it, so px4 still comes up with crsf_rc
  • a process that auto connected to px4’s crsf_raw starts the bridge when px4 stops under it, so an open voxl-portal ELRS page reaches the receiver again about 6 s after px4 stops instead of failing until portal goes idle
  • -p qup7 and monitor name the process holding the UART when they can’t open it (“qup7 is held by pid 1234 (voxl-elrs bridge, voxl-elrs-bridge.service)”); update and fw flash stop the bridge and keep it from restarting until they finish
  • with px4 stopped and the bridge running, mpa:crsf_raw clients (voxl-mavlink-server, voxl-io-server) get RC from the receiver
  • an unplugged serial port is reported as such: once the reader sees the port go away (unplugged or powered off), requests return -ENODEV at once instead of waiting out their timeout
  • frontend: unplugging the connected device disconnects, as Disconnect does, with “Disconnected: the device was unplugged”, so the port list is free for the next device instead of staying locked at “Connection lost”; the Update page’s last result (“Firmware update complete”) clears on disconnect
  • frontend: the Update page offers upgrades on the installed major only, as voxl-elrs update does: ELRS 3.x and 4.x do not link with each other, so a transmitter on 3.5.3.35 no longer reads “Out of date” or lists 4.1.0.13 as an upgrade, and the update dialog on connect is gone; Show all versions lists every release, newest first, and installing another major warns that it won’t link with the other one
  • frontend: the connection status names the port as the port list does (Zorro Blue) instead of its /dev/serial/by-id path, the PWM page is hidden while a transmitter is connected, and the update progress shows above the release list
  • firmware catalog drops ELRS 3.5.3.32 (3.5.3.33 to 3.5.3.35, 4.1.0.12 and 4.1.0.13 stay)
  • firmware catalog adds ELRS 3.5.3.35 (3.5.3.32 to 3.5.3.34 stay): the M0193 transmitter’s UID can be written, as on 4.1.0.13, as 12 hex digits that apply at once and are saved; receivers are unchanged from 3.5.3.34, and it still links with 3.5.3.x
  • frontend: the Parameters page (was Settings) edits a writable UID as hex, written on Enter or Apply instead of after each pause in typing, with a Bind phrase popover that shows the UID before writing it; a read-only UID is text to copy, and a device that keeps its old UID is reported
  • frontend: the port list names each device from its USB product string (Zorro Blue, VOXL 2, CH340 USB serial) with its device node and USB IDs underneath, lists radios and flight controllers first, keeps the selected port when it refreshes, selects the port last connected to at the next start, and sets the host mode for the device: EdgeTX, Betaflight or Direct
  • add voxl-elrs bind-state, which prints the receiver’s Bind State (Bound, Unbound or Binding): a receiver in bind mode sends no RC and no link statistics, the same as one whose transmitter is off; needs a receiver on ELRS 3.5.3.34 or 4.1.0.13, older firmware is reported as not having the parameter
  • firmware catalog adds ELRS 3.5.3.34 and 4.1.0.13 (3.5.3.32, 3.5.3.33 and 4.1.0.12 stay); receivers on both report a read-only Bind State parameter (Bound, Unbound or Binding): 3.5.3.34: settings changed from the Lua script no longer drop the link or desync hopping, M0193 transmitters no longer slip on rate changes or lose the receiver for ~3 s on a change into 50 Hz, telemetry ratio 1:2 works with M0184/M0193 receivers, and a UID written to a receiver applies without a reboot; it still links with 3.5.3.x on either end 4.1.0.13: M0193 transmitters in Gemini mode no longer hang after a telemetry ratio change or keep reporting a link while the receiver scans after an outage, and the transmitter UID can be edited from the Lua script
  • stock ExpressLRS firmware versions are read correctly: stock firmware packs only major.minor.patch into the device info firmware ID (3.3.0 is 0x00030300), which read as 0.3.3.0, so update found no 0.x firmware for a stock receiver, skipped the 3.x the catalog has and suggested --allow-major (4.x, which loses the link to a 3.x transmitter); ping also prints the decoded version
  • frontend for Windows: every release tag also builds voxl-elrs-<version>-windows-x86_64.zip (MinGW-w64 cross build on Fedora); serial devices appear as COM ports labelled with their USB product name, so a Zorro Blue still gets Recover Zorro TX; EdgeTX and Betaflight passthrough and XMODEM updates work, with the bundled firmware and HTTPS through a packaged CA bundle; no ADB backend (no VOXL connections) and no ESPTool
  • serial port I/O sits behind a platform layer: termios on Linux, as before, and overlapped COM port I/O on Windows; a write the port stops accepting now times out after 2 s instead of failing on the first EAGAIN
  • the AppImage and the Windows zip of a release tag are kept instead of expiring after a month, so download links stay valid
  • frontend: Recover Zorro TX, for a Zorro Blue whose internal M0193 TX was left with a half-written image by an interrupted update: after EdgeTX holds the TX in its bootloader (MDL held at power-on, needs EdgeTX with that bootloader hook), the button opens EdgeTX passthrough without identifying the TX and the Update page installs to MODALAI_M0193_TX; shown only for a Zorro Blue port
  • an update that loses its device (USB unplugged, handset powered off) ends at once with “No such device” instead of reading the hung-up port forever at full CPU, which also kept the frontend’s update lock; nor is a device that is gone retried
  • XMODEM uses CRC mode when the bootloader NAKs stray bytes before asking with ‘C’, instead of switching to checksum mode and having every block rejected (seen when a retried update found the bootloader already waiting)
  • update picks the transmitter image on a transmitter: without --target it treated every M0193 as a receiver, so -T update (or -E update) on an M0193 TX flashed the M0193 RX image; the role now comes from -T/-E as it does for fw flash
  • an explicit -b is kept when a TX target selects TX mode, so update --target MODALAI_M0193_TX -b 420000 --boot-baud 921600 can put the TX image back on an M0193 that runs RX firmware
  • firmware catalog adds ELRS 4.1.0.12 and drops 4.1.0.11 (3.5.3.32 and 3.5.3.33 stay): M0193 transmitters on 4.x ignored the reboot-to-bootloader command, so update and fw flash timed out on “bootloader prompt not detected” (“Connection timed out” in the frontend) and a 4.x transmitter could not be updated or downgraded; 4.1.0.12 transmitters take the command again; a transmitter still on 4.1.0.11 or older ignores it, so its first update to 4.1.0.12 takes SWD or the MSP UID-write reboot; receivers are unchanged and a 4.1.0.11 receiver updates in place (settings and binding kept)
  • the x86_64 AppImage of the frontend builds in CI again (it failed on the v1.2.3, sdk-1.8.0-2 and v1.3.9 tags): the AppImage runtime is pinned to a dated type2-runtime release instead of the “continuous” one, whose asset was replaced (404), and GTK 4.10.5 builds on GitLab’s shared runners, which answer close_range() with EPERM and made GLib’s spawn fail
  • add voxl-elrs pwm pin <pin> <us>…, which holds receiver pins at a raw pulse width (800-2200 us) until Ctrl-C or --for <seconds>, with or without an RC link the value bypasses the pin’s input channel, map and inversion, and other pins on the same channel don’t move; the pins are released on exit, and the receiver lets go of a pin 1 s after the last command; the receiver confirms every command, so firmware without it is reported as too old, pins that require arming are reported as holding their failsafe until ‘pwm arm’, and DShot, serial and I2C pins are refused; needs ELRS 3.5.3.33 or 4.1.0.10
  • firmware catalog adds ELRS 3.5.3.33 and 4.1.0.10 (3.5.3.32 and 4.1.0.9 stay): the pin output command behind pwm pin, M0184/M0193 On/Off pins switch again on 4.x, 10kHz Duty pins pulse on 3.x, and a pin switched from On/Off to a PWM rate pulses without a reboot
  • parameter writes read the value back up to three times, 100 ms apart, before failing, so configure through voxl-px4 no longer stops on “write verification failed” for a value that was written
  • firmware catalog is now ELRS 3.5.3.32 and 4.1.0.9 only (3.5.3.26-3.5.3.31 and 4.1.0.6-4.1.0.8 removed; ‘fw flash <file>’ still flashes an older image): M0184/M0193 receivers hold all four PWM pins low (No Pulses) until a preset or parameter configures them, instead of driving 1312 us (3.x) or 1824 us (4.x) from boot, which lit the Seeker light bars, updating a receiver to either version resets its settings and binding to defaults (configure reapplies the presets; bind again afterwards), and 3.5.3.32 receivers rescan rates after a disconnect instead of staying locked to their first rate
  • firmware catalog adds ELRS 4.1.0.8 (installed by update/configure only from 4.x, or with --allow-major): rate changes re-link in 0.1-1 s instead of 1-13 s, receivers rescan rates after a disconnect instead of staying locked to their first rate, and the M0193 transmitter resumes at once after a handset CRSF dropout
  • firmware updates recover instead of leaving the receiver or voxl-px4 broken: when the SLPI UART cannot be opened (DSP not ready yet: “Encountered error while initializing bus 17”), the command starts again in a fresh process, once a failed XMODEM transfer is retried twice; it leaves the receiver in its bootloader, which takes the next attempt after an update, voxl-px4 must recreate the crsf_raw pipe; if it does not, voxl-elrs resets the DSP and starts voxl-px4 again, and reports an error if that fails too
  • voxl-elrs records the version it flashed per target in /data/modalai/voxl-elrs/flashed; update --target on a device that does not answer stays on that major instead of falling back to 3.x
  • test hooks for the recovery paths: ELRS_TEST_FAIL_SLPI_OPEN=1 and ELRS_TEST_XMODEM_ABORT_AT=<blocks> (each fires once)
  • add voxl-elrs pwm write <channel> <value>…, which holds RC channels at a value until Ctrl-C or --for <seconds>, with or without an RC link the pins mapped to those channels follow through their maps; values are microseconds (880-2120) or percentages, e.g. pwm write 5 1900 --for 10 it resends the override every 100 ms because the receiver drops it after 1 s, and it goes through voxl-px4’s crsf_raw pipe, so voxl-px4 keeps running needs ModalAI receiver firmware (3.5.3.31 and 4.x take the override); an RC link that is up writes the same channels
  • update and configure stay on the major version the device runs: 3.x moves to the newest 3.x, never to 4.x, because a 4.x receiver does not link with a 3.x transmitter update --allow-major or configure --allow-major moves to a newer major; allow_major_update=true in /etc/modalai/voxl-elrs.conf allows it for every update a device already on 4.x keeps getting 4.x updates, and update says when a newer major is available and how to move to it
  • update says which version the device runs when there is nothing to do, and whether that is the newest local firmware or newer than anything in the catalog
  • fw flash writes ESP receivers at 921600 over SLPI: esptool syncs at 115200 and switches once its stub runs, taking a BetaFPV Nano 900 RX from ~2.5 min to ~45 s needs voxl-esptool 0.2.3, now the recommended version, which returns to 115200 before starting the new firmware
  • esptool progress shows live during fw flash instead of arriving all at once when it finishes
  • the “Received N bytes of data from SLPI while SLPI uart not in use” lines no longer flood the fw flash output
  • param list drops the banners and the root folder row, and ends with one line, e.g. “BFPV Nano 900RX: 16 parameters (hash 0x199e7187)”
  • group the commands under param, config, preset, pwm and fw; the old names still work as hidden aliases voxl-elrs help <command> or <command> --help explains a command, and typos get a suggestion
  • param get/set take a name or path, e.g. output-mapping/pin-1/map-mode, and param set takes selection options as text
  • config load and preset load print every change and take --dry-run; preset load takes several presets
  • presets are addressed by id (file name), name or path, and preset list shows which ones configure applies for the SKU
  • configure takes the SKU as an argument and --no-update replaces configure-sku
  • fw flash takes a catalog version, e.g. fw flash 3.5.3.30, or a file
  • exec <name> runs a receiver command parameter; an unknown command no longer enumerates the receiver before failing
  • tab completion comes from the binary and completes parameter paths, presets, firmware versions, targets and ports with nothing cached, the first Tab reads the parameter names through voxl-px4’s crsf_raw pipe
  • every command exits 0 or 1; failsafe exits 0, 1 in failsafe, 2 on error
  • merge the T7 and T8/T10 team race reset presets into reset_teamrace
  • log the per-command parameter count and serial open/close at DEBUG
  • add voxl-elrs monitor, which prints a timestamped line for each receiver reboot, RC gap and ping silence until Ctrl-C reboots come from the boot announcement ModalAI receivers send unprompted: 3.5.3.24+ on every receiver, 4.x on M0184/M0193 only it needs the receiver UART, so stop voxl-px4 first and run voxl-reset-slpi -t 8000 before starting it again
  • monitor --frames also logs the type, length and addresses of every frame received, RC and link statistics included
  • auto fails straight away when voxl-px4 runs with an RC mode other than CRSF_RAW, instead of timing out on the crsf_raw pipe
voxl-esc v1.6.5 → v1.6.6 1 changeSource CHANGELOG Diff
  • add d0020_xsl_3115 motor tune
voxl-esptool v0.2.2 → v0.2.3 3 changes
  • fail the SYNC wait after a few seconds when only non-bootloader data arrives (a receiver still running its firmware streams CRSF), instead of discarding it until the caller’s 300 s timeout
  • write to SLPI UARTs in 768-byte chunks instead of 64: each write is one DSP message and the DSP UART write blocks for about twice the transmit time, so a BetaFPV Nano 900 RX flash went from 105 s to 75 s at 115200 (12 s at 921600)
  • return the ESP8266 stub to 115200 before --after soft_reset runs the new firmware: after a write at a higher baud, ELRS 3.x hung with its LED dark until power-cycled
voxl-fpv-px4 v1.18.0-8.0.25 → v1.18.0-8.0.29 7 changes
  • Do not call voxl-reset-slpi after px4 reset on qcs6490 to avoid reset loop
  • Never block arming on magnetomoter failures
  • Stream STATUSTEXT on onboard links
  • Fixed missing actuator function assignment in voxl_esc driver
  • Updated GPS drivers for latest Teseo LIV4 support
  • Add cmdcounter and address fields back into the ESC log message
  • uxrce_dds_client: expose telemetry for DDS flight-control utilities
voxl-osd v1.2.1 → v1.3.2 3 changesSource CHANGELOG Diff
  • Show vtx hopping frequencies in OSD Menu
  • Update vtx_data to include camera_latency field
  • Add a radio menu to VTX and VRX OSD menus
voxl-portal v0.9.16 → v0.9.17 5 changesSource CHANGELOG Diff
  • camera server config editor page in camera multi-view, with a server log panel, load from a local file (open button or drag and drop), save locally, and raw text editing of broken json with the error highlighted
  • camera view: AE control buttons, HDR on / off button, save bayer frame button, HDR debug info, playback seek only in playback mode
  • multi-view: default downscale width 1280 px (was 320), config editor and server log split instead of overlaid
  • main menu always renders on top
  • fix DOM XSS in page rendering, guard string-keyed lookups against prototype keys, resolve semgrep and lint findings (Defect Dojo)
voxl-px4 v1.18.0-1.0.9 → v1.18.0-1.0.13 4 changesSource CHANGELOG Diff
  • Fixed missing actuator function assignment in voxl_esc driver
  • Bring the Teseo gps detection logic and BMM150 driver + board detection logic over from FPV build
  • Added cmdcount and address to ESC debug logging and enabled in default log profile
  • Moved to the ModalAI fork GPS drivers with latest Teseo support for LIV3 and LIV4
voxl-px4-params v0.9.35 → v0.9.38 4 changesSource CHANGELOG Diff
  • v1.18 fpv_helpers/enable_turtle_mode.params (all D0008 variants): VOXL_ESC_T_ON 9 -> 7, joystick turtle button on the Zorro’s ch10 like ELRS turtle mode (RC_MAP_AUX1 10); button 9 is a ch11 camera switch position, so switching cameras over IP (Silvus) turned turtle mode on
  • rename v1.18 fpv_helpers/seeker_v6b_m0197_board_rotation.params to other_helpers/m0197_board_rotation.params, voxl-configurator 1.1.55 loads the new name
  • m0197_board_rotation.params header describes the side roll (USB-C port moves to the other side of the drone) and that voxl-configurator loads it on Seeker V6B SKUs
  • v1.18 fpv_helpers/seeker_v6b_m0197_board_rotation.params: SENS_BOARD_ROT 12 for Seeker V6B (M0197 rolled 180 relative to V6), loaded by voxl-configurator 1.1.55 after the platform params
voxl-vtx v3.3.4 → v3.9.0 33 changes
  • VRX: recordings are pilot view (video + OSD), raw video as fallback
  • Gen1.5 VRX: pilot view recording and streaming support (needs libvoxl-codec 0.1.7)
  • Fix VRX crash when starting a recording on a read-only or pulled USB stick, and recordings after the first stopping right away
  • Add OSD toasts for USB recording failures (REC FAILED: USB ERROR, REC STOPPED: USB REMOVED, REC STOPPED: DISK FULL)
  • Gen1.5 VRX: fix display output after another application used the display
  • VRX pilot view: records and re-streams (RTSP/MPEG-TS) what the pilot sees (video + OSD) on vrx_pilot_encoded pipe, with or without a display
  • Take back interrupt signals from Qt for cleaner shutdown
  • OSD: weak-link edge glow, restyled AI detection boxes with fade and smooth tracking, OSD render rate increased to 60Hz
  • VRX width_scan param (default on) to turn off the stream-loss width scan
  • OSD: SNR shows – and the VTX bars are grey stubs while no video stream is arriving
  • Smoother channel-width changes; adaptive link can step down to 10 MHz with a VRX that supports 5/10 MHz
  • More accurate voxl-inspect-vrx
  • More robust in-process recovery when radios dropout
  • Fix Lepton decoding bug: Use CPU copy on QCS6490 when decoded frame stride does not match width
  • VRX switches between 5 and 10 MHz directly (needs the SDK 1.8.1 VRX system image)
  • Improved forward error correction defaults
  • voxl-inspect-vtx fec(ms) column now shows the error correction time per frame
  • Faster forward error correction encoding, lowering VTX CPU use
  • voxl-vtx and voxl-vrx flush stdout per line, so adaptive-link level changes reach the journal when they happen
  • Fix VTX latency readings on frames recovered by error correction
  • Initial working version of frequency hopping
  • Add OSD indication for frequency hopping
  • Add support for 5/10MHz bandwidth on M0185
  • Add camera_latency to vtx inspect tool
  • Add total_latency to vrx inspect tool
  • RC controls (rc_toggle stream switching, zoom_ch, invert_toggle, osd_rc_toggle and the ch7 LED status) read voxl-mavlink-server’s rc_active mux while it publishes, so a GCS joystick over IP drives them on the same channels as RF; setups without the mux keep using the autopilot’s RC_CHANNELS
  • remove the MANUAL_CONTROL joystick button settings (per-profile joystick_toggle, zoom_joystick_buttons, osd_joystick_toggle, led_joystick_button_off/ir), stale keys are dropped from voxl-vtx.conf; ch11 stream switching and ch12 zoom over IP need voxl-mavlink-server >= 1.4.23
  • ch7 LED status splits the channel into thirds (off below 1333 us, overt, IR above 1667 us) so a slightly off-center middle position no longer reads as IR
  • voxl-configure-vtx: rc_toggle defaults to 11 (the ch11 camera switch on the ModalAI TX presets), so radio presets (silvus, dtc, fiber, …) and plain factory setups switch cameras on ch11 like the seeker SKU setups; set -1 to disable.
  • Add a radio menu to VTX and VRX OSD menus
  • More reliable encrypted link start-up in weak signal
  • Fix lost packet counting
  • Update for new prod procedures

SDK 1.8.0 Support Matrix

PlatformPCB TargetsSupport Status
VOXL 2M0054-1, M0054-2, M0154-1, M0154-2Yes
VOXL 2 MiniM0104-1, M0204-1Yes
MVX-T0001M0204-1Yes
MVX-R0001M0205-1, M0206-1Yes
QCS6490M0197Yes

SDK 1.8.0 System Images

See the system image release notes for VOXL 2 and VOXL 2 Mini and the VRX.

PlatformSystem image
VOXL 21.8.09
VOXL 2 Mini1.8.09
VRX (ubun2.0-multi)2.0.2-perf-20261004
QCS6490v0.3.4

SDK 1.8.0 MD5 Hashes

SDKHash
voxl2_SDK_1.8.0.tar.gz7c83184458a3d4c89cf153fc8231f712
voxl2-mini_SDK_1.8.0.tar.gz1d487cea9c66d2f1ade4a394caee478d
ubun2.0-multi_SDK_1.8.0.tar.gz3b8eaeb1e61610402ef86562698f65e7
qcs6490_SDK_1.8.0.tar.gzdf4166c97c8bdb2bebedeb91e9326ec3

SDK 1.8.0 Package List

Release date: October 12, 2026

Meta-package: voxl-suite sdk-1.8.0 tag on GitLab, the exact package set pinned for this release.

Changes from SDK 1.6.8:

PackageSDK 1.6.8SDK 1.8.0 
libmodal-cvv0.6.1v0.6.2Changes
libmodal-flowv1.0.5v1.0.10Changes
libmodal-journalv0.2.7v0.2.8Changes · Diff
libmodal-pipev2.14.12v2.15.1Changes · Diff
libvoxl-cci-directv0.4.0v0.4.1Changes · Diff
libvoxl-codecv0.1.1v0.1.5Changes · Diff
modalai-adspv1.0.8v1.0.10Changes
modalai-slpiv1.2.3v1.2.4Changes
qrb5165-dfs-serverv0.2.0v0.3.0Changes · Diff
qrb5165-rangefinder-serverv0.1.6v0.1.7Changes · Diff
qrb5165-tflitev2.17.2v2.17.4Changes
voxl-camera-calibrationv0.6.2v0.6.3Changes · Diff
voxl-camera-serverv2.2.29v2.2.43Changes · Diff
voxl-configuratorv1.1.35v1.1.54Changes · Diff
voxl-elrsv1.1.7v1.2.3Changes · Diff
voxl-escv1.6.3v1.6.5Changes · Diff
voxl-esptoolv0.2.1v0.2.2Changes
voxl-focus-camerav0.6.2v0.6.3Changes
voxl-fpv-px4v1.14.0-8.148.0v1.18.0-8.0.25Changes
voxl-imu-serverv2.0.2v2.0.6Changes · Diff
voxl-io-serverv0.1.3v0.1.6Changes
voxl-lepton-serverv1.4.1v1.4.2Changes · Diff
voxl-loggerv0.6.3v0.6.9Changes · Diff
voxl-mavcam-managerv0.6.1v0.6.2Changes · Diff
voxl-mavlink-serverv1.4.16v1.4.20Changes · Diff
voxl-modemv1.2.5v1.2.6Changes · Diff
voxl-mpa-toolsv1.5.8v1.5.10Changes · Diff
voxl-open-vins-serverv0.6.2v0.7.8Changes · Diff
voxl-osdv0.4.12v1.2.1Changes · Diff
voxl-portalv0.9.4v0.9.16Changes · Diff
voxl-px4v1.14.0-2.0.142v1.18.0-1.0.9Changes · Diff
voxl-px4-paramsv0.9.15v0.9.35Changes · Diff
voxl-rc-serverv0.0.5v0.0.10Changes · Diff
voxl-remote-idv0.0.9v0.1.0Changes · Diff
voxl-state-estimatorv0.0.6v0.0.7Changes
voxl-utilsv2.0.5v2.0.10Changes · Diff
voxl-uvc-serverv0.1.8v0.1.9Changes · Diff
voxl-vision-hubv1.9.21v1.10.3Changes · Diff
voxl-vtxv2.2.42v3.3.4Changes
libvoxl-qtNewv6.5.3-r1 
voxl-aprilgrid-camera-calibrationNewv1.2.0 
voxl-bf-osd-fontNewv1.0.0 
voxl-portal-web-libsNewv1.0.0 
voxl-quectel-cmNewv1.0.0 
voxl-wireguardNewv1.0.1 
qrb5165-mini-tof-serverv0.2.2Removed 
libmodal-exposurev0.1.5Removed 

SDK 1.8.0 Full Changelog (from SDK 1.6.8)

libmodal-cv v0.6.1 → v0.6.2 2 changes
  • support fisheye calibrations in stereo rectification, both the CVP grid and CPU map paths previously applied the pinhole model to fisheye coefficients
  • accept “equidistant” as an alias for “fisheye” in mono and stereo distortion_model fields
libmodal-flow v1.0.5 → v1.0.10 11 changes
  • Add optional strided exclusion masks for detection, temporal tracking and stereo matching.
  • Validate mask geometry, preserve feature/descriptor alignment and update the public input ABI.
  • version stamp: pkg/control Version is the single source; cmake generates + installs modal_flow/Version.hpp (MODAL_FLOW_VERSION_STR, C-linkage modal_flow_runtime_version(), modal_flow::version_matches()) so consumers can refuse to run against a .so other than the release they compiled with – the public headers carry ManagerCL/StereoMatcherCL layouts (ABI)
  • stereo matcher: cold-sweep sample count derived from the z band (2.5 px disparity per sample, pow2 8..128; 0.1-100 m still 128, z_min 0.3 -> 64), scalar sliding-window ZNCC inner loop (2 texture reads/pixel, identical accept sets, 1.6x cold / 2x rematch), fused reverse pass (reverse kernel undistorts the forward match on the GPU – one host sync per call; two-sync legacy path removed), optional local reverse window (set_reverse_window_px), non-blocking readbacks
  • ManagerCL::set_queue_profiling(bool) (before add_camera) turns on CL event profiling so kernel-time accessors report; the benches use it
  • examples/modal-flow-stereo-sweep: cost/agreement sweep over z band, band, sample step and reverse window on logged frame pairs
  • stereo: perpendicular-band ZNCC tuning + offline stereo tooling merged from stereo-exp
  • stereo: source/target StereoMatchInput/Result field names, with legacy left/right reference aliases for pre-rename callers
  • ocl manager: immortal heap singleton – exit-order clRelease segfault in libgsl fixed (explicit shutdown() unchanged)
  • Fix critical and high severity warnings reported in defect dojo
  • Add ZNCC epipolar-band stereo matcher (match_stereo / StereoMatcherCL)
libmodal-journal v0.2.7 → v0.2.8 3 changesSource CHANGELOG Diff
  • fix the destructor sometimes blocking for 1 s at exit (lost wakeup of the scan thread)
  • time the scan interval on the monotonic clock
  • don’t join the scan thread when it was never started
libmodal-pipe v2.14.12 → v2.15.1 4 changesSource CHANGELOG Diff
  • VFC altitude flow submode shows as “3D HOLD (THERMAL FLOW)” on the OSD
  • add px4_vehicle_attitude_t interface
  • add vtx_state_t interface
  • fix warnings
libvoxl-cci-direct v0.4.0 → v0.4.1 3 changesSource CHANGELOG Diff
  • qcs6490: discover camera sensor subdevs by scanning sysfs for cam-sensor-driver nodes and sorting by kernel-reported slot id, instead of assuming subdev numbering (enumeration order is not consistent on qcs6490)
  • qcs6490: finding zero probed sensors is no longer a fatal init error since sensors are only probed by the camera stack once a camera opens. init re-scans on subsequent calls until probed sensors appear
  • make voxl_cci_init thread safe
libvoxl-codec v0.1.1 → v0.1.5 7 changesSource CHANGELOG Diff
  • Get rid of strcpy calls to fix potential security issues
  • [ROI] Remove the tier-2 QP-bias-budget rate controller: the FW clamps realized per-LCU deltas to ~±5, so the map is now static (offsets applied as configured)
  • [ROI] Simplify the user knobs: drop roi_floor and the budget controls; the only strength knobs are the ROI/periphery QP offsets in [-5,0] and [0,+5]
  • [ROI] Drop the base-QP NALU-stream readback (only fed the removed controller)
  • [ROI] Handle runtime fps and # of p frame changes to maintain bitrate
  • [OMX] Add support for ROI control mode
  • [OMX] Fix FPS Hack workaround and fix CBR mode
modalai-adsp v1.0.8 → v1.0.10 2 changes
  • Disable options that override UsbPhy driver
  • Increase flight controller UART RX buffer size from 512 to 2048
modalai-slpi v1.2.3 → v1.2.4 1 change
  • Added i2c bus uninitialization to slpi_link
qrb5165-dfs-server v0.2.0 → v0.3.0 5 changesSource CHANGELOG Diff
  • support two independent hardware-synced RAW8 input pipes per pair (e.g. dual AR0144) with timestamp-based frame pairing, enabled with the new input_pipe_right and sync_tolerance_ns config options
  • independent pipe mode locates calibration automatically: per-camera intrinsics resolved from the pipe names (tracking_left_misp_norm -> opencv_tracking_left_intrinsics.yml) and camera-to- camera extrinsics chained from /etc/modalai/extrinsics.conf via libvoxl_common_config, new dependency on voxl-mpa-tools
  • remove dead occlusion buffer work, the DFS calls never populated it and nothing consumed the result
  • link modal libs by name so both /usr/lib64 and /usr/lib layouts work
  • fix pipe name trimming for paths with trailing slashes and full /run/mpa paths which previously kept a leading slash
qrb5165-rangefinder-server v0.1.6 → v0.1.7 1 changeSource CHANGELOG Diff
  • change comp id in outoing distance sensor mavlink message
qrb5165-tflite v2.17.2 → v2.17.4 3 changesSource
  • set CMAKE_POLICY_VERSION_MINIMUM=3.5 so fetched deps configure under CMake 4 (voxl-cross 4.9)
  • disable qcs6490 build in ci
  • enable qcs6490 build
voxl-camera-calibration v0.6.2 → v0.6.3 1 changeSource CHANGELOG Diff
  • shift target boxes for D0008 V6 Stereo Tracking cameras to avoid gimbal occlusion
voxl-camera-server v2.2.29 → v2.2.43 24 changesSource CHANGELOG Diff
  • misp debayer accounts for imx412 en_rotate, fixes cyan colors on flipped imx412 with the generated config
  • qcs6490: apply imx412 cci settings (en_rotate) before stream start, on init and on re-init, fixes the stale band at the top of flipped frames
  • qcs6490 imx412-fpv-v2 sensormodules only expose 1936x1080 30/60fps to work around camx mode selection on M0197
  • add imx412-fpv-v2 sensormodules for qcs6490
  • qcs6490 (M0197) hires configs use imx664-or-imx412, Seeker V6 configs 60-62 flip the imx412
  • add imx664-or-imx412 sensor type: voxl-configure-cameras probes the slot and sets up imx664-fpv or imx412-fpv-v2, with an optional _ROTATE_IMX412 override
  • Seeker V5+ and V6 hires configs (46-51, 60-64) and Stinger configs (33-35) use imx664-or- imx412
  • new _ROTATE_IMX412_V6 override applies only when the SKU hardware version is V6, Seeker configs shared by V5 and V6 (46-51) flip the forward imx412 on V6 only, V6-only configs (46A, 47A, 60-64) always flip it
  • rename those config files to say “IMX664 or IMX412”
  • add imx412-fpv-v2 sensor modules for qrb5165, C36 and C37 now use imx412-fpv-v2
  • install chi-cdk sensor modules per platform from chi-cdk/<board>/
  • nyctis640: support Y16 frames with min/max normalization to 8-bit, publish raw stream as RAW16
  • print-camera-configs hides lettered sub-revision configs (46A, 47A, 60A, 61A, 62A) from the menu, they are selected through the SKU hardware sub-revision instead
  • 46A/47A: forward tracking camera rotated 180 degrees, downward tracking camera uses the rotated sensor type (90 degree encoded stream rotation) to match rev A mounting
  • add rev A camera configs 46A, 47A, 60A, 61A, 62A for VOXL 2 platform_config_1: hires IMX664 on J8 upper instead of J7 lower (60A identical to 60)
  • voxl-configure-cameras accepts config ids with a sub-revision letter (e.g. 61A), falls back to the base config if no lettered file exists
  • allow mono cameras to share exposure
  • sync exposure on D0008 V6 stereo tracking cams C61 and C62
  • add script to generate html showing all cam config options
  • add nyctis640 support
  • add option for independent zomm / drag control to misp channels
  • version bump for libvoxl-codec ROI feature set framerate changes
  • version bump to ensure libvoxl-codec changes are pulled in
  • remove libmodal_exposure dependency from dpkg control file
voxl-configurator v1.1.35 → v1.1.54 31 changesSource CHANGELOG Diff
  • Seeker (D0008, D0019, D0020) and Stinger camera config menu text says “IMX664 or IMX412” to match the hires autodetect in voxl-camera-server 2.2.39
  • D0008 V6 selects the d8v6 open-vins preset on QRB5165 and d8v6m on M0197/QCS6490 (needs the voxl-open-vins-server with the d8v6m preset)
  • modem 33 (Silvus): D0008/D0019/D0020 set up voxl-vtx, voxl-osd, voxl-static-ip-watcher and the elrs_ip_light_bar like DTC, MVX-R0002 sets up voxl-vrx, voxl-rc-server and voxl-static-ip- watcher (needs voxl-vtx 3.3.1, voxl-rc-server 0.0.10, voxl-utils 2.0.9)
  • D0008/D0019/D0020 IP, DTC and fiber paths use the single voxl-io-server elrs_ip_light_bar preset (needs voxl-io-server 0.1.6), XBright vs micro bright is only the voxl-elrs preset choice
  • load the renamed “Seeker Micro Bright LEDs” voxl-elrs preset in place of “XBright Patrios LEDs” (needs voxl-elrs 1.2.1)
  • D0008, D0019 and D0020 V6 select the rotated lepton preset (m0173_rotated_manual), the lepton is mounted upside down on all V6 seekers
  • Pass --tracking_stereo flag to voxl-vtx configuration script on stereo tracking camera configs (C61-C64)
  • D0019 handles the S, S1 and SL strike extras codes like D0020: vision-hub disabled, MRB-D0019-XS px4 params, strike voxl-vtx setup
  • MVX-S0001 V3 (M0197, board code 9): voxl-elrs configures the M0193 TX on /dev/ttyHS6 instead of /dev/ttyHS1
  • voxl-configure-sku: MVX-S0001 defaults to V3 on board code 9 and V0 otherwise, and no longer overrides a version passed with -v
  • select new voxl-vision-hub d0008v6 VFC config for D0008 V6 on M0197 (board code 9) only
  • load the “XBright Patrios LEDs” (micro bright) voxl-elrs preset on all D0008 and D0020 V6 and newer, not just XS1
  • voxl-io-server light bar profile picks micro bright on V6 and newer or XS1 across the IP, DTC and fiber paths, older D0008 IP units with XBright bars get the XBright profile
  • voxl-configure-sku: the V6 sub-revision prompt now states what rev A changes (hires IMX664 on J8 upper instead of J7 lower, extrinsics unchanged, lettered camera config); the letter stays optional
  • VRX SKUs: check for voxl-px4 units when the disable step runs, not when queued, so the modalai-adsp-vrx install removing voxl-px4 no longer reports a failed step
  • VRX SKUs: set_px4_conf_param steps are no longer queued at all instead of being queued and skipped
  • MVX-S0001 installs modalai-adsp-vrx on board code 9 like the other VRX SKUs
  • select the fpvm open-vins preset on M0197 (board code 9) for its BMI270 800Hz IMU
  • VRX SKUs (MVX-R0001, MVX-R0002, MVX-H0001, MVX-S0001) no longer call any px4 configure scripts in voxl-configure-mpa, installed voxl-px4 services are only disabled
  • support hardware sub-revision letters in SKUs (e.g. V6A), parsed as VOXL_HW_REV with VOXL_HW_VERSION still numeric
  • voxl-configure-sku accepts -v 6A or -r A, wizard asks for sub-revision on D0008/D0019/D0020 V6
  • voxl-configure-mpa applies sub-revision overrides on top of the base version config, camera config gets the letter appended (61 -> 61A)
  • add D0019 version prompt
  • change px4 calibration files path from /data/px4/param to /data/modalai/px4
  • move D0008-V6 to fpv estimator params for robustness
  • add XS1 sku option, XS behavior plus the micro bright LEDs elrs preset (then named XBright Patrios LEDs)
  • no imu thermal cal required on XS drones
  • add handling for D0008-V6-XS
  • disable mavcam-manager on platforms with M26 family modems
  • add V6 handling for D0008
  • enable mavlink-server elrs rc mux on D0008 and D0020
voxl-elrs v1.1.7 → v1.2.3 21 changesSource CHANGELOG Diff
  • cache parameter indexes per boot in /run/voxl-elrs, so bind, unbind, arm and other name lookups cost one ping and one read instead of a full enumeration the name at the cached index is checked before use, and a miss or mismatch re-enumerates firmware updates and the first device info after a ModalAI receiver reboot clear the cache, ELRS_PARAM_CACHE_DIR moves it and an empty value disables it
  • request parameter chunks and parameters back to back instead of sleeping 15 ms between them, enumeration takes ~2 s instead of ~8.9 s over mpa:crsf_raw and ~0.6 s instead of ~1.75 s over qup7
  • drop the fixed 200 ms settle after the crsf_raw pipe connects, every mpa command starts ~0.2 s sooner
  • bind and unbind no longer re-read the command parameter after the lookup
  • update M0220 RX and TX firmware over SMP v2 (MCUboot serial) instead of MAVLink FTP, the input is still an MRC bundle app and XIP go to the primary slots and both MCUboot hashes are checked before the SMP reset the bootloader runs at 420000 baud for HWID 0x01 and 921600 otherwise, receiver updates at 420000 need the updated bootloader
  • upload-firmware <bundle> smp recovers an M0220 left in its bootloader without CRSF discovery, add -T for a TX
  • update-mrc stays available for explicit legacy MAVLink FTP uploads
  • SMP uploads work over the adb: transport
  • bundle private static copies of libsmp and libcbor, SMP requires BUILD_JSON=ON
  • ship the libcbor license that the package installs, its missing file stopped every cross build at CPack
  • rename the “XBright Patrios LEDs” preset to “Seeker Micro Bright LEDs” (seeker_micro_bright_leds.json), it maps white to 1300us for micro bright bars XBright bars (white 1500us) use the default “Seeker LEDs” preset
  • presets match folders and parameters by name instead of field_id, so they survive parameter index changes between firmware builds config files no longer need field_id/type and use a compact layout: {“Output Mapping”: {“Pin 1”: {“Input Channel”: 7}}} verbose/save-json configs still load, a stale field_id only logs a warning
  • configure checks every preset entry against the device before writing, so an unknown name or wrongly typed value no longer leaves a partial config
  • merge the “Custom Domain RX” and “Custom Domain TX” presets into one “Custom Domain” preset (custom_domain.json) that works on both
  • fix receiver firmware updates over SLPI with voxl-px4 running: wait for the DSP after stopping voxl-px4 and before esptool, reset it before restarting voxl-px4
  • pass --before default_reset to esptool so the first sync attempt already asks ELRS for the bootloader
  • verify a flashed receiver with a ping from a fresh process and stop reporting a verified flash as a failure
  • bound the esptool subprocess with a deadline and say whether to power-cycle or hold the boot button when it fails
  • update ELRS to 3.5.3.31 to fix crsf compatibility
  • Warning this breaks compatibility with older voxl-elrs!
  • Added GUI frontend + adb bridge
voxl-esc v1.6.3 → v1.6.5 2 changesSource CHANGELOG Diff
  • update prod/test tools
  • update to 39.26 fw
voxl-esptool v0.2.1 → v0.2.2 9 changes
  • set the SLPI UART read timeout from esptool’s requested timeout (1 s when unset, clamped to 500 ms..5 s) instead of libvoxl_io’s fixed 100 ms default, and re-apply it after every baud change
  • inWaiting reports the bytes actually buffered on SLPI ports instead of always 256, and flushInput/reset_input_buffer clear the SLPI rx buffer instead of doing nothing
  • accept /dev/slpi-uart-<qup> for the SLPI QUPs libvoxl_io supports (2, 6, 7), not just /dev/slpi-uart-7
  • SLPI ports use the CRSF “bl” bootloader reset (Voxl2Reset) instead of the DTR/RTS resets that crashed with AttributeError ‘fileno’, so plain “esptool chip_id” works and sends “bl” once per connect attempt
  • before no_reset still makes its first attempt a plain sync, for a receiver already held in the ROM bootloader
  • Voxl2Reset restores the caller’s connect baud (normally 115200) instead of leaving the port at 460800, so a stub already running at that baud stays reachable
  • the ESP8266 stub loader inherits the ROM loader cache, so flash_id, --flash_size detect and the pre-operation flash chip checks work with the stub instead of raising AttributeError
  • no zero-length reads, and a failed read returns nothing instead of stale buffer bytes
  • do not close and re-init the SLPI UART when the baud is set to its current rate, e.g. connecting at 420000 with --passthrough re-initialised the port right after the “bl” frame
voxl-focus-camera v0.6.2 → v0.6.3 2 changes
  • added workstation script to loop the focus tool
  • fix locked awb
voxl-fpv-px4 v1.14.0-8.148.0 → v1.18.0-8.0.25 18 changes
  • ekf2: add gyro-frame filtering and adaptive weighting for gravity fusion
  • Wrap Linux settime to prevent GPS from setting the Linux realtime clock and affecting other services
  • Honor loopback interface when binding UDP sockets in Mavlink
  • Change RC position mode switch behavior. Engage once it can run.
  • Removed obsolete QURT definition that was preventing logging of GPS time
  • Fix to prevent qcs6490 system from deleting px4 lock files
  • Clean up BMI270 diagnostics, startup probes, and comments
  • BMI270: 800 Hz OSR4 filtering, FIFO fixes, gyro timing and cross-axis corrections.
  • Add optional BMI270 gyro retrimming and NVM storage support.
  • Add optional EKF gravity-fusion rate gate, disabled by default.
  • Restore turtle mode reporting in MAVLink heartbeat
  • Made sure that the virtual serial endpoint baud rate is set to 460800
  • Allow virtual serial endpoint baud rate parameter to be optional with 420000 default
  • Added new MPA bridge for PX4 attitude information including reset count and delta
  • Changed where sensor and thermal calibration files are stored to /data/modalai/px4
  • Switched to upstream tag v1.18.0-rc1
  • Rebased the FPV changes on upstream release/1.18 branch at commit 75395e11aa33f3cfa9496deeef314f4711368829
  • Don’t start DPS baro on M0226
voxl-imu-server v2.0.2 → v2.0.6 11 changesSource CHANGELOG Diff
  • voxl-calibrate-imu-temp: baro temp cal pipe changed from ‘px4_vehicle_air_data’ to ‘px4_sensor_baro’ (raw pressure + real die temp)
  • voxl-calibrate-imu-temp: add --no-apps to skip apps-proc IMUs (px4/baro only), leaves voxl- imu-server.cal untouched
  • voxl-calibrate-imu-temp: pace the heating loop when only the baro is enabled
  • voxl-calibrate-imu-temp: line-buffer stdout so stage messages reach voxl-portal promptly
  • bmi270: load Bosch’s standard config blob (bmi270_config.c) so the gyro cross-axis factor_zx is readable; custom blob reports 0
  • bmi270: add BMI270_BWP_MODE selector (normal / OSR2 / OSR4) with per-mode timestamp delay compensation, documented in bmi270.cpp
  • bmi270: use OSR4 on-chip filter mode for accel and gyro (was normal mode) to attenuate motor vibration before the FIFO; ODR unchanged
  • Fixes for security warnings
  • Moved px4 thermal cal files to /data/modalai/px4
  • fix LSB indices of 42688 IMU in 20-bit mode
  • fix PX4 temp cal param names
voxl-io-server v0.1.3 → v0.1.6 3 changes
  • d0020_ip_light_bar, d0008_ip_light_bar and d0008_v5_ip_light_bar replaced by one elrs_ip_light_bar preset for IP control, the receiver’s voxl-elrs pin preset sets the widths for XBright vs micro bright bars and voxl-configurator picks it per SKU
  • remove en_xbright (it set the micro bright widths), the receiver’s voxl-elrs preset sets the bar widths, a stale en_xbright is removed from the config
  • rc handling reads all channels from the rc_active pipe published by voxl-mavlink-server, joystick button config removed
voxl-lepton-server v1.4.1 → v1.4.2 3 changesSource CHANGELOG Diff
  • only reset the lepton at startup if it has not already booted (M0195 cannot recover a booted lepton from reset)
  • resync SPI without rebooting while the lepton still reports booted
  • resync if no frames arrive for 3 seconds
voxl-logger v0.6.3 → v0.6.9 12 changesSource CHANGELOG Diff
  • add bash completions for voxl-logger-auto
  • fix voxl-logger-auto configure crashing with UnicodeEncodeError on drones without a UTF-8 locale
  • add voxl-logger-auto configure, interactive and scriptable config editor
  • add V6 tracking_left/tracking_right pipes to -b, -j and -o presets
  • fix -j using its skip argument as the baro pipe name, now logs px4_baro
  • fix -j short option requiring an argument, skip is optional as documented
  • add raw buffer logging for raw8, raw10, raw12, yuv
  • add raw and uncompressed yuv playback to voxl-replay
  • clean up default voxl-logger-auto.conf
  • fix -Wstringop-truncation in control pipe info fields
  • add voxl-logger-auto
  • add logging support with -O for offboard_log, logs the mpa offboard data from VFC. Also logs the px4_baro pipe in addition
voxl-mavcam-manager v0.6.1 → v0.6.2 1 changeSource CHANGELOG Diff
  • fix debug flag being set incorrectly
voxl-modem v1.2.5 → v1.2.6 1 changeSource CHANGELOG Diff
  • move Quectel Connect Manager to the voxl-quectel-cm dependency
voxl-mpa-tools v1.5.8 → v1.5.10 4 changesSource CHANGELOG Diff
  • changed baro tc cal param directory from /data/px4/param to /data/modalai/px4
  • add conf files for D0008-V6
  • voxl-logger: update to allow raw images to be recorded as jpegs
  • add voxl-record-raw-image
voxl-open-vins-server v0.6.2 → v0.7.8 140 changesSource CHANGELOG Diff
  • ZUPT disabled (try_zupt: false) in fpv, fpvM, fpvhires, fpvhiresM, starling2 and starling2M; its noise inflation contaminated the state
  • startup: partial camera connections are cleaned up without recursive manager locking, fixing startup hangs; the health thread starts before subscribing and reports stalled camera, IMU or estimator inputs without triggering repeated resets
  • configured per-camera masks apply to live, calibration and tracker-only replay TrackOCL inputs; requires libmodal-flow 1.0.10
  • d0008-v6 and d0008-v6M: per-camera PNG tracking masks packaged and enabled, updated estimator configs, v6M uses the D0008-v6 camera pair calibration
  • new d8v6m preset in voxl-configure-open-vins for D0008 V6 on M0197 (QCS6490, BMI270); both D0008 V6 presets set using_stereo=0 and sync_config=true
  • CI replays use center stamps, auto-start and dynamic init with aligned baselines; failed replays no longer replace references
  • host tests for the camera manager, forced-sync input status, camera masks and CI scoring
  • voxl-zcalib: VIO forced sync applies only to cameras VIO flies; an any-pipe or VIO-disabled camera keeps its own exposure-center stamps, so calibrating one alongside VINS no longer requires the VIO reference camera
  • voxl-zcalib: a forced-sync session mixing VIO cameras with a camera outside the VIO chain is refused instead of dropping every unpaired frame group; calibrate the outside camera in a separate session
  • voxl-calib-to-extrinsics: output is written atomically (temp file, fsync, rename) and keeps the conf’s permissions
  • host test for the calibration session timing policy
  • forced camera sync: new force_camera_sync and cam_imu_dt_ref_camid estimator keys group synced dual-mono frames on the hardware stamp and share the reference camera’s center timestamp
  • live ingest, zcalib, vins-lab replay and tracker-only replay all use the same sync grouping and decimation
  • zcalib: forced-sync sessions require the reference camera; unpaired frames are counted in the run summary
  • zcalib: use the declared-camera intrinsics path from voxl-camera-server as-is (reported by Noah Sleeman, ASCEND)
  • calibration result, rollback and session record move to /data/ov_calib/; the calib tools follow
  • ov_calib.yaml: track_rate_hz 30, solve_budget_s 120, tg_max_sigma documented as an acceptance ceiling, BMI270 noise reference added
  • calibration hotstart: overlays composed in one frame, Tg and camera rotations transported, one snapshot path through boot and reset, incoherent reset rejected
  • calibration server: per-camera noise controls, independent IMU/Tg seed policies, gravity provenance, collection budget, atomic result writes
  • new fpvM profile and voxl-configure-open-vins fpvm preset for the M0197 synced AR0144 duo
  • fpv and starling2 profiles: forced sync on, eight init poses, 180-degree init tilt limits; starling2Bmi restores the master init policy
  • host regression tests under tests/ run with ctest, no board required
  • open_vins submodule: initializer S2 manifold and equidistant derivative fixes, lower warm- start overhead, opt-in structureless QR export, fixed-Tg preintegration invalidation
  • added after release: open_vins submodule changes from branch calibration-refinement (c6a903e..c698db5) that the original entries missed
  • ov_calib.yaml keys introduced in 0.7.5 (c6a903e) and never listed: bootstrap_epipolar and tg_precision_screen (default true), radtan_tangent_refine_sigma (0.001) and radtan_tangent_full_sigma (0.01); the shipped profile keeps the defaults
  • correction to the forced-sync line: cam_imu_dt_ref_camid is not new (parsed since 0.7.0), this release also makes it the camera that owns the group timestamp; use_stereo rigs (d0008-v6, d8spirit) take the same forced-sync path, and epoch_mode has no effect on synchronized rigs
  • correction to the open_vins submodule line: the S2 fix repairs the memory layout of the gravity tangent basis in the shared ceres-free solver, which corrupted the gravity Jacobian and covariance of every dynamic init since 0.7.0 and of zcalib window solves since 0.7.2; the equidistant optical-center derivative fix also applies to the filter camera model; the structureless QR export is enabled by the environment variable OV_ZCALIB_EXPORT_QR=1, not a YAML key, and applies to the initializer and zcalib
  • static and dynamic init apply the fixed IMU chain intrinsics loaded for the filter (Dw/Da, gyro/accel rotations, Tg) instead of raw IMU samples; every shipped IMU chain is non-identity, so every init seed changes
  • the initializer retimes each camera with its own timeshift_cam_imu; when offsets differ it returns only the IMU marginal and the filter starts a cold clone window, so init_warmstart_inject no longer injects clones on fpv, fpvhires, starling2 and starling2Bmi
  • soft reset keeps the live bias prior only for a fully fixed calibration model (no online camera/IMU calibration, zero readout, init_dyn_mle_opt_calib and init_dyn_fix_ba_on_reset off); every shipped profile estimates camera intrinsics and time offset, so soft-reset re-init now uses the configured bias seeds (0.7.5 always used the live prior); a kept prior carries the full 6x6 bias covariance, aged to the first new graph node, and excludes pre-reset measurements
  • dynamic init applies the gravity re-alignment at every accepted tilt (0.7.5 skipped it below 0.1 deg) and carries the fitted gravity uncertainty into the initial covariance
  • dynamic init is rejected when an optimized feature lies behind a camera; init outputs with non-finite values, non-unit quaternions or an invalid covariance are rejected before import and the filter stays uninitialized
  • warm start removes the observations the initializer consumed from the feature database, so the first filter update does not reuse them
  • initializer IMU windows require strictly increasing timestamps covering the whole interval; zero-dt samples used to be dropped
  • invalid initializer priors or IMU factors fail the attempt instead of exiting the process, and initializer exceptions count as a failed attempt; each attempt runs on a snapshot of its inputs and stale results are discarded after reset or restore; prior gradient whitening corrected (only priors with a nonzero gradient are affected)
  • epoch_mode defaults to true for unsynchronized multi-camera rigs whose estimator yaml omits it (shipped d0008-v4 and starling2Bmi)
  • new opt-in estimator keys, false by default and in every shipped profile: physical_camera_clones (physical warm start; global shutter and fixed calibration only, rolling-shutter cameras are rejected at startup) and async_frame_clones
  • rk4/analytical propagation (rk4 in every shipped profile) integrates continuous IMU white noise and bias random walk over each interval, including navigation/bias cross-covariance, instead of injecting the interval-average noise; discrete integration keeps its noise model
  • anchored landmarks are expressed in an unwarped virtual camera at the anchor clone; time offset, rolling shutter and epoch transport act only on observations (changes results on rolling-shutter rigs and for the non-reference camera of dual rigs)
  • time-offset warps of fixed zero-readout cameras use the clone velocity in the estimated world frame, in updates and in triangulation
  • SLAM delayed-init chi2 gate counts only the residual rows left after eliminating the landmark (tighter acceptance)
  • ZUPT chi2 counts every IMU residual row, including energy removed by QR compression; with non- identity IMU intrinsics or Tg (every shipped chain) ZUPT uses a raw-coordinate stationary model with matching Jacobians
  • epoch-bridge bias Jacobians include the IMU intrinsics and the Tg accel-bias coupling
  • dt_calib_gate freezes temporal calibration with a Schmidt update instead of dropping its Jacobian columns (d0008-v6, d0008-v6M)
  • IMU intervals are never extrapolated: an uncovered, non-increasing or non-finite interval skips the frame; propagation and ZUPT share one accepted IMU endpoint
  • numerical failures in EKF propagation, updates and landmark initialization roll back instead of exiting the process or admitting NaN (a failed anchor change marginalizes the landmark); non-finite innovations are rejected
  • filter camera projection runs fully in double precision (radtan and equidistant); feature triangulation refines in double precision and rejects empty tracks and non-finite geometry
  • Kalman gains are solved from the innovation factorization instead of an explicit inverse; chi2 thresholds above 4095 dof use Wilson-Hilferty instead of clamping
  • zcalib: calibration windows no longer add half the frame exposure to stamps that ingest already centers; earned time offsets differ from 0.7.5 by about half the mean exposure
  • zcalib: temporal reprojection optimizes the window velocity (0.7.5 held it fixed)
  • zcalib: bootstrap and window gyro-bias seeds apply the seeded IMU intrinsics and Tg before time-offset, hand-eye and bias estimation
  • zcalib: bias priors stay at the harvested window seeds for every candidate; held-out verification scores all candidates with fixed weights and noise
  • zcalib: an uncertified Tg triggers a refit with Tg held at its seed (stage A1a-fixed-tg; the A0 extrinsics/td are kept if it fails); a fixed nonzero Tg keeps its accel-bias coupling in the IMU factor
  • zcalib: the unresolved focal/center pair refit also covers equidistant cameras (stage B2-radtan-refit renamed B2-camera-refit)
  • zcalib: early live cutover also waits for the Tg precision target when Tg is estimated; guidance counts only windows from the current thermal bin
  • zcalib: the bench profile moves to split-half gate authority with Wald as a diagnostic, as flight already was; Wald sizes each retained Tg direction with its own quantile
  • zcalib: stages start only with solve budget for a complete pass; budget-truncated passes and gates are discarded, and an over-budget IMU stage keeps the A0 extrinsics/td instead of aborting
  • zcalib: ov_calib.yaml is validated strictly – duplicate keys, wrong types, out-of-range values and a profile other than flight/bench fail the load instead of falling back to defaults; new keys camera_pixel_sigma (1.0), camera_pixel_sigma_by_name (canonical camera names) and gravity_mag (0 = inherit)
  • zcalib: session records are format 7 (per-camera pixel sigma, completion footer); formats 5 and 6 still replay, a format-7 record without its footer is rejected, and 0.7.5 cannot read formats 6 or 7
  • zcalib: the JSON report adds gravity magnitude/source, solve budget, per-camera pixel sigma, hand-eye gyro-bias status and verdict/sigma semantics fields; report and result write failures are errors
  • zcalib: non-finite posteriors, solver steps, Wald statistics and relative-rotation seeds fail closed under fast-math
  • build: ov_core, ov_init and ov_msckf export fixed Eigen ABI definitions (EIGEN_MAX_ALIGN_BYTES=16, EIGEN_MAX_STATIC_ALIGN_BYTES=16, EIGEN_MALLOC_ALREADY_ALIGNED=0) to every consumer; the GPU tracker builds only with OpenCL plus the libmodal-flow Types.hpp and StereoMatcher.hpp headers, otherwise the CPU trackers are built
  • present but not selected by any runtime configuration: sampled-IMU propagation groundwork, sampled CPI statistics and BiasLinkedCalib (exercised only by tests)
  • host regression tests and oracles added across ov_core, ov_init, ov_msckf and ov_zcalib
  • add standalone voxl-zcalib live calibration and session replay, with declared or ad-hoc cameras
  • share sensor ingest and calibration with the server while preserving a running VIO process
  • add bounded JSONL status publishing, solve/abort/extend controls, and caller provenance
  • reject concurrent calibrator instances; preserve operator profiles during package upgrades
  • export JSON reports with gate evidence, posterior uncertainty, held-out costs, and stage timing
  • keep non-finite report values valid under fast-math compilation; serialize them as null
  • use centered frame timestamps consistently in bootstrap
  • detect motion-biased time correlation and refine rotation/time with matched-bearing geometry
  • distinguish provisional sparse-data seeds from geometrically verified timing
  • apply model-specific radtan/equidistant refinement gates and refit unresolved radtan pairs
  • share the solve deadline and worker budget across stages; reject truncated split-half evidence
  • cache exact reprojection transport and use fixed-size radtan derivatives
  • screen weak Tg precision before additional half-solves and improve single-camera guidance
  • accept JPEG log channels, with a warning that lossy captures cannot establish tracker parity
  • libmodal-flow version lock, fails configure below the floor and records the exact version
  • stereo front-end: one ZNCC call per detection frame
  • removed legacy concatenated-stereo camera path (StereoCameraMinimal)
  • “using_stereo” conf key overwrites the estimator YAML when sync_config is true
  • new “stereo_calibration” conf key: path to a voxl_stereo_calibration.yml from the offline stereo calibrator (blank = off)
  • stereo: IMU-aided KLT seeding compiled but OFF by default (A/B-togglable); up_*_sigma_px_stereo keys dropped from the estimator and the d0008-v6 profile – stereo and mono features share up_*_sigma_px
  • d0008-v6 profile: rs_convention top – synced pairs bundle on bit-equal SOF stamps; under center stamps the per-frame AE exposures desync the pair by tens of us, the ingest never bundles, and live dual-mono degrades into micro-epochs (one cam starved, quality reset-loop)
  • [stereo_calib] informational prints gated on using_stereo; warnings and errors stay unconditional
  • vins-lab: reliable replay init suite – det-init by default (init_dyn_mle_max_time=9999, multi_threading_subs=false, so init no longer depends on wall-clock load; --wallclock-init restores live-like timing), --dyn-init (skip the static path, init via the dynamic MLE at motion onset), --auto-start (gyro motion-onset detector starts the feed onset+1s), --static- init (init_max_disparity=0 for IMU-quiet logs); overrides are comment-preserving edits to the run’s config snapshot
  • clients: voxl-log-vins and voxl-evaluate-vins removed (unused; voxl-vins-lab owns record/replay/eval – dpkg drops the stale binaries from devices on upgrade)
  • estimator-yaml comment doctrine: a ‘:’ inside a TRAILING comment makes cv::FileStorage split the line and parse the key as a MAP – the key then silently reads as its parse DEFAULT (fpvhiresM on-device: calib_cam_extrinsics/timeoffset/readout, fast_threshold, num_opencv_threads all defaulting; latent for years because the old yaml-cpp sync STRIPPED comments, exposed by the comment-preserving sync). All 74 offending trailing comments across the 11 shipped profiles hoisted to their own lines (verified: every top-level key of every profile parses scalar under cv 4.6); voxl-vins-autoconf detects + --apply-fixes the class on any device; the strict rs_convention parse explains the trailing-comment cause when it reads an empty value
  • Boost retired end to end (build + runtime): rT profiling timers -> std::chrono::steady_clock (ov_core/utils/ChronoProf.h; boost’s microsec_clock::local_time resolved the TIMEZONE – glibc lock class – several times per frame on the estimator thread), chi-squared 0.95 gate thresholds -> baked constexpr table dof 1..4095 (ov_core/utils/chi_square/, generated aarch64-under-qemu against the exact runtime boost::math 1.83 so every entry is BIT-IDENTICAL to what the filter computed on-device; StateHelper’s delayed-init gate no longer solves a quantile per landmark), boost::filesystem -> 3 POSIX wrappers (FsLite.h), boost::lockfree::spsc_queue -> ov_core::SpscRing (the zcalib live-feeder ring generalized: acquire/release only, alignas(128) indices; pop() MOVES the frame out and resets the slot so popped pixel buffers release immediately instead of pinning capacity x frame memory)
  • include hygiene: VoxlVars.h no longer includes the estimator (fwd-decls; it reached every TU in server/ + lab/ dragging the full VioManager/tracker/OpenCL closure, ~280k preprocessed lines per TU), VoxlCommon/VoxlConfigure/VoxlHK/VoxlIngest/CameraBase slimmed to what their declarations use, opencv umbrella narrowed to core/mat.hpp where only cv::Mat is named, modal_pipe.h -> modal_pipe_interfaces.h where only types are needed; opencv_compat umbrella drops the 5 never-linked modules (videoio/objdetect/photo/ml/dnn) from every TU in the tree; OpenCL handles in camera headers now properly HAVE_OPENCL-gated (CPU-only configs compile again)
  • cmake: Boost find_package removed (first-party) / optional (submodule, ROS-visualizer-only); linker flags out of compile flags; duplicate march/O3 re-appends removed; dead EN_ION_BUF compile definition removed; clients/ drops OpenCV/Eigen/Boost discovery entirely (pure modal_pipe + libc); host-python matplotlib leak disabled; ov_msckf/ov_init fix the /../ov_core include-dir expansion (CMAKE_CURRENT_SOURCE_DIR)
  • rs_convention knob (top | center | bottom): the RS row-anchor convention is a DECLARED single- knob choice – the estimator-yaml key drives BOTH the filter’s row model (row v samples at stamp + (v/h - anchor) * readout) and the producer stamp anchoring in frame_timestamp_s (top = raw HAL3 SOF, the pre-flip system convention; center = center-row mid-exposure, the default; bottom = last-row mid-exposure); stamps and model structurally cannot disagree; all shipped profiles carry the key explicitly
  • voxl-vins-lab --rs-convention auto (default): a log whose captured conf predates the zcal keys is recognized as a pre-flip recording and replays under TOP – same command, same log reproduces the vins-lab-era results on this branch; post-flip logs follow their yaml; explicit top/center/bottom overrides; a pre-flip-era stereo log also reverts to that era’s T_cn_cnm1-first extrinsic source for the ZNCC pack (residual pre-flip deltas are numerical- noise class only: exact-SO(3) transport and the ceres-free init refactors are unconditional)
  • voxl-vins-lab: the stereo ZNCC pack runs ONLY when the estimator yaml says use_stereo – a dual-cam mono rig (fpvhires’ unrelated hires+tracking pair) no longer gets packed as a stereo pair
  • tools/voxl-vins-autoconf: inspect / validate / auto-fix the server .conf + VoxlConfig yaml tree as ONE coherent set (ChainYaml-strictness grammar, %YAML directive, shutter/readout/fps coherence, max_cameras vs chain, zcal key group, hot-start snapshot presence); writes rs_convention explicitly; --log mode reports a capture’s stamp-convention era plus the exact replay invocation; dry-run by default, --apply fixes textually (comments preserved, atomic writes, one-time .bak)
  • voxl-configure-open-vins: presets for the remaining shipped profiles (d8spirit, fpvhiresM, starling2M, starling2Bmi, zmono)
  • in-process targetless calibration mode: voxl-open-vins-server --calibrate runs a self- calibration session (engine: ov_zcalib) through the identical drivers and frame gating as VIO (TrackOCL front-end); lock-free SPSC ingest with a single arrival-sequence merge; mandatory session record mirror written at consumption (live == replay structural; no file I/O in RT callbacks); atomic result YAML + rollback under /data/modalai/ov_calib/; exit code = session verdict; per-pass solver prints gated behind -d
  • calibrator profile /etc/modalai/ov_calib.yaml: operator-controlled seeded-vs-earned policy (per-unit intrinsics seeded; extrinsics/td earned blind by default) + raw-Allan calibration noise keys
  • calibration CLI: -k/–calibrate, --calib-cam (global-shutter default, rolling explicit-only), --calib-out, --calib-flight, --calib-max-sec, --calib-budget, --calib-min-eig, --calib-config, --calib-no-perf-mode
  • calibration sessions request the performance CPU governor (measured 3.1x on the solve); already-performance rigs are never touched; restore is knob-gated
  • dual-camera calibration ingest: per-camera drop accounting – one camera’s dropped frames no longer invalidate the other camera’s windows
  • scripts/gauge_probe.py: scores a calibration result against a kalibr reference across gauge conventions
  • VIO hot-start from a committed calibration snapshot: values only, committed blocks only; filter noise/prior sigmas never touched; the IMU chain applies as the complete {Dw, Da, R_AtoI} triplet with a runtime gauge round-trip check
  • calibrate_first: a boot with no committed snapshot runs a calibration session first, then cold-starts VIO in-process; bounded retries; a hard reset reverts to the pre-calibration on- disk configuration unless opted in; all knobs default OFF (en_calib_hotstart, calibrate_first, calib_hotstart_on_reset, calib_restore_governor)
  • startup hygiene: process kill/signal/pidfile/priority/affinity precede any thread creation (solver workers inherit the big-core set); non-service runs stop an active systemd unit before the raw-kill fallback (cancels pending auto-restarts); SIGINT/SIGTERM attributed via SA_SIGINFO
  • SYSTEM TIMESTAMP CONVENTION FLIP: every frame stamp is now the center-row mid-exposure instant, applied ONCE at ingest (t = HAL3 SOF + (readout + exposure)/2; CameraBase::frame_timestamp_s is the single definition, shared by mono/stereo/VIO/calib and mirrored by the host log feeder). Exposure is per-frame (AE-exact); readout is the fixed HAL3 rolling-shutter skew of the sensor mode, plumbed config -> cam_info (camN_readout_time_s > chain t_readout). CameraData::exposures demoted to provenance.
  • rolling shutter is CENTERED inside the estimator and the calibrator: row v samples at stamp + (v/h - 0.5)*readout (was top-anchored v/h) – the calibrator/filter tr-anchor mismatch class is gone
  • exact SO(3) manifold transport everywhere the RS/dt kinematic shift is applied: exp_so3 replaces the first-order (I - skew(w) dt) in ov_msckf updaters/retriangulation and in the zcalib reprojection factor (quaternion exponential); Jacobians unchanged by contract
  • readout time is NEVER calibrated: tr estimation removed from ov_zcalib end to end (free_tr, C3 row-coverage gate, C3b td-aliasing guard, physics band, seed-vs-earned provenance, tr_hw_seed record field [kFormat 5], --tr-estimation CLI, estimate/seed_readout_time profile knobs); tr is the HAL3 hardware value, a fixed transport constant folded into each observation’s dt_ref; --tr <s> on the CLI now MEANS that value; calib_cam_readout forced false on RS platforms
  • td convention unified: the calibrated timeshift is defined against center stamps and consumed verbatim by the chain/VIO/hotstart – the mid->SOF conversion (timeshift_cam_imu_sof, td_sof) is retired; RS-platform chains re-baselined (IMX664 timeshift 0.006757 -> 0.000, the measured ballpark under center stamps)
  • pre-flip artifacts: session .bin records fail loudly (format bump), pre-flip chains carry (readout+exposure)/2 inside their timeshift until re-earned (the calib report says so)
  • docs: INFLIGHT_CALIBRATION.md (operator usage) + CALIBRATION_OPEN_ITEMS.md (upstream open items with proposed fixes and adjudicated design verdicts)
  • record_session profile key: the session record mirror is optional (default on; disabling it forfeits replay and forensics)
  • yaml-cpp dependency removed: the server speaks OpenCV YAML end to end – estimator-config sync patches its keys in place (file comments now survive a sync), and the camera chain loads/saves through an order- and key-preserving OpenCV-YAML model (ChainYaml.h)
  • tools/voxl-calib-to-extrinsics: writes committed calibration extrinsics into extrinsics.conf (conf-graph frame composition, gimbal-aware RPY extraction, plausibility gates, comment- preserving edits; ships in the deb)
  • tools/voxl-calib-commit-chains: writes a committed result permanently into the kalibr IMU + imucam chains (gauge-ported with an estimator-parse round-trip check; fed-frame gated; sync_config cross-checked against extrinsics.conf) and disarms the hot-start knobs; sync_config is set false by default so boot cannot undo the commit (--keep-sync-config preserves it, with extrinsics.conf cross-check warnings)
  • calibration tools: quoted provenance strings parse correctly (a quoted imu_frame no longer refuses the frame gate); voxl-calib-commit-chains -e also writes the committed extrinsics into extrinsics.conf
  • fpvhiresM VoxlConfig profile ships in the package (single-camera hires rigs whose conf points yaml_folder at it booted into a missing-profile abort)
  • voxl-vins-lab: offline replay harness that feeds a voxl-logger capture directly into an in- process VioManager – as fast as the filter can consume (--speed 0), Nx, or real-time – with per-frame CSV + summary metrics, optional publishing of the normal ov/ov_extended pipes, an interactive rewindable session (filter snapshot/restore/branch), and lineage-aware run persistence (a publishing drive writes a portal-loadable ov_extended data.raw)
  • shared sensor ingest (VoxlIngest): IMU batch build/route and mono/stereo CameraData construction factored out of the pipe callbacks so the live server and the lab feed the estimator through identical code – the center-stamp convention, per-frame exposure provenance and the calibrate-mode routing all live in the ONE shared conversion
  • server build split into vins_server_core static lib + thin spinner executable; lab links the same lib; build.sh prefers ninja + ccache with a RAM-aware job count
  • publisher raw ext sink is ASYNC by construction (RecordSpool: bounded SPSC ring + writer thread, wait-free producer, drop accounting at close) – storage latency structurally cannot stall the VIO thread; the camera hot path also sheds its staging memcpy (one ownership copy per frame remains, in the shared builder) and the ION path’s per-frame allocate-and-zero placeholder
  • vins-lab replay TIERS against the calibration session record (.bin, kFormat 5): --session <bin> drives the FILTER ALONE from recorded RawImu + post-tracking observations (TrackSIM feed; no images, no tracker), --tracker-only runs JUST the tracking front-end over a log and writes a session record seeded through the live calibrator’s own seed builder (calib_build_session_seed) – consumed unchanged by ov_zcalibrate --replay (calibration solve) or --session here; with the default full-system tier this decomposes any logged drive into system vs filter-math vs tracker
  • vins-lab x zcalib: --calib <ov_calib_result.yaml> replays a log under a committed calibration snapshot (cam-side blocks into the run’s private chain copy, IMU-side in-memory – the live hot-start mechanics); a flight that consumed a hot-start auto-reapplies the LOG-CAPTURED snapshot for parity (--no-calib-hotstart opts out); every run writes calibration.json provenance
  • ov_msckf: feed_measurement_simulation initializes via try_to_initialize instead of exiting – an observation-stream replay starts from a cold filter like a live boot
  • update cmake min version to 3.5
  • fix LD issue
  • async unsynced multi-camera support: lock-free per-camera ingest rings, epoch-anchored cloning, ACI2 preintegration bridge, deferred epoch marginalization (async meets synced; synced path bit-identical)
  • per-camera cam-IMU time offset and rolling-shutter readout states with online calibration and degenerate-motion gating
  • per-camera acquisition declarations (camN_shutter / camN_readout_time_s / camN_fps) with boot validation and config-drift guards
  • ceres-free dynamic initialization (ov_init::zbft_sfm): lock-free LM solver, S2 gravity, ~17-20 ms init (legacy ceres path was ~65 ms); drop voxl-ceres-solver runtime dep
  • any-attitude init/reset: server gravity gate, heading re-origin, warm-start clone injection
  • divergence-aware soft reset (RESET_VIO_SOFT) with live bias priors; episode purge of used- features map and zupt flags
  • async-aware quality metric: windowed feature union + time-constant EMA (replaces exact- timestamp scoring that starved async rigs)
  • auto-reset hardening: estimator-health error mask (transport warnings no longer hard-reset), warning decay, re-init grace arming, reset-race guards, hard-reset null-deref fix
  • new fpvhires config (IMX664 rolling-shutter + AR0144 tracking, unsynced); fpv restored to synced duo AR0144; fpvhires and d8v6 wired into voxl-configure-open-vins
  • estimator verbosity driven by the YAML key (-v only raises to ALL; warnings can no longer be swallowed)
  • stale-code purge: CameraQueueFusion removed, dead config knobs/globals/branches removed (~1.3k lines); duplicate includes fixed
  • docs: ov_msckf/README_ASYNC.md design doc (epoch cloning, ACI2 bridge, RS model, resets, YAML reference); authorship/copyright pass across both repos
voxl-osd v0.4.12 → v1.2.1 10 changesSource CHANGELOG Diff
  • flight mode switch positions with no saved ALT FAST/MED/SLOW choice keep the platform’s PSET_MODE instead of forcing FAST
  • requires libmodal-pipe >= 2.15.0
  • Fix turtle mode OSD indicator
  • Require voxl-cross 4.9 for all build targets
  • detect D0020 V6 sub-revision SKUs (e.g. V6A)
  • Implemented AR waypoints
  • Integrate QT OSD
  • Add ELRS submenu
  • Integrate LibELRS
  • add LOG ON ARM toggle to Debug OSD menu
voxl-portal v0.9.4 → v0.9.16 53 changesSource CHANGELOG Diff
  • ELRS: the preset and SKU defaults confirm modals list the parameters and current values of the compact name-keyed presets from voxl-elrs 1.2.1+
  • web UI scripts: index loops whose counter only reads arr[i] use for-of, Object.keys + obj[key] loops use Object.entries, and repeated reads of the same element go through one local (no behavior change)
  • suppress semgrep detect-object-injection where the index is provably a number (loop counters, index arithmetic, length/modulo clamps, ids decoded from binary frames)
  • Thermal Calibration: live sensor temperatures come from the portal’s own imu_apps_raw, px4_sensor_imu_raw, px4_sensor_baro and cpu_monitor pipe subscriptions instead of parsing the CLI stdout, so they update whether or not a calibration is running and a sensor that stops publishing shows as disconnected
  • Thermal Calibration: the Apps IMU can be deselected (--no-apps) and at least one sensor must be selected to start
  • Thermal Calibration: the cooling modal is a panel with an adjustable cold-start threshold (remembered per browser), a cooling trend readout that reports when the warmest sensor has settled, and a Start Now button for enclosed boards that never reach the threshold
  • Thermal Calibration: DONE is reported only when voxl-calibrate-imu-temp reaches COMPUTING RESULTS and exits 0; a sensor pipe dropping mid-run now reports an error instead of success
  • Thermal Calibration: a page opened or reloaded mid-run restores the current stage and control state
  • Thermal Calibration: websocket messages from the worker threads are queued and sent from the mongoose thread
  • VINS Calibration Configure tab edits estimator_config.yaml in the server’s yaml_folder; saves are refused while voxl-open-vins-server runs and rejected without the %YAML:1.0 directive or with a ‘:’ in a trailing comment
  • flag a package-owned estimator config under /usr/share and the keys sync_config rewrites at boot (prop_window, zupt_prop_window, max_cameras, use_stereo)
  • Results tab writes a session’s committed camera extrinsics into extrinsics.conf through voxl- calib-to-extrinsics: preview, map each camera to its entry, then write exactly the previewed request; refused while voxl-open-vins-server runs, extrinsics.conf.bak kept
  • flush configuration saves to storage before the atomic rename
  • voxl-logger capture and session record sources are picked from dropdowns like the Any-pipe camera: captures from /data/voxl-logger{,-auto} with their cameras and IMU (unusable ones disabled), records from /data/ov_calib and vins-lab tracker-only runs; a typed path still overrides
  • add estimator config, extrinsics write and source picker regression tests
  • use /data/ov_calib for new VINS calibration sessions
  • enable collection controls only when the backend session state permits them
  • render accepted/retained parameter decisions and raw uncertainty without inferring recovery from camera commits
  • show Tg guidance, solve-budget accounting, and timestamp/bootstrap diagnostics consistently across calibration and results views
  • add control-state and guidance regression tests
  • Solve now and Extend show the calibrator’s accept/reject reply (collection already closed, recorded source) and delivery failures, stay disabled for session-record and voxl-logger sources, and Extend adds recording time only without changing the solve budget
  • live tiles show tracked rate and feature count for every camera instead of the first camera only
  • the collection bar also tracks the Tg precision screen (raw sigma against its target) when Tg is estimated
  • an aborted session says when the calibrator could not write its report
  • Results open the report of the session that just finished, remember the last viewed report, and ignore a slower earlier report request
  • Results warn when the solve budget skipped the lens refinement stages
  • Results show the gravity magnitude and its source; the magnitude is fixed and the direction estimated
  • the block chart and table call 3-sigma posterior/prior the prior ratio and state that it is one of several commit checks
  • gates: WALD_UNOBSERVABLE from older reports shows as WALD_NOT_CERTIFIED, a Wald result computed next to split-half authority shows as a diagnostic, verdict texts no longer claim unobservability, and Tg Wald verdicts are explained
  • page text: calibration runs with VIO stopped or alongside it, the flight profile uses the configured solve budget, and the bootstrap prompt asks for smooth yaw, pitch and roll sweeps
  • Solve now, Extend +30 s and Abort controls for a running session; Abort asks the calibrator to finalize through its control pipe and sends SIGTERM (since 0.9.12)
  • calibration from voxl-logger captures as well as live cameras and session records (since 0.9.12)
  • one calibration session at a time; a second start reports the running session’s pid (since 0.9.12)
  • Configure view edits voxl-open-vins-server.conf and ov_calib.yaml; saves are refused while voxl-open-vins-server runs, keep a .bak and replace the file atomically, and a leftover ov_calib.yaml.dpkg-new is flagged (since 0.9.12)
  • Results view lists past sessions (per-session directories and the legacy flat layout) with committed blocks, time offset, prior vs posterior, parameter coupling, held-out verification, solve stages, bootstrap, committed values and gates (since 0.9.12)
  • deploy_to_voxl.sh syncs after installing the package (since 0.9.12)
  • add VINS Calibration for live camera sessions and recorded-session replay
  • support declared cameras and ad-hoc camera pipes with explicit intrinsics
  • relay session status and logs through the mongoose polling thread
  • show calibration verdicts, collection guidance, commit margins, uncertainty, and solve timing
  • separate raw time correlation, geometric initialization, provisional seeds, and committed offsets
  • fix scalar time-posterior lookup and omit uncertainty bands for retained time values
  • explain weak Tg precision and distinguish split-half gates from Wald gates
  • preserve configuration edits and use packaged defaults when the operator profile is absent
  • moved px4 cal files from /data/px4/param to /data/modalai/px4
  • warnings cleanup
  • fix width-only video dimensions
  • move third-party browser libraries to the voxl-portal-web-libs dependency
  • fix overflow with many camera pipes
  • force level horizon cal to happen after accel cal
  • vio page overhaul with improved live view and vins-lab
  • rendezvous and capture: Add follower/APN inspect
  • add follow_simple page for tracker-agnostic bbox subscribers
voxl-px4 v1.14.0-2.0.142 → v1.18.0-1.0.9 12 changesSource CHANGELOG Diff
  • Wrap Linux settime to prevent GPS from setting the Linux realtime clock and affecting other services
  • Honor loopback interface when binding UDP sockets in Mavlink
  • Removed obsolete QURT definition that was preventing logging of GPS time
  • Fix to prevent qcs6490 system from deleting px4 lock files
  • Changed where sensor and thermal calibration files are stored to /data/modalai/px4
  • Switched to upstream tag v1.18.0-rc1
  • Switched from ModalAI voxl-dev to upstream PX4 release/1.18 at commit 75395e11aa33f3cfa9496deeef314f4711368829
  • Raised minimum DSP package versions to modalai-slpi 1.2.3 or modalai-adsp 1.0.8
  • Fix Hexagon compiler NaN comparison issues in math library
  • Remove attempt to find DPS baro on bus 1 from DSP
  • Added another fence points QGC upload fix
  • Fix fence points QGC upload
voxl-px4-params v0.9.15 → v0.9.35 49 changesSource CHANGELOG Diff
  • D0008 V6 and D0020 V5/V6 gravity fusion filtering, EKF2_GRAV_FTAU 3, EKF2_GRAV_FTAU_F 0.5, EKF2_GRAV_PERS 6, needs px4-firmware with these params, older firmware skips them
  • D0020 V6 and V6-XS mag current compensation for the short GPS mast, CAL_MAG0_XCOMP/YCOMP/ZCOMP -4.3/24.7/-3.2 (was the tall mast 13/8/9)
  • move D0020 V6 mag compensation out of the base file into short and tall mast files, mirrors D0008
  • voxl-configure-px4-params and -18 skip any params or cal file containing nan/inf, a bad baro thermal cal loaded nan into TC_B0_X0/X1 and PX4 then fails every param save verify
  • reset any param left at nan/inf in PX4 to default (PX4 v1.12+ only, older param reset takes an exclude list), and exit 5 listing the skipped files and reset params
  • validation reports nan/inf instead of “doesn’t match 1”, and a nan already in PX4 now shows as a diff so the file value overwrites it
  • D0008 MPC_TILTMAX_AIR and MPC_MAN_TILT_MAX 32 to match the ALT SLOW boot mode, fixes param validation failing with 32.0 vs 50.0
  • D0008 ALT FAST/MED/SLOW now differ, PSET tilt 70/50/32 to match the deploy overlay (all three were 50)
  • D0008 boots in ALT SLOW, PSET_MODE 3
  • D0008 V4/V5 PSET_CHANNEL 0 like V6, voxl-osd picks the ALT speed per switch position instead of a fixed low SLOW, mid MED, high FAST
  • D0013 boots in ALT SLOW, PSET_MODE 3, keeps its own PSET tilts and Z velocities
  • D0019 and D0020 get the PSET ALT FAST/MED/SLOW block (tilt 50/40/32, PSET_CHANNEL 0), boot in ALT FAST
  • set SENS_IMU_AUTOCAL 0 in VOXL_2_defaults.params, 1.18 enables it by default and it rewrites the accel offsets from the EKF2 bias estimate after every flight
  • lower EKF2_GPS_V_NOISE from 3.0 to 0.5 in ekf2_outdoor_stm_gps_mag, the param is a floor so EKF2 now uses the accuracy the GPS reports, better GPS position hold and less tilt
  • re-enable fake position for EKF2 alignment when not on the ground, EKF2_FP_ALIM back to the PX4 default of 2.0 in VOXL_2_defaults.params and the 0.0 overrides dropped from ekf2_universal_tweaks and FPV_Rev0, allows hand launch like 1.14
  • add EKF2_DELAY_MAX 250 to VOXL_2_defaults.params so EKF2 fuses every GPS sample on 1.18, fixes dropping out of position mode and tilting outdoors
  • D0019 loads the RTL helper like D0020
  • add MRB-D0019-XS param set for strike extras codes, mirrors MRB-D0020-XS on the D0019 base
  • disable turtle mode on MRB-D0019, MRB-D0020 and MRB-D0020-V6-XS, no prop guards on these frames
  • set SDLOG_PROFILE 2083 in VOXL_2_defaults.params, logs full rate sensor data and EKF2 replay without the FIFO topics so logs stay a reasonable size
  • remove SDLOG_MODE -1 from VOXL_2_fpv_defaults.params and D0008_V4_V5_base.params and drop the SDLOG_PROFILE 0 override from the fpv defaults so the VOXL 2 logging profile applies, artifact mode still has to be disabled for logging
  • D0008 V4/V5 (px4 1.18) now loads the same shared helper chain as V6 (battery, ekf2 tweaks, velocities, failsafes, rc loadout, turtle mode) plus a small V4/V5 tweaks file for baro noise/gate, flight tested
  • strip duplicated RC, battery, EKF2, and MPC params from the D0008 V4/V5 base file now that the helpers provide them
  • enable SYS_HAS_GPS on D0008 V4/V5 so the GPS driver runs while EKF2_GPS_CTRL keeps it out of the estimator
  • move D0008 V6 land/takeoff speeds and land detector limit into D0008_velocities.params
  • remove retired FLGT_VZ_MAX from all 1.18 param sets, MPC_POS_MODE 1 now uses MPC_Z_VEL_MAX_UP/DN
  • set PSET_FST/MED/SLW_VELZ together in the D0008 and D0020 velocity files so param_set_selector does not fight MPC_Z_VEL_MAX
  • lower D0020 MPC_Z_VEL_MAX_UP/DN from 6.0 to 5.0
  • restore D0013 PSET_MED_VELZ to 2.0
  • add D0008_V6_tweaks.params, loaded last, with EKF2_GRAV_RMAX 40.0 and EKF2_GRAV_RMODE 2 to gate gravity fusion on gyro rate and fix the D0008 V6 tilt drift in aggressive flight, needs the matching px4 update to take effect
  • set RC_CHAN_CNT and COM_FLTMODE_BOOT in tbs_tango2_stinger and zorro_blue_fpv_v5 v1.18 radio helpers, PX4 1.18 ignores the RC without RC_CHAN_CNT
  • migrate calibration backups to /data/modalai/px4
  • update outdated 1.14 param COM_RC_OVVERIDE to the new 1.18 MAN_OVVERRIDE_SPD param
  • detect px4 version from px4 bin
  • update D0008-XS to use flat pack mag comp params
  • fix incorrect filename reference for D0008 V6 flat battery mag compensation params
  • update D0008 V6 3x2 battery mag compensation
  • slow down D0008 V6 GPS POS mode velocities
  • update old temp cal file to new format during platform param load (during sdk update)
  • fix motor spin direction on D0008 V6
  • remove never-used D0008 V5 params, params stayed the same from V4 to V5
  • cleanup D0008 V6 params and do some tuning
  • update D0008 param set to support gps position mode
  • update alt mode baro params
  • update D0008-V6-XS flight modes
  • add the Mag ID for D0008 V6. This prevents mag params set during flash from being wiped during calibration due to the ID being blank
  • set COM_RC_IN_MODE to 2 (RC and Joystick) on D0008
  • add param file for disabling turtle mode
  • add inital px4 1.18 params
voxl-rc-server v0.0.5 → v0.0.10 10 changesSource CHANGELOG Diff
  • factory_enable_silvus: VRX on a Silvus radio sends joystick RC over MAVLink straight to the drone at 172.19.16.10:14550
  • dgcs_tower config uses /dev/ttyHS6 for the CRSF TX on M0197 (MVX-S0001 V3), ttyHS1 elsewhere
  • give each platform it’s own build directory
  • fix native build
  • add dtc config
  • Added stock radiomaster zorro loadout
  • skip UDP socket recreation when D2S IP is unchanged
  • fix arm/terminate rejected by PX4 due to broadcast target_system
  • Add unbind feature mirroring the existing bind chain
  • subscribe to voxl-vtx d2s_ip_conn pipe and update UDP destination
voxl-remote-id v0.0.9 → v0.1.0 2 changesSource CHANGELOG Diff
  • Updated to reflect a manufacturer serial number length of 10 instead of 12
  • Updated for new voxl-cross docker and linter
voxl-state-estimator v0.0.6 → v0.0.7 2 changes
  • add qcs6490 build target and CI job
  • linter fixes, use vcc_find_extrinsic
voxl-utils v2.0.5 → v2.0.10 10 changesSource CHANGELOG Diff
  • voxl-configure-static-ip-watcher factory_enable_silvus_vrx: name the Silvus radio silvus0 instead of usb0, the 0.3.x system images create the adb NCM gadget as usb0 when the USB-C port comes up in device mode (seen after a UCSI timeout), the radio’s rename then failed and it got no IP, so the Silvus link and RC dropped with the display
  • voxl-configure-static-ip-watcher: factory_enable_silvus_drone (eth0 172.19.16.10/12) and factory_enable_silvus_vrx (Silvus usb0 172.18.71.10/12, developer USB-Ethernet eth0 10.0.0.2/24, both marked unmanaged in NetworkManager so its DHCP cannot drop the address), plus a udev rule naming the radio (USB 0525:a4a2) usb0 whichever of cdc_ether/cdc_subset binds it
  • voxl-static-ip-watcher: treat an interface as up on LOWER_UP, not “state UP”, USB NICs like a Silvus radio’s report UNKNOWN
  • voxl-static-ip-watcher: only add the 10.0.0.0/24 route for an interface on 10.0.0.x, DTC VRX eth0/eth1 no longer swap it every loop
  • voxl-static-ip-watcher: match the exact address before assigning, fall back to iproute2 when ifconfig is not installed
  • voxl-inspect-services: hide voxl-wireguard and voxl-wg-config-api from the service list
  • voxl-wifi-legacy: quote args so SSIDs containing spaces are not split
  • voxl-wifi-legacy: open-network station mode and wpa_passphrase failure handling
  • voxl-wifi: validate station password length and fail on legacy script errors
  • update DTC default IP loadout
voxl-uvc-server v0.1.8 → v0.1.9 2 changesSource CHANGELOG Diff
  • Fix linter errors
  • Updated min cmake version
voxl-vision-hub v1.9.21 → v1.10.3 7 changesSource CHANGELOG Diff
  • add d0008v6 VFC config (hover 0.27, vxy_max 4, kp/kd_xy_vio 4/3, xy_acc_limit_vio 4)
  • add vfc params for d0008v6 vehicle
  • add attitude interface to avoid px4 ekf2 yaw snaps in VFC
  • seed z integrator from px4 thrust on transition into offboard, fixes altitude drop
  • pre-stream px4’s live thrust before offboard instead of config hover thrust
  • no vertical velocity lead on position entry setpoint
  • revert atr changes, back to 1.9.21
voxl-vtx v2.2.42 → v3.3.4 24 changes
  • Fix voxl-configure-vtx failing on SDK install when the VTX radio is slow to come up
  • Update button mapping on gen2 VRX
  • Update the production power measurement tool
  • Fix hires zoom issue when not on a hires camera stream
  • Add support for zoom and white/black hot control via MSP (external fc use case)
  • voxl-configure-vtx/vrx --factory_enable_silvus: video, telemetry and MAVLink over a Silvus radio
  • More detailed link statistics in VRX logs and the debug OSD
  • Add secured state to OSD menu next to SDK version
  • requires voxl-osd >= 1.2.0 on the drone
  • Add --tracking_stereo to voxl-configure-vtx for stereo (tracking left/right) camera setups
  • Refactored vrx_encoded into it’s own class and added headless mode that runs without constructing decoder
  • Fix hires zoom and thermal white/black hot conflict on the shared RC wheel
  • Fix turtle mode OSD indicator
  • Add RF occupancy scanner: sweeps the tunable band and shows per-channel occupancy and noise floor on the Qt OSD by pressing function + up/down button
  • restoring tracking-down crosshair rendering updates
  • Publish vtx_state pipe
  • Implemented AR Waypoint system
  • Update the radio calibration script
  • Add framework for sending generic requests from vrx to vtx
  • Defer libelrs init until the first PX4 heartbeat when voxl-px4 is enabled, so loading libslpi_qrb5165_io.so onto the SLPI no longer blocks PX4 startup
  • Migrate to DRM/KMS rendering backend
  • Integrate QT OSD
  • Add adaptive link functionality and replace default profile with adaptive link profile
  • Add set_elrs_hardened_state VTX control command and OSD icon showing ELRS hardening state on the VRX