<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet type="text/xsl" href="https://itohi.com/feed.xsl"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Betaflight on ITOHI — Open-Source Hardware, Embedded Systems &amp; DIY Builds</title><link>https://itohi.com/categories/betaflight/</link><description>Recent content in Betaflight on ITOHI — Open-Source Hardware, Embedded Systems &amp; DIY Builds</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>2022 @ ITOHI - All rights reserved</copyright><lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://itohi.com/categories/betaflight/index.xml" rel="self" type="application/rss+xml"/><item><title>The Betaflight VTX Trap: aux_channel Is 0-Based, vtx_power Is 1-Based</title><link>https://itohi.com/fpv/betaflight-vtx-indexing-trap/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://itohi.com/fpv/betaflight-vtx-indexing-trap/</guid><description>
&lt;p&gt;Every programmer learns to count from zero. Betaflight agrees: AUX channels are 0-based, so AUX1 is &lt;code&gt;0&lt;/code&gt; and AUX6 is &lt;code&gt;5&lt;/code&gt;. Type a few CLI lines and your fingers stop thinking about it. Count from zero. It's the rule the whole configurator seems to run on.&lt;/p&gt;
&lt;p&gt;Then I lost an evening to a VTX that flatly refused to output 400 mW, and found the one field where Betaflight quietly counts from &lt;em&gt;one&lt;/em&gt; instead. Nothing warns you. The failure looked like a dead VTX, not a typo — which is exactly why it ate the whole evening.&lt;/p&gt;</description></item></channel></rss>