<?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[Near-zero feature extraction (single camera)]]></title><description><![CDATA[<p dir="auto">Hi ModalAI team,</p>
<p dir="auto">I'm running voxl-open-vins-server on a VOXL2 Mini (SDK 1.6.2) with two AR0144 tracking cameras in a non-overlapping front + down configuration (not stereo). I would appreciate guidance.</p>
<p dir="auto">ENVIRONMENT</p>
<ul>
<li>VOXL2 Mini, SDK 1.6.2</li>
<li>voxl-open-vins-server, internal tracker (en_ext_feature_tracker not used; voxl-feature-tracker disabled)</li>
<li>2x AR0144, front + down, non-overlapping FOV</li>
<li>estimator_config.yaml (fpv): use_stereo: false, max_cameras: 2, use_klt: true, use_gpu: true, num_pts: 50, fast_threshold: 15, min_px_dist: 10, histogram_method: HISTOGRAM</li>
<li>vio_cams.conf: both cams enabled</li>
</ul>
<p dir="auto">The issue is Near-zero feature extraction (single camera):  I disabled the down camera. However, even during motion over textured, well-lit scenes, voxl-inspect-vins reports only ~1 feature, quality 0%, state OKAY, and T_imu_wrt_vio runs away (tens of meters). The estimator loop is healthy but the tracker extracts almost nothing.</p>
<p dir="auto">What I've verified / ruled out:</p>
<ul>
<li>Both camera feeds live and clean at the pipe level: 1280x800 @ 30fps, RAW8, reasonable exposure/gain (voxl-inspect-cam).</li>
<li>Intrinsics present and valid (fisheye, both cams); extrinsics validated incl. body -&gt; imu_apps (voxl-inspect-extrinsics passes).</li>
<li>IMU vibration at rest all green (voxl-inspect-vibration).</li>
<li>Tried histogram_method HISTOGRAM and NONE; min_px_dist 50 -&gt; 10; use_gpu true/false (CPU path "sticks"); switched tracking pipes off the _ion variants to plain *_misp_norm. None of these moved the feature count off ~1.</li>
</ul>
<p dir="auto">Questions:</p>
<ol>
<li>For the single-camera case, what would cause the internal tracker to return ~1 feature on a sharp, textured image with the config above?</li>
<li>Is there a recommended way to visualize the internal tracker's extracted features for OpenVINS (the cameras-tab feat_overlay pipe is empty since voxl-feature-tracker is disabled — is ov_overlay under the VIO tab the correct view)?</li>
<li>Is there updated AR0144 driver / SDK guidance for non-overlapping multi-camera VIO on the VOXL2 Mini?</li>
</ol>
<p dir="auto">Best regards,<br />
Yoni</p>
]]></description><link>https://forum.modalai.com/topic/5265/near-zero-feature-extraction-single-camera</link><generator>RSS for Node</generator><lastBuildDate>Sun, 08 Nov 2026 08:30:25 GMT</lastBuildDate><atom:link href="https://forum.modalai.com/topic/5265.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 15 Jun 2026 17:28:37 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Near-zero feature extraction (single camera) on Thu, 18 Jun 2026 19:49:57 GMT]]></title><description><![CDATA[<p dir="auto">Regarding the feature track tab, I recommend upgrading to the latest available SDK, features should show on voxl-portal.</p>
<p dir="auto">The correct overlay is under VIO indeed</p>
]]></description><link>https://forum.modalai.com/post/26182</link><guid isPermaLink="true">https://forum.modalai.com/post/26182</guid><dc:creator><![CDATA[zauberflote1]]></dc:creator><pubDate>Thu, 18 Jun 2026 19:49:57 GMT</pubDate></item><item><title><![CDATA[Reply to Near-zero feature extraction (single camera) on Thu, 18 Jun 2026 19:47:34 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/yonim" aria-label="Profile: Yonim">@<bdi>Yonim</bdi></a> Hello,<br />
Quick question: Are you using a development drone? If not, have you calibrated your extrinsics and intrinsics properly?</p>
]]></description><link>https://forum.modalai.com/post/26181</link><guid isPermaLink="true">https://forum.modalai.com/post/26181</guid><dc:creator><![CDATA[zauberflote1]]></dc:creator><pubDate>Thu, 18 Jun 2026 19:47:34 GMT</pubDate></item></channel></rss>