<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[VOXL SDK]]></title><description><![CDATA[General questions regarding the VOXL SDK that do not fit into other categories]]></description><link>https://forum.modalai.com/category/47</link><generator>RSS for Node</generator><lastBuildDate>Wed, 12 Aug 2026 10:54:14 GMT</lastBuildDate><atom:link href="https://forum.modalai.com/category/47.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 03 Aug 2026 12:12:27 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[voxl-mavcam-manager in differnt versions]]></title><description><![CDATA[Hey Arvind,
Could you try using this version of voxl-camera-server: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-camera-server_2.2.32-202607291154_arm64.deb
Im able to get 2 camera streams, and every time I click the save picture button on QGC I see the snapshots saved without any issues.
Heres some versions of my packages I am using:
voxl-camera-server             2.2.32
voxl-mavcam-manager            0.6.1-202601081558
voxl-streamer                  0.8.1
]]></description><link>https://forum.modalai.com/topic/5360/voxl-mavcam-manager-in-differnt-versions</link><guid isPermaLink="true">https://forum.modalai.com/topic/5360/voxl-mavcam-manager-in-differnt-versions</guid><dc:creator><![CDATA[ApoorvThapliyal]]></dc:creator><pubDate>Mon, 03 Aug 2026 12:12:27 GMT</pubDate></item><item><title><![CDATA[Version upgrade]]></title><description><![CDATA[@royazriel ,
We do not recommend doing apt upgrade, since we do not test this update method. If you want to update the SDK, you should do that following our SDK install instructions.
As an advanced user, you may select to update your apt sources to use dev releases (basically latest dev branches) and selectively install packages that you want to test.
The recommended SDK release for Starling 2 (Max) is 1.6.4
With that in mind, please let us know if you have any more questions about this.
Alex
]]></description><link>https://forum.modalai.com/topic/5354/version-upgrade</link><guid isPermaLink="true">https://forum.modalai.com/topic/5354/version-upgrade</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Thu, 30 Jul 2026 11:29:03 GMT</pubDate></item><item><title><![CDATA[Platform-Specific PX4 Bug - Incorrect Evaluation of NaN]]></title><description><![CDATA[And the latest build of our fork with this fix is here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.146-202607161052_arm64.deb
]]></description><link>https://forum.modalai.com/topic/5320/platform-specific-px4-bug-incorrect-evaluation-of-nan</link><guid isPermaLink="true">https://forum.modalai.com/topic/5320/platform-specific-px4-bug-incorrect-evaluation-of-nan</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Wed, 15 Jul 2026 16:08:33 GMT</pubDate></item><item><title><![CDATA[[VOXL-SVC] WAIT_VIO: VIO velocity unstable (VIO backend converging) (30 s)]]></title><description><![CDATA[Hello @royazriel , please take a look at our documentation, which has some testing tips : https://docs.modalai.com/voxl-open-vins-server/
]]></description><link>https://forum.modalai.com/topic/5305/voxl-svc-wait_vio-vio-velocity-unstable-vio-backend-converging-30-s</link><guid isPermaLink="true">https://forum.modalai.com/topic/5305/voxl-svc-wait_vio-vio-velocity-unstable-vio-backend-converging-30-s</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Thu, 02 Jul 2026 15:50:33 GMT</pubDate></item><item><title><![CDATA[voxl-suite upgrade]]></title><description><![CDATA[@RoyAzriel 1.6.4 release is tested on Starling 2 now, go ahead and use that from the link I emailed you.
]]></description><link>https://forum.modalai.com/topic/5303/voxl-suite-upgrade</link><guid isPermaLink="true">https://forum.modalai.com/topic/5303/voxl-suite-upgrade</guid><dc:creator><![CDATA[tom]]></dc:creator><pubDate>Wed, 01 Jul 2026 11:54:07 GMT</pubDate></item><item><title><![CDATA[dsp is not running]]></title><description><![CDATA[@Eric-Katzfey thanks. before I did sdk reflash I found out the px4 params were somehow corrupted. I have tried to reproduce these values without success.
what made it work is taking a similar drawn read the params usign px4-param show -a and writing the to the corrupted one.
]]></description><link>https://forum.modalai.com/topic/5274/dsp-is-not-running</link><guid isPermaLink="true">https://forum.modalai.com/topic/5274/dsp-is-not-running</guid><dc:creator><![CDATA[RoyAzriel]]></dc:creator><pubDate>Thu, 18 Jun 2026 13:23:50 GMT</pubDate></item><item><title><![CDATA[Latest SDK versions - How to access?]]></title><description><![CDATA[@tom said in Latest SDK versions - How to access?:

https://storage.googleapis.com/platform-beta-releases/voxl2/voxl2_SDK_1.6.4-beta8.tar.gz

Thanks @tom !!!
]]></description><link>https://forum.modalai.com/topic/5250/latest-sdk-versions-how-to-access</link><guid isPermaLink="true">https://forum.modalai.com/topic/5250/latest-sdk-versions-how-to-access</guid><dc:creator><![CDATA[nl_vdi]]></dc:creator><pubDate>Fri, 05 Jun 2026 21:24:15 GMT</pubDate></item><item><title><![CDATA[voxl portal qvio]]></title><link>https://forum.modalai.com/topic/5227/voxl-portal-qvio</link><guid isPermaLink="true">https://forum.modalai.com/topic/5227/voxl-portal-qvio</guid><pubDate>Fri, 29 May 2026 10:33:26 GMT</pubDate></item><item><title><![CDATA[Request for How to use SPI (J10 port) in SDK 1.45-VOXL2-mini]]></title><description><![CDATA[Hi Kim,
There are a couple changes required here that will make this work:
1. Rebuilding Kernel with SPI14 enabled
You're going to have to rebuild and flash the kernel with QUP14 enabled as SPI. There is also a directional level shifter on GPIO67 that needs to be set to high in order for SPI on QUP 14 to work. I created this branch for you that should have the kernel changes that you need:

feature/voxl2-mini-spi-qup14 (link)

In order to actually build and flash the kernel please follow the instructions from our public docs on how to build the kernel

https://docs.modalai.com/voxl2-kernel-build-guide/

When building the kernel, after syncing but before building, make sure to go to the cloned meta-voxl2-bsp directory and checkout the branch that I created (feature/voxl2-mini-spi-qup14).
Also there is a chance you may need to build a kernel variant depending on your device so also make sure to check this document to see if you have a -2 device which would require building the kernel with the -v var02 flag

https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2

2. Configuring Trustzone with Correct QUP
I would recommend using the devcfg binary that comes from the `voxl2-mini_SDK_1.0.0.tar.gz. In order to flash devcfg you'll want to run the following command
fastboot flash devcfg &lt;path/to/voxl2-mini_SDK_1.0.0/devcfg&gt;/devcfg.mbn

You should flash the kernel and devcfg (Trustzone) during the same fastboot session to avoid running into any issues with the device booting.
Let me know if you have any additional questions or run into any issues!
]]></description><link>https://forum.modalai.com/topic/5200/request-for-how-to-use-spi-j10-port-in-sdk-1-45-voxl2-mini</link><guid isPermaLink="true">https://forum.modalai.com/topic/5200/request-for-how-to-use-spi-j10-port-in-sdk-1-45-voxl2-mini</guid><dc:creator><![CDATA[Hector Nevarez]]></dc:creator><pubDate>Fri, 08 May 2026 02:16:41 GMT</pubDate></item><item><title><![CDATA[QRB5165 emulator image 1.6]]></title><description><![CDATA[@Alex-Kushleyev Thank you so much for your response. It helped a lot.
]]></description><link>https://forum.modalai.com/topic/5179/qrb5165-emulator-image-1-6</link><guid isPermaLink="true">https://forum.modalai.com/topic/5179/qrb5165-emulator-image-1-6</guid><dc:creator><![CDATA[huy]]></dc:creator><pubDate>Thu, 23 Apr 2026 12:06:03 GMT</pubDate></item><item><title><![CDATA[voxl-vtx and voxl-vrx source not on gitlab?]]></title><description><![CDATA[@Alan_S The voxl-vtx repository is currently private, the source code for both voxl-vtx and voxl-vrx are contained within.
]]></description><link>https://forum.modalai.com/topic/5164/voxl-vtx-and-voxl-vrx-source-not-on-gitlab</link><guid isPermaLink="true">https://forum.modalai.com/topic/5164/voxl-vtx-and-voxl-vrx-source-not-on-gitlab</guid><dc:creator><![CDATA[tom]]></dc:creator><pubDate>Tue, 14 Apr 2026 17:59:53 GMT</pubDate></item><item><title><![CDATA[Latest voxl-cross images missing?]]></title><description><![CDATA[@ZuraNeb Perfect! Thank you!
]]></description><link>https://forum.modalai.com/topic/5163/latest-voxl-cross-images-missing</link><guid isPermaLink="true">https://forum.modalai.com/topic/5163/latest-voxl-cross-images-missing</guid><dc:creator><![CDATA[Alan_S]]></dc:creator><pubDate>Mon, 13 Apr 2026 17:30:05 GMT</pubDate></item><item><title><![CDATA[Multiple Critical Bugs in voxl-imu-server: Incorrect FIFO Latching and HiRes Indexing (ICM-42688)]]></title><description><![CDATA[@Alex-Kushleyev Hi Alex,
Thank you for the clarification.
That makes sense regarding the accel parsing—agreed that a 4 LSB discrepancy on a 20-bit value is negligible compared to in-flight noise, but it’s good to see it will be corrected.
Appreciate you taking the time to investigate and confirm.
Igor
]]></description><link>https://forum.modalai.com/topic/5147/multiple-critical-bugs-in-voxl-imu-server-incorrect-fifo-latching-and-hires-indexing-icm-42688</link><guid isPermaLink="true">https://forum.modalai.com/topic/5147/multiple-critical-bugs-in-voxl-imu-server-incorrect-fifo-latching-and-hires-indexing-icm-42688</guid><dc:creator><![CDATA[Igor]]></dc:creator><pubDate>Wed, 01 Apr 2026 19:45:08 GMT</pubDate></item><item><title><![CDATA[Starling 2 &#x2F; VOXL2 M0129 ESC not detected during voxl-esc scan or firmware upgrade]]></title><link>https://forum.modalai.com/topic/5125/starling-2-voxl2-m0129-esc-not-detected-during-voxl-esc-scan-or-firmware-upgrade</link><guid isPermaLink="true">https://forum.modalai.com/topic/5125/starling-2-voxl2-m0129-esc-not-detected-during-voxl-esc-scan-or-firmware-upgrade</guid><pubDate>Mon, 23 Mar 2026 16:37:19 GMT</pubDate></item><item><title><![CDATA[Ubuntu 20.04]]></title><description><![CDATA[@fhaltmayer , unfortunately, we do not have any updates at this time. It looks like we may never release Ubuntu 20.04 for VOXL2 because it is a LOT of work to switch to a new major Ubuntu release and test + maintain everything. Additionally, even Ubuntu 20.04 is already relatively old, so we are trying to focus our efforts on more forward-looking software development with larger impact.
Alex
]]></description><link>https://forum.modalai.com/topic/5114/ubuntu-20-04</link><guid isPermaLink="true">https://forum.modalai.com/topic/5114/ubuntu-20-04</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Wed, 18 Mar 2026 16:45:32 GMT</pubDate></item><item><title><![CDATA[Connect qrb5165-emulator to voxl-gazebo-docker]]></title><link>https://forum.modalai.com/topic/5086/connect-qrb5165-emulator-to-voxl-gazebo-docker</link><guid isPermaLink="true">https://forum.modalai.com/topic/5086/connect-qrb5165-emulator-to-voxl-gazebo-docker</guid><pubDate>Thu, 05 Mar 2026 17:13:13 GMT</pubDate></item><item><title><![CDATA[Starling-2 Max]]></title><link>https://forum.modalai.com/topic/5082/starling-2-max</link><guid isPermaLink="true">https://forum.modalai.com/topic/5082/starling-2-max</guid><pubDate>Wed, 04 Mar 2026 10:10:29 GMT</pubDate></item><item><title><![CDATA[voxl-cross error when building voxl-open-vins-server]]></title><description><![CDATA[@bendraper
Hello,
I hope this quick clarification helps for warnings:
CMake Policy warnings: OV internally (external dir in the repo) still uses boost and references an older cmake version -- it's a harmless warning for devs (as you are building from scratch)
Yaml-cpp lib warnings: This is a third party dependency that gets compiled from scratch during the make/build process. We use C++ 17 but the library is based on an older C++ version; nevertheless, it compiles fine on C++ 17 with minor warnings.  -- it's a harmless warning
TrackOCL warning: ModalFlow is a core library written in C++ 17 that allows function call usage as done in TrackOCL, i.e., the narrowing conversion is harmless in this case.
That being said, we are actively working on the dev branch, so all flight--impacting warnings are hopefully caught early. We currently have no flight-impacting warnings/bugs identified, but if you found one warning/bug that caught your attention, please feel free to share.
All the best,
ZBFT
]]></description><link>https://forum.modalai.com/topic/5076/voxl-cross-error-when-building-voxl-open-vins-server</link><guid isPermaLink="true">https://forum.modalai.com/topic/5076/voxl-cross-error-when-building-voxl-open-vins-server</guid><dc:creator><![CDATA[zauberflote1]]></dc:creator><pubDate>Thu, 26 Feb 2026 20:31:35 GMT</pubDate></item><item><title><![CDATA[Can&#x27;t start PX4 PCA9685 Driver]]></title><description><![CDATA[@Alex-Kushleyev Found the reason why it was skipping. In /px4-firmware/src/lib/parameters/CMakeLists.txt there is a line that skips all modules that match 'pwm_out'. I was able to disable that for PCA9685. Once I disabled the module.yaml file being skipped it worked. No need for the .c file (which makes sense, that is just the old way to do the .yaml)
]]></description><link>https://forum.modalai.com/topic/5037/can-t-start-px4-pca9685-driver</link><guid isPermaLink="true">https://forum.modalai.com/topic/5037/can-t-start-px4-pca9685-driver</guid><dc:creator><![CDATA[cbay]]></dc:creator><pubDate>Fri, 06 Feb 2026 16:17:10 GMT</pubDate></item><item><title><![CDATA[EGL example for voxl2]]></title><description><![CDATA[@Andrew-Jong , we are able to reproduce the error that you are seeing. I believe that you may need to set up a virtual display in order to get this to work. You could try doing so using Weston compositor, which would normally run if the display was available. Please try it and let us know if you are able to get it to work (or not).
You would need to create a config file /etc/xdg/weston/weston.ini
and try running it manually like this :
weston --idle-time=0 --config=/etc/xdg/weston/weston.ini

a sample config file might look something like this:
# configuration file for Weston
[core]
idle-time=0
repaint-window=15

[output]
name=virtual-1
mode=on

We have not tested this yet, but hopefully it's a good start.
Alex
]]></description><link>https://forum.modalai.com/topic/5016/egl-example-for-voxl2</link><guid isPermaLink="true">https://forum.modalai.com/topic/5016/egl-example-for-voxl2</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Wed, 28 Jan 2026 21:56:59 GMT</pubDate></item><item><title><![CDATA[Trouble configuring Boson+ on Voxl2]]></title><description><![CDATA[@Samuel-Lehman
If you have the original adapter for Boson+ which allows you to connect it to a USB port, then you can use the FLIR SDK (we use Boson Plus SDK 4.0). Unfortunately, M0153 board does not have J3 connector populated, which would allow you to connect a serial-to-usb adapter to it.
We have several python scripts, which use the Boson SDK to help set up the Boson sensor without the GUI.
query basic sensor info:
https://storage.googleapis.com/modalai_public/temp/boson/boson_read.py
set up sensor for 8bit MIPI mode, 60fps (option to set 30fps):
https://storage.googleapis.com/modalai_public/temp/boson/boson_set_8bit.py
You can put both of these scripts next to the BosonSDK directory and run them. Please check the USB port name inside the scripts.
Once you get that configured, you can put M0153 back on boson. Regarding where to plug it in on Voxl2, please tell me what other cameras you plan to use with your Boson.
Alex
]]></description><link>https://forum.modalai.com/topic/4998/trouble-configuring-boson-on-voxl2</link><guid isPermaLink="true">https://forum.modalai.com/topic/4998/trouble-configuring-boson-on-voxl2</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Tue, 20 Jan 2026 22:53:48 GMT</pubDate></item><item><title><![CDATA[Toolchain for m0054-data-fs.ext4]]></title><description><![CDATA[@Moderator Hi Modal,

Does this mean you can create a custom data file partition that you can flash using fastboot?

Yes that is correct.

We have not explored this before but it has been asked a few times. This could be very helpful for other developers.

I'm certainly hopeful that it will be helpful here at Cleo Robotics! So far with my prototyping it works as expected and cuts flashing time of some large docker images we have here at Cleo down by a noticeable fraction (no file overhead via fastboot like with ADB).
I think the snippet I posted covers the baseline functionality of getting a custom "payload" into the data partition. However if there is more I can elaborate on in terms of the toolchain / what's in the payload, and if that elaboration will be helpful to other VOXL2 developers, I would be happy to elaborate  Just let me know!
Other similar discussion points I tackled recently that I'm happy to talk about lessons of:

Flashing the system image and VOXL/CLEO SDK through a Windows Machine (journeys in USB device drivers)
Building Flutter applications for uniform flashing process across all operating systems
Building release bundles (i.e. a collection of partition binaries) in CI

]]></description><link>https://forum.modalai.com/topic/4934/toolchain-for-m0054-data-fs-ext4</link><guid isPermaLink="true">https://forum.modalai.com/topic/4934/toolchain-for-m0054-data-fs-ext4</guid><dc:creator><![CDATA[Rowan Dempster]]></dc:creator><pubDate>Wed, 17 Dec 2025 17:25:13 GMT</pubDate></item><item><title><![CDATA[voxl-px4 vs mainline px4 SITL questions]]></title><description><![CDATA[@jmltt
Looks the same bug as here: https://github.com/PX4/PX4-Autopilot/issues/22148
Added the change from this commit and it looks like it works now: https://github.com/PX4/PX4-Autopilot/pull/22194/commits/38f3c711084b349cb9ed82cf44ff181c6a40738a
]]></description><link>https://forum.modalai.com/topic/4930/voxl-px4-vs-mainline-px4-sitl-questions</link><guid isPermaLink="true">https://forum.modalai.com/topic/4930/voxl-px4-vs-mainline-px4-sitl-questions</guid><dc:creator><![CDATA[jmltt]]></dc:creator><pubDate>Tue, 16 Dec 2025 17:28:20 GMT</pubDate></item><item><title><![CDATA[Remote ID over Wifi]]></title><link>https://forum.modalai.com/topic/4904/remote-id-over-wifi</link><guid isPermaLink="true">https://forum.modalai.com/topic/4904/remote-id-over-wifi</guid><pubDate>Thu, 04 Dec 2025 20:09:18 GMT</pubDate></item></channel></rss>