Battery Telemetry and OSD Monitoring: Voltage, Current, and Capacity Explained
The on-screen display (OSD) is the FPV pilot’s instrument panel, and battery telemetry is the most critical data it provides. Unlike a car’s fuel gauge, which reports a simple percentage, a LiPo or Li-ion battery’s state of charge must be inferred from a combination of voltage, current, and consumed capacity measurements — each with its own limitations and failure modes. Understanding how these telemetry elements work, how they can mislead, and how to configure warnings appropriately is essential knowledge for every pilot who wants to land safely with healthy batteries rather than crater into the ground with a dead pack.
Voltage-Based Monitoring: The Simplest Method and Its Limitations
Voltage is the most universally available battery metric and the easiest to understand: a fully charged LiPo cell sits at 4.20V, and as the pack discharges, voltage drops in a characteristic curve. The discharge curve has three distinct regions — a steep initial drop from 4.20V to approximately 3.80V over the first 10–15% of capacity, a relatively flat plateau from 3.80V to 3.50V spanning roughly 60–70% of the usable capacity, and a final steep drop from 3.50V to 3.00V over the last 15–20% of capacity. Betaflight’s default “Land Now” warning triggers at 3.50V per cell under load, which corresponds to approximately 20% remaining capacity under the assumption of moderate current draw.
The fundamental limitation of voltage-based monitoring is voltage sag — the temporary voltage depression that occurs whenever current is drawn from the battery. A pack that reads 3.80V per cell at rest may sag to 3.40V per cell during a full-throttle punch-out. A voltage-based warning set at 3.50V will trigger prematurely during hard flying even though the pack has substantial capacity remaining, and then clear when throttle is reduced and voltage recovers. This “bouncing” warning behavior trains pilots to ignore low-voltage alerts — a dangerous habit that leads to over-discharge. Voltage-based monitoring works well for gentle cruising where current draw is relatively constant and sag is predictable, but it becomes unreliable during aggressive flying where current draw varies dramatically from second to second.
Capacity-Based Monitoring: The mAh Counter Method
Capacity-based monitoring, displayed in Betaflight as “mAh Drawn” or “Battery Capacity,” avoids the voltage sag problem by measuring the total charge removed from the battery via the current sensor. If you fly a 1300 mAh pack and land when the OSD shows 1040 mAh consumed (80% of capacity), you have discharged to a safe storage-adjacent level regardless of what the voltage was doing during flight. The “Battery Average Cell Voltage” element in Betaflight 4.3 and later shows a voltage figure that has been smoothed over several seconds, reducing the sag-induced false warnings that plague raw voltage monitoring.
The accuracy of capacity-based monitoring depends entirely on the current sensor’s calibration. Betaflight’s current sensor can be either an onboard ADC-based sensor built into the flight controller or an external sensor on the ESC or power distribution board. Onboard sensors are notoriously inaccurate out of the box, with errors of 20–30% being common. External sensors on quality hardware (such as the BLHeli_32 current sensor on modern ESCs) are more accurate but still require calibration. The calibration process involves flying a fully charged pack through a complete discharge, comparing the charger’s reported mAh put back into the pack against Betaflight’s reported mAh consumed, and adjusting the current meter scale in the Betaflight Power and Battery tab. The formula is straightforward: new scale = old scale × (charger mAh / OSD mAh). For example, if the charger put back 1200 mAh but the OSD reported 1000 mAh consumed, the scale should be increased by 20% (multiplied by 1.2). Two or three calibration cycles typically bring the error under 3%, at which point capacity-based monitoring becomes the most reliable method for battery management.
Current Sensor Calibration Procedure
Proper current sensor calibration follows a specific sequence. First, ensure Betaflight is configured with the correct current sensor source — this is set in the Configuration tab under “Battery Voltage Sensor Source” and “Current Meter Source.” For most modern builds, the current source should be “ESC Sensor” if using BLHeli_32 ESCs or “Onboard ADC” if using the flight controller’s built-in sensor. Second, verify the current meter scale value — the default of 400 is correct for many flight controllers with built-in sensors but may need to be adjusted based on your specific hardware documentation. Third, set the offset to zero initially and perform a calibration flight. Fly from a fully charged pack down to approximately 3.5V per cell resting voltage (after landing and waiting 30 seconds for voltage recovery). Note the mAh consumed from the OSD or the post-flight stats screen. Charge the pack fully and note the mAh the charger reports putting back in. Apply the correction formula and re-test. For builds where the current sensor cannot be made accurate through scaling alone (errors that vary with current draw, indicating nonlinearity), consider upgrading to an external current sensor module or relying on voltage-based monitoring with conservative thresholds.
Betaflight OSD Elements for Battery Management
Betaflight offers numerous OSD elements for battery telemetry, and selecting the right combination reduces cognitive load during flight. The essential elements for battery management are: Battery Average Cell Voltage — the smoothed per-cell voltage that ignores transient sag, providing a stable reference that correlates well with state of charge; mAh Drawn — the total milliamp-hours consumed, which should be compared to a known reference (80% of pack capacity); Battery Current Draw — instantaneous current in amps, which helps explain voltage sag and identify when aggressive flying is temporarily suppressing voltage readings; Battery Warning — the standard warning indicator that triggers based on the thresholds set in the Power and Battery tab; and Fly Time — elapsed flight time since arming, useful as a secondary cross-check against expected flight duration.
The “Battery Remaining Capacity” element attempts to display a percentage, but its accuracy depends on correctly entering the pack capacity in the settings and on the current sensor calibration being accurate. As a primary indicator, percentage is useful for general awareness; as a landing decision trigger, mAh consumed referenced against a known 80% threshold is more reliable. Many experienced pilots configure their OSD to show “1300 mAh” in the craft name field as a constant reminder of the pack size against which consumed mAh should be compared.
CRSF and ELRS Telemetry Back to Radio
Modern radio links can relay battery telemetry from the flight controller back to the radio transmitter, enabling audible alerts and haptic feedback that do not require looking at the OSD. Crossfire (CRSF) and ExpressLRS (ELRS) both support bidirectional telemetry, and the data path is straightforward: the flight controller sends telemetry frames over the receiver protocol, the receiver transmits them back to the radio module, and the radio’s operating system (EdgeTX or OpenTX) processes them as sensor values available for display and logical switch configuration.
CRSF telemetry provides RxBat (receiver voltage), Curr (current in amps), Capa (capacity consumed in mAh), and VFAS (flight battery voltage) sensors by default. The VFAS sensor reports the Betaflight-calculated voltage, which matches the OSD voltage display. ELRS telemetry provides the same sensor suite with minor naming differences depending on the radio operating system version. Both systems update at rates fast enough for meaningful battery monitoring — typically 10–50 Hz for voltage and current, and every 1–2 seconds for capacity.
Configuring Logical Switches for Battery Alerts
EdgeTX and OpenTX logical switches enable sophisticated battery alerts that go beyond simple voltage thresholds. The most useful alert configuration uses a combination of voltage and capacity triggers: configure a logical switch that activates when VFAS drops below 3.5V per cell AND the throttle has been below 30% for more than 2 seconds, indicating that the voltage reading is not sag-induced. Configure a second logical switch that activates when mAh consumed (Capa sensor) exceeds 80% of pack capacity regardless of voltage. Link both logical switches to an audio alert — “battery low” for the voltage trigger and “battery critical” for the capacity trigger. This dual-threshold approach provides reliable warnings during both gentle cruising (where voltage accurately reflects state of charge) and aggressive flying (where capacity tracking is more reliable than voltage).
For Li-ion packs, adjust thresholds downward to account for the cells’ different voltage characteristics. A Li-ion pack at 3.2V per cell under load has similar remaining capacity to a LiPo at 3.5V, and landing triggers should be set accordingly. Configure separate model profiles in the radio for LiPo and Li-ion packs with different warning thresholds, and be disciplined about selecting the correct profile before each flight.
Combining Telemetry Sources for Reliable Battery Management
The most reliable approach combines all three telemetry sources — voltage, current, and time — and uses them to cross-check each other. If your 1300 mAh pack typically provides 4 minutes of aggressive flying and the OSD shows 900 mAh consumed at the 3-minute mark, the current sensor is reading within expectations and the voltage-based warnings are supplementary. If the voltage warning triggers at 600 mAh consumed on a pack that normally reaches 800 mAh before the warning, something has changed — the pack may be cold, aging, or sagging more than usual. The discrepancy itself is actionable information. Experienced pilots develop an intuitive sense of expected consumption rates for different flying styles and immediately notice when telemetry deviates from those expectations.
Battery telemetry is not a set-and-forget system. Current sensors drift, packs age and lose capacity, and temperature affects every measurement. Regular calibration, conservative thresholds, and cross-checking between voltage and capacity keep the system trustworthy. A pilot who understands their telemetry will land with packs consistently at 3.70–3.75V resting — the healthiest range for LiPo longevity — and will never experience an in-flight battery failure due to over-discharge.