The flight controller tells the ESC what it wants thousands of times per second. So why doesn’t the ESC simply do exactly that, instantly?
For most builds, it nearly can.
But motors, propellers, and ESCs are physical systems. There are situations where changing power as fast as electrically possible is actually faster than the motor can usefully follow.
That’s what ramp-up and ramp-down control.
What ramp actually does #
Ramp limits how quickly the ESC is allowed to change its commanded output.
In Gen2 firmware:
100% = fastest response, approximately 1 ms
0% = slowest response, approximately 100 ms
So a higher percentage means a more aggressive ramp, while a lower percentage softens the change.
There are two independent settings:
Ramp-up controls how quickly power is allowed to increase.
Ramp-down controls how quickly power is allowed to decrease.
They solve slightly different problems.
Without any limiting, a large command change can become an extremely abrupt electrical event. Current changes rapidly, torque changes rapidly, and the motor is expected to follow immediately.
Usually it can.
Sometimes it can’t.
A good ramp setting keeps the ESC response fast enough that you don’t feel unnecessary delay, while avoiding changes that are faster than the motor and propeller combination can usefully follow.
Why the motor and prop matter #
How violently a motor responds doesn’t depend on the motor alone.
It depends on how much torque the motor can produce compared with how much the propeller resists changing speed.
That resistance is rotational inertia.
Propeller inertia increases very quickly with propeller size because mass farther away from the center contributes much more strongly to inertia.
A small, lightweight propeller therefore changes RPM extremely easily.
Combine that with:
- high KV,
- high battery voltage,
- a powerful motor,
- and a small prop,
and you can get a system capable of changing RPM extremely quickly.
A 3–3.5″ high-KV motor on 6S is a good example.
A large 7″ low-KV long-range motor is very different. The heavier propeller has much more inertia, so its RPM cannot change nearly as quickly regardless of how aggressively the ESC changes its command.
That’s why one ramp setting cannot be ideal for every build.
Ramp-up #
Ramp-up controls how quickly the ESC is allowed to increase its output.
At 100%, a large command change can be completed in approximately 1 ms.
That gives an extremely direct response, but it can also produce very large instantaneous current and torque changes.
On a difficult motor combination, an excessively aggressive acceleration can contribute to:
- large current spikes,
- voltage sag,
- magnetic saturation,
- rough acceleration,
- or loss of synchronization.
Reducing ramp-up slightly spreads that change over more time.
The important point is that this does not necessarily make the quad feel slow.
The motor and propeller already have a physical limit to how quickly they can accelerate. Asking them to accelerate significantly faster than that doesn’t create useful thrust any sooner; it can simply create more electrical stress.
Ramp-down matters too #
Ramp-down is often ignored because people naturally think acceleration is the dangerous part.
But rapidly removing power can be just as important.
When the flight controller suddenly asks for much less thrust, the motor RPM has to fall.
On a large propeller, inertia naturally slows this process down.
On a very small propeller with a powerful motor, RPM can collapse extremely quickly.
At very low RPM, two things become important.
First, thrust falls approximately with RPM squared. Once the motor gets close to idle, there is very little thrust available for the flight controller to work with.
Second, a sensorless ESC determines rotor position using the voltage generated by the spinning motor. As RPM falls, that signal becomes weaker and harder to measure.
So an extremely aggressive deceleration can push the motor into a region where it produces very little thrust and is harder for the ESC to track.
Then the flight controller asks for thrust again.
The motor has to recover RPM before meaningful thrust returns.
That delay can create a slow bobble after a hard throttle cut or a sharp maneuver: the flight controller requests a correction, gets less response than expected, increases the correction, and then overshoots when thrust returns.
This is very different from the fast oscillation normally associated with excessive PID gains.
Why a slower ESC can sometimes appear to “fix” it #
This can create a confusing situation during troubleshooting.
A quad may show a bobble with one ESC and appear completely fine after installing another.
It is tempting to conclude that the faster ESC has a problem.
But the slower ESC may simply be incapable of changing motor torque as quickly.
Its own limitations effectively act as a ramp.
The motor therefore never drops into the same very-low-RPM region, and the symptom disappears.
That doesn’t necessarily mean the slower ESC is controlling the motor better. It may simply be hiding the operating condition that exposed the problem.
With an ESC that offers independent ramp-up and ramp-down control, you can soften the problematic direction without unnecessarily slowing everything else.
For example, if acceleration is completely stable but the quad develops a slow bobble after aggressive throttle cuts, there is little reason to slow ramp-up.
You can soften ramp-down alone.
Idle matters too #
Ramp-down and idle are closely related.
If idle RPM is extremely low, there isn’t much margin between normal minimum speed and the region where:
- thrust becomes negligible,
- back-EMF becomes weak,
- and motor tracking becomes more difficult.
A slightly higher idle keeps the rotor spinning in a healthier operating region and gives the flight controller more immediate thrust authority when it asks for a correction.
This is especially useful on small, powerful, high-KV builds.
It doesn’t mean idle should simply be set as high as possible. It means there needs to be enough motor speed to maintain reliable control.
Starting points #
Start with the defaults before changing anything.
Remember:
100% = approximately 1 ms = fastest
lower percentage = progressively softer
| Build | Ramp-up | Ramp-down | Idle |
|---|---|---|---|
| 2–3″ high-KV micro | Fast | Slightly softer if needed | Slightly raised if necessary |
| 3–3.5″ high-KV on 6S | Fast unless acceleration causes problems | First setting to soften if throttle-cut bobble appears | Often benefits from slightly more idle |
| 5″ freestyle or race | Default | Default | Default |
| 6–7″ long range, low KV | Default or slightly softer | Usually default | Default |
| 8″+ or heavy-lift builds | Softer if current spikes are excessive | Softer where necessary | Default |
These are starting points, not rules.
Motor KV, propeller mass, battery voltage, motor inductance, vehicle weight, and flight-controller tune all change the result.
Match the setting to the symptom #
If the problem happens when throttle increases, investigate ramp-up.
If the problem happens immediately after throttle drops, investigate ramp-down.
If the motor struggles mainly around idle, investigate idle speed and low-RPM tracking.
If the quad has a continuous fast oscillation, prop wash, jello, or vibration throughout the flight, ramp probably isn’t where you should start.
This distinction matters.
Changing an ESC setting because the quad has “a wobble” without first asking when the wobble happens is how troubleshooting quickly goes in the wrong direction.
How to tune it #
- Start from defaults. Fly the quad before changing anything.
- Identify exactly when the problem occurs. Acceleration, high RPM, throttle cut, or idle are very different conditions.
- Change only the setting related to that condition.
- Change one step at a time.
- Fly the same kind of maneuver again.
- Check motor and ESC temperatures.
- Write down what changed.
Blackbox logs are extremely useful when available because they let you compare what the flight controller requested with what the quad actually did.
Don’t change PWM frequency, timing, ramp-up, ramp-down, idle, and PID tuning together.
If six settings change and the problem disappears, you haven’t found the cause. You’ve only made it harder to understand the next problem.
