Your 6S quad with 1950KV motors draws 120A at full throttle on the bench. Your 55A ESC is rated for 55A continuous, 65A burst. You have exactly 2 seconds of full throttle before the MOSFETs desolder themselves. The fix isn’t buying bigger ESCs — it’s configuring throttle limits so the hardware never sees that load in the first place.
Betaflight Throttle and Motor Output Limiting: Complete Configuration
Step 1: Understand Throttle Limit vs Motor Output Limit
These are two different features that achieve similar outcomes through different mechanisms:
Throttle Limit (throttle_limit_type and throttle_limit_percent): Scales the entire throttle curve. If set to 80%, your radio’s 100% throttle stick position sends an 80% command to the PID controller. The PID controller can still increase individual motor outputs above 80% for stabilization (I-term windup, anti-gravity, etc.). This is the “upper cap” approach — it limits your maximum commanded thrust.
Motor Output Limit (motor_output_limit): Clips the final motor signal after the PID controller has calculated all corrections. No individual motor output exceeds this percentage, regardless of what the PID controller requests. This protects hardware from transient spikes but can cause control issues if set too low — the FC can’t correct a disturbance if all four motors are already at the limit.
The correct approach for hardware protection: set both. Throttle limit at 80-85% for general power management, motor output limit at 85-90% for transient spike protection.
Step 2: Calculate Your Limit Percentage
Formula: limit_% = (ESC_burst_rating × 4) / (motor_max_current × 4) × 100
Example: 55A ESCs (burst), motors that draw 40A each at full throttle on 6S.
(55 × 4) / (40 × 4) = 220/160 = 1.375 → you're within limits, no scaling needed.
Example: 35A ESCs (burst), motors that draw 45A each at full throttle on 6S.
(35 × 4) / (45 × 4) = 140/180 = 0.778 → set throttle limit to 78% or lower.
The motor current values must come from real thrust stand data, not manufacturer spec sheets. Manufacturers quote static thrust current, which is 15-25% higher than in-flight current due to propeller unloading. The safest approach: measure your own amp draw with a current sensor, then add 10% margin.
Step 3: CLI Configuration
set throttle_limit_type = SCALE
set throttle_limit_percent = 80
set motor_output_limit = 90
save
throttle_limit_type = SCALE linearly scales the entire throttle range. CLIP hard-caps at the limit with no scaling below (not recommended — creates dead zone at high stick). OFF disables throttle limiting.
Verify with status in CLI — it should show throttle_limit_percent: 80 and motor_output_limit: 90.
Step 4: Test in the Air — Not Just on the Bench
Throttle limit reduces power, which changes how the quad flies. At 80% throttle limit, you lose roughly 36% of total thrust (power scales with the cube of RPM, not linearly). A quad that hovered at 25% throttle now hovers at 31%. Your PIDs were tuned for the original power-to-weight ratio — expect to retune after enabling limits.
Flight test procedure:
1. Enable limits, hover test. Verify stable hover without oscillation.
2. Punch-out test. The quad should accelerate cleanly without sag or oscillation.
3. Full-throttle sustained climb (5 seconds). Monitor ESC temperature after landing. If ESCs are cool, you’re within limits. If they’re warm (>50°C), reduce limits further.
4. Check blackbox logs for motor saturation. If any motor hits 100% output during aggressive maneuvers despite the limit, you’ve clipped control authority — raise motor_output_limit slightly.
Throttle Limiting Strategy Comparison
| Strategy | Mechanism | Protects ESCs? | Preserves Control Authority? | Best Use Case |
|---|---|---|---|---|
| Throttle Limit Only | Scales throttle input | Partial (PID can still spike motors) | Yes | General power management, noise reduction |
| Motor Output Limit Only | Clips final motor signal | Yes (absolute cap) | No (can saturate during corrections) | Hardware protection, absolute safety |
| Both (80% Throttle / 90% Motor) | Scales input + caps output | Yes (layered protection) | Mostly (90% headroom for PID) | Daily flying, ESC headroom |
| Motor Kv Limit (Hardware) | Lower Kv motors physically draw less current | Yes (physical limit) | Yes | New builds, permanent solution |
| ESC Protocol Limit | DShot command limiting | Yes | Varies by implementation | Racing leagues with class limits |
| Scale (Clip Type) | Linear 0-100% scaling | Partial | Yes (smooth response) | General use |
| Clip (Clip Type) | Hard cap at limit percent | Yes | No (dead band at top) | Avoid — use Scale instead |
Common Throttle Limiting Mistakes
Mistake 1: Using motor output limit alone at too low a value. At 75% motor output limit, the FC has zero headroom to correct a disturbance when you’re at full stick — all four motors are already clipped. A wind gust that requires differential thrust gets no response because the limit prevents any motor from exceeding 75%. The quad tumbles, you blame the tune, but it was the limit clipping your corrections.
Mistake 2: Calculating limits from manufacturer motor spec sheets without empirical verification. The T-Motor Velox 2207 1950KV spec sheet says 42A at 100% throttle on 6S with a 5-inch prop. In-flight current with forward airspeed (propeller unloading) is 30-32A. If you size ESCs based on 42A, you’re over-buying. If you set limits based on 42A, you’re under-limiting. Measure your own setup.
Mistake 3: Setting throttle limit without adjusting PID gains. Reducing maximum thrust changes the quad’s response dynamics. An over-tuned P gain that worked at 100% thrust will oscillate at 80% because the motor response curve is flatter. Reduce P gain by 10-15% after enabling limits, then tune back up.
Mistake 4: Forgetting that throttle limit applies to Turtle Mode too. At 80% throttle limit, Turtle Mode flip power is also 80%. If your quad lands upside-down in thick grass, 80% may not be enough to flip it. This is the tradeoff — you can temporarily disable limits for turtle mode by switching profiles or adjusting the value before attempting the flip.
Mistake 5: Using throttle limit to fix a noise problem instead of fixing the noise. Throttle limiting reduces motor RPM, which reduces vibration amplitude. If your gyro noise drops after enabling limits, you’re masking a mechanical issue — unbalanced props, bent motor shaft, loose frame. Fix the mechanical problem; don’t use throttle limit as a band-aid.
⚠️ Regulatory Notice: The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding flight altitude, no-fly zones, remote ID requirements, and registration before flying. Throttle limiting does not exempt you from altitude restrictions or airspace regulations. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
As we detailed in our motor desync troubleshooting guide, ESC timing and demag compensation are equally important for hardware protection. See our ESC protocols explained guide for protocol-level current limiting options.
For pilots building high-performance 6S quads, the uavmodel T-Motor Velox V3 2207 motors paired with a 55A BLHeli_32 ESC stack deliver clean power with enough burst overhead that throttle limiting becomes a tuning choice rather than a survival requirement.