<?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[Video and Image Sensors]]></title><description><![CDATA[General questions regarding the VOXL SDK that do not fit into other categories]]></description><link>https://forum.modalai.com/category/51</link><generator>RSS for Node</generator><lastBuildDate>Thu, 09 Jul 2026 09:22:53 GMT</lastBuildDate><atom:link href="https://forum.modalai.com/category/51.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 01 Jun 2026 16:42:53 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[AR0144 on voxl2 J8? Or alternative 4x AR0144 Config?]]></title><description><![CDATA[@jameskuesel ,
I think there is another option which i have not considered before. The first three cameras are the same as above:
: M0173 J1: AR0144 slot 0 : CCI0
: M0173 J2: AR0144 slot 6 : CCI1
: M0173 J5: AR0144 slot 2 : CCI2

Then if we use J8U (which can be done using M0181 - it allows you to connect a Boson sensor to lower slot, and a tracking / hires camera to upper slot). Then the fourth camera would be:
VOXL2 J8: M0181 Upper : AR0144 slot 5 : CCI3

And there are no CCI conflicts.
One issue is that we don't typically sell M0181 by itself (only in a kit). Instead you could use two other options, both of which allow connecting a tracking / hires camera to the upper slot:

M0194 : https://www.modalai.com/products/m0194/
M0172: https://docs.modalai.com/M0172/ / https://www.modalai.com/products/mdk-m0172-1-00

The only down side of using M0172 / M0194 instead of M0181 is that the two alternatives do not have a mounting hole that would align with VOXL2 mounting hole, but M0181 does have a tab with a mounting hole for VOXL2 J8, see below. The M0172 and M0194 were really designed as mainly options for VOXL2 mini.
[image: 1780458131518-98d5f0ec-7f07-44bf-b002-036aefd3921d-image.png]
[image: 1780458149322-c9c77086-b5fc-4215-99a2-fdc310d6f18c-image.png]
]]></description><link>https://forum.modalai.com/topic/5233/ar0144-on-voxl2-j8-or-alternative-4x-ar0144-config</link><guid isPermaLink="true">https://forum.modalai.com/topic/5233/ar0144-on-voxl2-j8-or-alternative-4x-ar0144-config</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Mon, 01 Jun 2026 16:42:53 GMT</pubDate></item><item><title><![CDATA[Add new Seek USB thermal camera sensor]]></title><description><![CDATA[@Jskim This is the repo we use for support of UVC cameras: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-uvc-server. I don't think it will work directly with Seek cameras but you can try. In my experience each new camera requires a bit of integration work and updates to that code.
]]></description><link>https://forum.modalai.com/topic/5223/add-new-seek-usb-thermal-camera-sensor</link><guid isPermaLink="true">https://forum.modalai.com/topic/5223/add-new-seek-usb-thermal-camera-sensor</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Thu, 28 May 2026 04:04:13 GMT</pubDate></item><item><title><![CDATA[Tracking and target ID]]></title><link>https://forum.modalai.com/topic/5193/tracking-and-target-id</link><guid isPermaLink="true">https://forum.modalai.com/topic/5193/tracking-and-target-id</guid><pubDate>Mon, 04 May 2026 18:45:21 GMT</pubDate></item><item><title><![CDATA[High res camera latency]]></title><description><![CDATA[Hi @bschulzhf ,
voxl-inspect-cam -a command should not be generally used as it puts a lot of stress on the system. just use it to inspect the stream that you need, such as voxl-inspect-cam hires_down_large_color.
Also, in your camera config changes, it is not clear exactly what changes you actually made, since you did not provide a diff (but i can see that you probably disabled all the streams except for the preview stream). In any case, you should revert your changes and just inspect the stream you need to estimate the latency.
If you want to provide more information about your application, we can suggest appropriate camera server parameter changes. I do see that ae_desired_msv": 60 is potentially too dark (the target average pixel value for auto exposure control) - you can try increasing it and see if the image is too dark.
Alex
]]></description><link>https://forum.modalai.com/topic/5189/high-res-camera-latency</link><guid isPermaLink="true">https://forum.modalai.com/topic/5189/high-res-camera-latency</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Thu, 30 Apr 2026 20:17:28 GMT</pubDate></item><item><title><![CDATA[Contributing back to voxl-camera-server]]></title><link>https://forum.modalai.com/topic/5185/contributing-back-to-voxl-camera-server</link><guid isPermaLink="true">https://forum.modalai.com/topic/5185/contributing-back-to-voxl-camera-server</guid><pubDate>Tue, 28 Apr 2026 16:18:34 GMT</pubDate></item><item><title><![CDATA[Periodic Intra Video Refresh]]></title><description><![CDATA[@Anthony-Kang , we are looking into this. However, initial attempts to enable Intra Refresh on VOXL2 via the OMX api did not succeed either for h264 or h265. Also h265 does not work with fixed Macro Blocks (Coding Tree Units instead), so it seems the OMX structures for this param would not work with h265.
Alex
]]></description><link>https://forum.modalai.com/topic/5167/periodic-intra-video-refresh</link><guid isPermaLink="true">https://forum.modalai.com/topic/5167/periodic-intra-video-refresh</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Wed, 15 Apr 2026 17:18:12 GMT</pubDate></item><item><title><![CDATA[Snapshot crashes voxl-camera-server]]></title><description><![CDATA[I tested the fix and snapshots work now, thank you very much!
]]></description><link>https://forum.modalai.com/topic/5166/snapshot-crashes-voxl-camera-server</link><guid isPermaLink="true">https://forum.modalai.com/topic/5166/snapshot-crashes-voxl-camera-server</guid><dc:creator><![CDATA[rddrone]]></dc:creator><pubDate>Wed, 15 Apr 2026 13:47:05 GMT</pubDate></item><item><title><![CDATA[Camera status when voxl-camera-server is not running]]></title><description><![CDATA[@SKA ,
Most of the supported cameras (except for Boson, Hadron) have their reset signal connected to VOXL2, so when the cameras are not in use, they are shut down via the reset pin. This means that the camera modules may still get power, but they are shut down.
There are many power rails and interposers - some power rails remain on all the time (5.0, 3.8V) and others may be shut down by PMIC when not in use. Different cameras use different power rails for their operation, so it is hard to answer this question without knowing the specific use case.
Alex
]]></description><link>https://forum.modalai.com/topic/5149/camera-status-when-voxl-camera-server-is-not-running</link><guid isPermaLink="true">https://forum.modalai.com/topic/5149/camera-status-when-voxl-camera-server-is-not-running</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Thu, 02 Apr 2026 15:12:13 GMT</pubDate></item><item><title><![CDATA[Hadron ov64b snapshots have a vertical image artifact]]></title><description><![CDATA[@cguzikowski ,
Sorry for the delay.
Regarding the new HW not working, since you have two identical setups, i would recommend swapping components to identify what exactly is not working. This is the most efficient way to diagnose it. From the logs you provided, the ov64b camera is detected and initialized, it seems, but no frames come in, which could be a cabling or interposer issue.
I will get back to you with an update on the lens shading tomorrow.
Alex
]]></description><link>https://forum.modalai.com/topic/5133/hadron-ov64b-snapshots-have-a-vertical-image-artifact</link><guid isPermaLink="true">https://forum.modalai.com/topic/5133/hadron-ov64b-snapshots-have-a-vertical-image-artifact</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Wed, 25 Mar 2026 19:50:02 GMT</pubDate></item><item><title><![CDATA[How to fix the UVC camera DEVICE ID]]></title><description><![CDATA[Thank you for the quick reply.
I will try doing as you instructed and post the results.
Thank you.
Kim
]]></description><link>https://forum.modalai.com/topic/5123/how-to-fix-the-uvc-camera-device-id</link><guid isPermaLink="true">https://forum.modalai.com/topic/5123/how-to-fix-the-uvc-camera-device-id</guid><dc:creator><![CDATA[Jskim]]></dc:creator><pubDate>Mon, 23 Mar 2026 01:00:24 GMT</pubDate></item><item><title><![CDATA[Support for other Thermal Cameras]]></title><description><![CDATA[Hi @Vinny
Thank you for your reply! That's good news:)
We are looking forward to it!
]]></description><link>https://forum.modalai.com/topic/5113/support-for-other-thermal-cameras</link><guid isPermaLink="true">https://forum.modalai.com/topic/5113/support-for-other-thermal-cameras</guid><dc:creator><![CDATA[saegsali]]></dc:creator><pubDate>Wed, 18 Mar 2026 09:42:40 GMT</pubDate></item><item><title><![CDATA[EIS cam-server crash]]></title><description><![CDATA[@SKA , I am not sure. please disable all streams except preview and try again. specifically disable:

small_video
large_video
snapshot

Double check to make sure:
en_raw_preview: true
en_preview: true
en_misp : true
It seems you have at least small_video enabled.
What camera resolution are you requesting? (preview_width, preview_height)
Alex
]]></description><link>https://forum.modalai.com/topic/5087/eis-cam-server-crash</link><guid isPermaLink="true">https://forum.modalai.com/topic/5087/eis-cam-server-crash</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Fri, 06 Mar 2026 14:45:32 GMT</pubDate></item><item><title><![CDATA[IMX664 MISP decoding issue]]></title><description><![CDATA[Hi @Alex-Kushleyev, sorry for the late reaction, it took some time before i could update to the new SDK (1.6). the system now works normally with the resolution 2704x1540, and downscaled to 1920x1080 for the MISP pipeline. Thanks for the help!
]]></description><link>https://forum.modalai.com/topic/5072/imx664-misp-decoding-issue</link><guid isPermaLink="true">https://forum.modalai.com/topic/5072/imx664-misp-decoding-issue</guid><dc:creator><![CDATA[mark]]></dc:creator><pubDate>Thu, 26 Feb 2026 08:49:57 GMT</pubDate></item><item><title><![CDATA[VOXL2 QVIO Auto-Resets &amp; I²C Errors on Startup]]></title><description><![CDATA[@yashpatel ,
Please see some responses below:
i2c_geni a84000.i2c / 884000.i2c: i2c error :-107

This is likely due to a service that is enabled for a sensor that's not present, so the service is restarting and trying to detect the sensor.

please make sure the voxl-rangefinder-server is not running and also voxl-lepton-server. you can disable the service using systemd : systemctl disable voxl-rangefinder-server.

CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22

this one is usually present when you have a sensormodule driver in /usr/lib/camera for a camera that is not actually plugged in, so the probe fails. Double check the cameras that you have plugged in vs sensormodules peresent in the directory above. However, this is usually harmless, if all of your cameras are working properly.
Pin conflict.. We will double check that, but GPIO 130 is on a Board to Board connector that you are most likely not using, so that should not be an issue.
VIO performance..

please review : https://docs.modalai.com/flying-with-vio/
try to identify the condition that caused the low feature count (look at the actual images, if possible). may need some hand-held testing and looking at the output.

Please let us know if you have any other questions.
Alex
]]></description><link>https://forum.modalai.com/topic/5066/voxl2-qvio-auto-resets-i-c-errors-on-startup</link><guid isPermaLink="true">https://forum.modalai.com/topic/5066/voxl2-qvio-auto-resets-i-c-errors-on-startup</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Wed, 18 Feb 2026 22:05:34 GMT</pubDate></item><item><title><![CDATA[M0173 with 4 AR0144 Tracking cameras]]></title><description><![CDATA[@Alex-Kushleyev sure thing. As per your suggestion, I modified voxl-lepton-server by moving all the Lepton camera-specific logic into a C++ class and added locks to any I2C operations to prevent race conditions. I then just created 2 instances of the LeptonCamera class I made which parse and publish the camera feeds to their own pipes which I can view in voxl-portal.
I didn't need to disable any I2C interface for the second Lepton. I'm not too sure what you were referring to by that.
In regards to the horizontal line artifacts, those don't seems to consistently appear and I don't know what causes it. I'll investigate it further.
My next steps are to get the Leptons working with voxl-open-vins-server. One question I had was that our VOXL 2 Mini appears to be running a service called voxl-lepton-tracker however I cannot find the source code for this anywhere on the voxl public GitLab. Was it removed or hidden?
]]></description><link>https://forum.modalai.com/topic/5010/m0173-with-4-ar0144-tracking-cameras</link><guid isPermaLink="true">https://forum.modalai.com/topic/5010/m0173-with-4-ar0144-tracking-cameras</guid><dc:creator><![CDATA[Haxerus]]></dc:creator><pubDate>Mon, 26 Jan 2026 16:31:39 GMT</pubDate></item><item><title><![CDATA[Calibration for EIS]]></title><description><![CDATA[Another question.. did this work for you before or is this the first time trying to calibrate at half resolution? if you request the full resolution, do you get the non-zoomed image? i know it will be slow to display in voxl-portal, but you could still check.
If you enable EIS with default camera calibration (no intrinsics cal file). does EIS and zoom work as expected? note that your version of voxl-portal may not have the browser support for zooming, but the config file zoom should still work. If you want to use the latest voxl-portal for EIS, please use this branch : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-portal/-/tree/eis-integration . however the initial zoom of the image coming from the camera server is not dependent on the version of voxl-portal.
Alex
]]></description><link>https://forum.modalai.com/topic/5004/calibration-for-eis</link><guid isPermaLink="true">https://forum.modalai.com/topic/5004/calibration-for-eis</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Thu, 22 Jan 2026 20:01:55 GMT</pubDate></item><item><title><![CDATA[camera not working and missing configuration]]></title><description><![CDATA[@mkriesel You'll need to re-flash the SDK and select the correct kernel option that supports C11.
When running ./install.sh you'll see the following options:
Would you like to continue with SDK install?
1) Yes, with questions along the way to configure VOXL 2
2) Yes, just update SDK keeping the same SKU configuration
3) No

Select, option 1, and you'll get the option to choose which kernel to flash
Detected: M0054-1 (QRB5165M)
Detected: Config 1 w/ M0173 Breakout Board (Starling 2 Max, Starling 2, FPV V5)

=======================================================================================================
In order to support all of VOXL's camera configurations, specific drones require differing kernel images.
Please select your drone hardware to proceed with flashing the appropriate kernel image.
=======================================================================================================

PLEASE SELECT WHICH KERNEL TO FLASH
0. M0054-1 -&gt; QRB5165M, Starling (D0005), Sentinel (D0006), FPV V4 (D0008), D0010, PX4 Dev Kit (D0011)
1. M0054-1 -&gt; QRB5165M w/ M0173 Camera Breakout Board, Starling 2 Max (D0012), Starling 2 (D0014), FPV V5 (D0008/D0019/D0020)

Select your choice from the options above
or press [Enter] to continue with current config: 

For your use case, you'll want to select option 0 as you are not using an M0173 camera breakout board and the C11 camera config is inherited from the sentinel (D0006) platform.
]]></description><link>https://forum.modalai.com/topic/4963/camera-not-working-and-missing-configuration</link><guid isPermaLink="true">https://forum.modalai.com/topic/4963/camera-not-working-and-missing-configuration</guid><dc:creator><![CDATA[tom]]></dc:creator><pubDate>Mon, 05 Jan 2026 21:36:33 GMT</pubDate></item><item><title><![CDATA[Minimizing voxl-camera-server CPU usage in SDK1.6]]></title><description><![CDATA[Hi @Rowan-Dempster ,
We just merged the changes to dev : https://gitlab.com/voxl-public/voxl-sdk/core-libs/libmodal-pipe/-/merge_requests/39.
A new build of the libmodal-pipe library will be added after tonight's nightly build here : http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/ .
Any SDK releases after this will include this support.
Alex
]]></description><link>https://forum.modalai.com/topic/4893/minimizing-voxl-camera-server-cpu-usage-in-sdk1-6</link><guid isPermaLink="true">https://forum.modalai.com/topic/4893/minimizing-voxl-camera-server-cpu-usage-in-sdk1-6</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Wed, 26 Nov 2025 17:48:18 GMT</pubDate></item><item><title><![CDATA[tracking down pipe switching to images of traccking front camera]]></title><description><![CDATA[Hi @mark ,
Thank you for the update. We will keep investigating the underlying issue that was a result of that questionable camera.
Meanwhile, if you think that the camera is defective and has no damage, you can fill out an RMA request and send it back for an exchange. I cant really comment on what could be causing this on the camera itself (it would be interesting to try it), but the camera is not serviceable by the user.
https://www.modalai.com/pages/rma
Alex
]]></description><link>https://forum.modalai.com/topic/4892/tracking-down-pipe-switching-to-images-of-traccking-front-camera</link><guid isPermaLink="true">https://forum.modalai.com/topic/4892/tracking-down-pipe-switching-to-images-of-traccking-front-camera</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Wed, 26 Nov 2025 16:02:10 GMT</pubDate></item><item><title><![CDATA[EIS functionality]]></title><description><![CDATA[@SKA ,
Does this happen right away after you start voxl-camera-server ?
What raw "preview" resolution / fps are you requesting in camera server config?
Also, can you post output of dmesg (everything after you start voxl-camera-server)
Alex
]]></description><link>https://forum.modalai.com/topic/4843/eis-functionality</link><guid isPermaLink="true">https://forum.modalai.com/topic/4843/eis-functionality</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Wed, 29 Oct 2025 16:01:25 GMT</pubDate></item><item><title><![CDATA[Boson 640 MIPI M0153 16-bit]]></title><description><![CDATA[save image on voxl:
voxl-record-raw-image boson640_bayer -n 1 -d ./

display image using python3:
import cv2
import numpy as np

WIDTH  = 640
HEIGHT = 512
FILENAME = "boson640_bayer_640x512.gray"

# read 16-bit file
img = np.fromfile(FILENAME, dtype=np.uint16).reshape(HEIGHT, WIDTH)

# simple normalize
vmin     = np.min(img)
vmax     = np.max(img)
img_8bit = cv2.convertScaleAbs(img-vmin, alpha=255.0/(vmax-vmin))

# show image
cv2.imshow("Normalized Image", img_8bit)
cv2.waitKey(3000)
cv2.destroyAllWindows()

[image: 1761928549434-b0c7843e-dbec-41e6-918b-b0f25085ee82-image.png]
]]></description><link>https://forum.modalai.com/topic/4794/boson-640-mipi-m0153-16-bit</link><guid isPermaLink="true">https://forum.modalai.com/topic/4794/boson-640-mipi-m0153-16-bit</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Thu, 02 Oct 2025 20:21:22 GMT</pubDate></item><item><title><![CDATA[J8 Sensor Header Use with M0173 Micro-Coax Kit on VOXL2]]></title><description><![CDATA[Hi @Alex-Kushleyev, thank you kindly for the support and apologies for the late response. My earlier question was for an attempt to equip an M0173 to VOXL2 for a C26/27/28 config, plus an M0010 stereo pair on a M0076 interposer on VOXL J8 (sorry for the lack of clarity). Our team is now looking to use a default camera config for M0173, but minus the ToF sensor and with an added M0161 4K Hires camera connected to VOXL J8 via the M0155 adapter. Planning to test this hardware config shortly
]]></description><link>https://forum.modalai.com/topic/4792/j8-sensor-header-use-with-m0173-micro-coax-kit-on-voxl2</link><guid isPermaLink="true">https://forum.modalai.com/topic/4792/j8-sensor-header-use-with-m0173-micro-coax-kit-on-voxl2</guid><dc:creator><![CDATA[isaac]]></dc:creator><pubDate>Thu, 02 Oct 2025 19:41:49 GMT</pubDate></item><item><title><![CDATA[VOXL2-Mini (QRB5165): YOLO on NPU&#x2F;NNAPI or GPU keeps falling back to CPU. Looking for a known-good export&#x2F;runtime path (or QNN&#x2F;HTP).]]></title><link>https://forum.modalai.com/topic/4789/voxl2-mini-qrb5165-yolo-on-npu-nnapi-or-gpu-keeps-falling-back-to-cpu-looking-for-a-known-good-export-runtime-path-or-qnn-htp</link><guid isPermaLink="true">https://forum.modalai.com/topic/4789/voxl2-mini-qrb5165-yolo-on-npu-nnapi-or-gpu-keeps-falling-back-to-cpu-looking-for-a-known-good-export-runtime-path-or-qnn-htp</guid><pubDate>Wed, 01 Oct 2025 20:51:17 GMT</pubDate></item><item><title><![CDATA[voxl-camera-server segmentation fault]]></title><description><![CDATA[@psafi ,
There was a libmodal-pipe library update earlier this week, so if you have updated that library on your VOXL2, then any other library or app (which uses libmodal-pipe) that you deploy to that VOXL2 needs to be built against the same version of libmodal-pipe.
So if you want use the latest dev version, you would update the drone.
make sure you are using dev for apt sources:
in /etc/apt/sources.list.d/modalai.list:
deb [trusted=yes] http://voxl-packages.modalai.com/ ./dists/qrb5165/dev/binary-arm64/

then update libmodal-pipe on VOXL2, this should also update any other packages that depend on it.
apt update
apt install libmodal-pipe

When building your application using voxl-cross docker, make sure you run the following in order to get the latest deps from dev:
./install_build_deps.sh qrb5165 dev

Most of the time you can get away not doing this, but this time there was an interface change in libmodal-pipe, so a mismatch occurred.
Alex
]]></description><link>https://forum.modalai.com/topic/4763/voxl-camera-server-segmentation-fault</link><guid isPermaLink="true">https://forum.modalai.com/topic/4763/voxl-camera-server-segmentation-fault</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Tue, 23 Sep 2025 18:04:18 GMT</pubDate></item><item><title><![CDATA[Voxl 2 Mini with Starvis 2 not detected]]></title><description><![CDATA[@aheyne ,
Thank you for the update.
Please note that our standard configuration 50 has the IMX664 camera in slot 3, as shown in the link below ( J7 upper = slot ID 3). Since it is the only camera connected in this config, it would still show up as ID 0 in the voxl-camera-server.conf file.
https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/misc_files/usr/share/modalai/voxl-camera-server/standard_configs/platform_config_2/50 - MVX-T0001 voxl2 mini hires imx664
Also, i think you meant that you copied the com.qti.sensormodule.imx664_1.bin file, not 3 after running voxl-configure-cameras.
The extra sensormodule file for slot number 3 in this case does not do anything because there is no camera actually connected in slot 3, so the camera pipeline will just try to probe the camera in this slot and will fail and move on. In general. I would recommend having only the sensormodule files that you are actually using in /usr/lib/camera in order to avoid any confusion in the future.
Also, thank you for letting me know what happened when you connected the camera to the wrong ucoax port (J1L, which is designed for a Boson camera, which needs 5V). Yes, the camera shorted the 5V rail to ground inside the camera, but it seems it has survived? Don't try it again 
By the way, did you have to update the kernel?
Is there anything else I can help you with, so you can get the most use of the IMX664 camera?
Alex
]]></description><link>https://forum.modalai.com/topic/4752/voxl-2-mini-with-starvis-2-not-detected</link><guid isPermaLink="true">https://forum.modalai.com/topic/4752/voxl-2-mini-with-starvis-2-not-detected</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Thu, 18 Sep 2025 21:35:25 GMT</pubDate></item></channel></rss>